LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VISA COM Port Communication


@bjoernde wrote:

Thank you all for the fast answers.

 

I wonder why I can use it on the development PC and it‘s shown in the drop down menu. I didn‘t install any drivers on the development PC. I connected the USB with the PC and it worked instantly correct. 
Doesn‘t matter if it‘s the programm directly or a executable.

 

I only can‘t handle COM Ports in general. My thought is there is any setting missing i can attach the exe-file such as „always included“.

 

Or am I completely wrong?


Yes, unfortunately you are completely wrong.   But we can help with that! 😀

 

Let's get the information from your development system first.

Open up the Device manager and show us the property screens for the working COM port.  The Driver details screen would be useful.   It's highly possible that your driver was previously installed by something else on your development machine!  It really only needs to install once and for VCPs is frequently stuck in quietly with other applications. 

 

Your LabVIEW application installer doesn't really know about additional hardware drivers.  However, you can manually include the driver installer exe and configure your installer to run that exe before installing your application in the build specification.


"Should be" isn't "Is" -Jay
0 Kudos
Message 11 of 16
(1,385 Views)

Receiving help from you guys helps a lot as a LV starter!

So there are the follwing steps I have to do:

 

- Read out the drivers properties (and attach them to my next post to show)

- Build a LV installer including the driver of the hardware

- After installing the driver of the hardware the LV installer has to run the exe in created

 

Are these the correct steps? 

 

I didn't work with installers yet. I manually installed the two runtime I needed on the second computer and ran the exe.

I think if the exe runs correctly it's better to create a installer with the LV runtime, the VISA runtime, the hardware driver and the .exe file. So I'll have everything together.

What do you think?

0 Kudos
Message 12 of 16
(1,356 Views)

Sounds like you're understanding perfectly.


"Should be" isn't "Is" -Jay
0 Kudos
Message 13 of 16
(1,347 Views)

Unfortunately the hardware I use isn't available today, but I want to prepare everything. So the screenshot of the hardware driver properties will follow soon.

 

I tried the installer part instantly. 

And I've attached two screenshots. The first question is; did you mean the checkbox "run executable at the end of installation" above?

 

And the second one is; I found the checkbox for "include hardware configuration from MAX". If the used hardware is listed in the NI MAX as communication port, can I choose the hardware driver in this menu to include it to the installer?

0 Kudos
Message 14 of 16
(1,336 Views)

Forgot the screenshot. Here they are.

0 Kudos
Message 15 of 16
(1,335 Views)

Those are the right checkboxes!

Now you just need the virtual COM port installer (.exe)


"Should be" isn't "Is" -Jay
0 Kudos
Message 16 of 16
(1,318 Views)