DSC stopped logging

[MarkfromSAGE]

I'm running Labview 7.1 and have up until very recently been successfully logging data using the DSC module.  The is no obvious cause for this, hence the posting.

I have the DSC module installed on a PC with an RS-Linx OPC server.  Many tags are configured and have been logging for over a year.  The tagengine is configured and launched upon PC startup.  Database is Citadel 5.

Basically, I cannot see any data beyond 8 aug 2007 when using MAX 4.1.  I have tried stopping an restarting the DSCEngine.  I also renamed the .SCF file and reloaded this into the tagengine.  Also I have added a new tag to see if that would log.   The tagmonitor shows all the tags are there and are updating.  However, when I try to add the new tag to a view in max, it is not present. I'm at a bit of a loss to understand how MAX cannot see it, and suspect this is the root of my problem.  Any help appreciated.

Mark

[unclebump]

try the read historical trace vi's  and see if they grab any data.

[MarkfromSAGE]

OK.  I tried this.  The read hisorical data .vi's behaved exactly like MAX, i.e. no data beyond a certain point.  All the tags appeared to be there, etc.

I had a couple of other thoughts which I tried - also to no avail.  I looked at the services which were running, thinking thte Citadel server may not be running.  I found I had two services related to Citadel running.  Starting and stopping these seemed to make no difference, although I did not reboot the PC, a it is running a pretty critical application - although it can be rebooted if absolutely necessary.

One thing: The Citadel service said it depended on something called NIPALK, which I did not see in the services list.  Any thoughts on what this is?

[Nick R]

Hi Mark,

NIpalk is an abstraction layer in LabVIEW. Its really just a generic interface to LabVIEW and provides the OS access to the hardware.