Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

Continued Unexpected Change in Table Definitions


MatthewBoyd Aug 9, 2014 10:59 PM

Data from one of four data tables on a CR1000 stops being copied to the local file via a scheduled data collection. After resetting the datalogger program by stopping it in Connect (choosing to "Delete Data") and then restarting it (choosing to "Delete associated data tables"), the data file updates for the first few collections, but then stops. During the reset I also rename the local files so new files are created.

Looking in LogTool at the Station Communication Log, I see the following messages repeated every minute:

"2014-08-09 5:41:10 PM","Ground","S","BMP5 message received","type: 0x89","Update Status Statistics"
"2014-08-09 5:41:10 PM","Ground","S","BMP5 message received","type: 0x89","table poll - AnalogAndSerialTable"
"2014-08-09 5:41:10 PM","Ground","S","BMP5 message received","type: 0x89","table poll - ModbusTCPTable"
"2014-08-09 5:41:10 PM","Ground","S","BMP5 message received","type: 0x89","table poll - OneMinTable"
"2014-08-09 5:41:10 PM","Ground","F","invalid table definitions"
"2014-08-09 5:41:10 PM","Ground","W","Unexpected change in table definitions"
"2014-08-09 5:41:10 PM","Ground","S","BMP5 message received","type: 0x89","table poll - RTDTable"
"2014-08-09 5:41:10 PM","Ground","S","BMP5 message received","type: 0x89","table poll - AnalogAndSerialTable"
"2014-08-09 5:41:10 PM","Ground","S","BMP5 message received","type: 0x89","table poll - ModbusTCPTable"
"2014-08-09 5:41:10 PM","Ground","S","BMP5 message received","type: 0x89","table poll - RTDTable"
"2014-08-09 5:41:10 PM","Ground","S","BMP5 message received","type: 0x89","table poll - AnalogAndSerialTable"
"2014-08-09 5:41:10 PM","Ground","S","BMP5 message received","type: 0x89","table poll - ModbusTCPTable"
"2014-08-09 5:41:11 PM","Ground","S","BMP5 message received","type: 0x89","table poll - RTDTable"
"2014-08-09 5:41:11 PM","Ground","S","BMP5 message received","type: 0x89","table poll - AnalogAndSerialTable"
"2014-08-09 5:41:11 PM","Ground","S","BMP5 message received","type: 0x89","table poll - ModbusTCPTable"
"2014-08-09 5:41:11 PM","Ground","S","BMP5 message received","type: 0x89","table poll - AnalogAndSerialTable"
"2014-08-09 5:41:11 PM","Ground","S","BMP5 message received","type: 0x89","table poll - ModbusTCPTable"
"2014-08-09 5:41:11 PM","Ground","S","BMP5 message received","type: 0x89","table poll - ModbusTCPTable"
"2014-08-09 5:41:11 PM","Ground","S","BMP5 message received","type: 0x89","table poll - ModbusTCPTable"
"2014-08-09 5:41:11 PM","Ground","S","BMP5 message received","type: 0x89","table poll - ModbusTCPTable"
"2014-08-09 5:41:20 PM","Ground","S","BMP5 message received","type: 0x9d","file receive - .TDFS"
"2014-08-09 5:41:20 PM","Ground","S","BMP5 message received","type: 0x9d","file receive - OneMinTable.TDF"
"2014-08-09 5:41:20 PM","Ground","S","BMP5 message received","type: 0x9d","file receive - OneMinTable.TDF"
"2014-08-09 5:41:20 PM","Ground","S","BMP5 message received","type: 0x9d","file receive - OneMinTable.TDF"
"2014-08-09 5:41:20 PM","Ground","S","BMP5 message received","type: 0x9d","file receive - OneMinTable.TDF"

Any idea why I get these invalid table definitions? Merging or resetting the table definitions in Setup does not resolve the issue.


rlwoell Aug 11, 2014 02:26 PM

We (engineers from CSI and I) are seeing a similar problem on my CR9000X programs.

Would mind posting your program, or at least the section of code which includes the table definitions?

It would also be useful to know which OS you are running in the logger.

Thanks.


MatthewBoyd Aug 11, 2014 03:57 PM

We are running OS 27 on a CR1000 with a 2GB CF card in an NL115. I'd be happy to send you my program if you give me an email address. Below are my table definitions: (I'm only having this problem with the OneMinTable.)

DataTable(AnalogAndSerialTable,True,-1)
CardOut(0,-1)
DataInterval(0,0,sec,DataTableLapses)
Sample(1,CR1000Temp_C,FP2)
Sample(1,DoorOpen,Boolean)
Sample(1,Pyra1_mV,FP2)
Sample(1,Pyra2_mV,FP2)
Sample(1,RefCell1_Wm2,FP2)
Sample(1,AmbTemp_C,FP2)
Sample(1,InvVDVoltage_V,FP2)
Sample(NumShuntModData,ShuntCurrent_A(),FP2)
Sample(1,WindDir_deg,FP2)
Sample(1,WindSpeed_ms,FP2)
Sample(1,WindRef_V,FP2) 'reference voltage (should be 3.5 V)
Sample(1,WindHeatStateID,FP2)
Sample(1,WindValid,Boolean)
Minimum(1,Battery_V,FP2,False,False)
Sample(1,Battery_A,FP2)
Sample(1,Load_A,FP2)
Sample(1,ChgState,FP2)
Sample(1,ChgSource,FP2)
Sample(1,CkBatt,FP2)
Sample(1,Qloss_Ah,FP2)
EndTable

DataTable(ModbusTCPTable,True,-1)
CardOut(0,-1)
DataInterval(0,0,sec,DataTableLapses)
Sample(10,InverterData(1),FP2)
Sample(1,InvEtot_kWh,Long)
Sample(2,InverterData(12),FP2)
Sample(NumInverterCodes,InverterCodes,UINT2)
Sample(1,SEWSAmbientTemp_C,FP2)
Sample(1,SEWSModuleTemp_C,FP2)
Sample(1,SEWSPOAIrrad_Wm2,FP2)
Sample(1,PwrMtrIa,FP2)
Sample(1,PwrMtrIb,FP2)
Sample(1,PwrMtrIc,FP2)
Sample(1,PwrMtrFreq,FP2)
Sample(1,PwrMtrFreqMin,FP2)
Sample(1,PwrMtrFreqMax,FP2)
Sample(1,PwrMtrPhaseRev,FP2)
Sample(1,PwrMtrVa,FP2) 'UINT2 more appr., but equiv to FP2, for consis.
Sample(1,PwrMtrVb,FP2) 'UINT2 more appr., but equiv to FP2, for consis.
Sample(1,PwrMtrVc,FP2) 'UINT2 more appr., but equiv to FP2, for consis.
Sample(1,PwrMtrP_kW,FP2)
Sample(1,PwrMtrP_kVAR,FP2)
Sample(1,PwrMtrP_kVA,FP2)
Sample(1,PwrMtrEdel_kWh,Long) 'received from grid
Sample(1,PwrMtrErec_kWh,Long) 'generated by array
Sample(1,PwrMtrEdel_kVARh,Long)
Sample(1,PwrMtrErec_kVARh,Long)
Sample(1,PwrMtrPF,FP2)
Sample(1,PwrMtrVaTHDMax,FP2)
Sample(1,PwrMtrVbTHDMax,FP2)
Sample(1,PwrMtrVcTHDMax,FP2)
EndTable

DataTable(RTDTable,True,-1)
CardOut(0,-1)
DataInterval(0,0,sec,DataTableLapses)
Sample(NumFourWireChs,RTD_C(),FP2)
EndTable

DataTable(OneMinTable,True,-1)
CardOut(0,-1)
DataInterval(0,1,Min,DataTableLapses)
Average(1,CR1000Temp_C,FP2,False)
Minimum(1,DoorOpen,Boolean,False,False) '-1=open, 0=closed
Average(1,Pyra1_mV,FP2,False)
Average(1,Pyra2_mV,FP2,False)
Average(1,RefCell1_Wm2,FP2,False)
Average(1,AmbTemp_C,FP2,False)
Average(1,InvVDVoltage_V,FP2,False)
Average(10,InverterData(1),FP2,False)
Maximum(1,InvEtot_kWh,Long,False,False)
Average(2,InverterData(12),FP2,False)
Average(1,InverterCodes(1),FP2,False)
Maximum(8,InverterCodes(2),UINT2,False,False) 'bit-arrays
Average(1,SEWSAmbientTemp_C,FP2,False)
Average(1,SEWSModuleTemp_C,FP2,False)
Average(1,SEWSPOAIrrad_Wm2,FP2,False)
Average(1,PwrMtrIa,FP2,False)
Average(1,PwrMtrIb,FP2,False)
Average(1,PwrMtrIc,FP2,False)
Average(1,PwrMtrFreq,FP2,False)
Minimum(1,PwrMtrFreqMin,FP2,False,False)
Maximum(1,PwrMtrFreqMax,FP2,False,False)
Average(1,PwrMtrPhaseRev,FP2,False)
Average(1,PwrMtrVa,FP2,False)
Average(1,PwrMtrVb,FP2,False)
Average(1,PwrMtrVc,FP2,False)
Average(1,PwrMtrP_kW,FP2,False)
Average(1,PwrMtrP_kVAR,FP2,False)
Average(1,PwrMtrP_kVA,FP2,False)
Maximum(1,PwrMtrEdel_kWh,Long,False,False) 'received from grid
Maximum(1,PwrMtrErec_kWh,Long,False,False) 'generated by array
Maximum(1,PwrMtrEdel_kVARh,Long,False,False)
Maximum(1,PwrMtrErec_kVARh,Long,False,False)
Average(1,PwrMtrPF,FP2,False)
Maximum(1,PwrMtrVaTHDMax,FP2,False,False)
Maximum(1,PwrMtrVbTHDMax,FP2,False,False)
Maximum(1,PwrMtrVcTHDMax,FP2,False,False)
Average(NumShuntModData,ShuntCurrent_A(),FP2,False)
Average(NumShuntModData,ShuntPDC_kW(),FP2,False)
Maximum(NumShuntModData,ShuntEtot_kWh(),Long,False,False)
WindVector(1,WindSpeed_ms,WindDir_deg,FP2,False,0,0,0)
FieldNames("WindSpeedAve_ms:,WindDirAve_deg:,WindDirStdDev_deg:")
Maximum(1,WindSpeed_ms,FP2,False,False)
Minimum(1,WindRef_V,FP2,False,False)
Average(1,WindHeatStateID,FP2,False)
Average(1,WindValid,FP2,False)
Minimum(1,Battery_V,FP2,False,False)
Average(1,Battery_A,FP2,False)
Average(1,Load_A,FP2,False)
Minimum(1,ChgState,FP2,False,False)
Minimum(1,ChgSource,FP2,False,False)
Maximum(1,CkBatt,FP2,False,False)
Maximum(1,Qloss_Ah,FP2,False,False)
Average(NumFourWireChs,RTD_C(),FP2,False)
EndTable


Dana Aug 12, 2014 07:32 PM

First off, make sure all your dataloggers in the LoggerNet network map have a unique PakBus address. If two dataloggers have the same address, you can see this problem.

If that checks out OK, send a copy of your program to support at campbellsci dot com, to my attention, and I will take a look. Also, please attach a copy of your LoggerNet logs. There is functionality in LoggerNet's LogTool to zip the logs (do not use the Save Log Window to file option, but the zip option). You may want to delete all logs first, reproduce the problem a time or two, and then zip/send the logs.

Thanks, Dana


MatthewBoyd Aug 14, 2014 07:54 PM

Thanks Dana. I also tried formatting the CPU storage and CF card too, but that did not help. However, I did upgrade the firmware to 27.04 (which I got from CSI to see if it would help with a different problem), and that has worked for the past three days. If the problem resurfaces, I will send the program and logs your way.


Dana Aug 14, 2014 07:56 PM

Thank you for following up. If you run into problems again, let us know.

Dana

Log in or register to post/reply in the forum.