LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How do LabVIEW DSC users handle citadel or DSC errors?

hi LabVIEW gurus,

 

 I am currently using LabVIEW 8.5.1 with LabVIEW DSC. I have finished a development using Citadel about a year ago and found out that there is a number of errors which Citadel and DSC will throw out which I am not sure how to handle or whether I can ignore. Sometimes, my only alternative is to reboot the machine. My code to write data into citadel database consist of 3 vis i.e -> Open Trace -> Write Trace -> Close Trace. Here are some errors and the way I handle it.

 

a) error  -1967386570 - Backward in time error. This happens because the new data is actually an older time stamp compared to the latest data in the citadel database. I will handle this by performing some archiving process to merge the traces together.

b) error -1967362023 - Access denied. I will ignore this error

c) error -1967362045 - Timeout error. I will increase the time out for Open Trace to a larger number.

d) error 1025 -  Application Reference is invalid. Reboot machine.

e) error -1967386589 - Failed to map database into shared memory. Right now, I am ignoring the error, hoping that citadel can correct itself but it never does, so I end up rebooting the machine.

f) error -1967386569 - Unknown. Reboot machine.

 

If there is any good suggestion, please let me know.Thanks.

 

 

 

 

0 Kudos
Message 1 of 1
(2,509 Views)