I want to write Spreadsheet Data to Citadel 4 (and Citadel 5)

[solar56]

I use the example "Write file to citadel".

http://zone.ni.com/devzone/conceptd.nsf/webmain/5A921A403438390F86256B9700809A53?opendocument

If I run the example, only the Row_String is running, the other tags at the front panel keep zero.
In the Database I can find Row_String Data, but they do have the actual date !
What's wrong ?

New test.:
I write my own csv-file.
Make a new Registration.
Only one Tag, 10 rows, Timestamps from 1 to 10 (which means 1.1.1904 12:00:01 and so on)
What do I get in citadel? The actual date!
What's wrong?

Will there be a better ore more elegant way to write data to Citadel?

How about Citadel5 and LabVIEW 7 ???

Thank you for your help

PS: I did read the dis
cussion : "Enable to have the Write File to Citadel Example working" It didn't help.

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=5065000000080000008C640000&ECategory=LabVIEW.Datalogging+and+Supervisory+Control

[AndreOliveira]

Hi,

Make sure you set it up correctly before running the example. I have just run the example with success... The key point is to copy the "Write to Citadel.cfg" to the LabVIEW home directory and then run the "Register Write File to Citadel Server.VI" with the exact configuration shown in the picture on the tutorial document.

I have carefully followed the instructions and I did have any problem with it, I could also verify that the tags logged to the database do have a different timestamp, (not the current one)...

Make sure you unregister the VI-based server and re-register it appropriatelly, you should be fine after that.

Best Regards

Andre

[solar56]

Hi Andre,

I did follow the instructions very carefully, at least 10 times.
By the way, the instructions say, that I don't have to unregister the server before making a new registration, this should be done automatically.
I also made my own example, it did work, but with the actual time as timestamp.
Is it possible, that I changed some configurations elsewhere in my system which could cause this behaviour ?
I will not be in office next week, so I can't make new experiments.

Thank you for helping

Thomas

[jdg]

I'm lloking for the same answer you are looking for. Before I visited this web page I'd tryed to run the same example with the same results. I will continue to make it run and will let you know if I find the trick to solve the problems. I would also appreciate, if you find the problem before me, your information to reduce my brain-srotming.
Thanks
Jose Javier

[AndreOliveira]

Hey Guys,

If you still have problem you may considerer ask for help with National Instruments.

Access the web page

http://www.ni.com/support/

and generate a service request number, with this you can directly call NI and will be routed to a engineer.

I hope it helps

Andre

[Roli]

I saw your problem and probably you've solved it already... but here I found an interessting KB which directs to the problem... VI-based servers serving own timestamps or will be ignored with a specific DSCEngine.ini setting: UseServerTimestamps=false which is default set to false to avoid race conditions in the DSCEngine and to avoid back in time problems... see more How Do I Avoid Out-of-Synch (a.k.a. Back-In-Time) Timestamps in the Citadel Database?

I agree with you, writing VI-based server to log timestamped values is not really convinient. We just can hope that NI will come up in the near future with a logger VI similar to Lookout's logg
er object.

Hope this helps
Roland