I have already posted this question on OpenG's forum but I haven't
seen much activity. Feel free to answer the question there:
http://www.openg.org/forum/viewtopic.php?t=117
Below is a copy of the message. Please disregard if you can view the
link and its attachments.
[start]
I would like to know how much success people have had using the nivisa-2.6
upgrade. I installed it last night after becoming determined to use my
serial port with my fancy OBDII adapter for my Ford Ranger. Since I just
"play around" with LV for Linux, I haven't had any prior need for visa
until now.
I went through all the upgrades: 6.0.1, 6.0.2, nicvirte-5.0.1,
nivisaserver-1.0. Other than having to convert all the rpms to tgzs
everyting went smooth. Oh yeah, I had to edit my ld.so.conf to provide the
path names /usr/local/vxipnp/linux/lib, /usr/local/cvirte/lib. The
visaconf and NIvisaic interfaces are awsome. Too bad they require X but
so does LV. I guess I could just as easily edit the .ini files with a
text editor.
MY PROBLEM:
I made a simple VI to test my new nivisa stuff (see attached). When I
placed a VisaResourceName control on the front panel I noticed the that
everything in the LV environment slowed down. I checked out my CPU and it
was at 15%. I wasn't even running the VI. I did notice that the control
was flickering quite a bit so I figured that so long as it's visible LV
must constantly poll it for user input. Based on that, I moved it on the
front panel so it couldn't be seen and that dropped my CPU cycles way
down. On the front panel I changed my visa control to a constant and gave
the front panel a string control instead.
In the diagram I hid the visa constant in a sequence frame so I'd never
have to see it again (it really slows down the wiring diagram to a crawl
when visible). Then I typecast the string to a visa data type. It worked
perfect. BTW, you'll see that the app doesn't really configure the port. I
didn't want to post something that would mess with with your hardware. All
it does is open and close a visa session with the serial port. Anyone else
run into this problem or notice similar quirkiness to the LV environment?
Please describe it and provide LV, Linux distro, kernel, and desktop
versions you are using. My hardware: 933MHz Dell with Slackware 8.0,
2.4.18 kernel, and Gnome 1.4 desktop
Thanks, Kevin Valentine
[stop]
