SAI I/O module
- Thread starter Frunple
- Start date
Desert_AIP
Senior Member
I use a couple of them.
They are controlled via UPB.
I use them for my secuirty lights which are all wired in the attic. The motion sensors energize a 5V wall wart wired to an input on the IO module which in turn sends UPB ON/OFF commands.
This allows me to turn the security lights on by motion, manually, or via alarm or other Omni commands.
I have the 5V signal wired through an Omni relay so I can interrupt the signal and prevent the IO module from transmitting the UPB commands. This disables the motion sensors if they are tripping too much becase of wind, etc.
I will use the outputs wired to Elk relays to control separate segments of landscape LV lighting.
They have worked great. I probably would not use the outputs for something like a garage door since they aren;t 100% reliable and a UPB command could open the door.
They are controlled via UPB.
I use them for my secuirty lights which are all wired in the attic. The motion sensors energize a 5V wall wart wired to an input on the IO module which in turn sends UPB ON/OFF commands.
This allows me to turn the security lights on by motion, manually, or via alarm or other Omni commands.
I have the 5V signal wired through an Omni relay so I can interrupt the signal and prevent the IO module from transmitting the UPB commands. This disables the motion sensors if they are tripping too much becase of wind, etc.
I will use the outputs wired to Elk relays to control separate segments of landscape LV lighting.
They have worked great. I probably would not use the outputs for something like a garage door since they aren;t 100% reliable and a UPB command could open the door.
I meant how do you use them from the omni. Are they considered units etc?Frunple - what Desert_AIP was saying is that they are controlled via "UPB Mode" instead of the "HLC Mode" within the Omni. Since the device only has one UPB ID, you need to use links to control the individual ports. You'll need to do configuration from both PC Access as well as UPStart.
Desert_AIP
Senior Member
JonW is right, sorry for being obtuse.
The Omni has no idea what the IO module is.
All the interaction is via the UPB network.
So from the inputs, I have the Omni listen for the links the IO module transmits, and then take action based on them.
For the IO outputs, the Omni sends a UPB link to control it.
You can't send it a unit on command, the IO module only responds to links. So a "Kitchen Lights ON" type unit command, like "IO Module 1 ON", will have no effect.
You set up the links in Upstart and PC Access then send and receive the links.
Whether the Omni uses HLC or UPB, you can use spare links for anything you want.
I define all the links in my setup in the Omni, even those that don't directly control units, just to remind me.
I assign them unit numbers but they are in a "room" all their own.
The Omni has no idea what the IO module is.
All the interaction is via the UPB network.
So from the inputs, I have the Omni listen for the links the IO module transmits, and then take action based on them.
For the IO outputs, the Omni sends a UPB link to control it.
You can't send it a unit on command, the IO module only responds to links. So a "Kitchen Lights ON" type unit command, like "IO Module 1 ON", will have no effect.
You set up the links in Upstart and PC Access then send and receive the links.
Whether the Omni uses HLC or UPB, you can use spare links for anything you want.
I define all the links in my setup in the Omni, even those that don't directly control units, just to remind me.
I assign them unit numbers but they are in a "room" all their own.
You can only assign a single unit ID to the IO module. This is going to be used for programming from UPStart only - the Omni cannot interact with the IO module based on this ID. The IO module has a single ID with multiple "channels". Since the Omni has no concept of channels, you need to assign links to the channels so that the Omni can send/receive links to interact with the channels.
The individual input and output channels (ports) will each have a link(s) assigned to their actions. You can setup the output ports to open or close based on receiving a link. Likewise, you can setup the IO module to transmit links when it senses an open or close event on the input ports.
The Omni needs to be setup to transmit a link to get the output ports to open or close. Likewise, the Omni needs to listen for links that the input ports would transmit to be able to perform any action. You cannot monitor the IO module status like an on/off of a light switch from within the Omni.
Since the Omni has no concept of channels within a single UPB device ID, the link interaction also must be done for other multi-channel UPB devices like the US22-40.
Desert_AIP
Senior Member
The IO Unit has to have a UPB unit to participate in the UPB network, set up in UPStart.
The Omni has no idea what it is. So it doesn't matter how you set it up to the Omni.
If you don't assign a unit number in the Omni, the links will still control the IO module.
And the Omni will still receive the UPB links the IO Module transmits.
I assign it a unit number in PC Access for "housekeeping", but it's only the UPB links that control it and it can only communicate via links as well.
The Omni has no idea what it is. So it doesn't matter how you set it up to the Omni.
If you don't assign a unit number in the Omni, the links will still control the IO module.
And the Omni will still receive the UPB links the IO Module transmits.
I assign it a unit number in PC Access for "housekeeping", but it's only the UPB links that control it and it can only communicate via links as well.
