blksmth

Thank you for your kind critique. 1) Great to know thank you I will restructure 2) I will look into a more refined way of doing this, really It's because I wanted a parallel function of being able to manually trigger the relays for testing as well as have them be triggered by the system state/scheduler 3) Ok. 4) I will try to find a way to simplify. I was guided by tech support to use the increment function as a way to test and see if the relays were actually firing. It's only for testing purposes really. I'm still trying to get the different between the different contacts and coils. We don't use this terminology in my other programming languages but they're also based off Boolean logic so somewhat similar. Thanks I take pride in a clean UI The main reason I reached out to the group is that our first PLC crapped out during testing the relays ( or it never worked to begin with ) I was told by support my previous version of the program may have burned the relays out because I was switching them on and off too fast. So I just wanted another set of eyes on it to be sure I didn't have any really big issues.

Hello All, I'm new to Unitronics and PLC programming as a whole. I have been an automation programmer for 20 years in other fields so programming is not foreign to me. I have been working with Unitronics support but they seem reluctant to offer up suggestions on how things should be programmed. Would someone be so kind as to critique the program that I have attached? A little info on the program. There are two analog sensors configured, they're 4-20 pressure sensors that range from 0-700psi. I also have a Dwyer differential pressure sensor, Door Sensor ( to see if someone opened the chassis ) Estop Sensor ( push button ) Any help would be greatly appreciated! DisV Sandfly 20190417 NRB.zip