From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
02-15-2019 09:30 AM
USB communications gives intermittent error "The resource is valid but VISA cannot currently access it". The main program accesses the same subroutine to communicate with the USB instrument in two places (ptA and ptB). If the Visa Resource Name line is probed, the program interrupts (breaks) only when the subroutine is accessed from ptB. The reason is that the tab marked 'Condition' has both 'Is session valid?' and 'Is Instr' 'stop if not valid' boxes checked, and it reports both as invalid. It does not display anything on the 'general' tab for 'Canonical VISA resource name' when it interrupts the program execution.
I placed an 'Instrument Property Node' and checked the Rsrc Name, Rsrc Class, Intf Type, and Intf Inst Name, and now it is running fine.
Any ideas on why it runs from ptA but not ptB, and from ptB if instrument property node is checked?
02-15-2019 09:40 AM
Additional info:
Added Instrument Property Node reduced the frequency of the error, but the 'resource is valid but VISA cannot currently access it' error still pops up.
02-15-2019 11:54 AM
02-15-2019 01:25 PM
It's a good thought, but the calls are in separate parts of a stacked sequence with flow control using shift registers.
02-15-2019 01:37 PM