03-25-2008 05:40 AM
Hi,
datalog.log is log file used, it is contained in the .zip file.
thanks,
03-25-2008 06:09 AM
Hi,
Sorry about that, I have now re-created the issue and searched our database, this is a known issue with datalog records and is known to R&D and is therefore under investigation to be fixed.
All the best,
03-25-2008 06:36 AM
Hi again,
Does this issue exist with 8.5 also? I beleive this is now available for me to use here.
thanks
03-25-2008 06:42 AM
Sadly when I reproduced it here it was under 8.5, it's something that's due for fix shortly, I'm trying to consider possible work arounds but I don't believe any exist for this particular issue. What do you require this functionality for under your application and I can maybe come back with some workarounds for the application?
All the best,
03-25-2008 07:07 AM
Hi,
We have used this method of datalogging extensively (for IC evaluation), whilst aware of being able to save directly to .html, saving to .TDMS or other such methods we have found this very usleful, quick method of capturing data of which quick screen shots can be grabbed and circulated amongst our group(s). Our vi front panels contain a lot of visual info as well as set-up conditions passed from many globals etc. Its a quick way of capturing all this data in a simple step, as well as having graphs/plots or other info later by making the vi database accesable and reading particular records.
I do realise that this method of capturing data is not a very efficient use of memory but has been a quick easy solution. Where results captured are incorrect or not needed for records they are deleted, this may then make 8.2/8.5 unusable at present. A lot of time would be needed to employ other data capturing functionality into all of our vi's
04-23-2008 11:45 AM
Hi,
Any updates on a fix for this bug?? It is most important to us, this will keep us unable to upgrade 8.2 or 8.5 until resolved
Regards,
ds