Jump to content

BTDT

Members
  • Posts

    4
  • Joined

  • Last visited

    Never

BTDT's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. So after a few more hours of testing I think I've got a solution, I had to set the environment variables as follows before starting up the PERL debugger PERLIO=:stdio PERLDB_OPTS=TTY=/dev/tty0 Readline=0 Hope this helps someone. Now I have the problem that the PIPES don't seem to be working in LabVIEW 8.0. Guess this projects stays with 7.x
  2. Using LabVIEW I would like to create a pipe to PERL so that I can interactively execute PERL commands. I have been trying to create the PIPE with the command line "perl.exe -de 42" to start up the debugger, but it opens a terminal window and requires me to type in the commands. It appears as if the PERL debugger does not connect to the standard IO streams. I am using: Windows 2000 LabVIEW: 7.0 OpenG Pipe Toolkit: From CVS on April 6, 2005 Perl: ActivePERL 5.22 Does anyone know how to get this to work? Is there a way to tell PERL (or the PERL debugger) to attached to the standard input and output streams? Any other ideas? Unfortunately I must keep perl.exe running for what I am doing and cannot call it with a number of small scripts. I've attached a test VI (including the necessary PIPE vi's from CVS) if anyones interested in testing. You will need ActivePERL V5.22 installed, be running windows NT/2000/XP and will have to update the PERL5LIB path on the block diagram. The test VI demonstrates that the DIR command works as expected, while the PERL command does not. BTW, there does seem to be a bug in the openG pipe library where the first call to it doesn't properly attach to the standard output stream. You can see this with the test VI without installing PERL. Thanks for the help Download File:post-2949-1144443407.llb
  3. OK, I've solved the problem, although I didn't have to interpret the connector pane type descriptor. I just got a reference to the connector pane and then pulled of the connector pane pattern, and references to all the controls. Thanks BTDT, BTDT.
  4. Has anyone done any work interpreting the type descriptor for a connector pane (0xF0)? The OpenG tools don't like them. Specifically, I would like to be able to check the connector pane of a VI to determine how to dynamically call it. Thanks for any help.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.