04-03-2025 08:29 AM - edited 04-03-2025 09:06 AM
@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?
04-03-2025 08:40 AM
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?
yes, I closed labview and rebooted the machine, I've also tried switching to a different COM port...
04-03-2025 09:02 AM
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.......
04-03-2025 09:05 AM
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… 😄
04-03-2025 09:14 AM
@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. 😄
04-03-2025 09:20 AM
@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
04-04-2025 02:58 AM
@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.
04-04-2025 03:25 AM
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...
04-08-2025 09:43 AM
The Visa port is still open in Development blocking the .exe?
04-08-2025 10:58 AM
@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