IRQL_NOT_LESS_OR_EQUAL Serial Read

[Will_E]

Previously I have been using a USB GPS device with LabVIEW 8.5 with excellent results.  Now, I have another project that requires a GPS input, and I tried to use the same GPS unit and drivers.  Now, with LabVIEW 8.6, within five minutes, my computer will lock up, screen frozen, no mouse movement, and CTRL-ALT-DEL doesn’t even work, or I will get the blue screen of death and the message IRQL_NOT_LESS_OR EQUAL. 

 

I have tried installing LabVIEW 8.6.1 and its device drivers along with version 9.0.  All have the same results.

 

The USB GPS is a Pharos GPS-500, and the USB to Serial driver is the Prolific 2.0.0.18.

 

Looking for suggestions.

[Sammy Z]

Hi Will_E,

A corruption may have been caused during installation of your NI software. I would suggest doing a repair of all NI software on your machine, or a full re-install.

Why are you using a USB to Serial adaptor? Does you PC not have a USB port?

By version 9.0, did you mean LabVIEW 2009?  What driver versions do you have installed for NI-VISA?

Regards,

Sammy Z.

[Mathan]

Also see here

[Will_E]

Currently running NI-VISA 4.1 (LabVIEW 8.6) and 4.5.1 (LAbVIEW 9.0.0) on the two machines I have here.  The one that is working, LabVIEW 8.5 is at another location, so not sure what version that is, will get it later. 

 

I have followed and tried all of the suggestions in the multiple threads on the IRQL_NOT_LESS_OR_EQUAL topic, all to no solution.

[Will_E]

Some clearification.  The Pharos GPS device is a serial device that has a serial to USB adapter built in.  So, we use the Prolific driver to allow us to read this via the LabVIEW VISA Serial Read.   I attached a picture so this might help you see why it is a Serial to USB conversion.

When this is working, it is great.  Latitude, Longitude, time, altitude, speed are all easily readable.

[Dennis_Knutson]

You've confused things by starting two threads on the same subject.

Have you tried using Hyperterminal to communicate? Have you tried a different driver for the USB-RS232 converter?

[Will_E]

I didn't feel that this was a duplicate thread because the problem is of a different nature, similar fault, but situation was different.   I have also tried all of the suggested solutions in the other threads with no help.

Also, the comment about it being a bad load of LabVIEW, where I have loaded this on multiple machines, different versions of LabVIEW, and anything after version 8.5 is showing this problem, I don't think that it is a bad load of software.  I have even gone as far as a total delation of LabVIEW prior to the reload to see if that helped, which it didn't. 

I have tried multiple versions of the Serial to USB converter driver.  They work great with other programs, but LabVIEW does not like them.  All has caused this error.

The version of NI VISA (from LabVIEW 8.5) that works is version 4.2.  Something changed in the later versions that is causing this problem.  When I get back home I am going to try and install this version of NI VISA on a later version of LabVIEW and see what happens.

[JasonSmith]

Is this on the same machine as the other thread? Is this the same application, or does this application use only the GPS? 

A complete lockup of the machine as you are describing is generally due to a problem with a device driver and not an application such as LabVIEW. It could be that with the new version of LabVIEW, or some other change in this machine compared to others, the timing of the calls into the driver change so that you are happening to hit a flaw somewhere.

Does your GPS unit have to be used over USB, or is there an option to use it directly over serial? If you can use a serial port directly I would recommend that you connect it to the built-in serial port of your computer, to see if you still encounter problems. If this USB adapter is the only hardware you are using in this application, then it seems most likely related to the Prolific driver, although it is impossible to determine that without further debugging. Just as in the other thread, crash dumps can help to identify the problem. If other hardware is involved, you should try to reduce the scope of the hardware used in order to narrow down the possible sources of the failure.

-Jason S. 

[JasonSmith]

---

Will_E wrote:

The USB GPS is a Pharos GPS-500, and the USB to Serial driver is the Prolific 2.0.0.18.

---

You should check to see if there is a newer driver available. I don't know exactly which Prolific chip is used, but if it is this one, the current version is 2.0.9.122. I don't know whether the driver from Prolific will work directly, or if you will have to receive it through Pharos.

 -Jason S. 

[Will_E]

What has puzzled me is that this has work perfectly with LabVIEW 8.5, anything after that, it has this problem.  So something has changed in the newer versions of LabVIEW. 

 

The program I am running is just the GPS receiver.  I had hoped to imbed this in other applications to database the GPS information.

 

I have also tried the multiple versions of the Prolific driver including the most current and have had no success. 

 

Thanks for your inputs.