Instrukcja RASP-UZK/en: Różnice pomiędzy wersjami
(Utworzono nową stronę "free space on your hard drive") |
(Utworzono nową stronę "It appears randomly, it means that the crossing isn't powered from the energetical network. After 3,5 hours it causes appearing of the defect") |
||
(Nie pokazano 201 wersji utworzonych przez 2 użytkowników) | |||
Linia 3: | Linia 3: | ||
__FORCETOC__ | __FORCETOC__ | ||
== About the program == | == About the program == | ||
− | + | The Simulator of Crossing Devices (SUP) is the simulator of remote control devices RASP-UZK in versions 4F 2.0 and 4.4Ft. In the simulator SUP also works as crossing container, being responsible for reporting its state to UZK and following the orders.<br>SUP doesn't support at the moment the crossings which are confirmed in rail courses, also aroused by rail courses and on many-track routes (by >2 tracks RASP serves as the additional signalisation on the crossings of A category). It's also supported to double sensors by adding a letter 'a' or 'b' at the sensor's end. | |
== Hardware requirements == | == Hardware requirements == | ||
− | ► | + | ► The recommended operation system Microsoft Windows 10 64-bit or newer (on version Windows 7 64-bit Service Pack 1 turns on but its operation isn't guaranted)<br>► .NET Framework 4.8<br>► >10MB free space on your hard drive<br>► Monitor with minimal resolution 1024x768 |
− | == | + | == Making the connection with the scenery == |
[[Plik:Instrukcja_RASP-UZK-npzs-1.png|500px|thumb|right|Connecting with the scenery]]After starting up the scenery in dispatcher mode, you must load a configuration file by selecting in the menu <code>Plik > Wczytaj</code>.<br> | [[Plik:Instrukcja_RASP-UZK-npzs-1.png|500px|thumb|right|Connecting with the scenery]]After starting up the scenery in dispatcher mode, you must load a configuration file by selecting in the menu <code>Plik > Wczytaj</code>.<br> | ||
After that, you should start the connection by selecting <code>Plik > Połącz</code>. In the new window you must confirm host's IP adress and port number, otherwise you should correct those datas.<br> | After that, you should start the connection by selecting <code>Plik > Połącz</code>. In the new window you must confirm host's IP adress and port number, otherwise you should correct those datas.<br> | ||
The process of connection lasts about 20 seconds. In this time railroad crossings are set to the default state, then during a train ride <u>YOU MUST NOT</u> start a new connection with the simulator.<br><br><br> | The process of connection lasts about 20 seconds. In this time railroad crossings are set to the default state, then during a train ride <u>YOU MUST NOT</u> start a new connection with the simulator.<br><br><br> | ||
== The main window (4F 2.0) == | == The main window (4F 2.0) == | ||
− | [[Plik:Instrukcja_RASP-UZK-oknog4f20-1.png|500px|thumb|right|The main window (4F 2.0)]] | + | [[Plik:Instrukcja_RASP-UZK-oknog4f20-1.png|500px|thumb|right|The main window (4F 2.0)]]In the main window there is shown basic information about monitored crossings. Reproduction of SSP state is realised with filling the apropriate fields with colours. Defects are signalised additionally with a continuous sound (I category) or interrupted (II category).<br><br>► <big>'''Fields in main window'''</big> |
{| class="wikitable" style="font-weight:bold;" | {| class="wikitable" style="font-weight:bold;" | ||
|- style="text-align:center; vertical-align:middle;" | |- style="text-align:center; vertical-align:middle;" | ||
Linia 41: | Linia 41: | ||
== The main window (4.4Ft) == | == The main window (4.4Ft) == | ||
− | [[Plik:Instrukcja_RASP-UZK-oknog44ft-1.png|500px|thumb|right|The main window (4.4Ft)]] | + | [[Plik:Instrukcja_RASP-UZK-oknog44ft-1.png|500px|thumb|right|The main window (4.4Ft)]]Like in 4F 2.0 UI, the main window in 4.4Ft presents basic information about controlled crossings and status of proper crossings is displayed as filling fields with information about it. Failures are also marked by the sound signal: still (cat. I) or broken (cat. II).<br><br>► <big>'''Fields in the main window'''</big> |
{| class="wikitable" style="font-weight:bold; text-align:center;" | {| class="wikitable" style="font-weight:bold; text-align:center;" | ||
Linia 58: | Linia 58: | ||
|- | |- | ||
| colspan="2" style="vertical-align:middle;" | ZEROWANIE | | colspan="2" style="vertical-align:middle;" | ZEROWANIE | ||
− | | style="font-weight:normal; text-align:left;" | » gray (OK zer.) - default state<br>» darkred (Zerowanie) - | + | | style="font-weight:normal; text-align:left;" | » gray (OK zer.) - default state<br>» darkred (Zerowanie) - remote opening |
|- | |- | ||
| colspan="2" style="vertical-align:middle;" | USTERKA I | | colspan="2" style="vertical-align:middle;" | USTERKA I | ||
Linia 67: | Linia 67: | ||
|- | |- | ||
| colspan="2" style="vertical-align:middle;" | TRANSMISJA | | colspan="2" style="vertical-align:middle;" | TRANSMISJA | ||
− | | style="font-weight:normal; text-align:left;" | » gray (OK transm.) - transmission correct<br>» red (BRAK transm.) - | + | | style="font-weight:normal; text-align:left;" | » gray (OK transm.) - transmission correct<br>» red (BRAK transm.) - no communication between SUP and TD2 or batteries are dead |
|- | |- | ||
| colspan="2" style="vertical-align:middle;" | ZASILANIE | | colspan="2" style="vertical-align:middle;" | ZASILANIE | ||
− | | style="font-weight:normal; text-align:left;" | » gray (OK 230V) - | + | | style="font-weight:normal; text-align:left;" | » gray (OK 230V) - SSP container sourced from the main<br>» orange (BRAK zasil.) - SSP container sourced from the battery |
|- | |- | ||
| colspan="2" style="vertical-align:middle;" | TOR I | | colspan="2" style="vertical-align:middle;" | TOR I | ||
− | | style="font-weight:normal; text-align:left;" | » gray (Tor 1 ZAŁ.) - | + | | style="font-weight:normal; text-align:left;" | » gray (Tor 1 ZAŁ.) - sensores of track 1 on<br>» red (Tor 1 WYŁ.) - sensores of track 1 off |
|- | |- | ||
| colspan="2" style="vertical-align:middle;" | TOR II | | colspan="2" style="vertical-align:middle;" | TOR II | ||
− | | style="font-weight:normal; text-align:left;" | » gray (Tor 2 ZAŁ.) - | + | | style="font-weight:normal; text-align:left;" | » gray (Tor 2 ZAŁ.) - sensores of track 2 on<br>» red (Tor 2 WYŁ.) - sensores of track 1 off |
|} | |} | ||
− | == | + | == Detailed window (4F 2.0 & 4.4Ft) == |
− | [https://wiki.td2.info.pl/index.php?title=Plik:Instrukcja_RASP-UZK-4F20s-1.png | + | [https://wiki.td2.info.pl/index.php?title=Plik:Instrukcja_RASP-UZK-4F20s-1.png View of detailed window 4F 2.0]<br>[https://wiki.td2.info.pl/index.php?title=Plik:Instrukcja_RASP-UZK-44fts-1.png View of detailed window 4.4Ft]<br>Entrance to the particular window can be done by choosing the right crossing on the bar at the bottom. Except small visual differences it's the same in 4F 2.0 and 4.4Ft. In the window there is shown particular information about the crossing's state and the list of statements got from the system. The particular window allows to send the order by choosing the right button with Ctrl keypad and right mouse button.<br>On the upper bar there are 7 fields (5 for C crossing's category). Filling that field with red color means that there has appeared a fault of the I category.<br><br>► <big>'''Crossing's scheme'''</big><br>In the central part there's a crossing's scheme. The scheme shows the mapping of tools on the crossing. Zone filling means the occupying by a train. The interpretation of train's movement direction takes place by occupying the following zone.<br><br>► <big>'''Functional buttons'''</big><br>On the left side of the particular window there are functional buttons (table). |
{| class="wikitable" style="font-weight:bold; text-align:center;" | {| class="wikitable" style="font-weight:bold; text-align:center;" | ||
|- | |- | ||
Linia 87: | Linia 87: | ||
|- style="font-weight:normal;" | |- style="font-weight:normal;" | ||
| style="vertical-align:middle;" | '''Zezwolenie na ster. LOKALNE''' (4F 2.0)<br>'''Sterowanie LOKALNE''' (4.4Ft) | | style="vertical-align:middle;" | '''Zezwolenie na ster. LOKALNE''' (4F 2.0)<br>'''Sterowanie LOKALNE''' (4.4Ft) | ||
− | | style="text-align:left;" | » | + | | style="text-align:left;" | » orange - crossing is manipulated locally (manually)<br>» blinking orange - allowed for local manipulation<br>» gray - steered automatically |
|- style="font-weight:normal;" | |- style="font-weight:normal;" | ||
| style="vertical-align:middle;" | '''Sterowanie AUTOMATYCZNE''' (4F 2.0)<br>'''Sterowanie AUTOMAT.''' (4.4Ft) | | style="vertical-align:middle;" | '''Sterowanie AUTOMATYCZNE''' (4F 2.0)<br>'''Sterowanie AUTOMAT.''' (4.4Ft) | ||
− | | style="text-align:left;" | » | + | | style="text-align:left;" | » green - crossing is steered automatically<br>» blinking green - crossing is steered locally (only 4.4Ft)<br>» grey - local steering |
|- | |- | ||
| style="vertical-align:middle;" | T1 ZAŁ. / T2 ZAŁ. | | style="vertical-align:middle;" | T1 ZAŁ. / T2 ZAŁ. | ||
− | | style="font-weight:normal; text-align:left;" | » | + | | style="font-weight:normal; text-align:left;" | » gray - sensors in the track off<br>» green - sensors in the track on |
|- | |- | ||
| style="vertical-align:middle;" | T1 WYŁ. / T2 WYŁ. | | style="vertical-align:middle;" | T1 WYŁ. / T2 WYŁ. | ||
− | | style="font-weight:normal; text-align:left;" | » | + | | style="font-weight:normal; text-align:left;" | » grey - sensors in the track on<br>» red - sensors in the track off |
|- | |- | ||
| style="vertical-align:middle;" | ZEROWANIE | | style="vertical-align:middle;" | ZEROWANIE | ||
− | | style="font-weight:normal; text-align:left;" | » | + | | style="font-weight:normal; text-align:left;" | » gray - default state<br>» purple (4F 2.0) - system zeroed via the remote control system<br>» darkred (4.4Ft) - system zeroed via the remote control system |
|} | |} | ||
− | + | Blue filled blinking field means that the order has been given out but not sent. To send the order Enter keypad must be used. The time for sending the order with Enter pad is timely limited up to 20 sec for 4F and up to 9 sec for 4.4Ft. After order sending the field changes color into.<br><br>► <big>'''The way of using function buttons'''</big><br>Circumstances were shown in ''Fault table''.<br>The order choosing takes place every time by clicking on the right field <u>with right</u> mouse button with a keypad <u>Ctrl</u> (Ctrl+RMB). After choosing the command, you must transmit it by pressing <u>Enter</u>.<br><u>In case of fields ''T1 zał / T2 zał'' and ''ZEROWANIE'' before choosing the order additionally there will be shown a window ''UWAGA''. The time to click a the button ''Dalej'' is time-limited.</u><br>In case when the field's color is another than the default state or SUP isn't connected with TD2 it's impossible to choose the order.<br><br>► <big>'''Turning on and off the track sensors'''</big><br>Turning off / on the sensors is used by track repairs, a ride of measure train, a defect of turning on sensor.<br>Field ''T1 ZAŁ. / T2 ZAŁ.'' in green means that sensors are on. ''T1 WYŁ. / T2 WYŁ.'' in red means that sensors are off.<br>'''WARNING: after turning off the sensors signalisation won't be turned on by the train ride! If there are no TOP signals, the speed must be reduced to 20 km/h with a proper written order (Rozkaz pisemny)!'''<br><br>► <big>'''Setting the crossing to default state'''</big><br>Setting the crossing to the default state is an attempt to set everything to the default state - turning off the warning. It should be done after fault's appearing. After setting to the default state there's done whole crossing's diagnostics while which the faults can be found again.<br>The ride of the first train on any track and in any direction should be completed with reduced speed (for crossings with TOP there'll be litten orange lights).<br>If the fault doesn't pass after setting to the default state, you'll have to follow orders written in ''Fault table''.<br><br>► <big>'''Automatic / local steering'''</big><br>In SUP there's no possibility to change the local steering way to automatic and in opposite way. SUP changes work mode automatically after connecting with the simulator and after setting the crossings to default state. | |
== Alerts == | == Alerts == | ||
− | [[Plik:Instrukcja_RASP-UZK-lus-1.png|500px|thumb|right|Alert list]] | + | [[Plik:Instrukcja_RASP-UZK-lus-1.png|500px|thumb|right|Alert list]]Down in the detailed window there's a list of statements which appeal to the SSP crossing.<br>Information included in announcements:<br>► state of crossing devices,<br>► crossing state,<br>► appearing the faults on the crossing,<br>► faults' confirmation.<br>By using the right mouse button there'll be shown a context menu which allows to change the mode of displayed statements (simplified or detailed list). |
− | == | + | == Settings == |
− | [[Plik:Instrukcja_RASP-UZK-ust-1.png|500px|thumb|right|Settings]] | + | [[Plik:Instrukcja_RASP-UZK-ust-1.png|500px|thumb|right|Settings]]After choosing in the menu <code>Narzędzia > Ustawienia</code> there opens a settings' window. The settings are global - it means that they appeal to all SUP instances irrespective of loaded configuration crossing's file.<br>The change of frequency of occuring the random fault takes place by moving the slider in the wanted position. |
{| class="wikitable" style="font-weight:bold; text-align:center;" | {| class="wikitable" style="font-weight:bold; text-align:center;" | ||
|- | |- | ||
Linia 126: | Linia 126: | ||
| style="font-weight:normal;" | 5 | | style="font-weight:normal;" | 5 | ||
|} | |} | ||
− | Button <code>Wezwij automatyka</code> | + | Button <code>Wezwij automatyka</code> serves to delete the faults. After its using you should follow the tips given by an automatician. |
− | == | + | == Editor == |
− | [[Plik:Instrukcja_RASP-UZK-edytor-1.png|500px|thumb|right| | + | [[Plik:Instrukcja_RASP-UZK-edytor-1.png|500px|thumb|right|Editor field]]SUP allows to create the configuration crossing files on your own by usage of an built-in tool.<br><br>► <big>'''Crossing'''</big><br> |
{| class="wikitable" style="font-weight:bold; text-align:center;" | {| class="wikitable" style="font-weight:bold; text-align:center;" | ||
|- | |- | ||
− | ! | + | ! Field |
− | ! | + | ! Value |
|- | |- | ||
− | | | + | | Crossing's kilometer |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | form XX.YYY |
|- | |- | ||
− | | | + | | TD2 name |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | form PXXYYY |
|- | |- | ||
− | | | + | | Line number |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | text |
|- | |- | ||
− | | | + | | The crossing's length along the road axis |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | digit from range 6-50 |
|- | |- | ||
− | | | + | | Crossing type |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | one-track / two-track |
|- | |- | ||
− | | | + | | Barriers |
− | | style="font-weight:normal;" | 4 | + | | style="font-weight:normal;" | 4 barriers / 2 barriers / no barriers |
|- | |- | ||
− | | | + | | Road designation |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | vertical / sloping / none |
|- | |- | ||
− | | | + | | Interface version |
| style="font-weight:normal;" | 4.4Ft / 4F 2.0 | | style="font-weight:normal;" | 4.4Ft / 4F 2.0 | ||
|- | |- | ||
− | | | + | | TOP description |
| style="font-weight:normal;" | TOPx [xx] / TOPx xx / TOPx | | style="font-weight:normal;" | TOPx [xx] / TOPx xx / TOPx | ||
|- | |- | ||
− | | | + | | TOP usage |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | no / yes |
|- | |- | ||
− | | | + | | Synchronical TOP (4F 2.0) |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | no / yes |
|- | |- | ||
− | | | + | | Station names (4.4Ft) |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | no / yes |
|- | |- | ||
− | | | + | | Compatibility mode with Ie-119 (4.4Ft) |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | yes / no |
|- | |- | ||
− | | | + | | SSP reversing |
− | | style="font-weight:normal;" | | + | | style="font-weight:normal;" | no / yes |
|} | |} | ||
− | <br>► <big>''' | + | <br>► <big>'''Signalistaion'''</big><br>The choose of postioning between 2 to 8 road signals. The nummeration is ordered by the Editor - on the scenery road signals should be named in way which is shown in the following tab, adding also a prefix <code>Nazwa TD2</code>.<br><br>► <big>'''Names'''</big><br>Defying the names of crossing warning's signals (in the editor without prefix - they're used only on sceneries) and track names and neighbour stations.<br><br>► <big>'''SSP list'''</big><br>Workind on the already definied railway crossings - changing their order, loading, saving the changes, deleting. Adding a new crossing takes place in a mark <code>Przejazd</code>.<br><br>► <big>'''Calculations'''</big><br>Evaluation of the minimal distance of turning on sensors from the crossing including:<br>» the minimal warning time for chosen category,<br>» train leaving time from the crossing,<br>» warning sequence (8-16-16-6 for old guidelines, 13-10-x-10-7 for the new ones, where x - minimal time of a train leaving a crossing). |
− | == | + | == System's reaction for traffic situation == |
− | ► <big>''' | + | ► <big>'''Typical situation'''</big><br>Train riding on a turning on sensor (C1, C4, C11, C14) initializes the work of crossing devices. |
− | * | + | * SSP work cycle in compatiblity mode with Ie-119 |
− | 1) | + | 1) showing for 0,5s Osp2 signal on the warning crossing signal right for the track and train ride direction,<br> |
− | 2) | + | 2) enabling road signals,<br> |
− | 3) | + | 3) after 13s: beginning of closing the entrance barriers,<br> |
− | 4) | + | 4) after time needed for a train to leave the crossing (counted from the crossing's length, normally about 12 - 15s): beginning of opening the exit barriers,<br> |
− | 5) | + | 5) after closing: waiting for a train for at least 7 seconds,<br> |
− | 6) | + | 6) after realeasing the crossing zone (zone C2C3): the TOP signal is turned off,<br> |
− | 7) | + | 7) after 6s: beginning of opening the exit barriers,<br> |
− | 8) | + | 8) after opening: beginning of opening the entry barriers,<br> |
− | 9) | + | 9) after opening: turning off the road signals. |
− | * | + | * SSP work cyclus in the "classic" mode |
− | 1) | + | 1) showing the Osp2 signal on the crossing's warning signal right for the track and ride direction OR on all warning signals (synchronous mode) within 0,5s,<br> |
− | 2) | + | 2) enabling road signals,<br> |
− | 3) | + | 3) after 8s: beginning of closing the entrance barriers,<br> |
− | 4) | + | 4) after 16s: beginning of closing the exit barriers,<br> |
− | 5) | + | 5) after closing: waiting for a train for at least 6 seconds,<br> |
− | 6) | + | 6) after realeasing the crossing zone (zone C2C3): the TOP signal is turned off,<br> |
− | 7) | + | 7) after 6s: beginning of opening the exit barriers,<br> |
− | 8) | + | 8) after opening: beginning of opening the entry barriers,<br> |
− | 9) | + | 9) after opening: turning off the road signals. |
− | <br>► <big>''' | + | <br>► <big>'''Untypical situation'''</big><br>In case of appearing the fault of the 1st category it's necessary to reduce the maximal speed up to 20 km/h. The limitation is realised by showing the Osp1 signal on the crossing warning's signals (selectively for the track and direction or for all the signals). For faults of the 2nd category it isn't necessary to introduce the speed limitation on the crossing.<br><u>If there are no crossing warning signals, the speed will have to be reduced on the crossing using an appropriate written order.</u><br>A fault can occur when the crossing is in rest state - in RASP container every 30 seconds it's done PULS-TEST of all the crossing components, including the continuity of light bulb fibre.<br>The detailed course of action is shown in ''Fault table''. |
− | == | + | == Crossing's scheme == |
[[Plik:Instrukcja_RASP-UZK-schematprzejazdu-1.PNG|800px]] | [[Plik:Instrukcja_RASP-UZK-schematprzejazdu-1.PNG|800px]] | ||
− | == | + | == Fault table == |
{| class="wikitable" style="text-align:center;" | {| class="wikitable" style="text-align:center;" | ||
|- style="font-weight:bold;" | |- style="font-weight:bold;" | ||
− | ! style="vertical-align:middle;" | | + | ! style="vertical-align:middle;" | Fault name |
− | ! style="vertical-align:middle;" | | + | ! style="vertical-align:middle;" | Fault description |
− | ! | + | ! Conduction |
|- style="font-weight:bold;" | |- style="font-weight:bold;" | ||
− | | colspan="3" style="vertical-align:middle;" | | + | | colspan="3" style="vertical-align:middle;" | Defect of I category |
|- | |- | ||
| style="vertical-align:middle; font-weight:bold;" | Usterka czujnika włączającego <br />(C1; C4; C11; C14) | | style="vertical-align:middle; font-weight:bold;" | Usterka czujnika włączającego <br />(C1; C4; C11; C14) | ||
− | | style="vertical-align:middle;" | | + | | style="vertical-align:middle;" | It appears randomly after detecting a failure in axis counting or after occupying the zone for more than 9 minutes.<br>It causes the automatic enabling of warning on the crossing. Sensors' failure makes turning it off impossible. |
− | | style="text-align:left;" | 1) | + | | style="text-align:left;" | 1) setting to the default state<br />2) if the defect hadn't dissapeared:<br /> a) setting again to the default state<br /> b) disabling the sensors after the announcement “System wyzerowany z UZK” <br>(after enabling the diagnostics the crossing 'doesn't see' the defect)<br /> c) calling an automatician (PL: Wezwij automatyka) |
|- | |- | ||
| style="vertical-align:middle; font-weight:bold;" | Awaria napędu | | style="vertical-align:middle; font-weight:bold;" | Awaria napędu | ||
− | | style="vertical-align:middle;" | | + | | style="vertical-align:middle;" | It appears randomly or after 'manual' change made by a dispatcher.<br />Usually it means an ucontrolled change of drive location. In the detailed window there's additionally signalised as the indirect state. |
− | | style="text-align:left;" | 1) | + | | style="text-align:left;" | 1) setting to the default state<br />2) if the defect hadn't dissapeared:<br /> a) calling an automatician (PL: Wezwij automatyka) |
|- | |- | ||
| style="vertical-align:middle; font-weight:bold;" | Awaria ciągłości drąga | | style="vertical-align:middle; font-weight:bold;" | Awaria ciągłości drąga | ||
− | | colspan="2" style="vertical-align:middle;" | | + | | colspan="2" style="vertical-align:middle;" | Doesn't appear in SUP. |
|- | |- | ||
| style="vertical-align:middle; font-weight:bold;" | Awaria sygnalizatora | | style="vertical-align:middle; font-weight:bold;" | Awaria sygnalizatora | ||
− | | style="vertical-align:middle;" | | + | | style="vertical-align:middle;" | It appears randomly after burning out the bulb in one of the chambers |
− | | style="text-align:left;" | 1) | + | | style="text-align:left;" | 1) setting to the default state<br />2) if the defect hadn't dissapeared:<br /> a) calling an automatician (PL: Wezwij automatyka) |
|- | |- | ||
| style="vertical-align:middle; font-weight:bold;" | Niskie napięcie / Rozładowanie akumulatorów | | style="vertical-align:middle; font-weight:bold;" | Niskie napięcie / Rozładowanie akumulatorów | ||
− | | style="vertical-align:middle; font-style:italic;" | | + | | style="vertical-align:middle; font-style:italic;" | 'Low currency' appears after 3,5 hours after appearing the 'Brak ładowania' (No loading) defect. It causes self-acting enabling of warning on the crossing.<br>After 30 minutes the batteries discharge fully and the communication with the crossing disappears |
− | | | + | | It's impossible to repair or set the defect to the default state,<br>calling an automatician doesn't help at all |
|- | |- | ||
| style="vertical-align:middle; font-weight:bold;" | Brak transmisji | | style="vertical-align:middle; font-weight:bold;" | Brak transmisji | ||
− | | style="vertical-align:middle;" | | + | | style="vertical-align:middle;" | Completelly no communication between SUP and TD2.<br />In the case of critical error SUP disconnects with the simulator and shows a window with a information about the appeared failure. |
− | | style="text-align:left;" | 1) Menu -> SUP -> Połącz | + | | style="text-align:left;" | 1) Menu -> SUP -> Połącz if it is available<br />2) If it's unavailable - the reason of transmission loss is discharging the batteries or a programm's critical error |
|- style="font-weight:bold;" | |- style="font-weight:bold;" | ||
| colspan="3" style="vertical-align:middle;" | Usterki kat. II | | colspan="3" style="vertical-align:middle;" | Usterki kat. II | ||
|- | |- | ||
| style="vertical-align:middle; font-weight:bold;" | Usterka czujnika wyłączającego <br />(C2; C3; C12; C13) | | style="vertical-align:middle; font-weight:bold;" | Usterka czujnika wyłączającego <br />(C2; C3; C12; C13) | ||
− | | style="vertical-align:middle;" | | + | | style="vertical-align:middle;" | It appears randomly after detecting a failure in axis counting or after occupying the zone for more than 9 minutes. To release the crossing zone instead of broken down sensors there'll be used enabling sensors of the opposite direction. The sensors' defect doesn't allow to turn them off. |
− | | style="text-align:left;" | 1) | + | | style="text-align:left;" | 1) setting to the default state<br />2) if the defect hadn't dissapeared:<br /> a) calling an automatician (PL: Wezwij automatyka) |
|- | |- | ||
| style="vertical-align:middle; font-weight:bold;" | Brak ładowania | | style="vertical-align:middle; font-weight:bold;" | Brak ładowania | ||
− | | style="vertical-align:middle;" | | + | | style="vertical-align:middle;" | It appears randomly, it means that the crossing isn't powered from the energetical network. After 3,5 hours it causes appearing of the defect “Niskie napięcie”. |
− | | | + | | It's impossible to repair or set the defect to the default state,<br>calling an automatician doesn't help at all |
|- | |- | ||
| style="vertical-align:middle; font-weight:bold;" | Usterki świateł białych / pomarańczowych tarcz TOP | | style="vertical-align:middle; font-weight:bold;" | Usterki świateł białych / pomarańczowych tarcz TOP | ||
− | | style="vertical-align:middle;" | | + | | style="vertical-align:middle;" | It appears randomly, it means the burning out one of the bulbs. |
− | | style="text-align:left;" | 1) | + | | style="text-align:left;" | 1) setting to the default state<br />2) if the defect hadn't dissapeared:<br /> a) calling an automatician (PL: Wezwij automatyka) |
|} | |} |
Aktualna wersja na dzień 19:14, 25 maj 2023
Spis treści
About the program
The Simulator of Crossing Devices (SUP) is the simulator of remote control devices RASP-UZK in versions 4F 2.0 and 4.4Ft. In the simulator SUP also works as crossing container, being responsible for reporting its state to UZK and following the orders.
SUP doesn't support at the moment the crossings which are confirmed in rail courses, also aroused by rail courses and on many-track routes (by >2 tracks RASP serves as the additional signalisation on the crossings of A category). It's also supported to double sensors by adding a letter 'a' or 'b' at the sensor's end.
Hardware requirements
► The recommended operation system Microsoft Windows 10 64-bit or newer (on version Windows 7 64-bit Service Pack 1 turns on but its operation isn't guaranted)
► .NET Framework 4.8
► >10MB free space on your hard drive
► Monitor with minimal resolution 1024x768
Making the connection with the scenery
After starting up the scenery in dispatcher mode, you must load a configuration file by selecting in the menu Plik > Wczytaj
.
After that, you should start the connection by selecting Plik > Połącz
. In the new window you must confirm host's IP adress and port number, otherwise you should correct those datas.
The process of connection lasts about 20 seconds. In this time railroad crossings are set to the default state, then during a train ride YOU MUST NOT start a new connection with the simulator.
The main window (4F 2.0)
In the main window there is shown basic information about monitored crossings. Reproduction of SSP state is realised with filling the apropriate fields with colours. Defects are signalised additionally with a continuous sound (I category) or interrupted (II category).
► Fields in main window
Field name | Field colour | |
---|---|---|
(crossing's name) | » crossing's kilometer | |
STEROWANIE | » greeen - steered automatically » orange - local steering | |
USTERKA I | » gray - no defects of I category » red blinking - defect of I category | |
USTERKA II | » gray - no defects of II category » red permanent - defect of II category | |
TRANSMISJA | » gray (TRANSMISJA OK) - transmission correct » red (BRAK TRANSMISJI) - no connection with the simulator or batteries are dead | |
TOR I | » gray - sensors on the no. 1 track are enabled » red- sensors on the no. 1 track are disabled | |
TOR II | » gray - sensors on the no. 2 track are enabled » gray - sensors on the no. 2 track are disabled |
The main window (4.4Ft)
Like in 4F 2.0 UI, the main window in 4.4Ft presents basic information about controlled crossings and status of proper crossings is displayed as filling fields with information about it. Failures are also marked by the sound signal: still (cat. I) or broken (cat. II).
► Fields in the main window
Field name | Field colour | |
---|---|---|
(crossing's name) | » crossing's kilometer | |
STAN (simplified crossing's scheme) |
» white - no SUP communication with TD2 » purple - awaiting » gray - warning » red/white blinking - defect of I or II category | |
STEROWANIE | » green (OK auto) - automatical steering » orange (OK lokalnie) - local steering | |
ZEROWANIE | » gray (OK zer.) - default state » darkred (Zerowanie) - remote opening | |
USTERKA I | » gray (OK ust. 2) - no defects of I category » red blinking (Ust. kat.1) - defect of I category | |
USTERKA II | » gray (OK ust.2) - no defects of II category » yellow (Ust. kat.2) - defect of II category | |
TRANSMISJA | » gray (OK transm.) - transmission correct » red (BRAK transm.) - no communication between SUP and TD2 or batteries are dead | |
ZASILANIE | » gray (OK 230V) - SSP container sourced from the main » orange (BRAK zasil.) - SSP container sourced from the battery | |
TOR I | » gray (Tor 1 ZAŁ.) - sensores of track 1 on » red (Tor 1 WYŁ.) - sensores of track 1 off | |
TOR II | » gray (Tor 2 ZAŁ.) - sensores of track 2 on » red (Tor 2 WYŁ.) - sensores of track 1 off |
Detailed window (4F 2.0 & 4.4Ft)
View of detailed window 4F 2.0
View of detailed window 4.4Ft
Entrance to the particular window can be done by choosing the right crossing on the bar at the bottom. Except small visual differences it's the same in 4F 2.0 and 4.4Ft. In the window there is shown particular information about the crossing's state and the list of statements got from the system. The particular window allows to send the order by choosing the right button with Ctrl keypad and right mouse button.
On the upper bar there are 7 fields (5 for C crossing's category). Filling that field with red color means that there has appeared a fault of the I category.
► Crossing's scheme
In the central part there's a crossing's scheme. The scheme shows the mapping of tools on the crossing. Zone filling means the occupying by a train. The interpretation of train's movement direction takes place by occupying the following zone.
► Functional buttons
On the left side of the particular window there are functional buttons (table).
Field name | Field colour |
---|---|
Zezwolenie na ster. LOKALNE (4F 2.0) Sterowanie LOKALNE (4.4Ft) |
» orange - crossing is manipulated locally (manually) » blinking orange - allowed for local manipulation » gray - steered automatically |
Sterowanie AUTOMATYCZNE (4F 2.0) Sterowanie AUTOMAT. (4.4Ft) |
» green - crossing is steered automatically » blinking green - crossing is steered locally (only 4.4Ft) » grey - local steering |
T1 ZAŁ. / T2 ZAŁ. | » gray - sensors in the track off » green - sensors in the track on |
T1 WYŁ. / T2 WYŁ. | » grey - sensors in the track on » red - sensors in the track off |
ZEROWANIE | » gray - default state » purple (4F 2.0) - system zeroed via the remote control system » darkred (4.4Ft) - system zeroed via the remote control system |
Blue filled blinking field means that the order has been given out but not sent. To send the order Enter keypad must be used. The time for sending the order with Enter pad is timely limited up to 20 sec for 4F and up to 9 sec for 4.4Ft. After order sending the field changes color into.
► The way of using function buttons
Circumstances were shown in Fault table.
The order choosing takes place every time by clicking on the right field with right mouse button with a keypad Ctrl (Ctrl+RMB). After choosing the command, you must transmit it by pressing Enter.
In case of fields T1 zał / T2 zał and ZEROWANIE before choosing the order additionally there will be shown a window UWAGA. The time to click a the button Dalej is time-limited.
In case when the field's color is another than the default state or SUP isn't connected with TD2 it's impossible to choose the order.
► Turning on and off the track sensors
Turning off / on the sensors is used by track repairs, a ride of measure train, a defect of turning on sensor.
Field T1 ZAŁ. / T2 ZAŁ. in green means that sensors are on. T1 WYŁ. / T2 WYŁ. in red means that sensors are off.
WARNING: after turning off the sensors signalisation won't be turned on by the train ride! If there are no TOP signals, the speed must be reduced to 20 km/h with a proper written order (Rozkaz pisemny)!
► Setting the crossing to default state
Setting the crossing to the default state is an attempt to set everything to the default state - turning off the warning. It should be done after fault's appearing. After setting to the default state there's done whole crossing's diagnostics while which the faults can be found again.
The ride of the first train on any track and in any direction should be completed with reduced speed (for crossings with TOP there'll be litten orange lights).
If the fault doesn't pass after setting to the default state, you'll have to follow orders written in Fault table.
► Automatic / local steering
In SUP there's no possibility to change the local steering way to automatic and in opposite way. SUP changes work mode automatically after connecting with the simulator and after setting the crossings to default state.
Alerts
Down in the detailed window there's a list of statements which appeal to the SSP crossing.
Information included in announcements:
► state of crossing devices,
► crossing state,
► appearing the faults on the crossing,
► faults' confirmation.
By using the right mouse button there'll be shown a context menu which allows to change the mode of displayed statements (simplified or detailed list).
Settings
After choosing in the menu Narzędzia > Ustawienia
there opens a settings' window. The settings are global - it means that they appeal to all SUP instances irrespective of loaded configuration crossing's file.
The change of frequency of occuring the random fault takes place by moving the slider in the wanted position.
Level | Multiplier |
---|---|
None | 0 |
Very rare | 0,5 |
Rare | 1 |
Frequent | 2 |
Very frequent | 5 |
Button Wezwij automatyka
serves to delete the faults. After its using you should follow the tips given by an automatician.
Editor
SUP allows to create the configuration crossing files on your own by usage of an built-in tool.
► Crossing
Field | Value |
---|---|
Crossing's kilometer | form XX.YYY |
TD2 name | form PXXYYY |
Line number | text |
The crossing's length along the road axis | digit from range 6-50 |
Crossing type | one-track / two-track |
Barriers | 4 barriers / 2 barriers / no barriers |
Road designation | vertical / sloping / none |
Interface version | 4.4Ft / 4F 2.0 |
TOP description | TOPx [xx] / TOPx xx / TOPx |
TOP usage | no / yes |
Synchronical TOP (4F 2.0) | no / yes |
Station names (4.4Ft) | no / yes |
Compatibility mode with Ie-119 (4.4Ft) | yes / no |
SSP reversing | no / yes |
► Signalistaion
The choose of postioning between 2 to 8 road signals. The nummeration is ordered by the Editor - on the scenery road signals should be named in way which is shown in the following tab, adding also a prefix Nazwa TD2
.
► Names
Defying the names of crossing warning's signals (in the editor without prefix - they're used only on sceneries) and track names and neighbour stations.
► SSP list
Workind on the already definied railway crossings - changing their order, loading, saving the changes, deleting. Adding a new crossing takes place in a mark Przejazd
.
► Calculations
Evaluation of the minimal distance of turning on sensors from the crossing including:
» the minimal warning time for chosen category,
» train leaving time from the crossing,
» warning sequence (8-16-16-6 for old guidelines, 13-10-x-10-7 for the new ones, where x - minimal time of a train leaving a crossing).
System's reaction for traffic situation
► Typical situation
Train riding on a turning on sensor (C1, C4, C11, C14) initializes the work of crossing devices.
- SSP work cycle in compatiblity mode with Ie-119
1) showing for 0,5s Osp2 signal on the warning crossing signal right for the track and train ride direction,
2) enabling road signals,
3) after 13s: beginning of closing the entrance barriers,
4) after time needed for a train to leave the crossing (counted from the crossing's length, normally about 12 - 15s): beginning of opening the exit barriers,
5) after closing: waiting for a train for at least 7 seconds,
6) after realeasing the crossing zone (zone C2C3): the TOP signal is turned off,
7) after 6s: beginning of opening the exit barriers,
8) after opening: beginning of opening the entry barriers,
9) after opening: turning off the road signals.
- SSP work cyclus in the "classic" mode
1) showing the Osp2 signal on the crossing's warning signal right for the track and ride direction OR on all warning signals (synchronous mode) within 0,5s,
2) enabling road signals,
3) after 8s: beginning of closing the entrance barriers,
4) after 16s: beginning of closing the exit barriers,
5) after closing: waiting for a train for at least 6 seconds,
6) after realeasing the crossing zone (zone C2C3): the TOP signal is turned off,
7) after 6s: beginning of opening the exit barriers,
8) after opening: beginning of opening the entry barriers,
9) after opening: turning off the road signals.
► Untypical situation
In case of appearing the fault of the 1st category it's necessary to reduce the maximal speed up to 20 km/h. The limitation is realised by showing the Osp1 signal on the crossing warning's signals (selectively for the track and direction or for all the signals). For faults of the 2nd category it isn't necessary to introduce the speed limitation on the crossing.
If there are no crossing warning signals, the speed will have to be reduced on the crossing using an appropriate written order.
A fault can occur when the crossing is in rest state - in RASP container every 30 seconds it's done PULS-TEST of all the crossing components, including the continuity of light bulb fibre.
The detailed course of action is shown in Fault table.
Crossing's scheme
Fault table
Fault name | Fault description | Conduction |
---|---|---|
Defect of I category | ||
Usterka czujnika włączającego (C1; C4; C11; C14) |
It appears randomly after detecting a failure in axis counting or after occupying the zone for more than 9 minutes. It causes the automatic enabling of warning on the crossing. Sensors' failure makes turning it off impossible. |
1) setting to the default state 2) if the defect hadn't dissapeared: a) setting again to the default state b) disabling the sensors after the announcement “System wyzerowany z UZK” (after enabling the diagnostics the crossing 'doesn't see' the defect) c) calling an automatician (PL: Wezwij automatyka) |
Awaria napędu | It appears randomly or after 'manual' change made by a dispatcher. Usually it means an ucontrolled change of drive location. In the detailed window there's additionally signalised as the indirect state. |
1) setting to the default state 2) if the defect hadn't dissapeared: a) calling an automatician (PL: Wezwij automatyka) |
Awaria ciągłości drąga | Doesn't appear in SUP. | |
Awaria sygnalizatora | It appears randomly after burning out the bulb in one of the chambers | 1) setting to the default state 2) if the defect hadn't dissapeared: a) calling an automatician (PL: Wezwij automatyka) |
Niskie napięcie / Rozładowanie akumulatorów | 'Low currency' appears after 3,5 hours after appearing the 'Brak ładowania' (No loading) defect. It causes self-acting enabling of warning on the crossing. After 30 minutes the batteries discharge fully and the communication with the crossing disappears |
It's impossible to repair or set the defect to the default state, calling an automatician doesn't help at all |
Brak transmisji | Completelly no communication between SUP and TD2. In the case of critical error SUP disconnects with the simulator and shows a window with a information about the appeared failure. |
1) Menu -> SUP -> Połącz if it is available 2) If it's unavailable - the reason of transmission loss is discharging the batteries or a programm's critical error |
Usterki kat. II | ||
Usterka czujnika wyłączającego (C2; C3; C12; C13) |
It appears randomly after detecting a failure in axis counting or after occupying the zone for more than 9 minutes. To release the crossing zone instead of broken down sensors there'll be used enabling sensors of the opposite direction. The sensors' defect doesn't allow to turn them off. | 1) setting to the default state 2) if the defect hadn't dissapeared: a) calling an automatician (PL: Wezwij automatyka) |
Brak ładowania | It appears randomly, it means that the crossing isn't powered from the energetical network. After 3,5 hours it causes appearing of the defect “Niskie napięcie”. | It's impossible to repair or set the defect to the default state, calling an automatician doesn't help at all |
Usterki świateł białych / pomarańczowych tarcz TOP | It appears randomly, it means the burning out one of the bulbs. | 1) setting to the default state 2) if the defect hadn't dissapeared: a) calling an automatician (PL: Wezwij automatyka) |