From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

system exec.vi fails sometimes on user executable

I have an executable file that drives hardware. This executable takes command line arguments and runs from a shell prompt under windows2000/XP. The executable issues IO commands to the parallel port address to configure the hardware. The IO addressing is implemented correctly in 2000/XP using the PortTalk driver.

The executable works fine from the command line, embedded in a TCL/TK application and from within VEE.

We are now attempting to use it with LabView and it only works sometimes. Sometimes we get one or the other of the messages below.

Error 2 occurred at System Exec.vi. Command was "cgrfic".

Possible reasons:
LabVIEW: Memory full.
or
NI-488: Write detected no Listeners.

Any ideas? Is it pos
sible there is contention in the kernel for locking access to the ioport address. How can I get LabView to not attempt to claim a port address?
The application is <100k in size so the out of memory error is bogus.
0 Kudos
Message 1 of 2
(2,635 Views)
Hi,

If the executable returns a string (STDOUT), then this string is passed to
labview. Perhaps the buffer is to small, causing the error. There is an
optional input in the System Exec.vi to set the buffer size.

The Memory Full message is the explanation LV gives to error code 2. The
System Exec.vi returns 2, but the error has most likelly nothing to do with
the LV error database.

Regards,

Wiebe.



"richg" wrote in message
news:50650000000800000078BD0000-1075935269000@exchange.ni.com...
> I have an executable file that drives hardware. This executable takes
> command line arguments and runs from a shell prompt under
> windows2000/XP. The executable issues IO commands to the parallel port
> address to configure the hardware. The IO addressing
is implemented
> correctly in 2000/XP using the PortTalk driver.
>
> The executable works fine from the command line, embedded in a TCL/TK
> application and from within VEE.
>
> We are now attempting to use it with LabView and it only works
> sometimes. Sometimes we get one or the other of the messages below.
>
> Error 2 occurred at System Exec.vi. Command was "cgrfic".
>
> Possible reasons:
> LabVIEW: Memory full.
> or
> NI-488: Write detected no Listeners.
>
> Any ideas? Is it possible there is contention in the kernel for
> locking access to the ioport address. How can I get LabView to not
> attempt to claim a port address?
> The application is <100k in size so the out of memory error is bogus.
Message 2 of 2
(2,635 Views)