LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

System Exec

Solved!
Go to solution

I am having trouble with the System Exec.vi in my stand alone application. Here is the scenario:

 

I am using System Exec.vi with a command "devcon find =ports" to find all of the connected COM ports. When I run the program within LabVIEW, I am able to see all of my COM ports. It works great.

 

When I run the application on my computer, it does not error out. No COM ports are returned in the output.

 

I then right-click on the application and select "run as administrator". The program runs and outputs the same COM ports I see when I run the program in LabVIEW.

 

Is there a way to work around this issue? I read into manifest files but was not able to completely understand how to do what it was asking. Even then, did not know if it would fix my problem. Manifests seem to ask the user for admin right access rather than running the program as an admin...

 

Thank you in advance for your help.

CLD Certified 2014
0 Kudos
Message 1 of 9
(3,963 Views)

Hi ADrexel,

 

what about using VISAFindResource to find all COM ports?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 9
(3,958 Views)
Hi GerdW,
When using VISAFindResource, I cannot see the type of connection i.e. rs232 to usb adapter manufacturer to identify the correct connection.
CLD Certified 2014
0 Kudos
Message 3 of 9
(3,954 Views)

What chipset?  ftdi, SiLabs or prolific?

 

The system API should be able to return the vendor id (VID) for any PnP actually connected.  The System registery keys would be able to get any serenum HKEYs reserved for disconnected VCPs.  Either way System exe.vi is not the best means to get the info you want.... dig just a bit deeper into the OS


"Should be" isn't "Is" -Jay
Message 4 of 9
(3,943 Views)
Prolific.
CLD Certified 2014
0 Kudos
Message 5 of 9
(3,940 Views)

@ADrexelDragon wrote:
Prolific.

Errr

I was afraid of that... thats  the one I have had the least problems with so its idiosyncraties are less known to me.   Try the system hardware API.  The COM ports VID should identify the VCPs that are from Prolific


"Should be" isn't "Is" -Jay
Message 6 of 9
(3,934 Views)
I'll look up system hardware API and try to understand that and report back with any updates. Thank you!
CLD Certified 2014
Message 7 of 9
(3,931 Views)

Hi Jeff,

I am unable to find information regarding this "System API" that you speak of. Is this in the Instrument I/O tab in the palette?capture1.png

 

CLD Certified 2014
0 Kudos
Message 8 of 9
(3,910 Views)
Solution
Accepted by topic author ADrexelDragon

Thank you for your help!

COM_Port_Solution.png

CLD Certified 2014
Message 9 of 9
(3,891 Views)