02-10-2016 10:58 PM
Hi all,
I have a USB device with correct drivers installed that shows up as a COM port with NI VISA. I am having issues with the VISA read function. It appears to be dropping bytes. After thinking it was an issue with my application, I started using the NI basic serial read. The same set of bytes are being dropped.
I know the bytes are there because I have a CVI application that reads the bytes from the same setup (not at the same time). This shows a specific set of bytes not being read by the VISA read function. I have confirmed the bytes are being sent by the device by using a device monitor.
Has anybody had issues with NI VISA dropping bytes from the example program but being fine in CVI and other applications?
I have posted on the LabVIEW board because it appears to be LabVIEW causing the issue rather than CVI.
Many thanks for your help.
02-10-2016 11:08 PM
LabVIEW has been known to have issues with some USB to Serial chipsets, but I can't remember the specifics. 😞
02-11-2016 05:16 AM
I have had issues with one USB-Serial adapter dropping a single byte every few hours or so. It was enough to really throw off collected data. Since that instrument just streamed data constantly, I just detected the missing byte and used the next message when there was an issue.
If memory serves correctly, the USB-Serial adapters that use the real FTDI chipset (not the counterfit) have data the most success with LabVIEW and VISA. This is one of the reasons I plea for my customers to use a PCI(e) card for serial ports.
02-15-2016 10:26 PM
Two questions follow on from your reply,
Assuming this is a hardware issue, is there a safe list or know unsupported hardware list somewhere? My searching the forums have not appeared to have found anything
Does CVI use different different method to read serial devices when using VISA? If this is the case, can LabVIEW access that method some how?
Thanks for taking the time to reply. The net connection where I am can be a bit iffy!
02-15-2016 10:53 PM