glossary:glossary_e
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
glossary:glossary_e [2019/04/07 19:24] Bob Vetterlein [ESR] |
glossary:glossary_e [2019/04/08 09:42] Bob Vetterlein [EV] |
||
|---|---|---|---|
| Line 33: | Line 33: | ||
| =====EV===== | =====EV===== | ||
| __E__vent __V__ariable a [[glossary:glossary_c#cbus|CBUS]] term referring to a value which controls the action to be taken by a 'consumer' module when a specific event is received. One or more EVs are associated with each event that a module should respond to. As an example in the CANACC8 there are two EVs per event, in the first a set (1) bit indicates that the associated output is affected and normally follows the 'state' of the event. The second EV is a modifier and any set (1) bit that matches EV1 will invert the action for that output. So if the two EVs for a given event were 00000011 & 00000010 then on receipt of that event output 1 would assume the 'state' defined by the event while output 2 would assume the inverse. | __E__vent __V__ariable a [[glossary:glossary_c#cbus|CBUS]] term referring to a value which controls the action to be taken by a 'consumer' module when a specific event is received. One or more EVs are associated with each event that a module should respond to. As an example in the CANACC8 there are two EVs per event, in the first a set (1) bit indicates that the associated output is affected and normally follows the 'state' of the event. The second EV is a modifier and any set (1) bit that matches EV1 will invert the action for that output. So if the two EVs for a given event were 00000011 & 00000010 then on receipt of that event output 1 would assume the 'state' defined by the event while output 2 would assume the inverse. | ||
| + | |||
| + | =====Event===== | ||
| + | A [[glossary:glossary_c#cbus|CBUS]] term for a message that indicates some outside action has taken place such as the press of a button, change in state of a switch, a train has entered or left a particular section of track, a point actuator has completed its commanded move or any number of other things. These messages consist of three or four parts. First, the OPCODE a single byte which defines the meaning and length of the message. Second & third constitute the 'Event' two bytes designating the source module ID and two bytes designating the 'device' within that module that has caused the event. Fourth (optional) from 1 to 3 additional data bytes used to convey other information. | ||
| + | ====Long Event==== | ||
| + | An event that uses both the module ID and the device ID and so constitutes a unique event within the system. | ||
| + | ====Short Event==== | ||
| + | An event where the module ID is ignored and only the device ID is relevant, thus the event is not unique and may seemingly be produced from two or more sources. | ||
glossary/glossary_e.txt ยท Last modified: 2019/12/13 06:07 by tgerbic
