Event Data Grid in the FCU
(also E2PROM) stands for Electrically Erasable Programmable Read-Only Memory and is a type of non-volatile memory
Is a Peco term for live (power) frog Turnout (Switch or Points),which some people call power-routing.
Wiring a Peco 3 way point
A coil of wire in air or on a former that if current is passed through the wire a magnetic field will be produced
DCC throttle for Android phone app https://enginedriver.mstevetodd.com
A Discharge of high voltage Static Electricity that can destroy some types of semi-conductor components. Often caused by friction with a good insulator, such as synthetic clothing in a dry atmosphere.
MERG kit building instructions offer advise such as the following:-
While most modern Integrated Circuits (ICs) are reasonably protected from static electricity, today’s centrally-heated houses, & man-made fibres used in carpets (and underwear!) can cause significant static charge to build up as you move around. Before opening any kit, wear an earth strap or touch a nearby radiator or other earthed metal, and then stay seated while you open and assemble the kit. Leave all the (ICs) in their protective packaging until ready to insert into their sockets.
Event Variable a 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.
A 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.
An event that uses both the module ID and the device ID and so constitutes a unique event within the system.
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.