06-04-2014 11:11 AM
Hi guys, i have a big, but 'simple' problem here. I am using a Fluke 2640 to acquire temperature. The problem is following:
The start of modules are slow, because it, I initialize the modules before I really initialize the data acquisition. So, when a really initialize acquisition, my Vi read all the values include, the values before i really start acquisition, how this data were in a buffer, and I dont read the real value in that time.
Sorry my wrongs in english.
06-04-2014 11:33 AM
Post your code or a link to the drivers used.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
06-04-2014 11:51 AM
Follow the drivers. I cant upload the VI because it is property of my boss.
06-04-2014 11:57 AM - edited 06-04-2014 11:58 AM
Guess your boss should be posting to this thread, too.
Can't tell you why the car is sluggish if we can't see the car.
Maybe you can upload a dumbed down version?
06-04-2014 12:08 PM
Follow the VIs hehe.
06-04-2014 12:56 PM
@Kossmann wrote:
Follow the VIs hehe.
Wow and this program actually works? How can you maintain this? I can't make heads or tails of it. Partly because I only speak English.
I guess what if you took 2 readings, then did a compare. If the values are exactly the same one would think that the readings have been updated, and the data is from the previous reading.
What about flushing the buffer between reads. I don't have the DLL that the drivers call but there is a chance that there is an unexposed method for clearing the buffer.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
06-04-2014 01:06 PM
The code is rife with places where I could see potential race conditions - this may be one of them. I can't even begin to follow this thing around. 😞
I hate to say it, but this is what happens when someone decides to "wing it" and write a bunch of LabVIEW code without really understanding how LabVIEW works. Eventually you wrap yourself up in spaghetti and can't find a way out. 😞
06-04-2014 01:09 PM
@billko wrote:
I hate to say it, but this is what happens when someone decides to "wing it" and write a bunch of LabVIEW code without really understanding how LabVIEW works. Eventually you wrap yourself up in spaghetti and can't find a way out. 😞
But the NI rep said it was so easy and anyone can do it. They opened an example and it did 90% of what I wanted.
In any case here are some free training links I give out to those that want to learn more.
3 Hour Introduction http://www.ni.com/white-paper/5243/en/
6 Hour Introduction http://www.ni.com/white-paper/5241/en/
LabVEW Basics http://www.ni.com/gettingstarted/labviewbasics/
Self Paced training for students http://www.ni.com/academic/students/learn/
Self Paced training beginner to advanced, SSP Required http://sine.ni.com/myni/self-paced-training/app/ma
LabVIEW Wiki on Training http://labviewwiki.org/LabVIEW_tutorial#External_L
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
06-04-2014 01:56 PM
I understand what you said, but this VI is not made by me, because it, i need to your help to understand a fix the problem, hehehe.
Sorry.