LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

simple labview VI functions correctly, but when built into application the serial comms do not function


@Sholyoake wrote:

given this application is very simple and doesn't use bytes at port or anything else, can folks please suggest why it's not functioning?


Because LabVIEW is still open? Your VI might not have closed the reference and LV might still be claiming the VISA resource...

 

Did you try closing LabVIEW before running the exe?

 

See Re: simple labview VI functions correctly, but when built into application the serial comms do not f...

0 Kudos
Message 11 of 24
(289 Views)

wiebe@CARYA wrote:

@Sholyoake wrote:

given this application is very simple and doesn't use bytes at port or anything else, can folks please suggest why it's not functioning?


Because LabVIEW is still open, and your VI might not have closed the reference, and therefor LV might still be claiming the VISA resource...

 

Did you try closing LabVIEW before running the exe?

 

See Re: simple labview VI functions correctly, but when built into application the serial comms do not f...


yes, I closed labview and rebooted the machine, I've also tried switching to a different COM port...

Message 12 of 24
(288 Views)

turns out my simple VI was working, but just so slowly it looked like it wasn't, only updating the read value every minute or thereabouts.......

0 Kudos
Message 13 of 24
(281 Views)

Hi Sholyoake,

 


@Sholyoake wrote:

turns out my simple VI was working, but just so slowly it looked like it wasn't, only updating the read value every minute or thereabouts.......


So the Vi was working as you programmed it, but maybe not like intended… 😄

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 14 of 24
(278 Views)

@GerdW wrote:

Hi Sholyoake,

 


@Sholyoake wrote:

turns out my simple VI was working, but just so slowly it looked like it wasn't, only updating the read value every minute or thereabouts.......


So the Vi was working as you programmed it, but maybe not like intended… 😄


There's always a difference between what you want the code to do and what you tell it to do; as you fix things, the hope is that eventually the two converge to the point where you cannot distinguish one from the other.  😄

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 15 of 24
(273 Views)

@GerdW wrote:

Hi Sholyoake,

 


@Sholyoake wrote:

turns out my simple VI was working, but just so slowly it looked like it wasn't, only updating the read value every minute or thereabouts.......


So the Vi was working as you programmed it, but maybe not like intended… 😄


I'm only referring to my simple VI from post #10 here, literally opens the VISA reference, writes three characters, reads the response and closes the reference... my issue now is how to make that run more quickly+stably so I can rewrite the rest of the code round it

0 Kudos
Message 16 of 24
(271 Views)

@Sholyoake wrote:

@GerdW wrote:

Hi Sholyoake,

 


@Sholyoake wrote:

turns out my simple VI was working, but just so slowly it looked like it wasn't, only updating the read value every minute or thereabouts.......


So the Vi was working as you programmed it, but maybe not like intended… 😄


I'm only referring to my simple VI from post #10 here, literally opens the VISA reference, writes three characters, reads the response and closes the reference... my issue now is how to make that run more quickly+stably so I can rewrite the rest of the code round it


I'm sure we could help, but that VI is LV25, and most of us are stuck in older versions.

0 Kudos
Message 17 of 24
(228 Views)

wiebe@CARYA wrote:

@Sholyoake wrote:

@GerdW wrote:

Hi Sholyoake,

 


@Sholyoake wrote:

turns out my simple VI was working, but just so slowly it looked like it wasn't, only updating the read value every minute or thereabouts.......


So the Vi was working as you programmed it, but maybe not like intended… 😄


I'm only referring to my simple VI from post #10 here, literally opens the VISA reference, writes three characters, reads the response and closes the reference... my issue now is how to make that run more quickly+stably so I can rewrite the rest of the code round it


I'm sure we could help, but that VI is LV25, and most of us are stuck in older versions.


I was quite happy with LV21 but NI tech support made me upgrade to LV25 'just in case' and it didn't solve my issue

 

I'll rebuild the VI in LV21 and share it...

 

Message 18 of 24
(223 Views)

The Visa port is still open in Development blocking the .exe?

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 19 of 24
(53 Views)

@Yamaeda wrote:

The Visa port is still open in Development blocking the .exe?


but that doesn't explain why it doesn't communicate or throw an error when the development machine has had a full reboot.....

 

or why it doesn't communicate when run on the deployment target when that machine doesn't even have labview installed, obvs it has runtime engine, NI VISA and NI Serial drivers

0 Kudos
Message 20 of 24
(42 Views)