02-24-2020, 06:44 AM
(This post was last modified: 02-24-2020, 06:45 AM by gReatAutomation.)
(02-23-2020, 05:51 PM)Dean Roddey Wrote: Correct something in the RA2 driver now before it's too late. Contact closures are semantically read only. The read/write contacts on the Visor should be marked as relays, since those are semantically read/write. So the field names will change for the previously added r/w contact closures.
When you add a Contact Closure Output (CCO), it reads TRUE. If you want to actuate the CCO, you have to set the field to FALSE and then back to TRUE.
(02-23-2020, 05:51 PM)Dean Roddey Wrote: Add what I think is correct support to the Radio RA2 driver for the contact inputs. We'll see if it works. We assume if it as a component id of 32 or 33 then it's an input, else an output.From reading the integration protocol manual you cannot get the state of the input LEDs. If this is the case, what type of device do we add for reading the status of the Contact Closure Inputs (CCI)?
(02-23-2020, 05:51 PM)Dean Roddey Wrote:I removed and re-added the thermo and was only able to set the set point from the driver after tinkering with it a couple of times. It then started acting normal again (i.e., can set set points via driver or IV whereas before I would try to set the set point and get the ????The Radio RA2 driver complains if the low set point is >= to the high. Let them be equal at least, though that may cause some confusing in user logic if the difference is zero.