Differences

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

--- sensor-int-en [2020/09/18 12:00] – [RFID] rjversluis
+++ sensor-int-en [2022/01/29 16:38] (current) – [Interface ID] smitt48
@@ Line 10: / Line 10: @@
 SensorDialog Interface Tab.\\
-{{:sensor-int-en.png}}\\
+{{:sensor-int-en.png?500}}\\
  \\
 =====Interface ID=====
-If you have more than one Command Station you can use this field to link this sensor with the CS you actually wired it with.\\
+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.
-Leave blank in case you have only one CS or when it is wired to the default CS. (First digint in the rocrail.ini)\\
- \\
 =====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 Bus number supported by:
+Alternative to the Node-ID supported by:
   * BiDiB (String: //Username//)
   * RocNet
@@ Line 27: / Line 29: @@
 =====RFID=====
 The 32bit RFID number printed on the Tags. (Leading zeros can be left out.)\\
-This can be used in combination of WIO-Drive.\\
+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=====
@@ Line 40: / Line 49: @@
 >**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=====
+====Offset====
 | :!: Only for small layouts because of performance penalty. :!: |
 Optional, __not supported__, offset variable.\\
@@ Line 48: / Line 63: @@
 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.\\
@@ Line 73: / Line 90: @@
 =====Type=====
-^ Value  ^ Type  ^ Manu ^ Remark  ^
+|< >|
+^ 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. |
@@ Line 80: / Line 98: @@
 | 4 | RailCom | - | Not used; Same as type=0. |
 | 5 | RFID | MERG, LDT | Not used; Same as type=0. |
-| 6 | Wheel counter | **[[:gca173-en|GCA173 Hall Sensors]]**, **[[:mgv141-en|GCA141]]** | Used for wheel or car counting. |\\
+| 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]]**__. (Selectrix based systems)  |
+| 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 ====