04-27-2008 04:19 AM
04-28-2008 06:57 AM
Steve,
I agree it should be faster. There are at least 3 things I can think of that will affect speed.
1 - Your vi has something in it that is slowing you down. Suggest you post your vi. 8.2 seems to be a version that most forum users can open.
2 - How is your FP connected to PC? Serial port, ethernet?
3 - What filtering options did you select in MAX for your FP I/O channels?
04-28-2008 10:28 AM
The VI is the standard FP function from the functions palette, requesting a read of all channels as a array of doubles.
The filtering is set to 50Hz (I am in Europe). I changed it to none, but did not seem to have any affect.
I am communicating over RS-232.
S
04-28-2008 12:07 PM
04-30-2008 04:58 AM
04-30-2008 06:47 AM
05-02-2008 10:12 AM
05-05-2008 07:30 AM
wa5cg,
I misinterpreted your initial post as possibly some sort of problem communicating with the FP. I expect a FP Read to take a couple of mS max.
After reading Jeff's post and rereading your intial post I don't think the delays you mentioned are slow execution of the FP Read. Based on the fact that you mentioned MAX, I'm pretty sure that your problem is the update rate of the actual modules. As Jeff has pointed out, multiple FP Reads will return the same value if you are trying to read the I/O faster than the update rate.
Published 'All Channel Update Rate' for the AI-110 is 5Hz to 0.66Hz depending on filter settings. With filters off, it will take 200mS minimum before multiple FP Reads will return the new value. In comparison an AI-118 has a published all channel rate of 10.42kHz with filtering turned off.
Published 'All Channel Update Rate' for the TC-120 is 0.88 Hz. No option to turn filtering off on the TC-120. TC-125 does have the option to turn the filtering off and has an update rate of 4.5Hz.
This all goes back to the fact that most of the FP modules have been optimized for industrial control and monitoring. Very rugged with isolation and filtering, not very fast when compared to something like a DAQmx device.