Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Communicating with CNC machine via ethernet

Hi everyone.

 

I am trying to communicate with a morisiki CNC machine via Ethernet.

 

I have not attended the Instrument Control course as of yet so may be missing something important.

 

We have a program that runs on one PC, but as soon as we copy that program onto another PC, it no longer works.

 

We think it's related to the .dll files and shared libraries. 

 

Any suggestions on what might be the problem?

0 Kudos
Message 1 of 11
(7,123 Views)
What dll and what shared libraries? What programming language? If you are using LabVIEW, what functions are you calling, VISA or tcp/ip? Copying an exe is never a good idea. You should create an installer.
Message 2 of 11
(7,118 Views)

fwlib32 is the dll file we are using. The shared library is also called fwlib32 and is derived from the dll and header file.

 

Didn't use any programming languages except LabVIEW.

 

Not sure regarding VISA vs TCP/IP. How do I find out?

 

We didnt use an EXE or installer, we wanted the raw labview files copied across so did a "save as" with all dependencies included.

0 Kudos
Message 3 of 11
(7,114 Views)
So you aren't using the built-in LabVIEW functions at all. Did you copy the dll over? Is it in the same location? What is the type of dll - c type, ActiveX, .NET? What is your error message?
Message 4 of 11
(7,110 Views)

The way that we imported the .dll files etc was on the main NI project explorer screen, Tools -> Import -> Shared Library

 

When it asks you for a header and .dll file we referenced the .dll files that we purchased from the CNC manufacturer.

 

My understanding is that this imports the relevant files into a shared library on the local machine that all LabVIEW programs can access when they run on that machine.

 

As we have tried to copy across the labview code onto a new PC and tried to reinstall the libraries on that PC, it doesn't seem to work.

 

The error we are getting is -15, which according to the documentation for the CNC machine manufacturer is a missing .dll file

 

How do I determine the type of .dll file?

0 Kudos
Message 5 of 11
(7,085 Views)

@David-Baratheon wrote:

The way that we imported the .dll files etc was on the main NI project explorer screen, Tools -> Import -> Shared Library

 

When it asks you for a header and .dll file we referenced the .dll files that we purchased from the CNC manufacturer.

 

My understanding is that this imports the relevant files into a shared library on the local machine that all LabVIEW programs can access when they run on that machine.

 

As we have tried to copy across the labview code onto a new PC and tried to reinstall the libraries on that PC, it doesn't seem to work.

 

The error we are getting is -15, which according to the documentation for the CNC machine manufacturer is a missing .dll file

 

How do I determine the type of .dll file?


I have no idea what you think you are doing there.

 

Tools -->  Import --> Shared Library is to generate VIs.  

 

http://www.ni.com/white-paper/2818/en/

 

If your LabVIEW program already runs on one PC, you have all the VIs you need. You don't need to be generating more.

 

Most DLLs cannot just be copied. They generally are installed when a program is installed.

 

 

 

 

Message 6 of 11
(7,074 Views)

We did also try manually copying them into the windows -> system32 folder.

 

The .dll files we have didn't come with any installer.

0 Kudos
Message 7 of 11
(7,067 Views)

@David-Baratheon wrote:

We did also try manually copying them into the windows -> system32 folder.

 

The .dll files we have didn't come with any installer.


Are you sure the DLL files were not installed as part of a software package?

 

It is rare for a vendor to just give you a DLL to use.

 

Where is the person who developed the LabVIEW code? Why aren't you asking that person?

0 Kudos
Message 8 of 11
(7,064 Views)

He can't work it out either lol

0 Kudos
Message 9 of 11
(7,058 Views)
You don't have a LabVIEW problem. You have a problem repeating the installation of the vendor's software. Contact the vendor.
0 Kudos
Message 10 of 11
(7,055 Views)