LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Find available COM ports

Hello

 

I have a labview program made by a colleague who has found a new job, but after changing production computer (win10 to win11) no COM ports are found.

The device is a Virtual Com Port and has an FTDI chip. FTDI chip drivers are installed. 

 

I see that it find the COM port but then it checks "SYSTEM\ControlSet001\Control\COM Name Arbiter\Devices" in the registry and there is nothing saved there. And it then returns -603.

I have found a fix by inverting the error and starting the labview program (inHouseTest.exe) in administrator mode. 

 

But why is this?

0 Kudos
Message 1 of 10
(363 Views)

I would just use the VISA Find Resource and it will just return the available VISA resources.  You can apply a filter to the search to make it only the COM ports that show up.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 2 of 10
(316 Views)

Yeah I know.

 

But why did it work before on the old computer and have stopped working now? Both on the old and the new production computer. 

And it works on my computer but not on the production computers. 

 

I guess it has something to do with the registry SYSTEM\ControlSet001\Control\COM Name Arbiter\Devices beeing empty at the prooduction computers.

0 Kudos
Message 3 of 10
(264 Views)

Microsoft has never been particularly concerned about compatibility.

0 Kudos
Message 4 of 10
(241 Views)

Can you get to the COM port using a regular terminal program (like Termite or TeraTerm)?

 

It sounds like your FTDI drivers are not actually installed correctly, or perhaps you didn't get NI VISA installed correctly.

0 Kudos
Message 5 of 10
(224 Views)

Yes i can open the COM port in realterm.

 

FTDI drivers are installed twice. (Did not find a way to remove them)

And have tried a repair of NI VISA.

0 Kudos
Message 6 of 10
(203 Views)

Do you have another control set in the registry? Is SYSTEM\CurrentControlSet\Control\COM Name Arbiter\Devices also empty?

0 Kudos
Message 7 of 10
(196 Views)

Yes, SYSTEM\CurrentControlSet\Control\COM Name Arbiter\Devices is also empty on my production computers.

 

slarve_0-1718350236256.png

 

 

0 Kudos
Message 8 of 10
(187 Views)

I think you are best off just ignoring the registry.  Even Microsoft says you should avoid using it.  Just use the Find VISA Resource like I showed above and you will know what ports are available regardless of where things may be stored in the registry.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 9 of 10
(167 Views)

It works fine with my fix for one program but another labview program has some vi's lacking so I can't build it again. 

It's not used that often but would be nice to have that working as well.

 

That would probably involve editing the registry or installing some drivers. 

0 Kudos
Message 10 of 10
(161 Views)