LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Historical Database Error: TELOG_LogVal.vi, Error Code: -1967390689

We have a custom-built VI-based device server that occasionally causes the Tag Engine to produce the following event:

Historical Database Error
TELOG_LogVal.vi
Error Code: -1967390689

Historical data logging is then automatically turned OFF. However, if I turn logging ON again immediately afterward, then it continues to work OK.

Also note: I think this error might occur when our device driver attempts to write "large" chunks of data to Citadel. I have not found out exactly what "large" means... I am just guessing. Any ideas?
http://www.medicollector.com
0 Kudos
Message 1 of 5
(3,940 Views)
John Paul,

the error reported is:
"Warning -1967390689 occurred at an unidentified Location.
Possible reasons:
LabVIEW DSC: (Hex 0x8ABC001F) Attempted to log to a buffer that is full."

Maybe the citadel service that is responsible to take the "large chunks" of data from your VI-based server will run into a buffer overflow. There is a logos.ini file that could be generated and customized for such "non-default" use cases.

Here is a link to the KnowladgeBase article:
http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc10862567a100753500/862567530005f09e862567c700746a65?OpenDocument

Let me know if you still get an error when you increase the MaxQueueSize under the [Citadel] section in the logos.ini file.

Hope this helps
Roland
Message 2 of 5
(3,940 Views)
Thanks Roland! I thought it might have something to do with "overloading" Citadel. I'll play with the logos.ini to try and fix it (I have done that before on a different machine to fix a similar problem, actually).

ALSO: I occasionally get the message "Input queue compacted". I am also quite certain that I get this message because I am writing large chunks of data to the queue. But what exactly does "compacted" mean? Is it some kind of internal memory shuffling that Citadel or the Tag Engine uses (in which case, I don't really have to worry about it)? Or is it throwing out some of my data points?
http://www.medicollector.com
0 Kudos
Message 3 of 5
(3,940 Views)
Whoops... just found the answer to my own question in the NI Knowledgebase:

Getting "Input Queue Compacted" from the DSC Engine

http://www.accn.no/Member_Organizations/Member_Organizations.htm
http://www.medicollector.com
0 Kudos
Message 4 of 5
(3,940 Views)
Whoops again. That was the wrong URL:

Getting "Input Queue Compacted" from the DSC Engine

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/997917b2db2460c28625699d0076f9ca?OpenDocument
http://www.medicollector.com
0 Kudos
Message 5 of 5
(3,940 Views)