IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing PanelView 600 DH+ errors 208 and 685

HMI and touchscreens Published 6 min read

Short answer

Errors 208 and 685 on a PanelView 600 talking to a ControlLogix 5555 over DH+ are address failures, not cable failures: the HMI requests PLC/SLC file numbers the controller has not mapped. Assign each requested file number a controller-scoped array long enough for every requested element and bit, and skip the BTR/BTW block-transfer logic - it does not fix HMI addressing.

On this page
  1. What each error is telling you
  2. Why the ControlLogix rejects the address
  3. Confirm the DH+ path once, then leave it alone
  4. Worked example: mapping file 7 for a ten-word request whose first element is 20
  5. Where BTR and BTW rungs actually belong
  6. The fix, in order
  7. Questions asked

Error 208 at startup and error 685 the moment you use your tags, on a PanelView 600 linked to a ControlLogix 5555 over DH+, is an addressing failure rather than a cable failure. The PanelView asks for PLC/SLC-style numbered files; the ControlLogix keeps application data in controller-scoped arrays and only answers a file-number request that its mapping table resolves. The fix is the mapping: one controller-scoped array per file number the HMI requests, each sized past every requested element and bit. Adding BTR and BTW block-transfer rungs to the control program fixes nothing here, because the PanelView never executes them.

What each error is telling you #

Publication 2711-UM014, the PanelView Standard operator terminals user manual, lists 685 as a comm-status file access error and defines it in one line: "The terminal is trying to access one or more controller data files that are unavailable." Error 208 is the write-side twin: a write to the remote device could not be completed. Read together on one machine, they say the terminal reaches a controller and then asks for data the controller cannot hand over under that address.

Symptom Where to look First check
208 at terminal startup A write fires as the application loads Find the startup write in the PanelBuilder 32 application and read its destination address
685 when an object updates The requested file, element, or bit is outside the mapping Compare the object's address with the mapped array's length
Every controller object fails at once Shared cause: mapping, node, or route Do one read of a known mapped element
Values display but writes fail The write destination or its length Write one unused element and watch it in the controller

Neither code convicts the cable by itself. If one known, mapped element updates on the display, the DH+ link and the routing into the controller work, and the rest of the job is addresses.

Why the ControlLogix rejects the address #

The PanelView's file-address fields were built for SLC and PLC-5 data tables, where file 7 is the default integer file (N7), file 8 the default floating-point file (F8), and file 3 the default bit file (B3). A ControlLogix controller holds no N7 unless you create one: its data lives in named, controller-scoped arrays. A file-number request crossing DH+ resolves only through the controller's legacy-message mapping. In the ControlLogix programming software, open Logic → Map PLC/SLC Messages, choose the file number, and assign a controller-scoped array to it; build one array per file number the HMI uses, and match the array's element type to what the objects expect.

Four rules keep the mapping clean:

  • Cover the whole transfer, not just the first element: a request touches the elements from its first element through first + length - 1.
  • Keep bit references in the range 0 through 15, selecting a bit inside an element the request actually touches.
  • Never type a controller tag name into a file-address field. That is the other addressing system, and pasting one into the other does not connect them.
  • Leave the mapped arrays to the HMI interface where you can; program logic that also writes them makes 208-style failures look random.

Bit-level objects have their own version of the boundary trap; toggling PLC BOOLs from HMI screens across the display boundary shows the same failure on tag-based panels. And if this terminal is eventually replaced by a tag-based panel on Ethernet, file numbers disappear entirely; selecting a compact HMI for ControlLogix over Ethernet covers that route.

Confirm the DH+ path once, then leave it alone #

Spend one pass on the path so a real network fault cannot masquerade as a mapping problem:

  • Read the PanelView communication setup: its own node address, the DH+ rate, the target node, and the controller type it expects.
  • Read the DH+ interface in the ControlLogix chassis the same way: actual node address, actual rate, and no duplicate node numbers anywhere on the link.
  • Check the routing from that interface to the processor slot where the 5555 actually sits; reaching the bridge module is not reaching the controller.
  • Look at the interface diagnostics for link or routing faults, and chase cable and termination only when diagnostics or intermittent behavior point there.
  • Prove one known mapped element updates on the display.

If that read is live, stop adjusting network settings and work the addresses. A configuration copied from another application without checking the chassis arrangement sends requests confidently to the wrong destination.

Worked example: mapping file 7 for a ten-word request whose first element is 20 #

Inputs, all typical for this fault: a numeric-entry object and a display object both addressed to N7:20 (file 7, element 20), the numeric entry configured to write, and the screen collecting 10 consecutive words with element 20 as the first. On the controller side sit two candidate integer arrays: one with 16 elements, one with 32.

The rule in words: a request touches the elements from its first element through first + length - 1, the mapped array must include every one of those indexes, and any bit reference must fall between 0 and 15 inside a touched element.

The arithmetic: 20 + 10 - 1 = 29, so this request touches elements 20 through 29.

  • A 16-element array covers indexes 0 through 15. The request begins at 20, already past the end: the reads throw error 685 and the numeric entry's write throws error 208.
  • A 32-element array covers indexes 0 through 31. Element 29 sits inside it with two spare elements above, and bit 12 of element 29 is a legal bit inside a touched word.

Decision: map file 7 to the 32-element array. Any integer array running through index 29, that is, at least 30 elements, clears this request, and 32 leaves room for edits. The threshold is mechanical: if first + length - 1 is greater than the array's top index, the request fails; lengthen the array or move the first element until it is not.

Where BTR and BTW rungs actually belong #

The advice to program BTR and BTW blocks into the ControlLogix confuses two mechanisms. Block-transfer rungs are programmed where a documented interface moves fixed blocks of words between a processor and an I/O or legacy device; how the requested word count is configured on an SLC 500 BTR/BTW pair shows that use, where the word counts must match the interface. The PanelView executes none of it: its file-number requests are translated by the controller's mapping table and by nothing else. Adding transfer rungs gives the terminal nothing new to talk to and clears neither error, so leave them out unless a documented interface on your machine calls for them.

The fix, in order #

  1. In the PanelBuilder 32 application, record the communication configuration and, for each failing tag, the full file address, data type, element count, and whether it reads, writes, or both.
  2. On the controller side, confirm one known mapped element reads live on the display; if nothing at all reads, clear the node, rate, and routing items first.
  3. Open Logic → Map PLC/SLC Messages and create one controller-scoped array for every file number the HMI requests.
  4. Size each array past the highest element any object touches, first + length - 1, and keep every bit reference inside 0 through 15.
  5. Apply the controller change through your normal change-control procedure.
  6. Test the read path with two different values forced in the controller, so a stale display cannot pass the test.
  7. Test the write path on an unused element only, and watch that element change in the controller while its neighbors stay put; a test write must never reach a real machine output.
  8. Re-transfer the application, then walk the screens you rarely open and every configured startup write, holding each address to the same mapped-array rule.

Questions asked

Does error 685 mean my DH+ cable or network is faulty?

Not by itself. Error 685 is a comm-status file access error: the terminal reached the controller and asked for a data file that is unavailable to it. A dead DH+ link shows up as connection or timeout symptoms on the comm status, not as a file complaint. If one known mapped element updates on the display, the link works and the remaining faults are addresses.

Do I need BTR and BTW rungs in the ControlLogix to talk to the PanelView?

No. Block-transfer read and write rungs belong where a documented interface moves fixed blocks of words, such as block-transfer I/O on an SLC 500, and their word counts must match that interface. The PanelView never executes them. File-number requests are resolved by the controller's PLC/SLC mapping table, so add the mapping, not the rungs.

How long should the array mapped to file 7 be?

Long enough that the highest request fits: with a request whose first element is 20 for 10 words, the last touched element is 20 + 10 - 1 = 29, so the array must run through index 29, which means at least 30 elements. Mapping 32 leaves room for edits, and every bit reference must stay within 0 through 15 of a touched element.

Why does error 208 appear at startup before anyone touches the screen?

Because something in the application writes as soon as it loads. Inspect the objects and startup actions configured to write on load, note which address each one targets, and hold them to the same rule as every other object: the destination file number must be mapped, and the destination element must sit inside the mapped array.

Keep reading

  • Troubleshooting

    Fixing a PanelView Plus selector that does not respond

    When the PLC sees the selector signal but the PanelView Plus screen does nothing, compare the communication shortcut's PLC address with the controller's real IP first. In the case behind this article, repointing the shortcut from 192.168.1.150 to 192.168.1.105 was the entire fix. Only if other tags still update should you open the object and compare its Value and Indicator connections.

    HMI and touchscreens

  • How-to

    How to Display Dynamic PLC Messages on a PanelView 800

    Write the selected label into one MicroLogix 1100 string element sized to the longest configured message, map one string-type HMI tag to that element in Connected Components Workbench, and assign that tag to the String Display object's Read Tag. Priority is a ladder decision: when several rungs write the same element in one scan, the last executed write is what the terminal shows.

    HMI and touchscreens

  • Troubleshooting

    Fixing an HMI Date and Time Tag That Fails Over S7

    When ordinary tags read and write but a Siemens date and time tag returns a communication error, the driver imported the tag but cannot transfer that data type. Copy the clock into ordinary component variables in PLC logic and read and write those from the HMI. The Ethernet side needs no changes.

    HMI and touchscreens