The following measurements were performed using the complete CONV-TTL system, meaning that a CONV-TTL-RS485 was used as well as a front-module.
Complete CONV-TTL signal chain
In this setup, a TTL pulse is fed into Channel 1 input of the CONV-TTL-RS485, converted to optical and delivered to a fiber on output 1 of CONV-RS485-OPT-RTM.
Scope channel 1 (yellow) is also receiving the TTL pulse from the source.
Through a short fiber, Channel 1 output of CONV-RS485-OPT-RTM is looped back to Channel 2 input of CONV-RS485-OPT-RTM.
Scope channel 2 (green) is connected to Channel 2 output of CONV-TTL-RS485.
Latency μ (Avg) | 229ns |
Latency σ (S-dev) | 72ps |
Longer Term Statistics
Using the same setup as in the "Complete CONV-TTL signal chain" case above, a different scope was used to gather longer term statistics.
Latency μ (Avg) | 230ns |
Latency σ (S-dev) | 87ps |
Comparison with previous pulse distribution system
In this setup, we test the previous pulse distribution system, based on CTDAB and CTDPR.
Scope channel 1 (yellow) is receiving the TTL pulse from the source.
Scope channel 2 (green) is connected to a TTL output of the CTDPR.
Latency μ (Avg) | 27ns |
Latency σ (S-dev) | 25ps |
CONV-TTL TX received by CTDPR
In this setup, the TTL pulse is converted to optical by CONV-TTL and then it is delivered to a legacy CTDPR.
Scope channel 1 (yellow) is receiving the TTL pulse from the source.
Scope channel 2 (green) is connected to a TTL output of the CTDPR.
Latency μ (Avg) | 140ns |
Latency σ (S-dev) | 67ps |
CTDAB received by CONV-TTL RX
In this setup, the TTL pulse is converted to optical by a legacy CTDAB and then it is delivered to CONV-TTL.
Scope channel 1 (yellow) is receiving the TTL pulse from the source.
Scope channel 2 (green) is connected to the TTL output of the CONV-TTL-RS485.
Latency μ (Avg) | 132ns |
Latency σ (S-dev) | 50ps |