RTSI connection to DAQ not working

[denisseg_m]

Hello everyone,

I am trying to trigger my frame grabbers using a trigger signal (pulse) sent to the DAQ card using RTSI cable. I have configured the RTSI cable in NI Max and added the DAQ. Additionally, I can confirm that the signal is being sent to PFI 14 in my DAQ but for some reason it refuses to send it through the RTSI cable. I am attaching the .vi i use to initialize the cameras, the connections I am doing and the .vi where i want to test the camera. I dont have issues when i use Free Run mode, but when I change it to Triggered, it just gives a time out error because of no buffers found. I have changed number of buffers, time that it waits to receive the trigger and every possible thing that I could find online but nothing seems to work. I am using DAQ (PCIe-6353) and the frame grabbers are NI PCIe-1433. The cameras are Basler 140 km 4096. 

I would really appreciate the help as this is extremely urgent to finish my master thesis project and I have really tried everything.

[Kevin_Price]

You say you added the DAQ to the RTSI cable in MAX.  Did you also add the 1433 frame grabber(s)?

Do you have any other DAQ devices you could use to troubleshoot whether the intended RTSI signals actually make it out onto the RTSI bus?

Could you back-save "Initialize Camera.vi" to LV 2019 like the other posted vi's?   That one's still in LV 2025 and I couldn't open it.

-Kevin P 

[denisseg_m]

Hi Kevin,

It doesn't allow me to add any other devices. when I right click on the RTSI cable that has been generated, the only device I can add is the DAQ even though I have the frame grabbers in my NI MAX. I don't have any other devices I could test for that sadly. Here I am attaching the files in V18; let me know if they open properly.

Thank you for helping!

[Kevin_Price]

I can open it but because I don't have IMAQ installed, all the functions are empty ghost icons.  Still, I see a place where you seem to be configuring to use RTSI 0 for something.  I don't see any place where RTSI 1 is used.

I've never used NI's frame grabbers (or even IMAQ in general) so I have no detailed knowledge for configuring them.  Just some general DAQ-related knowledge of RTSI use to sync devices in the same PC.

More troubleshooting ideas:

1. Use one of your DAQ device's other counters to count edges on either RTSI 0 or 1 when you run the counter part of your program.  That will at least confirm *part* of the signal path when you try to export to RTSI.   (I'm pretty sure it'll tap into the RTSI bus *internal* to the card, so this doesn't really confirm whether the signal gets out to the connector and all the way through to the other end.)

2. In case the RTSI cable is partly damaged, try using any/all the other RTSI lines for your frame grabber app. 

3. Is the RTSI cable keyed to guarantee that it's connected in the right orientation?  I'm sure it would be if it's an "official" RTSI cable, but possibly not if it's a generic homemade ribbon cable.

-Kevin P

[denisseg_m]

I have tried in all ports of RTSI without success. And as far as I know the RTSI is from NI but I have also tried to connect them in a different "orientation" and still nothing sadly.

[Kevin_Price]

Have you tried step 1 from my msg #4 -- trying to count edges from RTSI using a different counter from your 6353.  The listed caveats apply, but I think you've done enough to treat the RTSI cable itself as an unlikely suspect.  I suppose you could still open your case, unplug the frame grabber side, and probe into the appropriate pin of the cable end connector.

Unfortunately, I have no experience with NI's frame grabbers and wasn't able to set one up in MAX as a simulated device to explore.  I've gotta believe that RTSI is supported if they bothered to put the connection on the card, I just can't vouch for any of the syntax involved to configure it on the frame grabber side.

-Kevin P

[denisseg_m]

I am not sure I understand but I have tried with all other counter clocks without success.