Hey there, i will be glad to find someone who could help me solve a problem connected with “remote controlling power supply throw visa”
I have power supply Tektronix PWS4323 and wanna establish remote connection using visa library commands. After connection to a host next stages were finished successfully:
define device by the host
add file device usbtmc
opening session by call viOpenDefaultRM
connection with device viOpen
An the same time requests without reply go on well (like "*RST", "VOLTAGE 3V", "SYSTEM:REMOTE" ....) and finish with the status VI_SUCCESS. Transmissions execute by the command viWrite, and write and read operations to registers end without mistakes.
However command needing reply on a request often finishes with mistake VI_ERROR_TMO (viBufRead or viScanf) Why I write “often” instead of “always”, because sometimes it finishes successfully but I couldn't find clear dependence on such behavior. For example there're exist commands like *ESR?, *TST? Returning a short answer in a few symbols. If i use an additional delay after each operation writing then reading could finish successfully too, but *IDN? always finishes with an error
What could be reason for such behavior. Honestly I have already wasted two weeks and almost give up to find solution.
Additional info:
OS – LINUX, setting a visa library were going through deb packets libivivisa0_7.0.0-0_x86_64.deb, libivivisa0-devel_7.0.0-0_x86_64.deb, libivivisa-confmgr0_7.0.0-0_x86_64.deb, libivivisa-confmgr0_7.0.0-0_x86_64.deb, libivivisa-utilities0_7.0.0-0_x86_64.deb
After the end of connection I have tried set some addition attributes to setup session VI_ATTR_TMO_VALUE, VI_ATTR_TERMCHAR, VI_ATTR_TERMCHAR_EN, VI_ATTR_SEND_END_EN
I have power supply Tektronix PWS4323 and wanna establish remote connection using visa library commands. After connection to a host next stages were finished successfully:
define device by the host
add file device usbtmc
opening session by call viOpenDefaultRM
connection with device viOpen
An the same time requests without reply go on well (like "*RST", "VOLTAGE 3V", "SYSTEM:REMOTE" ....) and finish with the status VI_SUCCESS. Transmissions execute by the command viWrite, and write and read operations to registers end without mistakes.
However command needing reply on a request often finishes with mistake VI_ERROR_TMO (viBufRead or viScanf) Why I write “often” instead of “always”, because sometimes it finishes successfully but I couldn't find clear dependence on such behavior. For example there're exist commands like *ESR?, *TST? Returning a short answer in a few symbols. If i use an additional delay after each operation writing then reading could finish successfully too, but *IDN? always finishes with an error
What could be reason for such behavior. Honestly I have already wasted two weeks and almost give up to find solution.
Additional info:
OS – LINUX, setting a visa library were going through deb packets libivivisa0_7.0.0-0_x86_64.deb, libivivisa0-devel_7.0.0-0_x86_64.deb, libivivisa-confmgr0_7.0.0-0_x86_64.deb, libivivisa-confmgr0_7.0.0-0_x86_64.deb, libivivisa-utilities0_7.0.0-0_x86_64.deb
After the end of connection I have tried set some addition attributes to setup session VI_ATTR_TMO_VALUE, VI_ATTR_TERMCHAR, VI_ATTR_TERMCHAR_EN, VI_ATTR_SEND_END_EN