Routing Counter Outputs Need to be Called by Their Internal NamesHardware: Counter/Timers (TIO)>>Devices>>PCI-6602
Problem: I am using several counter outputs to time another board (both PCI-6602 boards). When I try to route them out, calling them by their PFI line, I get an error stating that the route is unable to be satisfied. What can I do to get around this? Solution: Each physical pin is co-listed with several other names for that pin, each depending on what type of operation you are performing. In most cases where you want to route multiple lines you need to call each by its name in Measurement and Automation Explorer (MAX). Navigate to the following in MAX:
Here is an example function from CVI that connects a pfi line (Counter 0 Output) to a RTSI Synchronization Pin. Using PFI (which stands for "Programmable Function Interface") would be counterintuitive in this case since this is routing the line for output: INCORRECT: DAQmxConnectTerms ("/Dev3/PFI36", "/Dev3/RTSI0", DAQmx_Val_DoNotInvertPolarity); Instead of Calling the Counter 0 Output by its PFI number, we should call it by its internal name given in MAX: CORRECT: DAQmxConnectTerms ("/Dev3/Ctr0InternalOutput", "/Dev3/RTSI0", DAQmx_Val_DoNotInvertPolarity); Related Links: KnowledgeBase[1LK9SPX4]: How Do I Configure the PFI Lines on the PCI-6602 for Digital I/O? KnowledgeBase[2WF52B8E]: Why Does Start Trigger Not Work When Routed From a RTSI Line? Attachments:
Report Date: 10/19/2004 Last Updated: 11/12/2004 Document ID: 3EI98GZ6 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
