The Sensor Table
This table contains a list of the sensors that exist for this panel.
Sensor Table Columns
- User Name
- You can directly enter or change the "User Name" for an existing sensor.
- State
- Pushing the "State" command button will change the state of an existing sensor.
- Delete
- Pushing the "Delete" button will remove the sensor from the
table.
Note that this doesn't remove the sensor from any files you've saved that contain it. If you load one of those files, perhaps when you restart the program, the sensor will reappear. You should use one of the "Store to file" options in the "File" menu to save new versions of any files that contain this sensor.
- Inverted
- When checked, the sensor command and status is inverted. For example, an inverted sensor means that when the layout sends an "active" sensor command, it becomes "inactive" to JMRI.
- Use Global Delay
- When checked, the sensor will use the system values specified in the "Debounce|Defaults.." menu option for the duration which the system waits for before it registers the change of state.
- Active Delay/ InActive Delay
- Specify the amount of time in milliSeconds that the system waits before registering the state change of a sensor.
Sensor Table Controls
There is also a button at the bottom of the Sensor Table- Add
- Push this button to add a new sensor. For more information see Adding/Editing Sensors.
Sensor Debounce
The Sensor Debounce facility is there to help prevent false triggers of a sensor
being passed into the system and triggering other events in the system.
Such false triggers could be due to a dirty piece of track or electrical interferance.
The facility allows you to assign a period in miliseconds before the change
is registered with the rest of the system. If after that period the state has
not changed then the sensor state will be passed onto the rest the of the system.
However if the sensors state is different after the timer has finished, then the
system will restart the process, this time after the timer has finished it will
check to see if the sensor state is in the same state as it was before it restarted
the process. If not the process is re-started again until the state is the same
before and after the timer is run.