Differences

This shows you the differences between two versions of the page.

@@ Line 1: / Line 1: @@
+======Interface======
+[[:english#objects|{{  :objects.png}}]][[:english|{{  :rocrail-logo-35.png}}]]
+[[:english|Content]] -> [[:english#objects|Objects]] ->  [[sensor-en|Sensors]]
+  * [[sensor-index-en|Index]] | [[:sensor-gen-en|General]] | **Interface** | [[sensor-wiring-en|Wiring]] | [[sensor-gps-en|GPS]] | [[sensor-statistic-en|Statistic]] | [[sensor-usage-en|Usage]] | [[sensor-bi-directional-en|Bi-Directional Communication]] | [[sensors|Sensor Types]]
+// \\ // \\
+SensorDialog Interface Tab.\\
+{{:sensor-int-en.png?500}}\\
+ \\
+=====Interface ID=====
+If more than one command station is used, then the command station that is responsible for controlling the sensor-decoder is specified in this field. The "Interface identifier" field can remain empty if the object is connected to the first command station (first 'digint' in rocrail.ini) from the list of command stations.
+=====UID-Name=====
+| :!: //Use with care! The UID is case sensitive and __must match__, otherwise the sensor event cannot be processed and will be lost.// |
+Alternative to the Node-ID supported by:
+  * BiDiB (String: //Username//)
+  * RocNet
+ \\
+=====RFID=====
+The 32bit RFID number printed on the Tags. (Leading zeros can be left out.)\\
+This can be used in combination with __**[[:arduino:wio-en#id-12la|WIO-Drive and an ID-12LA reader]]**__.\\
+All other addressing, like Node ID and Address, are ignored if the RFID did match. (But an additional fake address makes it possible to check the plan virtually.)\\
+{{:wio:rfid32.jpg?600}}\\
+Example of the blue Tag scan:\\
+{{:wio:rfid-index.jpg}}
+<code>
+OWIO     0885 Mobile 18 [BR218] RFID event [12.0.197.167.148] [12953492]
+OModel   5329 trying to match sensor event: [WIO] id=[12.0.197.167.148] 0:0 uidname=[] state=0 code=BR218 regval=0 info=
+OFBack   0796 fb[s18-] state=ON code=BR218 dir=0 val=0 count=5 regval[0]=0
+</code>
+=====Bus=====
+See: **[[:addressing-en#bus|Addressing]]**
+ \\
+=====Address=====
+Sensors have flat addresses in Rocrail as described in chapter **[[:addressing-en#addressing_sensors|Addressing]]**\\
+>**Note:** Generally a sensor needs an address, exceptions are virtual sensors
+====Address setting using the sensor-monitor====
+The most elegant address setting works by using the **[[:sensormon-en|sensor-monitor]]** or by clicking on the **[ ? ]** Button\\
+  * Driving a loco around the layout every sensor event is reported in the sensor-monitor.\\
+  * Just drag the shown address of the reported sensor with the mouse and drop it on the right sensor object in the plan.\\
+  * With this action this address is written in the object interface definition.
+====Offset====
+| :!: Only for small layouts because of performance penalty. :!: |
+Optional, __not supported__, offset variable.\\
+The value of the variable will be added to the sensor address.\\
+This can be of use in case of sensor systems, like S88, and modular layouts. Only for each sensor module the variable value has to be changed instead of changing all sensor addresses. (Mostly 16 per unit.)\\
+====[ ? ]====
+Selecting the **[ ? ]** activates the __**[[:sensormon-en|Sensor Monitor]]**__
+\\
+=====Register bits=====
+Optional for sensor type **register** only.\\
+If the used Command Station does not natively support register sensor, it can be simulated with max. 8 register bits.\\
+A register bit is just an address of a normal sensor. The register value is after every change event of one of the bits re-calculated.\\
+The register value can be used for turntable position or action control: **regval**.\\
+ \\
+=====Short circuit=====
+Optional cutout address for detecting a short circuit in this section.\\
+Server message on short circuit:
+<code>
+20120617.082116.315 r9999E cmdr1016 OFBack   0367 Sensor [fb3b] report: SHORT CIRCUIT detected
+</code>
+Rocview:\\
+{{:rocview-sensor-short-circuit.png}}
+ \\
+=====Type=====
+|< >|
+^ Value  ^ Type  ^ Manufacturer ^ Remark  ^
+| 0 | Current sensors | - | Most commonly used; Can also report bi-directional information; Also for Hall Sensors when not used as wheel counters. |
+| 1 | IR Lissy | Uhlenbrock | Can be used with the __**[[:sensor-gen-en#timer|Off timer]]**__ to get it unoccupied. |
+| 2 | Transponding receivers | Digitrax | Not used; Same as type=0. |
+| 3 | Barcode | BarJut | Not used; Same as type=0. |
+| 4 | RailCom | - | Not used; Same as type=0. |
+| 5 | RFID | MERG, LDT | Not used; Same as type=0. |
+| 6 | Wheel counter | **[[:gca173-en|GCA173]]**, **[[:gca179-en|GCA179]]** and **[[:mgv141-en|GCA141]]** \\ for Hall sensors and Reed contacts. | Used for wheel or car counting. |\\
+| 7 | GPS | **[[:got:got-en|GamesOnTrack]]** | Using the GPS coordinates on the GPS tab. |
+| 8 | Register | - | Can be used for __**[[:turntable-int-en#position_sensors|Turntable position sensor]]**__.  |
+Read **[[sensor-bi-directional-en|Bi-Directional Communication]]** for more information on this topic.\\
+ \\
+=====Register trigger=====
+Specifies the physical quantity for which the value represented by the register bits is defined.
+===== Options =====
+==== Active low ====
+Sensor has the signal inverted and can be reverted with this option.\\
+==== Reset ====
+For type Wheel Counter __**[[:mgv141-en|GCA141]]**__ only! Do not use in case of software counting.\\
+Send a reset switch command with the same address as used for this sensor on a reset counter event for __**[[:mgv141-en|GCA141]]**__.\\
+| **Attention :!::** The sensor address in this case must not be the same as the one of an existing switch! |
+==== Threshold ====
+The minimal value to signal the sensor high in case of type register.\\
+=====Note=====
+For the assignment of addresses to sensor\feedback in the track plan, there is help with **[[sensormon-en#Tip for the assignment of addresses to sensors\feedback in a track plan|Sensor Monitor]]** \\
+ \\