Jump to content
Posted 01 April 2014 - 06:23 PM
Posted 02 April 2014 - 07:24 AM
You can read about command-response mode and stream mode here:
What are you using for excitation for your 4 load cells?
Since you have the LJTIAs as pre-amps, are you using the +/-10V range on the U6-Pro (gain=1)?
If you are using the +/-10V range, then to acquire 4 channels in <250ms the maximum ResolutionIndex you can use in command-response mode is 10:
In stream mode, you can't use the hi-resolution converter, so the max ResolutionIndex is 8:
To see the expected noise level see Appendix B. You should be able to recreate these numbers if you test with a grounded channel:
So I suggest you use command-response mode. I suggest you use a single Add/Go/Get block:
... where you do 4x iotypes LJ_ioGET_AIN or LJ_ioGET_AIN_DIFF and 1x iotype LJ_ioGET_COUNTER. In LabVIEW, start with "U6 Multiple IO Example.vi", or for something with a loop look at "U3 Multiple IO Example Loop.vi".
Posted 02 April 2014 - 07:52 AM
Here is a new example "U6 Multiple IO Example Loop.vi" that would be a good starting place for you.
Posted 02 April 2014 - 08:26 AM
Hi the excitation voltage is the pre amp 2.5 volts, and yes the range is +/-10V.
I've been using the U6 eAIN example,which works, should I change it to U6 Multiple IO? If I reduce the number of channels to two could it reduce the 250ms? How do I do it? with IOtypes?
Also I include an image of my IO code
Posted 03 April 2014 - 04:22 PM
Your code generally looks OK, but my first observation is that you have split the error cluster. This makes it difficult to follow the data flow and determine where an error came from. I suggest you wire the error cluster in series only.
Look at the loop example I posted above and follow these guidelines demonstrated in the example:
1. Error cluster is in series only. No splits.
2. When error cluster passes in/out loop use a shift register.
3. Stop loop if there is an error.
4. User ErrorToString when done to interpret error.
0 members, 0 guests, 0 anonymous users