Hello,
I'm working on a steam turbine control with a Mark V and a Cimplicity HMI. There are two things that are confusing me in Cimplicity:
1. Command buttons are using the AbsoluteSetpoint action to set a point's value to 16. These points are associated with contacts in the Mark V ladder logic. I was expecting to see the point set to 1 for a contact, not 16. Apparently the Mark V does not support a Boolean data type, so an 8-bit integer is used in Cimplicity. Any idea why this integer is set to 16?
2. I don't see a command button that sets the point back to 0. It looks like the point gets set to 16 once and then holds that value forever. I'd like to know how the command button's point gets set back to 0 so it can be used again. I've looked through the Mark V logic and I don't see it setting any of these command values back to 0 either.
Hopefully someone with more Cimplicity / Mark V experience than me can shed some light on this. Thanks for your help.
I'm working on a steam turbine control with a Mark V and a Cimplicity HMI. There are two things that are confusing me in Cimplicity:
1. Command buttons are using the AbsoluteSetpoint action to set a point's value to 16. These points are associated with contacts in the Mark V ladder logic. I was expecting to see the point set to 1 for a contact, not 16. Apparently the Mark V does not support a Boolean data type, so an 8-bit integer is used in Cimplicity. Any idea why this integer is set to 16?
2. I don't see a command button that sets the point back to 0. It looks like the point gets set to 16 once and then holds that value forever. I'd like to know how the command button's point gets set back to 0 so it can be used again. I've looked through the Mark V logic and I don't see it setting any of these command values back to 0 either.
Hopefully someone with more Cimplicity / Mark V experience than me can shed some light on this. Thanks for your help.