Differences

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

--- znf:znf-en [2025/08/16 22:23] – [Hostname:Port] - easy fix for two IP Netzworks skippa
+++ znf:znf-en [2025/08/16 22:56] (current) – add chapter Offer, Accept/Reject via ZNF skippa
@@ Line 99: / Line 99: @@
 See: [[#using_the_monitor_to_track_telegrams|Tracking Monitor]]\\
 ===Server===
-Enables the local ZN-Server.\\
+Enables the local ZN-Server. Use only when there is no other ZN server active.\\
@@ Line 107: / Line 107: @@
 **Note:** //No find will be issued in case the Hostname and Port are set.//\\
+====Report ghost====
+Enables sending 10 telegrams (track not available) when a GHOST message comes in.
+During shunting movements in the station this can result in a large number of unwanted 10 telegrams.
+Therefore "off" is recommended.
+====Ignore rename====
+By means of a 30 (rename) telegram the shortID of a loco can be changed from outside.
+Other stations use the 30 telegram for example when a train changes direction and its number changes.
+Because (depending on settings) Rocrail shows the corresponding locoID and not the shortID, this can lead to a changed assignment and wrong trains being displayed.
+Therefore "on" is recommended.
- \\
 =====Block=====
-====Tracking & Transfer ID====
+:====Tracking & Transfer ID====
-{{: znf:block-wiring-en.jpg?600|}}\\
+{{: znf:znf-block-tracking-en.png?600|}}\\
 ===Tracking ID====
 This ID is used to publish movements to the ZN-Server. The first two digits of the trackingID contain the substation number (UST).\\
@@ Line 123: / Line 134: @@
 Determines the direction of newly placed locos in the transfer block (Übergabeblock). Set the hook to place locos in the **+** direction.
- \\
+====Options====
-====CTC Display====
+===Reserve if accepted===
-{{:znf:block-wiring-ctc-tracking-en.jpg?600}}\\
-//The CTC Display must be set active to the ZNF controller to be able to publish movements to the ZN-Server.//\\
-===Interface ID===
+Only in connection with offer/accept: if a train is accepted, the block is automatically reserved (yellow).
-The ZNF Controller IID.\\
-===Display Nr.===
-Must be set greater than zero te be active.\\
-===Text===
-The locomotive **[[:loc-gen-en#use_short_id|Short ID]]**.\\
-**Note:** //Leading zeros in the Short ID should be avoided.//\\
+===Reject if occupied===
+Only in connection with offer/accept: if the block is currently occupied, offered trains are directly rejected.
+ \\
 =====Supported Telegram Types=====
@@ Line 177: / Line 185: @@
 ^	Telegram type recieved 	^	Action in RR 	^	Description 	^	use-case	^
 |	21	|	Query shortID shortID = null	|	Delete train number	|	For compatibility only.	|
-|	30	|	Query shortID shortID = new train number	|	Replace train number	|	Train has startet with wrong number, i.e. Fehlernummer or because of human error.	|
+|	30	|	Query shortID shortID = new train number	|	Replace train number	|	Train has startet with wrong number, i.e. Fehlernummer or because of human error. Is ignored if "ignore rename" option is set in central station (recommended)	|
@@ Line 190: / Line 198: @@
 |04| A train enteres the transfer block (Übergabeblock) while the block is occupied with other train | not supported | not supported |
 |05| An transfer block is reserved for loco. | Create loco if shortID not existent. Reserve Block for Loco | A train is being pre-announced to enter the RR district. |
-|06| Transfer block is entered by loco. | Fire enter-Event in transfer block |A pre-announced train is underway into RR district. |
+|06| Preceeding block reservation is reset. |  |A pre-announced train has arrived in RR district or is being cancelled. |
 |10 with train number| Loco is set into transfer block. | Create loco if shortID non existent in loclist. Set block assignment | A train is entering the RR district. |
 |10 with Verfügbarkeitshinweis 00000 oder 0F0F0	| Close transfer block |Put transfer block out of operation | transfer block is blocked/not available announcement by other station. |
@@ Line 275: / Line 283: @@
 open up the //Rocrail properties// and define a new [[:controllers-en|controller]] type ZNF.
 Enter InterfaceID and Station Abrreviation. Get in touch with the [[https://forum.fremo-net.eu/c/spezial/signal/|FREMO Signal forum]] and aquire a [[https://fremo-stw.sourceforge.net/ZNF800/zn800/usnr.de.html|substation number (UST)]] to be entered. Typically, Hostname can be left empty and ZN-Server unhooked.\\
-{{:znf:znf-controller.png?400|}}
+{{:znf:znfdlg-en.png}}\\
 ==== Step 2: Identify blocks with train movements and enter ZNF tracking details ====
 Tracking should be enabled whereever trains move. Note that shunting operations do not need to be tracked. Siding tracks and blocks that are designated for shunting purposes only do not need to be tracked.\\
-In each [[:block-details-en|block definition]], go to the //wiring// tab and enter values for the //CTC interfaceID / display nr / text//. This enables publishing of train movements as such to the "display" ZNF. Just think of the ZNF of a big CTC table with a lot of train number fields.\\
+In each [[:block-details-en|block definition]], go to the //tracking// tab and enter values for the //CTC interfaceID / display nr / text//. This enables publishing of train movements as such to the "display" ZNF. Just think of the ZNF of a big CTC table with a lot of train number fields.\\
 The values in the //Tracking// box define the adress of that display field. Enter an unique trackingID for each block. The trackingID is composed of the own substation number followed by the 5 digit track number with leading zeros. Track 1 in the substation 96 would hence get the trackingID 9600001.\\
-{{:znf:znf-block-details-wiring-de.png?400|}}\\
+{{:znf:znf-blockproperties-trackingid-en.png?400}}\\
 **repeat entering details for every block!**
 ==== Step 3: Identify transfer blocks and enter transferID ====
 The transfer blocks lie on the very border of your interlocking district. A transfer block is usually a stretch of branch line connecting two stations. These stretches are modelled in both adjacent interlocking systems, on each side with it's own trackingID. Trains present in a transfer block are hence visible in both stations and are usually being handed over from one district to another. To enable the handover, you just have to enter the trackingID of your neighbours block into the transferID of your block.
-So if the neighbour had the substation number 98 and the branch line was called 0400 on his system, you enter 980400 into the transferID of your transfer block.\\
+So if the neighbour had the substation number 30 and the branch line was called 0100 on his system, you enter 300100 into the transferID of your transfer block.\\
 As layouts change from FREMO-meeting to meeting and hence the neighbours change, you will have to adjust the transferID in preparation of the meeting. Note that it's possible to agree on one single ID for that block. In this case, the ID needs to be entered both in trackingID and transferID the same.\\
-{{:znf:znf-block-wiriging-transferid-de.png?400|}}\\
+{{:znf:znf-blockproperties-trackingid-en.png?400|}}\\
 **make sure to enter transferIDs in all of your transfer blocks**
 Transfer blocks are the only blocks that execute RR actions in response for a ZNF telegram. In example, a loco will be (created and) set in transfer block with a 02 type telegram arriving for that block. To avoid interference, resulting actions are blocked if the block is allready occupied with a loco that has targets and a route set (running in automode).
@@ Line 298: / Line 306: @@
-=====Proposed additional wiki changes====
+=====Offer, Accept/Reject via ZNF=====
-<del>[[:controllers-en|Supported Command Stations]]: add ZNF controller\\</del>
-  * **Note:** ZNF is as **[[:english#protocol|Protocol library]]** defined.
+On a single-track line, the dispatchers of two neighboring stations A-station and B-station must agree on who may release a train onto the line next.
-[[:block-details-en|Details]]: add ZNF in the display description
+ZNF can be used for this.
+A train 4711 is standing in block A-station. In the block context menu there is now the option Tracking » offer via and all transfer blocks of the plan are available for selection.
+We select A-line and in the offer field of the neighbor B-station the train number is shown blinking.
+The neighbor B-station can now accept or reject. In case of acceptance the line block is reserved and the train can depart. If the neighbor rejects, this is displayed in the offer text field.
+If the neighbor in B-station offers us a train, it appears in the offer text field.
+In addition, the number is shown in white in the block.
+Via the context menu of the line block the train can then be accepted or rejected.