01-13-2013 11:23 AM
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.
Solved! Go to Solution.
01-13-2013 11:48 AM
01-13-2013 11:54 AM
01-13-2013 01:14 PM - edited 01-13-2013 01:20 PM
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
01-13-2013 01:17 PM
01-13-2013 01:23 PM
@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
01-13-2013 01:27 PM
01-13-2013 03:58 PM
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?
01-13-2013 10:18 PM
Thank you for your help!