topic Rif.: Executable file didn't work with multiple devices communicate using serial port in LabVIEW

Executable file didn't work with multiple devices communicate using serial port

hw23 — Sat, 13 Aug 2022 03:17:28 GMT

I wrote a program to communicate with several devices using RS485 protocol. The VI works, I can read-write to each devices as I wanted. However, when I build it up to executable, apparently, none of RS485 devices have communications. I wrote another VI to control one of devices, and both VI and executables are OK. It looks like the executables are unable to control multiple RS485 devices, but why?

I tried to install VISA run time engine, didn't solve the problem. Attached is VI that tests all devices and VI that tests only one devices.

Urgent, please help.

Thanks!

d 回复： Executable file didn't work with multiple devices communicate using serial port

hw23 — Sat, 13 Aug 2022 03:24:12 GMT

Both VI and executable are tested on same computer.

Rif.: Executable file didn't work with multiple devices communicate using serial port

andcadev — Sat, 13 Aug 2022 10:21:49 GMT

In your EXE, is the VISA Resource drop down list populated? I mean, can you see the list of available COMs?

Moreover, your first loop (the loop you use to wait the user to click Start) doesn't have a time control. You should use a Wait function.

Finally, put some debug indicator in order to understand if your code stucks in some points.

Rif.: Executable file didn't work with multiple devices communicate using serial port

santo_13 — Sat, 13 Aug 2022 13:13:34 GMT

Do you mean both applications fight for the same serial port for different devices on that serial port?

Re: Executable file didn't work with multiple devices communicate using serial port

RTSLVU — Sun, 14 Aug 2022 01:08:36 GMT

Besides missing a bunch of sub-vi's so we really can't troubleshoot it. That code architecture is so bad, the fact that it works at all in all surprises me. You have flat sequences inside of flat sequences and even a stacked sequence inside of a flat sequence inside of a flat sequence...

You need to go through some tutorials and understand what they mean by Data Flow programming.

But in general multiple devices on an RS-485 bus is nothing special unless it uses some other communication protocol like Modbus.

Rif.: Executable file didn't work with multiple devices communicate using serial port

hw23 — Sun, 14 Aug 2022 04:17:17 GMT

I have dropdown list, so call the COMs. The VI works fine. It is just the exe. I don't know how to debug exe while it is running, it is not supposed to run with Labview installed.

Re: Executable file didn't work with multiple devices communicate using serial port

hw23 — Sun, 14 Aug 2022 04:26:10 GMT

The sub Vis are based on Modbus. The device sent binaries, and Labview only process ascii.

Anyway, it is just a code to test that my devices are under control work. The VI with multiple devices works but not the exe. It looks like Labview needs to install something for exe to work on multiple devices. I wonder if someone has the experience.

I just heard the multiple device exe works in my friend computer, but we don't know who ever did something extra.

Rif.: Executable file didn't work with multiple devices communicate using serial port

hw23 — Sun, 14 Aug 2022 04:35:25 GMT

I think it is sort of like what you guessed. But I have given each of devices a address#, so that they won't fight each other. The weird thing is Vi with multiple devices works, until it has been compiled to exe. Both Vi and exe of single device works. The serial port communication is used modbus to process binary to ascii.

Anyway, a friend has run the multiple device exe in his computer, it works. I wonder, I need to add something to Labview run time engine..... I just installed Visa run time engine, it ididn't solve my problem.

Rif.: Executable file didn't work with multiple devices communicate using serial port

hw23 — Sun, 14 Aug 2022 08:40:11 GMT

Full VI (with sub Vis) are attached.

Rif.: Executable file didn't work with multiple devices communicate using serial port

hw23 — Tue, 16 Aug 2022 10:50:14 GMT

I kind of solved the problem by accident. The executable starts running automatically when you click it. And channeltest.exe looks like stucked somewhere. But when I click stop and terminate the program, and run it with channels has be selected by last run, it works as expected.

I though it might take some time to for the computer to commute to the port, so I add a frame to wait 1min after I click start. I started the program, choose the right port from port list, then click "start", and the computer will wait a minute to process next frame, still, it didn't work. Looks like the exe won't figure out the port no matter what at first run.

Anyone has idea how to click exe file without running it after click?

Rif.: Executable file didn't work with multiple devices communicate using serial port

hw23 — Tue, 16 Aug 2022 11:41:11 GMT

Another solution is to put the port control inside the while frame.

Rif.: Executable file didn't work with multiple devices communicate using serial port

billko — Tue, 16 Aug 2022 18:22:23 GMT

@hw23 wrote:

Another solution is to put the port control inside the while frame.

I am going to strongly recommend that you STOP RIGHT THERE and learn how to program using dataflow. Properly programmed, you probably would never have encountered this issue.

Rif.: Executable file didn't work with multiple devices communicate using serial port

hw23 — Wed, 31 Aug 2022 08:03:57 GMT

Wonder where were you when I first posted the problem? It is alway easy to criticize the other than give advices.

I have posted the problem for quite some time and I beleive alot of people read the codes. Some of nice people gave me advices but didn't figure out why. I really appreciate the advices.

There are many levels of developers, and they are seeking helps to solve their problems.

I am posting my solution trying to help whoever/which level that may encounter the problem I had and save their times.

You are not humble, you are just mean. There are many levels of developers. The worst is the mean level.

Rif.: Executable file didn't work with multiple devices communicate using serial port

GerdW — Wed, 31 Aug 2022 08:21:39 GMT

Hi hw,

@hw23 wrote:

I kind of solved the problem by accident. The executable starts running automatically when you click it. And channeltest.exe looks like stucked somewhere. But when I click stop and terminate the program, and run it with channels has be selected by last run, it works as expected.

…

Anyone has idea how to click exe file without running it after click?

I also recommend to stop and start by learning proper "THINK DATAFLOW!"

Your description sounds like your exe does NOT properly close its frontpanel when you stop it - do you know any other executable that behaves this way?
Your description sounds like your executable has the toolbar (including the Abort and Run button) visible: do you know any other executable with an UI working this way?
Your description sounds like you don't OBEY DATAFLOW when reading the FP controls and so you need to fill the controls with proper values, stop the program and start it again to read their values correctly…
Your description sounds like there is no proper error handling ("stucked somewhere")…

So please: learn to THINK DATAFLOW and implement proper UI handling (next to error handling)!

Rif.: Executable file didn't work with multiple devices communicate using serial port

billko — Wed, 31 Aug 2022 12:55:32 GMT

@hw23 wrote:

Wonder where were you when I first posted the problem? It is alway easy to criticize the other than give advices.

I have posted the problem for quite some time and I beleive alot of people read the codes. Some of nice people gave me advices but didn't figure out why. I really appreciate the advices.

There are many levels of developers, and they are seeking helps to solve their problems.

I am posting my solution trying to help whoever/which level that may encounter the problem I had and save their times.

You are not humble, you are just mean. There are many levels of developers. The worst is the mean level.

I'm not being mean. Sometimes advice hurts, like when the doctor says you are overweight and need to lose x amount of weight. The answer to poor programming isn't to add more poor programming. I felt the need to be abrupt, like an intervention.