Albert Geven

Hi A lot is solved with quickdrop but not everything...

I still use a framework developed within Philips long ago. It is a qmh with good default initialization and a modified ini-file library that handles 2D data readable for excel sheets. played with DQMH looked only at actor framework

Hi This is happening because of objects. There has been a discussion on the NI-site and Steven mentioned not to use typedefs in objects. I hesitated to do this but when thinking along I accepted that typedefs are not necessary in objects. In fact the object itself is the typedefinition. I now only use typedefs when interfacing to an object but not in the object definition itself and no problems anymore. I beleive I had this problem in five different situations and getting it fixed took a lot of editing. I don't say it is a bug and indeed should be solved but for now I can live with it because indeed a typedef is not necessary in an object.

I just tested in LV2011-0f1 and it behaved correctly. probably fixed in 2011, the 0f1 release had something to do with the runtime installer and daqmx-base.

Hi Ben You sure advertise the classics again and not a lot has changed in 200 years except for LabVIEW .... But I sure agree that fear is a bad guide to meet other people and I hope we will see that bad people cannot be recognised by color or nation. So let all sports be sport, and not concentrate on money or war. Irene, thanks for pointing me to this link from info-labview, and keep the chinese spirit strong. QUOTE (neB @ Apr 11 2008, 01:40 PM)

Congratulations Ben

QUOTE(rolfk @ Dec 24 2007, 04:46 AM) Thanks Rolf by reminding me on this book, I really liked it and I hope peace will really come some day.

A simple way to get into problems we don't completely understand. open the project open the Main Vi Open also the display vi " Sensors fglb with graph error.vi" arrange the windows so that the "Sensors fglb with graph error.vi" is visible and the Main vi is in the left top corner and the error cluster is visible now run the main vi you may switch in the sensor display between raw data and temperatures and in any way I see in temperatures an error half of the time when delivering no data to the graph and don't tell that this is a feature So we decided this was due to the data yes or no available. But when switching to show all data I still see the error appear. Especially when the frontpanel of the sensor display is covered with a window (some window) This last one bothers me most.

Thanks Norm I guess I get too lazy to see all enhancements, or are my glasses too hazy....

Hi my last modifications, now you should learn a bit of LabVIEW without express vi's I changed the boolean for simulation to a frontpanel control, you did not need the simulation I needed it because I have no daq card in or on my system. I also restored the daq assistent. If you study the converted vi (from a daq assistent) you already learn better labview. I found out that excel understands a file with tab separation if you name it .txt The only problem left is that you have to right click on the file in the file exploder and open with excel. By the way, If your program grows you build modular code with a subvi, just as in other real programming languages. The way to keep them together is called a folder and a way to transport more than 3 vi's is usually a zipfile. good luck in playing in test and measurement world

You already had more than one vi and if you edit the readDAQ vi you can change it just as you want.This was incorporated in your program by the daq wizard, I only opend up this vi and got rid of the dynamic datat type.That all of your data is imported in excel in the first column is a mistake by excel. (copyrighted by MS)In previous versions they allowed this and handled it well.You can remove the "'," string on the array to spreadsheet function (and in the header line) and you will get a tab character instead.maybe that is accepted by the microsofware.The feature is now that you can run this program also when excel is not installed on the system.Soory for forgetting how to use your DAQ DEVICE.I have a boolean simulate added in the code.change that one into false and it is addessing your daq device

Here is my simple example the file written is a comma separated value file. If you give it the extension .csv excel should import it correctly. good luck

I'll make an example to save the median value of the 200 samples each 10 seconds. display it in a graph and save the data in a textfile (csv) that is easily readable in any value of excel. Look tomorrow.

I tried to modify your example and saw that you also needed a for around the build table. withou the dynamic data type I can really simplify this eaxmple. attached is a cleaned up version.

Hi Matej You have to move the table and the excel reporting outside the while loop. In fact that is all what you ask. A problem is your wiring technique. Pleas wire a bit cleaner and use "cleanup wire" more often. The dynamic data is for a program like this more of a handicap than a solution. you are reading 3 times 200 samples at 1kHz These are transformed in 3 elements in a table for each loop. If I look at the timeout of the Daq assistant it seems to repeat each 10 seconds (or more) In the table you seem to remeber all the 200 elements of each temperature measurement. Is this what you want or do you need the rms data in the table?