LabVIEW
LabView Rant - lack of Express node support
@BertMcMahan wrote:
Also, if you are JUST looking to log data to files and not do any actual programming, NI's FlexLogger program might help you out. It's super easy to set up random data collection schemes, plot them, save them to files, etc. You can't do any programming in it outside of a few triggers ("start recording data when this analog value goes above 2 V") but it's very easy to collect data from cDAQ chassis.
Along the same lines is DAQExpress. I'm not sure if it is compatible with cDAQ (at one point it was USB DAQ only), but it is FREE.
@Rich_Tennant_Tech wrote:
>>>>>>>>>>>>>>>
That's fine, having a node that can run everything at one speed would just be another option in our tool box - something that you would only use if needed and not used if you wanted to run at different speeds. Not wanting to change the game, just expand its capability.
Another option to that would be to let a higher speed card run at that higher speed but then have a node that would average that back down to a common speed. So then I would be getting a the lower scan rate that I'm looking for (average of 1 second) but then not have to worry about a buffer over run.
Or just make it possible to specify that any card can run at any speed requested as long as it doesn't exceed its max speed design limit or cause a buffer over run - or any other unseen error caused by running too slow.
Case in point would be a test I'm running right now on 12 water pumps set to run for 3000 hours (estimated full life) - we're looking at case temperature (9211 card) and current (measured with a shunt into a 9239 card). The 9211 maxes out at 15 Hz, the 9239 wants to run at 4 times that and to prevent a buffer over run you need to average the 9239 readings. Which seems kind of silly, why not just make it possible to run them all at a lower speed and be done with it?
Our solution was to pay a company to write a program that will save data at a 1 second interval across all channels. Sad but true.
If you press the quote button, you get the post you're quoting in a formatted way. It's the " icon...
Search LabVIEW like a graph!
@Rich_Tennant_Tech wrote:
>>>>>>>>>>>>>>>
That's fine, having a node that can run everything at one speed would just be another option in our tool box - something that you would only use if needed and not used if you wanted to run at different speeds. Not wanting to change the game, just expand its capability.
Another option to that would be to let a higher speed card run at that higher speed but then have a node that would average that back down to a common speed. So then I would be getting a the lower scan rate that I'm looking for (average of 1 second) but then not have to worry about a buffer over run.
Or just make it possible to specify that any card can run at any speed requested as long as it doesn't exceed its max speed design limit or cause a buffer over run - or any other unseen error caused by running too slow.
Case in point would be a test I'm running right now on 12 water pumps set to run for 3000 hours (estimated full life) - we're looking at case temperature (9211 card) and current (measured with a shunt into a 9239 card). The 9211 maxes out at 15 Hz, the 9239 wants to run at 4 times that and to prevent a buffer over run you need to average the 9239 readings. Which seems kind of silly, why not just make it possible to run them all at a lower speed and be done with it?
Our solution was to pay a company to write a program that will save data at a 1 second interval across all channels. Sad but true.
I'm not that into DAQmx, so really can't comment on that.
But in general, suggesting a global to fix things in not a good idea. In this case, it seems you want a global speed? Or just a global default speed?
If you really thing it will help people, you can suggest it in the idea exchange. Probably the Data-Acquisition-Idea-Exchange.
@Rich_Tennant_Tech wrote:
I don't have a quote button, only a reply button - strange.
You get that button in your reply window, or rather above your reply entry:
On narrow screens (mobile) you might have to press ... first.
wiebe@CARYA wrote:
@Rich_Tennant_Tech wrote:
I don't have a quote button, only a reply button - strange.
You get that button in your reply window, or rather above your reply entry:
On narrow screens (mobile) you might have to press ... first.
Do you know how long it took me to find that quote button? When they switched from having the quote button on the bottom to putting it on the tool bar, it messed me up for at least a few weeks... so finally I stopped to ask for directions. 😉
