Bluetooth confuses VISA Find Resource

[wired]

Chris,

I think I see the problem now.  I added some code to display more information returned by VISA VIs.  I was trying to get descriptive information for each of the resources I found, and apparently the Interface Description property provides incorrect results.  I did load the NI-VISA 3.5 with latest MAX as you requested.  Attached is the visaconf.ini file you requested, as well as some screen shots of the Max device list and the vi front panel and block diagram that I am using to process the VISA resource list.  Let me know what you think.

[wired]

Additional attachments showing VISA resource processing.

[GPIB_Guru]

Your VI does not have error clusters connected between the VISA open and the get property. I can almost guarantee you that your VISA open is failing for your strange ports, but that you are still wiring in the output refnum into the VISA property node. VISA open will fail if it cannot open the hardware (i.e., if the comm port is in use since comm ports and only be opened by one entity at a time).

If the VISA Property node is invoked with a successful status (default value to Error IN), but an invalid handle, it will not reinitialize the outgoing wire for the property (not certain if that is a bug or not, but it does appear to be the behavior on my system), so you get stale data. If you wire in the error cluster with a failed status, you will get an empty string on the output.

[wired]

Good call.  I assumed that if I got a valid VISA resource from the resoource list, that I would at least be able to get its description.  Guess I should know what happens when I assume something...