Last modified by sndueste on 2024/03/13 14:48
From version 5.1
edited by sendels
on 2019/11/19 08:39
Change comment: deleted link because it pointed to internal site
To version 3.1
edited by sendels
on 2019/08/07 08:40
Change comment: added attachments and links

Summary

Details

Page properties
Content
... ... @@ -26,7 +26,7 @@
26 26  
27 27  Each //pulse train// is identified by an **//Train ID//** (synonyms: **//bunch ID, timestamp//**).
28 28  
29 -Recording this Train ID on the user side allows the correlation of data acquired by the user with all the data saved at FLASH in the DOOCS system, especially with the photon intensity data measured by the GMD system.
29 +Recording this Train ID on the user side allows the correlation of data acquired by the user with all the data saved at FLASH in the DOOCS system, especially with the photon intensity data measured by the [[GMD>>doc:FLASHUSER.Gas Monitor Detector]] system.
30 30  
31 31  Within DOOCS the Train ID is a 32-bit number. For the users it is transmitted via a socket connection over ethernet - TCP socket. The ID is set 20 ms before the train starts and stays 80 ms after the train. To read the Train ID by the user there are 2 options provided by FLASH:
32 32  
... ... @@ -40,7 +40,7 @@
40 40  
41 41  Note: If the central Train ID server crashes it will not resume the ID numbers where it was. In most times it will restart with ID 0, sometimes it is set to some high number by hand. For this reason you will see Train IDs with some high bit not as often as expected.
42 42  
43 -[[Contents>>doc:||anchor="Contents"]]
43 +\\
44 44  
45 45  == Train ID reading with local ID reader (Advanced ID Server) //recommended// ==
46 46  
... ... @@ -107,8 +107,6 @@
107 107  * [[attach:AdvancedIDServer-inline.vi]]: Example how to use the Advanced ID Server with Labview (LV11)
108 108  * [[AdvancedIDServer on github~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://github.com/Finii/AdvancedIDServer||shape="rect"]]
109 109  
110 -[[Contents>>doc:||anchor="Contents"]]
111 -
112 112  == Direct reading of Train ID ==
113 113  
114 114  Receiving the Train ID via ethernet is rather simple. Just open a TCP socket to the one of the servers and read from it.
... ... @@ -149,7 +149,7 @@
149 149  
150 150  The time and date have leading zeros as necessary to ensure a constant field width. The ID number is not zero padded and thus has a varying field width.
151 151  
152 -[[Contents>>doc:||anchor="Contents"]]
150 +\\
153 153  
154 154  == Train ID sender program (TIDS) //obsolete// ==
155 155  
... ... @@ -165,7 +165,7 @@
165 165  
166 166  The TIDY: known issues also apply here.
167 167  
168 -[[Contents>>doc:||anchor="Contents"]]
166 +\\
169 169  
170 170  == Train ID Yelling server (TIDY) ==
171 171  
... ... @@ -197,7 +197,7 @@
197 197  * 20.9.18: The .exe always try [[hasfhvctrl.desy.de>>url:http://hasfhvctrl.desy.de||shape="rect"]] first. So start with additional parameter via the commandline.
198 198  [[attach:AdvancedIDServer.exe]] [[hasfcpuexp2.desy.de>>url:http://hasfcpuexp2.desy.de||shape="rect"]]
199 199  
200 -[[Contents>>doc:||anchor="Contents"]]
198 +\\
201 201  
202 202  == Short presentation by Fini ==
203 203