Labview 2011 32-bit, Tescom ER3000, Windows 7 64-bit

[apatel225]

I currently have Labview 2011 32-bit installed on a Windows 7- 64-bit machine.  I am trying to run the VIs found in the attachment below, but I get the error that function called in the DLL  has failed and that TESCOM.DLL may be in use.  Any thoughts as to why this is happening?  I've already checked to make sure the path referenced in the VIs' function call nodes is correct...  any and all help is appreciated!!

~Avi

[NateTheGreat]

Have you tried turning it off and on again?

As in the TESCOM ER3000 sensor?

You probably are trying to use a dll already in use somewhere else in your machine. I don't think this is lv's problem.

[apatel225]

I have tried turning it on and off, and it does not seem to fix the problem.  The weird part is that if I use the Tescom program to control the ER3000, it works fine.  I'll close the Tescom program, then open up the VI and then I get the error I described above.  I've even tried restarting the computer, then running the VI without opening the ER3000 program, and it still doesn't work.

[NateTheGreat]

Open task manager (ctrl+shift+esc). I bet you the Tescom program is running in the background.

[apatel225]

Nothing from Tescom is running. 

[smercurio_fc]

The problem is that whoever created those VIs hard-coded the location of the DLL. The CLFNs have the location of the DLL hard-coded to C:\Windows. THIS IS BAD. Or at least, not the right way it should be done. If the DLL comes from sort of installation then it may reside in Windows\system32. Or, the DLL could be one that you place in the same folder as your application. Either way, the CLFN path should say just "tescom.dll".

[apatel225]

Changing the path in the CFLN did not seem to solve the problem.  However,  I tried replacing the TESCOM.DLL with another copy, thinking it possibly may have been corrup or something, and Windows gave me an error saying I couldn't delete the DLL because it was in use by Labview.  I had the Startup VI open, but not running while this happened.  Once I closed the VI, I was able to overwrite the DLL.  Seems as though if the VI is referencing the DLL, it accesses the DLL, and thus does not let the VI use it when you go to run the VI.... this is kind of confusing.... any thoughts?

[apatel225]

another thing to note is that the shutdown VI works fine, no errors, however, the others give me the DLL error...

[Simon-P]

Greetings;

I have been reading up a bit on the company and the DLL itself, and are we sure it is supposed to work well with Win7? Would it be possible to try booting up LabVIEW in compatibility mode (XP) to try it out?

http://www.documentation.emersonprocess.com/groups/public/documents/data_sheets/der301767x012.pdf

Only mentions up to XP, hence the question.

[sigaman]

Thanks for the reply!  When speaking to their customer support, they were unable to provide much information as far as windows 7 support.  They  mentioned that they are currently developing a replacement for the product that works with 64-bit OS and further development/support on the ER3000 was unavailable.  How do I boot LabVIEW in compatibility mode?  I was not aware that this existed.  Thanks!