Time Tagger Network on Swabian Instruments

Accessing the Web Application Server from Another PC

Tue, 20 Aug 2024 00:00:00 +0000

This article relates to the now deprecated Time Tagger Web Application. Please consider using Time Tagger Lab (GUI) for local control of the Time Tagger hardware or Time Tagger Network for remote time tag streaming.

For security reasons, the Time Tagger Web Application server does not allow connections from the network computers; only localhost connections are allowed. The Time Tagger Web Application neither manages access rights nor encrypts the communication. Nevertheless, networking tools like SSH can provide secure access to a remote Time Tagger Web Application server. This requires an SSH server to be set up and run on the machine where you run your Web Application server. The remote clients then establish an SSH tunnel from their PC to the Time Tagger server (listening on the “localhost” of the server PC) and use the Web Application the same way as locally connected.

Difference Between TimeTaggerNetwork and Pyro Control

Tue, 20 Aug 2024 00:00:00 +0000

The Time Tagger software allows you to access the device over the network from one or more clients. Two different approaches are possible (the second one only employing Python):

The TimeTaggerNetwork functionality, that is an integral part of the Time Tagger engine, allows you to send the time-tag stream to remote clients so that each client can process the stream independently. Multiple clients can connect to the server and subscribe to the channels they want to receive the stream. You can choose if the clients can change the hardware settings, like trigger level, deadtime, etc. This is done through server access mode. The direct operation to the time tagger object on the server always provides full access. The Time Tagger network server does not provide more fine-grained access control management. It is the user’s responsibility to distribute channels among the clients and define how they access them.

Scanning for Time Tagger Servers on Different Subnetworks

Tue, 20 Aug 2024 00:00:00 +0000

The function ScanTimeTaggerServers() uses multicast UDP messages to find the server IP addresses. This works within local subnets, but its effectiveness across different subnets depends on whether the specific network routers pass on the multicast requests or not. If the TimeTaggerServer cannot be found by calling ScanTimeTaggerServers(), it is very likely that in the network, multicast routing is not allowed or unreliable. In this case, the only alternative is then to input the server IP address manually in the call createTimeTaggerNetwork() in the client PC.