The DL06 counter’s BCD value appears to jump from 9 to 16 because the C-More tag is assigned as an integer instead of a 16-bit BCD integer. Correct the HMI tag’s data type so it interprets the counter’s BCD digits consistently; changing the V-memory display format alone does not fix that mismatch.
Correct the C-More tag type before changing the preset
The quick fix—asking operators to enter a decimal equivalent of the displayed hexadecimal value—works around the interpretation error but leaves the HMI and PLC using different numeric representations. That invites entry mistakes and can still produce the wrong magazine index.
For this counter interface, assign the C-More tag that reads or writes the preset as BCD int 16. The reported setup used an integer tag, so the panel treated the same bit pattern as an ordinary integer. For example, a BCD value whose digits represent ten can be interpreted as the integer value 16 when the bit pattern is read as binary integer data. The panel’s count display then seems to skip values even though the counter is advancing in BCD.
Changing the V-memory display format to decimal changes how a value is presented in the programming environment; it does not change the HMI tag’s data type or convert the value written to the counter. Check the tag assignment itself before altering PLC logic or asking operators to compensate.
Check: In the C-More project, identify the exact tag used for the preset and confirm its assigned type is BCD int 16, rather than an integer type.
Recreate the tag when C-More locks its data type
In the reported C-More programming workflow, the assigned data type could not be changed on an existing tag. Trying to edit the value display or reformat the V-memory address will not correct a locked tag assignment.
- Record the existing tag name, PLC address, and any screen objects or numeric-entry objects that use it.
- Delete the incorrectly typed tag from the tag database.
- Create a tag with the same name if desired, point it to the same V-memory location, and select
BCD int 16. - Check that the HMI objects still reference the recreated tag. If the software removed or invalidated those references when the tag was deleted, reassign the objects to the new tag.
- Compile or validate the HMI project and transfer the corrected project using the site’s normal change procedure.
Do not delete a tag until you have captured its address and confirmed its use; a same-name replacement is not guaranteed to restore every object reference automatically.
Check: Open the tag properties after recreation and verify the name, address, and BCD data type, then confirm the preset entry and display objects point to that tag.
Prove the display and preset agree before production
Use a controlled test with the machine in a safe state where an unintended index cannot damage product or equipment. Compare the operator-entered preset, the value shown on the HMI, and the value observed in the PLC’s V-memory or counter monitor. Do not rely on a single display: compare the value at both ends of the interface.
- Enter a small, known test preset through the HMI.
- Read the corresponding PLC value and confirm its BCD digits represent the entered count.
- Run or simulate count increments under the approved test method and watch the HMI and PLC monitor together.
- Confirm the count advances through the decimal sequence without the apparent 9-to-16 jump, and confirm the preset condition occurs at the intended count.
If the displayed value is now correct but the magazine still indexes early, stop treating it as an HMI-format issue. Trace the actual counter preset reference, the counter’s done condition, and the logic that commands magazine indexing. The original symptom involved premature indexing, so verify the physical transition as well as the number on the screen.
Check: The entered preset, PLC-observed BCD value, HMI count, and index transition agree during a controlled test.
Separate a temporary production restore from the permanent repair
If production must resume before the HMI project can be corrected, a supervised operator entry using the required numeric representation may serve as a temporary workaround. The original installation reported that operators were being asked to enter a decimal equivalent of the hexadecimal preset. Treat that as a controlled workaround only: document the conversion convention for the specific PLC value and verify one known preset at the PLC before enabling automatic indexing.
Do not assume a generic hex-to-decimal conversion is the right permanent solution. BCD encodes decimal digits in a bit pattern; interpreting that pattern as a binary integer produces a different numeric value. The correct entry and display method depends on the tag’s data type and the PLC counter’s representation, not simply on whether a programming screen labels a value as hexadecimal or decimal.
Restore normal automatic operation only after a test shows the intended preset, count, and index point match. Then schedule the HMI tag correction and remove any temporary operator conversion instruction so a workaround does not become the long-term operating method.
Check: The temporary entry procedure is documented and independently checked, or the corrected tag is installed and tested before operators resume normal preset entry.
Check the remaining causes if the count still looks wrong
| Observation | Next check |
|---|---|
| HMI still shows 16 where ten is expected | Confirm the live tag—not just a similarly named tag—uses BCD int 16, and inspect the object binding. |
| PLC value is correct but the HMI is wrong | Check the HMI tag’s address and type, then compare its live value with the PLC monitor. |
| HMI and PLC agree but indexing occurs early | Trace the counter preset reference and the logic that triggers magazine indexing. |
| Count stops, wraps, or behaves inconsistently | Inspect the configured counter instruction, preset source, and surrounding logic in the DL06 program. |
A decimal display setting cannot repair a data-type mismatch, and changing the counter logic before confirming the transferred value can mask the actual fault. If a recreated tag does not behave as expected, verify the exact counter and V-memory configuration in the project and controller rather than guessing at another conversion.
Check: Identify whether the discrepancy first appears at HMI entry, in PLC memory, or at the index output; make the next correction at that boundary.
Verify the magazine indexes at the intended count
Before returning the machine to routine operation, test at least one representative preset through the complete path: operator entry, HMI tag, V-memory, counter preset, count display, and magazine index. Observe the PLC value and physical index event during the test. Confirm that the machine indexes once at the intended count and does not advance early.
Remove temporary conversion notes only after the corrected HMI project is active and operators can enter the preset directly. Record the final tag type and address in the machine documentation so future HMI edits do not reintroduce an integer/BCD mismatch.
Check: A complete controlled cycle reaches the entered preset and produces the expected single magazine index.
FAQ
What happens if a C-More integer tag reads a DL06 BCD counter?
The same bit pattern can be interpreted as a binary integer rather than decimal digits encoded in BCD. This can make the displayed count appear to jump, such as from 9 to 16.
What happens if I change the V-memory display from hexadecimal to decimal?
That changes the programming environment’s display format, not the C-More tag’s data type. Set the HMI tag to BCD int 16 for the counter interface described here.
What happens if C-More will not let me edit the tag type?
Record its name and address, delete the tag, and recreate it with the same address and BCD int 16. Then verify that the HMI entry and display objects reference the recreated tag.
What happens if the HMI count is fixed but the magazine still indexes early?
Check the preset value in PLC memory, the counter preset reference, and the logic driving the index. A corrected display does not prove that the indexing condition is correct.
What happens if the count still disagrees after I recreate the tag?
Stop automatic operation and compare the HMI value, PLC V-memory value, counter preset, and index condition while testing safely. If the tag binding or counter configuration remains unclear, stop and contact official AutomationDirect support with the DL06 program and C-More project available.