06-01-2022 06:31 AM
Hi, I have an executable that uses the serial port to connect to an instrument but also GPIB to connect to other intsruments and I am facing the following annoying issue:
I have installed NI-VISA, 488.2 and NI-MAX but also Runtime engine in the deployment machine. GPIB works fine in all cases. But serial port is not working (note that serial ports works via a terminal like PuTTY). When I try to check it via NI-MAX the open test panel returns an error "error opening resource ASRL1::INSTR Labview: (HEX 0xBFFF009E) Visa or code library" which typically means that some driver is missing. Then I moved to repair of NI-VISA which completes with an 1603 error
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9c0SAC&l=en-GR
When I restart the machine the serial port works OK. I can see that both in my executable application but also in NI-MAX "open test panel" which works fine and I can send commands.
If the machine is left turned on then the port is working. If I make a restart (or shutdown) then the serial port is not working (!) and it is needed to make a repair again and then after restart works again!.
I found also another way to make it work without enabling the repair process: I make a "reset configuration settings" in NI-MAX and then after a forced restart the serial port works again!
Any suggestions or ideas ?
BR, Stelios, Greece
06-01-2022 02:48 PM
@stsat wrote:
Hi, I have an executable that uses the serial port to connect to an instrument but also GPIB to connect to other intsruments and I am facing the following annoying issue:
I have installed NI-VISA, 488.2 and NI-MAX but also Runtime engine in the deployment machine. GPIB works fine in all cases. But serial port is not working (note that serial ports works via a terminal like PuTTY). When I try to check it via NI-MAX the open test panel returns an error "error opening resource ASRL1::INSTR Labview: (HEX 0xBFFF009E) Visa or code library" which typically means that some driver is missing. Then I moved to repair of NI-VISA which completes with an 1603 error
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P9c0SAC&l=en-GR
When I restart the machine the serial port works OK. I can see that both in my executable application but also in NI-MAX "open test panel" which works fine and I can send commands.
If the machine is left turned on then the port is working. If I make a restart (or shutdown) then the serial port is not working (!) and it is needed to make a repair again and then after restart works again!.
I found also another way to make it work without enabling the repair process: I make a "reset configuration settings" in NI-MAX and then after a forced restart the serial port works again!
Any suggestions or ideas ?
BR, Stelios, Greece
That error usually means another application most likely Putty has not released COM1 because Putty is still open.
06-02-2022 01:22 AM - edited 06-02-2022 01:36 AM
Hi, thank you for your response but the problem appears when I restart the machine without using PuTTY.
I am trying to solve this by various means, it is strange and annoying....
06-02-2022 08:47 AM
@stsat wrote:
Hi, thank you for your response but the problem appears when I restart the machine without using PuTTY.
I am trying to solve this by various means, it is strange and annoying....
That's not what you wrote in your first post. When I restart the machine the serial port works OK
06-02-2022 09:35 AM
Hi again, thank you for your time.
It is a really strange issue. Please check what I was mentioned above:
"When I restart the machine the serial port works OK. I can see that both in my executable application but also in NI-MAX "open test panel" which works fine and I can send commands.
If the machine is left turned on then the port is working. If I make a restart (or shutdown) then the serial port is not working (!) and it is needed to make a repair again and then after restart works again!.
I found also another way to make it work without enabling the repair process: I make a "reset configuration settings" in NI-MAX and then after a forced restart the serial port works again!"
I am not sure if it is a NI or WIndows issue. I am working on setting another machine using older versions of NI-VISA, 488.2 and Runtime. The executable was made on Labview 2017 and I am using the latest versions of all the above. I am pretty sure that will not solve the issue.
Thanks again,
Stelios
06-02-2022 09:49 AM - edited 06-02-2022 09:50 AM
Again, you are making contradictory statements. It makes NO sense.
How is restarting and make a restart different ????????
06-02-2022 09:55 AM
I work for a company, another colleague has the same issue.
I am describing what is happening which is very strange but is a true problem.
Only a video session would help to see that this actually happens!. If needed I can do it.
BR,
Stelios