Aaron Teitlebaum

For the custom alarm type, you can specify HiHi, Hi, Lo, and LoLo limits that will trigger the alarm. Is there any way to tell which of the four limits has been exceeded when the alarm is triggered, other than manually comparing the PV value to each of the limits? The documentation says: This seems to imply that these are four separate alarms (Hi, HiHi, Lo, and LoLo), but as far as I can tell, exceeding any of the limits will all generate the same one alarm. If that's the case, what's the point of being able to specify a HiHi or LoLo alarm limit when this alarm will already have been triggered when the Hi or Lo limit is exceeded?

Hello, I have several US5 models out in the field which I often check on using VNC to interact with their HMIs. I recently updated UniLogic to version 1.34.192 and then updated the firmware on one of the US5s to match, and then reloaded the updated project. However, now it seems like VNC only works to view the HMI but I can no longer interact with it. I've tried both RealVNC and TightVNC, I've rebooted the PLC and re-downloaded the project several times, I've tried adding and removing a VNC password but it still ignores all of my clicks. The other units that haven't been updated yet still work normally. Has anyone else experienced this or do you have any suggestions? Thanks.

The ability to programmatically set Modbus slave addresses, as well as REST server addresses, would've saved me a lot of work on my most recent project. I hadn't considred those features could be missing when I selected the UniStream, and if I'd known I might not have. I ended up having to roll my own routines using the Advanced Modbus functions (despite their missing documentation) as well as my own REST functions using the Message Composer (which also has very lacking documentation). If the Modbus and REST server addresses could be changed programmatically then I would've been able to use those built-in features and it would've saved me a lot of frustration.