Page: SDL: FAQ - Gleisreporter CS1
Last update: 2009-01-10
Using "GleisReporter" connected to CS1 /
Benutzung des "GleisReporter" bei Anschluß an eine CS1
The "GleisReporter" is a sensor module similiar to a s88-module, but operating on the CAN-Bus. The "GleisReporter" module was invented by Dipl.-Ing. Thorsten Mumm in 2008 and was first described in the magazine "MIBA 12/2008" (link to overview in German: http://www.miba.de/miba/08/12/22.htm). The official site of his projects is now (2010): http://www.can-digital-bahn.com/
This sensor module can be used in combination with a CS1/ECoS up to the CS1Rel/ECoS-firmware version 3.0.x. Newer firmware versions will cause a sensor flickering when using this sensor module. See this forum entry .
This short report will tell you how to connect such a "GleisReporter" module to the CS1/ECoS and how to use it with SimpleDigitalLocomotive. First you must know is that you need an adapter cable "CAN-Bus to CAT5", because the module itself has two CAT5-connecters (it doesn't matter which one of this two CAT5 connecters will be used).
The CAN-plug of this adaptor cable must be pluged into one of the three CAN-plugs of the CS1. You will need no additional adaptor.
Then plug the CAT5 plug of the adaptor cable into the first "GleisReporter" module.
Then you must adjust the dip-switches of the "GleisReporter" module. In the picture above the module is set to address #6 (if counted from 1). Now turn on your CS1. Inside the CS1 you must go to "Settings of the CS1":
1. select the "Settings" screen,
2. go to "Setup 1",
3. select "Components in system",
4. select "S88-Bus Control" to see the "S88-Bus Control" screen:
In this "S88-Bus Control" screen you must define all the sensor modules connected to your CS1, no matter which bus they are using. You can mix "GleisReporter" modules with S88-modules. In this case you must avoid address collision: the S88-Bus will occupy the first addresses, because you cannot determine their addresses by dip-switches. S88-Bus modules will be addressed automatically without any gap between them. so give the first "GleisReporter" module an address higher than the last available S88-module in your system connected to your CS1/ECoS. In the following example we will have space left for 5 S88-modules, although only one S88-module is connected. The first "GleisReporter" will get address #6 (the CS1-user inetrface counts the sensor modules from #1), so we must have defined in the following window 6 sensor modules as a minimum:
1. click on the "+" button until you have enough modules defined,
2. then click on the checkmark in the lower right corner of the window to save your settings and to leave this window.
3. Click also on the checkmark in the now reappearing settings window to leave "Settings" screen.
Then launch SimpleDigitalLocomotive. Goto "Preferences" window:
1. select "Startup items",
2. checkbox "program startup with sensor module(s)" must be set,
3. and you must set the desired number of sensor modules.
In our example we want to watch only the first S88-Bus module and the first "GleisReporter" module. So we will need two windows.
In this example we might alternatively set the number to 6, but it is allowed to use any other amount of windows greater than zero, because the CS1 will report sensor events automatically once they are requested by the computer program. SimpleDigitalLocomotive will do this request for every sensor window containing a sensor module number. Gaps are allowed. It this not necessary to create sensor windows for non-existing modules. Please obey: this is only valid in case you are using a CS1/ECoS/Dynamis!
4. Leave "Preferences" window. Settings will have effect on next program relaunch.
Now in our example, with one S88-Bus module and one "GleisReporter" set to address #6, we will define in the already running SimpleDigitalLocomotive application two sensor windows to watch the modules immediately:
1. menubar item "Sensors",
2. click on the item "New s88-window" twice to see two new sensor windows.
Make the approbiate settings inside the upcoming sensor windows: set the refresh rate always to "no polling". And set their module numbers: the one showing the S88-Bus results of our example must get #1, and the window showing the sensors of the CAN-Bus connected "GleisReporter" with it's dip-switches set to address #6 (counted from 1) must get module number #6:
If you turn the "Ethernet protocol" window on, you will see the commands SimpleDigitalLocomotive had sent to the CS1: first requesting state and then view for both open windows. These requests will be renewed if you are changing the sensor window's module number afterwards. Sensor window settings will be saved at program shutdown and will be rebuilded on next program start, if you made the approbiate settings within the window "Preferences", tab "Startup items" as mentioned above.