routing a RTSI signal to a connector

[Benoit_Provost]

I am using the "Multi Board Synchronization" example VI and modifying it to simultaneously generate data from a PXI6533 and acquire with a PXI6534, both synchronized from the internal clock of the master (the 6534) through the RTSI. I need to get the clock signal to also synchronize my test board. Is there a way to output the clock signal to a connector? I read that the "REQ" pin on the 653X generates one pulse for every new data on the port, but after acquiring it on a scope, I saw that the pulse is not clean. It toggles twice while the port stabilizes. If I send this directly to my board, it will latch corrupted data. I need a clean edge when new port data is stable.
Thank you for your help.

[bman]

Benoit

Does this only happen when you are trying to synchronize two boards together with RTSI, or does it happen when you just use one board by itself. Try to narrow down where these extra pulses are coming from. Use the highlight execution function in LabVIEW while you look at the REQ line with the scope. Knowing what vi is causing this may help me figure out why it is occuring.

Brian

[Benoit_Provost]

Thank you for the reply. I tried a simple continuous generation VI with the 6534 and I have the same problem. I am using a mixed-signal scope to view the digital data. I then monitored the REQ pin with an analog channel. It seems that the pulse is too fast. It has a lot of ringing and lasts for only about 50ns when a 1KHz sampling rate is selected. It lasts longer for slower clock rate, but since I would like to use a clock of at least 1MHz, this is not a solution. I checked the pulse on a 500MHz scope, so it should not be a scope/probe problem. Could it be that the connector (a SH68-68 cable and a TBX-68 screw box) cannot transmit such short pulses? Is there a way to make the pulses longer?