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.

CR800 compilation errors


nuno Apr 28, 2017 10:36 AM

Hello,

I need some help with a CR800 logger. It stoped working well and I don't know why. Can't connect with it using PC200W software and using the Device Configuration Utility it connects but only sometimes. When I try to send a program it fails, supposedly the connection. I get errors like:

Failure: 27/04/2017 12:21:34.721
PakBus framing error","Invalid low level signature
Warning: 27/04/2017 12:21:46.062
transaction failure","timed out or resource error","file receive - .TDF
Failure: 27/04/2017 12:21:46.076
PakBus framing error","Invalid low level signature
Failure: 27/04/2017 12:21:46.077
file is not accessible","file receive - .TDF
Warning: 27/04/2017 12:22:29.551
transaction failure","timed out or resource error","file receive - .TDF
Failure: 27/04/2017 12:22:29.567
file is not accessible","file receive - .TDF
Failure: 27/04/2017 12:22:29.567
PakBus framing error","Invalid low level signature

Meanwhile I updated the operating system (version 31.02) but it isn't much better. When I try to send a program it says that fails and return some errors that weren't supose to be errors. What I mean is that the reported errors are about constants of the programming language, or something like that. Sometimes I get a mem fail3. FP2 is to use floating point, Min is for minuts. If I replace True with 1, the first error disappears. I used the example of the termocouple that comes with the Operator's Manual of CR800-Series Dataloggers using Short Cut.

line 14: Undeclared variable True.
line 15: Undeclared variable Min.
line 15: Variable illegal in Parameter: Min.
line 16: Undeclared variable FP2.
line 16: Variable illegal in Parameter: FP2.
line 17: Undeclared variable FP2.
mem fail3.

I installed the trial version of the LoggerNet to use the CRBasic Editor and the program compiles without errors. 

Is it possible that the logger is somewhat damaged?


GaryTRoberts May 1, 2017 02:19 AM

Nuno,

Try using a different RS-232 cable to connect to the datalogger.  Does the same behavior happen when that is done?  If it does not, send me you program at gtroberts =at= campbellsci.com.


nuno May 2, 2017 03:55 PM

Thank you for your reply,

I tried with some Windows version (XP, Me, 7 and 8), with some RS232 cables (using my old computer with that interface and windows XP), and with RS232 to USB adapters. The result is always the same.

When the CR800 logger was handed to me it had the OS version CR800.std.24. It was working fine, I could read data from sensors, etc. Then it stopped responding. I could only connect with the logger using the Device Configuration Utility app, but the connection attempt fails some times before a success. In the Logger Control tab no current program was available (why?). Every time I tried to upload a program the connection with the logger failed.  

With no solutions in sight, someone told me to update the operating system, which I did. Now I do not loose the connection with the logger but the upload of programms results in the compile errors I posted before.

The program I used to test it is nothing special.

CR800 Series
'Created by Short Cut (3.2)

'Declare Variables and Units
Public BattV
Public PTemp_C
Public Temp_C

Units BattV=Volts
Units PTemp_C=Deg C
Units Temp_C=Deg C

'Define Data Tables
DataTable(OneMin,True,-1)
DataInterval(0,1,Min,10)
Average(1,BattV,FP2,False)
Average(1,PTemp_C,FP2,False)
Average(1,Temp_C,FP2,False)
EndTable

'Main Program
BeginProg
'Main Scan
Scan(1,Sec,1,0)
'Default CR800 Datalogger Battery Voltage measurement 'BattV'
Battery(BattV)
'Default CR800 Datalogger Wiring Panel Temperature measurement 'PTemp_C'
PanelTemp(PTemp_C,_50Hz)
'Type T (copper-constantan) Thermocouple measurements 'Temp_C'
TCDiff(Temp_C,1,mV2_5C,1,TypeT,PTemp_C,True,0,_50Hz,1,0)
'Call Data Tables and Store Data
CallTable OneMin
NextScan
EndProg


JDavis May 3, 2017 03:36 PM

Check your program again. The code compiles fine for me on a datalogger running OS 31.03

I had just copied all of your code and pasted it into a new program in CRBasic Editor. Maybe you had extra spaces or unprintable characters.

 

'Created by Short Cut (3.2)

'Declare Variables and Units
Public BattV
Public PTemp_C
Public Temp_C

Units BattV=Volts
Units PTemp_C=Deg C
Units Temp_C=Deg C

'Define Data Tables
DataTable(OneMin,True,-1)
  DataInterval(0,1,Min,10)
  Average(1,BattV,FP2,False)
  Average(1,PTemp_C,FP2,False)
  Average(1,Temp_C,FP2,False)
EndTable

'Main Program
BeginProg
  'Main Scan
  Scan(1,Sec,1,0)
    'Default CR800 Datalogger Battery Voltage measurement 'BattV'
    Battery(BattV)
    'Default CR800 Datalogger Wiring Panel Temperature measurement 'PTemp_C'
    PanelTemp(PTemp_C,_50Hz)
    'Type T (copper-constantan) Thermocouple measurements 'Temp_C'
    TCDiff(Temp_C,1,mV2_5C,1,TypeT,PTemp_C,True,0,_50Hz,1,0)
    'Call Data Tables and Store Data
    CallTable OneMin
  NextScan
EndProg

 


nuno May 5, 2017 09:58 AM

I used Short Cut so I did nothing (add spaces or characters) with the program.

All I need is to know if the problem is the operating system (a bug or something) or the logger (electronics, like a memory error or something like that).


JDavis May 5, 2017 07:08 PM

The compile errors you got all relate to predefined constants. So, it appears the precompile stage didn't run. I have never seen that before. Maybe there is some type of memory corruption. Try putting 31.03 on the CR800.


nuno May 8, 2017 10:45 AM

With OS version 31.03 is a little bit worst. I get the same compilation errors as before and now it also fails connection with the logger when I try to set the clock. With OS version 31.02 the set clock function works fine. I'm using the Device Configuration Utility 2.13.

With PC200W I cannot connect with the logger.

Is there a way to download older versions of the operating system, just to rule out that possibility (bugs from new versions). If it doesn't work with any, then the problem may be in the hardware.  

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