excessive CPU usage from nicitdl5.exe

[David Moerman]

Hello,

Ever since installing my LabVIEW DSC module (v7.1) onto my laptop (Dell Inspiron 8600, 1.4GHz Centrino, 1GB RAM), I've noticed "excessive" CPU usage from the nicitdl.exe service, even if the tag engine is not running.  It's not really huge:  it averages around 12% of my CPU continuously.  It wouldn't be a real big deal except I have to shut down this service to keep my battery from draining too quickly.  The strange thing is that I installed the DSC module onto a much slower desktop and the CPU usage for that service doesn't even register.

Has anyone else had a similar experience, or perhaps have any insight why this may be happening?

Thanks,

David Moerman
TruView Technology Integration Ltd.

[Prashanth]

Hi David,

I have not come across this issue before. It may be that some of the services on your laptop have been corrupted. I suggest that you uninstall and reinstall the DSC 7.1 module and make sure to install the latest fixes as well < http://digital.ni.com/softlib.nsf/websearch/6A771B1EBA7E670786256F49006F3693?opendocument&node=13207... >. The installation procedures for the DSC 7.1 fixes are described in the readme file of the download. Hope this helps!

Prashanth

[David Moerman]

Thanks for the suggestions, Prashanth, but it didn't work.  I uninstalled, verified that the CPU usage was indeed back down to nil (with LabVIEW running), re-installed LV DSC 7.1, rebooted, and nicitdl5.exe again begins to consume CPU cycles as it did before.

I noticed upon DSC re-installation that it recommended upgrade to SQL Server 2000 SP3, which I also did just in casel. (Actually, I upgraded to SP4).  No effect.

-Dave

[Prashanth]

Hi Dave,

What happens if you detach all your databases from MAX? Does the CPU usage go down?

I suspect there is something not right about the interaction between citadel and SQL server. As you may know, all the alarms are logged to SQL database and not to the citadel database. However, citadel takes care of logging these alarms to SQL and hence if this communication isn't right, citadel may consistently try to open connection to the SQL database which might explain the CPU usage.

Regards,

Prashanth

[David Moerman]

Great suggestion, indeed it was caused by one of the databases shown in MAX.  In fact, it was a demo database created by one of the DSC examples.  The database that caused the problem was located in C:\Program Files\National Instruments\LabVIEW 7.1\examples\lvdsc\servers\Demo\data.  As soon as I detached it, the nicitdl5.exe service CPU usage dropped to 1% or less, even when I re-attached my other databases.  Not sure why the demo database turned into a problem, but it's not bothering me anymore.

Thanks!

-Dave

[Chieudam]

I have the same problem with the DSC NICITDL.EXE takes up the CPU usage. it is about 50 to 93% after boost the PC. When I load the LabVIEW  application it goes to 100% frequently ( the PC and application crashed very often). I did disassociate the database, system CPU usage is better alittle bit and it comes back the same way. I deleted the historical database (it will create the new one) CPU goes down 30% then when the database gets bigger (few weeks later) the CPU usage problem comes back. 

If you guys find the solution please share with me. Thank you very much

My email is dam.nguyen@aarcorp.com

Dam Nguyen

Message Edited by Chieudam on 10-13-2006 02:12 PM

[Ryan.S]

your DSC version? 6.x or 7.x?

If you set the NI Citadel service not to startup automatically and restart pc, then start it manually, what will happen?

What's your logos version. If it's 4.5.0 or below, I suggest you to upgrade to 4.5.1 first. You can download it on NI ftp. ftp://ftp.ni.com/support/logos/