Counter/Timer

cancel
Showing results for 
Search instead for 
Did you mean: 

How to route a signal to another board through a RTIS bus?

I've used a counter's source to route the PFI8 to RTIS0, the counter of another board use RTIS0 as the source. But I cann't find the signal.What's happened?
The boards are PCI-MIO-16E-4 and PCI-6602.Thanks first!
0 Kudos
Message 1 of 8
(4,093 Views)
Hi,

To Route To RTSI:
To program this operation you would use a Route Signal.vi (LabVIEW) or Select_Signal() in NI-DAQ function calls. You would select your GPCTR 0 Source as the "source signal" and your RTSI 0 as the "signal name" or destination. The NI-DAQ Reference Manual would have the constant names for these.

To Read From RTSI:
To reference RTSI 0 you would use GPCTR_Change_Parameter in NI-DAQ function calls or a Counter Set Attribute.vi. Some of the shipping examples make use of these functions.

That would be all the programming you would need. Another thing to make sure of is that you have a RTSI cable connecting the two boards inside the computer. I wasn't sure if you had this or not from your post.

To debug this type of application,
I would first get a counter working with an external source on PFI8. Once that is working I would route it to RTSI. I would also make sure the second counter works using an external signal. If it does, then I would change it's source to use the RTSI signal.

Hope that helps.

Ron
0 Kudos
Message 2 of 8
(4,093 Views)
I've test your answer, and found that my real pulses (random TTL level) cann't be routed from PCI-MIO-16E-4 to PCI-6602 by RTIS bus, but the simulative pulses from PCI-6602 can be routed. I read the specifications, but cann't explain it. It's strange.
0 Kudos
Message 3 of 8
(4,093 Views)
Hi,

I was able to route from my PCI-MIO-16E-4 to my PCI-6602. I have the exact same setup. Check my code.

Ron
0 Kudos
Message 4 of 8
(4,093 Views)
This has no problem. But my question is why the real pulses (TTL) can not be routed from PCI-MIO-16E-4 to PCI-6602 and the pulse train from PCI-6602 can. I've tested that the real pulses(TTL) can be counted by PCI-6602, but can not by PCI-MIO-16E-4. However the specifications don't explain this. Thank you very much!
0 Kudos
Message 5 of 8
(4,093 Views)
Hello,

What do you mean the "real" pulses?

The pulse train generated by the counter then routed to the AO Update clock and then to the RTSI is a real TTL pulse train.

Are you talking about it being a direct path to the RTSI bus? You are correct in this case, but if you are not using your analog output on your DAQ board then it won't make a difference if it is direct or indirect. Anyway, have a good day.

Ron
0 Kudos
Message 6 of 8
(4,093 Views)
I used the counter source on PCI-MIO-16E-4 to route the signal ( from single-channel analyzer, random TTL pluse train ) to RTSI bus, it failed. But the pulse train(TTL) generated by PCI-6602 can be routed, even the frequency is 100000Hz and the duty cycle is 0.01. And I said before, real pulse(TTL) can be counted (just used count edges examples) by PCI-6602, but can not be counted by PCI-MIO-16E-4. So I think it's the counter's problem.
Thank you very much!
0 Kudos
Message 7 of 8
(4,093 Views)
Hello,

Help me understand what you are trying to accomplish.

You are trying to generate a square wave from a counter on your PCI-MIO-16E-4 and are trying to route this pulse train to the RTSI bus. You try to read this pulse train on the PCI-6602 but can not. Is this correct?

In the reverse case, when you generate a pulse train from the PCI-6602 you can route it to the RTSI bus and you can read it and count it using the PCI-MIO-16E-4. Is this correct?

Let me know exactly what signals are generated and being routed and I could help determine a way to get things to work. From my perspective, I am able to route from both my counters on my PCI-MIO-16E-4 to the RTSI bus. Also, what is the "single-channel a
nalyzer, random TTL pulse train" you speak of.

Thanks,

Ron
0 Kudos
Message 8 of 8
(4,093 Views)