NI-VISA

[jgent]

Hi Dave

The ports hardware ID are:

COM6
USB\VID_8087&PID_0ADA&REV_0100&MI_00
USB\VID_8087&PID_0ADA&MI_00
COM8
USB\VID_8087&PID_0ADA&REV_0100&MI_02
USB\VID_8087&PID_0ADA&MI_02

and the driver details of the ports are enclosed.

For the device I want to connect:

In Device Manager it is listed under "other devices" the Hardware ID is:

USB\VID_0403&PID_D38B&REV_0600
USB\VID_0403&PID_D38B

and the driver Info can't be found for the Xsense sensor see (attachment).

@Rolf thanks for elaborating

[jgent · Accepted solution]

Thanks all for your suggestions. The driver of my sensors needed to be installed, this solved my issue. However, I still don't understand why there are COM port which I can't access (when I have nothing pluged in). Anyway it works now.

Cheers,

Jeremy

[rolfk]

Ok that starts to make sense. As to the COM port you can't access there are many possibilites. For instance a TPM hardware that hasn't been (fully) activated,or some motherboard resources that Windows recognizes but are actually used by some onboard monitor or whatever. Usually the according System Device Drivers should disable such hidden hardware in the Windows device registry but either they are not properly installed or there is a bug in them. 

VID_8087 is for Intel, so it is most likely indeed some chipset feature that Windows, rightly or not, identifies as a serial port. 

VID_0403 PID_D38B, is the XSens USB Serial Converter, which seems indeed to be a proprietary serial port (not using the standard USB-CDC profile) so yes you need to install the according drivers of course!

If you really want to know why you have phantom serial ports, you have to get the answers from the support people for your computer. But usually tracking them down and getting them to return anything but a standard support response of how happy they are that you contacted technical support, and to please check that you have plugged in your device (only slightly exaggerated), is not worth the trouble for something like this, which is at worst annoying but doesn't prevent you from using the computer.

[DavidBoyd]

It's a rare day when Rolf omits a step in a troubleshooting process, he is very thorough, logical, and methodical.

Rolf, you forgot the part where the IT support people also send you three follow up emails asking you to rate the support you received 😄

Dave

[rolfk]

---

@DavidBoyd wrote:

Rolf, you forgot the part where the IT support people also send you three follow up emails asking you to rate the support you received 😄

---

😁

Well to be fair, it's the automated support system. I still like to think that most real humans would feel too ashamed to do that (or to afraid to get a devastating review 😎 )

[sna_31]

Hello all!!

Following up with error Hex 0xBFFF0072, I have a RS232 port that I called COM2 and that controls two MFC from Bronkhorst. 

When testing, I made an independent VI and it worked without problem.

Now that I am integrating this control to a project lead by a cRIO-9057, I get this error and I cannot even find the COM2 option(that I can find in the independent VI), just the "ASRL 1::INSTR" that keeps giving me error.

I saw a few suggestions (closing everything so the port knows for whom he works, reinstalling VISA, tried on disable the Console out, but for this RIO could not find that option) but I still cannot make it work. I have the notion that there must be some way of telling the cRIO that there is this port guest and he has to let it pass, but I don't know how to make that -__- 

Hope that someone can give me some idea 🙂

[santo_13]

Since this thread has already been solved, please create a new post with your question/concern that you like help with.

[sna_31]

I'll do, thank you for your suggestion!

[RTSLVU]

---

@santo_13 wrote:

Since this thread has already been solved, please create a new post with your question/concern that you like help with.

---

Lots of people think this is a good thing when this happens but I do not.

You could also kudo my suggestion to lock old threads to prevent long solves threads being brought back from the dead...

[billko]

---

@RTSLVU wrote:

---

@santo_13 wrote:

Since this thread has already been solved, please create a new post with your question/concern that you like help with.

---

Lots of people think this is a good thing when this happens but I do not.

You could also kudo my suggestion to lock old threads to prevent long solves threads being brought back from the dead...

---

Not sure what you mean.  What is not a good thing when it happens?  Now we're posting ambiguously.  😄
Did you mean that you don't think it's a good thing to add to a post that's already been solved?  I'm with you 100% on that.