Hello!
I am installing a new datalogger, with a program that we use as standard in our logger boxes(i.e. the program has been successfuly installed in other devices), and I am facing an issue:
Datalogger: CR1000 / OS 32.03 ;; Loggernet Version 4.5.0.1
- the program should create some some tables and store the data in the card
- in file Control I can see that the data files are created in CRD
- when connecting I can only see the Tables: Status, Public and DataTableInfo, and not the Data Tables
- on DataTableInfo I can see the tables created and its info except the DataTableName()
From resetting the datalogger, formatting the card, ... I've tried several actions without success.
What could be the cause and solution?
Best regards
Márcio
Try connecting with Device Configuration Utility (DevConfig). Do you see the same behavior with DevConfig? Also, can you send us a snapshot of your status table? That might give us some clues as to what is going on.
Below is the Status table data, and connecting with DevConfig shows the same behaviour, the data tables aren't shown.
A bit more info:
- In this case the station has OS version 31.03, but it is also happening in another station with OS 32.03.
- the common aspect between these two is that the datalogger internal battery was removed and repaced again, could this have any influence?
TIMESTAMP 51:56.4 RECORD 305 OSVersion CR1000.Std.31.03 OSDate 04/14/2017 OSSignature 17728 SerialNumber 32836 RevBoard 17.008 StartTime 41:44.6 RunSignature 3829 ProgSignature 2217 WatchdogErrors 0 PanelTemp 26.83967 Battery 12.19742 LithiumBattery 3.433389 Low12VCount 0 Low5VCount 0 CompileResults CPU:v1.3c.CR1 -- Compiled in PipelineMode. StartUpCode 0 ProgErrors 0 VarOutOfBound 0 SkippedScan 0 SkippedSystemScan 0 ErrorCalib 0 MemorySize 4194304 MemoryFree 43096 CommsMemFree 19(17),25(25),15(13),4(3) 298 99(99),32(30),34(32),20(19) FullMemReset 0 CardStatus Card OK. MeasureOps 81 MeasureTime 186300 ProcessTime 107962 MaxProcTime 287274 BuffDepth 0 MaxBuffDepth 0 LastSystemScan 51:48.1 SystemProcTime 14848 MaxSystemProcTime 14848 PortStatus(1) 0 PortStatus(2) 0 PortStatus(3) 0 PortStatus(4) 0 PortStatus(5) 0 PortStatus(6) 0 PortStatus(7) 0 PortStatus(8) 0 PortConfig(1) SDM PortConfig(2) SDM PortConfig(3) SDM PortConfig(4) Input PortConfig(5) TX PortConfig(6) RX PortConfig(7) Input PortConfig(8) Input SW12Volts 0 PakBusRoutes 1,4089,4089,1000 105,4094,4094,5000 Messages CalGain(1) 0 CalGain(2) -0.6852465 CalGain(3) 0 CalGain(4) 0 CalGain(5) 0 CalGain(6) 0 CalGain(7) 0 CalGain(8) 0 CalGain(9) 0 CalGain(10) 0 CalGain(11) 0 CalGain(12) 0 CalGain(13) -0.6851663 CalGain(14) 0 CalGain(15) 0 CalGain(16) 0 CalGain(17) 0 CalGain(18) 0 CalSeOffset(1) 0 CalSeOffset(2) 6 CalSeOffset(3) 0 CalSeOffset(4) 0 CalSeOffset(5) 0 CalSeOffset(6) 0 CalSeOffset(7) 0 CalSeOffset(8) 0 CalSeOffset(9) 0 CalSeOffset(10) 0 CalSeOffset(11) 0 CalSeOffset(12) 0 CalSeOffset(13) 0 CalSeOffset(14) 0 CalSeOffset(15) 0 CalSeOffset(16) 0 CalSeOffset(17) 0 CalSeOffset(18) 0 CalDiffOffset(1) 0 CalDiffOffset(2) 0 CalDiffOffset(3) 0 CalDiffOffset(4) 0 CalDiffOffset(5) 0 CalDiffOffset(6) 0 CalDiffOffset(7) 0 CalDiffOffset(8) 0 CalDiffOffset(9) 0 CalDiffOffset(10) 0 CalDiffOffset(11) 0 CalDiffOffset(12) 0 CalDiffOffset(13) 0 CalDiffOffset(14) 0 CalDiffOffset(15) 0 CalDiffOffset(16) 0 CalDiffOffset(17) 0 CalDiffOffset(18) 0
If it is permissible, please send me a copy of your program. gtroberts -at- campbellsci.com I will see if something in the logger OS or software is causing the issue.
Hello,
It happens to have found the cause:
The datalogger had the Security Code level 1 set = 0; after setting the Secudity Code to a value different from 0 it worked properly.
Not sure if this is intended like this, on the manual there is this reference:
Up to three levels of lockout can be set. Valid pass codes are 1 through 65535 (0 confers no security).
but wasn't sure that setting the Security Code 1 = 0 would case this trouble.
Anyway, it's solved.
Thank you!