LABVIEW USB Interfacing with PIC 18F4550 using HID

[CocaCola]

The topic fits. I'm interfacing a PIC 18F4550 to LabView. The PIC side is solved but for LabView I'm  locking for a solution.

Hmm, as suggested multiple times now, did you bother reading the post above your inital post, I suspect not since it has EVERYTHING you are asking for!!!

http://www.sonsivri.to/forum/index.php?topic=26537.msg133404#msg133404

[CocaCola]

I'm again, post #22 uses NI Visa with the disadvantage that everything stops working when the port is changed.

Labview uses NI-Visa by default to communicate it's kind of a package deal, and since NI-Visa is pretty much the de-facto industry standard it's not a bad thing...

[bbarney]

I don't know if I should laugh or cry , but my mute finger is getting awful itchy 

[biomed12]

I wonder, what is the better side of HID over CDC? It is very simple to communicate with labview via serial protocol. I have one project like that. It is about real time chart plotting. Its costumization is not perfect but the protocol works properly.

[motox]

I wonder, what is the better side of HID over CDC? It is very simple to communicate with labview via serial protocol. I have one project like that. It is about real time chart plotting. Its costumization is not perfect but the protocol works properly.

With HID it is much easier to do auto-detect and to auto-run a program or a subprogram when the device is connected.
Forcing the user to open the Device Danager to see the port number, insert that number in a box and click on the ‘open port’ button is not very professional. Imagine that for a ‘normal’ Windows user that doesn’t even know what Device Manager is…

[Gallymimu]

With HID it is much easier to do auto-detect and to auto-run a program or a subprogram when the device is connected.
Forcing the user to open the Device Danager to see the port number, insert that number in a box and click on the ‘open port’ button is not very professional. Imagine that for a ‘normal’ Windows user that doesn’t even know what Device Manager is…

For a "professional" option you can simply detect your serial port automagically.  It's not that hard.  See 3.6 below for an example with FTDI
http://www.ftdichip.com/Support/Documents/AppNotes/AN_123_How%20COM%20Ports_Are%20Allocated%20on%20Driver_Installation.pdf

[motox]

For a "professional" option you can simply detect your serial port automagically.  It's not that hard.  See 3.6 below for an example with FTDI
http://www.ftdichip.com/Support/Documents/AppNotes/AN_123_How%20COM%20Ports_Are%20Allocated%20on%20Driver_Installation.pdf

How do you implement that in LabVIEW without using FTDI chips?

I don't have any doubts about its possibility, but I think it is much easier with HID, WinUSB or a custom driver.

[Martin Miranda]

Moved  & stickyed

Have you looked at the Bitwacker

http://www.schmalzhaus.com/UBW/

THANKS! i think i still have some few 18f2550's around.

Posted on: February 15, 2020, 05:47:49 05:47 - Automerged

With HID it is much easier to do auto-detect and to auto-run a program or a subprogram when the device is connected.
Forcing the user to open the Device Danager to see the port number, insert that number in a box and click on the ‘open port’ button is not very professional. Imagine that for a ‘normal’ Windows user that doesn’t even know what Device Manager is…

i concur.