Hello everyone! I recently developed HMI screens using FTVIEW ME version 6.00. While conducting tests on the application, I found that the majority of the screens functioned correctly. However, I encountered runtime errors with certain components, particularly the push buttons. I investigated the issue and discovered a common factor across all affected screens: the input addresses were in the range of I:3/31 or I:6/20. What surprised me is that the application does not display errors for input bits from 0 to 15, such as I:2/7, yet it throws errors for input bits 16 to 31. The specific runtime error message reads: "tag has an error at ::[shortcut]I:3/31." It appears that whenever I use input addresses higher than 15, the application fails to function properly. Has anyone experienced similar issues? I would greatly appreciate any insights or solutions you might have. Thank you in advance for your assistance!
It’s possible that your PLC (Programmable Logic Controller) lacks support for 32-bit notation, which could explain why you are currently utilizing only 16-bit integers.
The identifier I:3/31 does not specifically correspond to a 32-bit word (DINT) in all cases. SDN (Synonymous Device Network) cards can accommodate extensive data tables. For instance, an input card located in slot 1 of a SLC (SLC Controller) can range from I:1/00 to I:1/960, or any size you have configured it to. The data is organized into segments like this: - I:1.0/0-15 corresponds to I:1/0-15 - I:1.1/0-15 corresponds to I:1/16-31 - I:1.2/0-15 corresponds to I:1/32-47 and so forth. This method of segmentation enhances clarity in data access and management within larger automation systems.
In your logic editor, you may typically input addresses exactly as you’ve written them in your project thread, and the software should handle them correctly. However, FTView might not function this way. For instance, I:3/31 (if considering 16-bit words) corresponds to I:4/15, while I:6/20 aligns with I:7/4. It's important to identify the correct equivalent reference for each address that adheres to the 16-bit constraint. I've made some assumptions in my previous remarks, and as the saying goes, "to assume makes an ass out of you and me." Be cautious when working with address references in your logic programming to ensure accuracy and functionality.
OkiePC noted that in the context of 16-bit words, I:3/31 is equivalent to I:4/15, while I:6/20 aligns with I:7/4. For further clarification, I:3/31 can be interpreted as I:3.1/15. The '3' indicates the slot number assigned to the input card, and this number remains constant even when transitioning to an additional 16-bit word.
In this case, the SDN card is positioned in slot 1. However, it's important to note that I:1/31 and I:1.1/15 represent the same bit.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.