PXI BACKPLANE Resource Does Not Always Persist Trigger Mappings on LabVIEW RTPrimary Software: Driver Software>>NI-VISAPrimary Software Version: 3.1 Primary Software Fixed Version: N/A Secondary Software: LabVIEW Modules>>Real-Time Module Hardware: PXI/CompactPCI>>Chassis>>PXI-1006, PXI/CompactPCI>>Chassis>>PXI-1045
Problem: Does the PXI BACKPLANE resource persist trigger mappings through NI-VISA's viMapTrigger() operation on LabVIEW RT? Solution: On LabVIEW RT, triggers mapped with viMapTrigger() must be unmapped before closing the session, otherwise the behavior is unpredictable. If VISA Server or another process using the PXI Passport is open, the mappings will be kept around and can be unmapped later, but if the session doing the mapping is the only client of the PXI Passport, the Passport will unload when that client closes the session, and the mappings will be lost (unmapped). Because information about other clients using the PXI Passport under LabVIEW RT is not readily exposed, the recommended solution is to keep your VISA session open during the time you need trigger mappings, and to then unmap those routings when you are ready to close the VISA session. Related Links: Attachments:
Report Date: 06/28/2004 Last Updated: 07/04/2004 Document ID: 3738NKF7 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
