This shows you the differences between two versions of the page.
hardware:lan-bridge:lan-bridge-configuration:slots-tab [2014/02/15 09:54] jarrod |
hardware:lan-bridge:lan-bridge-configuration:slots-tab [2014/02/17 14:29] (current) jarrod [Slot Startup Commands] |
||
---|---|---|---|
Line 62: | Line 62: | ||
==== 3 - CFLink ID ==== | ==== 3 - CFLink ID ==== | ||
- | If `Destination Slot` is configured to `CFLink`, the CFLink ID is the device on the CFLink network to forward data to/from. This allows you to subscribe a communication slot to a single device on the CFLink bus. | + | If ''Destination Slot'' is configured to ''CFLink'', the CFLink ID is the device on the CFLink network to forward data to/from. This allows you to subscribe a communication slot to a single device on the CFLink bus.\\ |
+ | Use a value of ''FF'' to broadcast all data received from the ''Slot'' to all devices on the CFLink bus. Doing this requires that the incoming data be a valid CFLink Protocol packet or it will be ignored. | ||
==== 4 - Module ==== | ==== 4 - Module ==== | ||
- | If the `CFLink ID` is used, and the target CFLink device is a modular base unit (ie. MOD4 or DIN-MOD4), this setting is used to bridge the data to only a specific module on the device. | + | If the ''CFLink ID'' is used, and the target CFLink device is a modular base unit (ie. MOD4 or DIN-MOD4), this setting is used to bridge the data to only a specific module on the device. |
==== 5 - TX Command ==== | ==== 5 - TX Command ==== | ||
- | If the `CFLink ID` is used, this setting allows you to define a specific CFLink Command name to wrap all incoming data with.\\ | + | If the ''CFLink ID'' is used, this setting allows you to define a specific CFLink Command name to wrap all incoming data with.\\ |
- | eg. If you configure the `TX Command` to be `TRLYSET` (the command to set a relay state on a CFLink device) then any data coming from the `Slot` will be first wrapped in the entire CFLink packet before being sent out to the CFLink bus.\\ | + | eg. If you configure the ''TX Command'' to be ''TRLYSET'' (the command to set a relay state on a CFLink device) then any data coming from the ''Slot'' will be first wrapped in the entire CFLink packet before being sent out to the CFLink bus.\\ |
- | So if the incoming data was simply `P01:1`, then the data would first be wrapped in the `TRLYSET` command, resulting in the full data being sent onto CFLink as: `[F2]<CFLinkID>[F3]TRLYSET[F4]P01:1[F5][F5]`. | + | So if the incoming data was simply ''P01:1'', then the data would first be wrapped in the ''TRLYSET'' command, resulting in the full data being sent onto CFLink as: ''[F2]<CFLinkID>[F3]TRLYSET[F4]P01:1[F5][F5]''. |
==== 6 - RX Command ==== | ==== 6 - RX Command ==== | ||
- | If the `CFLink ID` is used, this setting allows you to define a specific CFLink Command name to look for and strip from all outgoing data before sending back to the `Slot`.\\ | + | If the ''CFLink ID'' is used, this setting allows you to define a specific CFLink Command name to look for and strip from all outgoing data before sending back to the ''Slot''.\\ |
- | eg. If you configure the `RX Command` to be `RRLYSTA` (the reply notification sent from a relay on the CFLink bus when it changes state) then any relay state data coming from the `Destination Slot` will be first stripped of all CFLink packet formatting before being sent out to the `Slot`.\\ | + | eg. If you configure the ''RX Command'' to be ''RRLYSTA'' (the reply notification sent from a relay on the CFLink bus when it changes state) then any relay state data coming from the ''Destination Slot'' will be first stripped of all CFLink packet formatting before being sent out to the ''Slot''.\\ |
- | So if the incoming data was `[F2]<CFLinkID>[F3]RRLYSTA[F4]P01:1|P02:0|P03:0|P04:1[F5][F5]`, then the resulting data sent to the `Slot` would be simply `P01:1|P02:0|P03:0|P04:1`. | + | So if the incoming data was ''[F2]<CFLinkID>[F3]RRLYSTA[F4]P01:1|P02:0|P03:0|P04:1[F5][F5]'', then the resulting data sent to the ''Slot'' would be simply ''P01:1|P02:0|P03:0|P04:1''. |
- | ===== Slot Startup Commands ===== | + | ===== Slot Startup Commands - COMING SOON IN FIRMWARE UPDATE ===== |
{{:hardware:lan-bridge:lan_bridge_slots_tab-2.png?nolink|}} | {{:hardware:lan-bridge:lan_bridge_slots_tab-2.png?nolink|}} | ||