how to get access to a serial port after a labview crash?

[thiemaluphagus]

I have been having endless communication and dropped port issues, and it just so happens I have a "Prolific" usb-serial converter!  I'm self taught in labview and everything I know about this issue (little that I do know) I have learned from google and the ni forums.  I know next to nothing about Plug and Play.  Can you recommend a PnP implementation that you have found to be robust?

[RavensFan]

I've used quite a few of the iogear USB serial converters and never had a problem.  I believe they use the FTDI chipset.

http://www.iogear.com/product/GUC232A/

[MarcosBelgo]

Hi, hou did you solve this problem? Thanks

[thiemaluphagus]

I still haven't, sorry.

[jackieflat]

---

falkpl ha scritto:

I had a very bad experience with prolific usb driver, It actually always lead to a blue screen on windows (within a few hours depending on the frequency of the calls to visa).  I looked in the crash log files and chased it down to the prolific driver dll call.  Replaced the usb to serial converter with a different brand and the application is running without anm issue for over a year now.  This was not a Visa or Labview issue but some wierd compatability issue.

---

I'm having the same experience with LabView running on Windows 7. I'm using a prolific USB to RS232 converter and after few hundreds write and read calls, either LabView crashes or the fearing blue screen appears. As a consequence windows needs to be restarted.

Is there anyone else dealing with this issue?

Could someone suggest me another USB to serial converter with no such a drawback?

Thank you.

[GerdW]

Use a converter with a FTDI chipset!

[Minions]

If leaving the port in an unknown state is the issue, then do the following:

1. When opening the port, save the handle/reference into a configuration file.
2. Normally remove the entry when it is closed properly.
3. Now edit your port opening to check if any port handle/reference is still active.

• If one is active at the beginning, close that handle/reference first before trying to open up a new handle/reference.

[JÞB]

---

@jackieflat wrote:

---

falkpl ha scritto:

I had a very bad experience with prolific usb driver, It actually always lead to a blue screen on windows (within a few hours depending on the frequency of the calls to visa).  I looked in the crash log files and chased it down to the prolific driver dll call.  Replaced the usb to serial converter with a different brand and the application is running without anm issue for over a year now.  This was not a Visa or Labview issue but some wierd compatability issue.

---

I'm having the same experience with LabView running on Windows 7. I'm using a prolific USB to RS232 converter and after few hundreds write and read calls, either LabView crashes or the fearing blue screen appears. As a consequence windows needs to be restarted.

Is there anyone else dealing with this issue?

Could someone suggest me another USB to serial converter with no such a drawback?

Thank you.

---

What Version of LabVIEW? What version of VISA?

Are you opening the port more than once? Can you provide a snippet of the crashing code?

[jackieflat]

I'm using LabView Professional 2016. Attached my BD. The SubVI at the beginning just sets the serial port depending on the instrument I need. I veriifed the connection effectively work by using puTTY before developing my LabView application. The VI is very similar to the NI example Continuous Serial Write and Read.vi.

[Minions]

What Mechanical Actions are set for your Write and Read Booleans?  If they are set for any of the switches and possibly the latch when pressed or latch until released, you might be inadvertently overflowing the instrument buffer.  The preferred usage would be to set the mechanical action of those for latch when released.