04-14-2023 02:35 AM
For this expression "ASRL[0-9]*::?*INSTR" also the list is empty in exe.
04-14-2023 03:36 AM
Just drop a VISA resource on the front panel and use its properties instead.
04-14-2023 04:01 AM - edited 04-14-2023 04:03 AM
I had used the visa resource name, it has com ports in drop down in development vi, but in exe the drop down is empty.
Fig1. Development VI
Fig 2. Filtering property
Fig 3. EXE (No com ports in drop down)
04-14-2023 04:10 AM
Could it be that you are using the Exe on a virtual machine and the Development vi on your standard session ?
Strange that you cannot see a port in Exe when working on development, moreover COM 1 is (most of time) a RS232 port so it is always there.
04-14-2023 04:54 AM
Both exe and vi are in the same computer
04-14-2023 06:58 AM
What if you run the exe as administrator?
Have you tried to change the search mode for VISA Find ?
04-14-2023 08:49 AM
The issue is resolved after the antivirus firewall security was disabled, now the exe is able to find the com port. Thanks all for helping me out.
04-14-2023 08:55 AM
@sabah_TASL wrote:
The issue is resolved after the antivirus firewall security was disabled, now the exe is able to find the com port. Thanks all for helping me out.
And thanks for coming back and telling us what the solution was. Undoubtedly someone will find this very useful one day.
04-14-2023 10:37 AM
It was my belief that COM ports (Serial) are exemption when it comes to antivirus restrictions, good to know one more troubleshooting technique.
But still how did it was allowing when run from development system? (Application was allowed in exemption list !!!?)
04-14-2023 11:12 AM
I think the enterprise antivirus system is more cautious whenever a exe is run.