01-24-2017 12:28 PM
Hi,
I have some trouble with my fresh built application.
The little program uses serial/visa communication to gather data from a device via serial port.
Everything is working well on my development machine: The device is found and the COM port is assigned.
But when building an application and run it on the destination machine the serial device is not found.
So I built an application from the vi which is finding the communication port (e.g. COM4) to my device and it works properly on the desination machine.
Can you help me please.
development computer:
- W7 32bit
- LV 2012 Sp1
- LV Run-Time 2012 SP1
- NI-VISA 5.4
- MAX 5.5
- DAQmx 9.7
destination computer:
- W7 64bit
- LV Run-Time 2012 SP1 32bit
- NI-VISA 16.0
- MAX 16.0
- DAQmx 16.0
Any hint is welcome.
Many Thanks and Best Regards,
Christian
Solved! Go to Solution.
01-24-2017 12:32 PM
My initial guess is that you have the serial port hardcoded and it is the wrong port. Would need to see code in order to provide any additional help.
01-24-2017 12:47 PM
Hi Crossrulz,
thank you much for your reply.
No, the serial port is automaticaly assigned by using VISA-find and sending *IDN? Query in a For Loop. (I attached a picture).
On the development computer the device is found on different serial ports.
I tried a hardcoded version to comunicate to the known serial port (COM4) on the destination computer but this did not work.
Best Regards,
Christian
01-24-2017 02:52 PM
01-25-2017 08:08 AM
Hi guys,
I playd around a bit and noticed that the built application does not find my serial device when running on the development computer, too.
It is working well before the bult
Why can this happen?
Many Thanks,
Christian
01-25-2017 11:19 AM - edited 01-25-2017 11:22 AM
Hi,
when buiding an application from the vi that finds a serial device it works.
when using the same vi as SubVi it does not work after building an application.
Any hint is welcome.
01-26-2017 08:17 AM
Why don't you upgrade / downgrade the VISA and DAQmx drivers on both the machines to be same?
01-26-2017 11:53 AM
Hi grimmy123,
the problem occured on the development computer after building the application.
Enable debugging during application build solved that issue.
Many Thanks,
Christian