Hello
I've a CR1000 with 190 vibrating wire sensors and thermistors connected, using an AVW200 and 6pcs of 16ch multiplexers. The scan intervall is one hour. It takes about 5 minutes to scan through all channels (there is some oversampling on some channels, which takes quite long). The system is running fine since severeral months.
Now I've seen in PC400>File>Station Status that there were 173340 of "Skipped System Scans" occured during about 4 months. (See Status Table list at bottom of this post.)
I've restarted the logger and during the last week, the system accumulated again 13401 of "Skipped System Scans".
Is this something I've to worry about?
Is there still successful background calibration?
Is there something I can change to eliminate these skipped scans? (Increase buffers? Which buffers???)
Anyone can answers these questions?
Best regards
Manuel
STATUS TABLE:
Status Summary
24.05.2011 09:47:43
Datalogger Information
Reported Station Name: 34175
OS Version: CR1000.Std.21
OS Date: 100922
OS Signature: 55356
PakBus Address: 212
Security Settings(1): -1 (Security Set)
Security Settings(2): -1 (Security Set)
Security Settings(3): -1 (Security Set)
Panel Temperature: 19.23 °C
Memory: 4194304 bytes
Watchdog Errors: 0
Program Information
Current Program: CPU:D.CR1
Start Time: 07.02.2011 16:22:07
Run Signature: 27083
Program Signature: 52222
Compile Results for Last Program Sent: CPU:D.CR1 -- Compiled in SequentialMode.
Program Errors
Skipped Scans: 0
Skipped System Scans: 173340 - The main scan interval or number of scan buffers may need to be increased.
Skipped Records in FSDATA: 0
Variable Out of Bounds: 0
Battery Information
Battery Voltage: 13.78
Lithium Battery: 3.52
Number of times voltage has dropped below 12V: 0
Number of times voltage has dropped below 5V: 0
Card Information
Card Status: No Card Present.
Bytes Free: -1 bytes
* Last updated by: Monte on 6/1/2011 @ 6:41 AM *
Hi,
is the problem new or has it been there always?
Do the sources compile with an older compiler in pipeline mode?
I am experiencing currently the same and it's because new compilers suddenly compile in sequential mode although the sources compiled in pipeline mode just fine with earlier compilers -> no Skipped scans there...
HTH
Henry
A skipped system scan indicates there was not enough time for the logger to do its background calibration procedures, which it does on a regular cycle (please see the manual for more details).
If these system scans are skipped they are usually deferred until the next time they should run. This may not necessarily be a problem as long as the system scan does run some of the time. All it means is the logger becomes slower to respond to changes in temperature etc which can affect its calibration.
So I guess that my logger will execute sufficient background procedures during his idle time (55minutes of each hour).
Is there a way to check when the last background calibration was executed?
Is there a way to check when the last background calibration was executed?
The datalogger's Status table has a LastSystemScan field that provides this information.
Dana W.
I see in LastSystemScan that my logger is doing the background calibration well when it is in idle time.
Thanks for your help.