When tags are defined in the system as boolean and then reference a given bit in PLC, the system provides for easy status reading of these bits. I’m not sure I follow the logic for keeping the ability to write the bits in a register out of the driver.
Competitor products (three of them) have register bit level read/write capability built into their driver. If I was trying to create a work around for a few points, I would agree this scripting is a possible work around. I think scripting for each “bit” level write is adding unnecessary overhead to the system.
How would you suggest keeping a corelation between a tag to read the bit (boolean)and the tag holding the bit to write (int4)?
I really think this functionality belongs in the driver. At least it would be much more intuitive to have it there. The tag would be entered into the system and reference the memory space where it resides in the PLC. You then read and write you boolean tag.
When porting an existing HMI/PLC system to Ignition, working with exporting and importing tags from an existing system to Ignition. It would be so much more straight forward to define the boolean tags and import them to ignition and use them to read from AND write to.
I would love to understand the technical issue for adding this to the Modbus Driver and why the bushback when other products are doing this already.