LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to log RT data to remote citadel database using citadel writing api

Solved!
Go to solution

I'm trying to get an RT target to launch a VI when booted, that  acquires data and sends it to a Citadel database on a networked computer. 

 

I'm trying to do this with the Citadel Writing API, specifically the functions in the DSC module; open trace, write trace, and close trace.

 

I have a project with the RT target added. I have a simple VI under My Computer generating data and sending it to the local Citadel database. This VI works fine and data is written to the database. However, I have a similar VI under the RT target but the Open Trace VI is broken and the VI will not run. It appears that one of the subVIs in Open Trace VI is broken and will not run.

 

I'm missing something here. Can anyone help me figure this out?

0 Kudos
Message 1 of 5
(4,385 Views)
Solution
Accepted by rdaxon
The VI is likely not compatible with real-time, perhaps it calls a DLL or something. What you need to do it transfer the RT data to a Windows-based host computer and let that host do the insertion into Citadel.

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
0 Kudos
Message 2 of 5
(4,362 Views)

It is possible! It is not needed to use any API. Everything you need is to design TWO project libraries with the network-published Shared Variables. The first Library is cRIO-targeted Library for uploading the values. The second one is the PC-library with aliasing to cRIO's library and  "Logging" to Citadel Database attribute turned on. All the Variables will be logged into Citadel database after both libraries have been deployed. At present time my measurement system is working while cRIO library is publishing data via Modbus Slave I/O and PC library is getting the values and logging into PC-Citadel database. cRIO vi was built and set as startup vi. It is not necessary to open and start any VI on the PC. You can check the system's state trough the Distributed System Manager or MAX Historical trend view. There is a problem with the time synchronization (about 20-30 seconds delay), but the data is logged :-).

Sorry for my poor English 🙂

0 Kudos
Message 3 of 5
(3,874 Views)

I have a very similar system with cRIO's and RT NSV's bound to Windows NSV with Citadel logging enabled.  It works very well and I see very good time synchronization < 100ms since my PC and cRIO system clocks are sync'd using 1588 PTP.

0 Kudos
Message 4 of 5
(3,645 Views)

I know this is an old thread but I am in the same position as the original poster. Using a cRIO-9035 which I would like to log data and write to Citadel. Ideally directly without the need of a PC, but it appears as though this is not supported. Wondering if anybody has had a workaround or can offer suggestions??

0 Kudos
Message 5 of 5
(3,605 Views)