MKS FTIR Error Code 37: Device not found

[LabViewer1]

Hi,

I recently got the same error as was discussed here http://forums.ni.com/t5/LabVIEW/Errors-37-and-42/td-p/1835683 while using a MKS FTIR (MultiGas 2030). Error code 37 LABview: Device not found. The device has been working for years and there have been no changes but I now get this meesage when I try to start it up. The laser voltage. Does anyone have any experience with this error particularily when using the same device?

The device communicates via ethernet connection. I am using Labview 7.1.

Thanks.

[SeaSick]

LabViewer1,

Have you tried the steps discussed in the Knowledge Based linked in the forum post you referenced?

Are you able to communicate with the device in any other way? Are you able to see the device in the Windows Device Manager? 

Has anything changed with the set up since the device was able to communicate?

Any additional information about how your device is set up will be helpful in finding the cause of the error. 

Regards

[LabViewer1]

SeaSick,

The steps appear to be for parallel port connected devices while I am using an ethernet connection. The network exits in the network and sharing centre and when I try to connect bytes are sent and received in the networks status window.

Regards,

[SeaSick]

LabViewer1,

Can you test to see if the device can communicate via TCP/IP? Try running a simple TCP/IP example to communicate with the device.

If you haven't changed the LabVIEW code since the device was able to communicate it leads me to believe that it is a communication problem with the network or the device, not the architecture of the LabVIEW code. 

If you can communicate via TCP/IP it will help us narrow down what changed to cause this error. 

Regards

[LabViewer1]

Hi Carli,

Yes, the device can communicate via TCP/IP. A ping of the device's IP address was successful. The supplier has informed that it is likely that the device needs a replacement part. I tried this forum because my device did not exhibit the signs I was told are normally associated with that problem and the error message seemed to be refering to a communication issue. Seeing that someone had the same error message on this forum, I thought I should confirm that the replacement part is what worked for them

Thank you for your help but if the original poster is not available then I think my best bet would be to just follow the supplier's advice.

Thanks,

[MKSGPS]

Hello everyone,

I am a senior field service engineer for MKS instruments - the maker of the Multigas 2030 being discussed here. Forgive me for being so late to the party, but I've just stumbled onto this thread completly by accident as a result of an unrelated internet search. I just joined this forum for the express purpose of responding to this thread. First of all - I am NOT a Labview expert, in fact I know little about it. I am however, an expert on the Multigas.  

The fault you are getting simply indicates that the Labview based software "MG2000" can not communicate with the Multigas. This may be for an assortment of reasons:

-Bad Calbles

-Failure to set your PC IP address correctly

-The Multigas itself may have stopped functioning.

If you have been happily using your Multigas for quite a while, and have suddenly started getting this error, by far the most common reason would be that the laser onboard the instrument has reached its end of life and stopped functioning. The laser has an average lifespan of about 2 years. When it dies, the instrument stops running and so will not communicate with your PC or software, and you receive this error.

I recommend that you either contact our Field Service group to arrange for the laser replacement at your facility, or contact our factory to arrange to have it sent to us for service. Should you want it serviced at your facility, please feel free to contact me at Matt_Bellemare@mksinst.com or visit our website to arrange for its return at mksinst.com.

I hope that this help!