Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
This Document is not yet Rated  Rate this Document

Motion RTSI Signal Appears on Lines That Are Not Mapped

Hardware: Motion Control>>Controllers>>PCI-7340, Motion Control>>Controllers>>PCI-7350

Problem:
I am routing my encoder signals over the RTSI Bus and using the signals as a DAQ scan clock. I have my DAQ program set to read RTSI 0 as the clock source. If I map my encoder signal to RTSI 0 then the DAQ program works fine. However, if I then map my motion signal to RTSI 1, or any other RTSI line, and then run the programs again, the DAQ program still gets the encoder signal. What is happening?

Solution:
This behavior is caused because the motion signals are not un-mapped when you map them to a second RTSI line. What is happening is that the encoder signal is routed to each successive RTSI line that you define (i.e. RTSI 0 and 1). Therefore, the DAQ program is still receiving those signals on RTSI 0.

If you want to ensure that there are no mappings to a particular RTSI line, complete one for the following steps:
  1. Go to Measurement & Automation Explorer (MAX), expand the motion device and select Synchronization Settings. From here, right click on the white area and select Remove All Routings. This will remove all routings that appear in the MAX window, or
  2. Call the Select Signal.flx VI and select the RTSI line for the Destination input, and 'Don't Drive RTSI Line' for the source input. See the attached image for clarification.
Once un-mapped, the DAQ program should no longer be getting the signal on RTSI 0.

Related Links:
NI Developer Zone: Integration with Motion Using RTSI

Attachments:

 



UnmapRTSI.gif

Report Date: 10/18/2004
Last Updated: 07/28/2007
Document ID: 3EHEJTI3

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit