Hi All,
I am trying to achieve sample level triggering between two bladeRF devices (xA4 and xA9). I have made a test set up using a C++ code that closely follows the API documentation for trigger. TX_1 from one of the bladeRF transmits a sinusoid, RX_1 on the same bladeRF acts as master, and, RX_1 of another bladeRF acts as slave. The sinusoid transmitted from TX_1 is connected to the master and slave through a splitter and coaxial cables. J51_1 and GND from both the bladeRFs were connected together, and, the CLKOUT from the master is connected to the CLKIN of the slave with appropriate CLKIN/CLKOUT configurations in software. Init, arming, and firing the trigger are all done as per the documentation, and they seem to be working fine (at least, no errors were thrown). Both master and slave record the samples, so I guess the triggering is happening properly. However, the samples of the sinusoid (of frequency 1 KHz) recorded by the two receivers show considerable shift between them. What could be going wrong here?
Triggering does not work
-
- Posts: 1
- Joined: Thu Nov 07, 2024 1:43 am
- Contact:
Re: Triggering does not work
Check these key points for troubleshooting:
1. Clock Sync: Ensure both devices use the same sampling rate and the slave is set to use the master’s external clock.
2. Trigger Timing: Confirm both devices are properly triggered with minimal delay.
3. Cable Length: Use equal-length cables to avoid propagation delay.
4. Processing Delay: Differences in ADC startup or processing may introduce shifts.
5. Calibration: Measure the delay between devices and adjust in software if needed.
If the issue persists, Nuand support might offer further assistance.
1. Clock Sync: Ensure both devices use the same sampling rate and the slave is set to use the master’s external clock.
2. Trigger Timing: Confirm both devices are properly triggered with minimal delay.
3. Cable Length: Use equal-length cables to avoid propagation delay.
4. Processing Delay: Differences in ADC startup or processing may introduce shifts.
5. Calibration: Measure the delay between devices and adjust in software if needed.
If the issue persists, Nuand support might offer further assistance.