Hello togehter,
I need urgend help with one error message.
See below:
CardStatus Unable to access Card. errno: 42.
Error creating new files!
Setup is:
- CR1000
- NL115
We changed the NL115 module against another one and also against an CFM100. All of these modules cannot create a new file and causes the error. Therefore we think, that the problem is not in the modules. The crosscheck confirmed, all three card modules are working with a second CR1000, which we have on stock. The logger has the newest OS.
The use of formatting the card with the CR1000Keyboard did not worked. It shows the same error on display.
Should we send the logger directly to Campbell UK, in case that we cannot solve the problem. (We are pressed for time to finished all systems.)
Thanks for any help
Tim
Postet below is the status table:
Field Name Data Value
-------------------------------------------------
RecNum 2
TimeStamp 25.02.2009 17:38:33
OSVersion CR1000.Std.16
OSDate 081029
OSSignature 21784
SerialNumber 18984
RevBoard 012.007
StationName Giarratana_02
PakBusAddress 510
ProgName CPU:giarratana_02_v5.CR1
StartTime 25.02.2009 17:34:37
RunSignature 62339
ProgSignature 1204
Battery 12.24314
PanelTemp 20.1297
WatchdogErrors 0
LithiumBattery 3.483344
Low12VCount 0
Low5VCount 0
CompileResults CPU:giarratana_02_v5.CR1 -- Compiled in PipelineMode.
StartUpCode 0
ProgErrors 0
VarOutOfBound 0
SkippedScan 0
SkippedSystemScan 0
SkippedSlowScan(1) 0
SkippedSlowScan(2) 0
ErrorCalib 0
MemorySize 4194304
MemoryFree 32084
CPUDriveFree 467968
USRDriveFree 0
CommsMemFree(1) 1.401501E7
CommsMemFree(2) 305
FullMemReset 0
DataTableName(1) AVE_CARD
DataTableName(2) AVE_LOGGER
DataTableName(3) EVENTS
SkippedRecord(1) 0
SkippedRecord(2) 0
SkippedRecord(3) 0
DataRecordSize(1,1) 144
DataRecordSize(1,2) 0
DataRecordSize(2,1) 13582
DataRecordSize(2,2) 0
DataRecordSize(3,1) 100
DataRecordSize(3,2) 0
SecsPerRecord(1) 600
SecsPerRecord(2) 600
SecsPerRecord(3) 1
DataFillDays(1,1) 1
DataFillDays(1,2) 0
DataFillDays(2,1) 94.31944
DataFillDays(2,2) 0
DataFillDays(3,1) 0.001157407
DataFillDays(3,2) 0
CardStatus Unable to access Card. errno: 42.
Error creating new files!
CardBytesFree -1
MeasureOps 193
MeasureTime 558100
ProcessTime 71280
MaxProcTime 164774
BuffDepth 0
MaxBuffDepth 0
LastSystemScan 25.02.2009 17:38:00
LastSlowScan(1) 25.02.2009 17:38:00
LastSlowScan(2) 25.02.2009 17:38:00
SystemProcTime 9763
SlowProcTime(1) 1540
SlowProcTime(2) 338
MaxSystemProcTime 10249
MaxSlowProcTime(1) 1540
MaxSlowProcTime(2) 338
PortStatus(1) False
PortStatus(2) False
PortStatus(3) False
PortStatus(4) False
PortStatus(5) False
PortStatus(6) False
PortStatus(7) False
PortStatus(8) False
PortConfig(1) Input
PortConfig(2) Input
PortConfig(3) Input
PortConfig(4) Input
PortConfig(5) Input
PortConfig(6) Input
PortConfig(7) Input
PortConfig(8) Input
SW12Volts False
Security(1) 0
Security(2) 0
Security(3) 0
RS232Power False
RS232Handshaking 0
RS232Timeout 0
CommActiveRS232 True
CommActiveME False
CommActiveCOM310 False
CommActiveSDC7 False
CommActiveSDC8 False
CommActiveCOM320 False
CommActiveSDC10 False
CommActiveSDC11 False
CommActiveCOM1 False
CommActiveCOM2 False
CommActiveCOM3 False
CommActiveCOM4 False
CommConfigRS232 4
CommConfigME 4
CommConfigCOM310 4
CommConfigSDC7 4
CommConfigSDC8 4
CommConfigCOM320 3
CommConfigSDC10 4
CommConfigSDC11 4
CommConfigCOM1 0
CommConfigCOM2 0
CommConfigCOM3 0
CommConfigCOM4 0
BaudrateRS232 -9600
BaudrateME -115200
BaudrateSDC 115200
BaudrateCOM1 0
BaudrateCOM2 0
BaudrateCOM3 0
BaudrateCOM4 0
IsRouter False
PakBusNodes 50
CentralRouters(1) 0
CentralRouters(2) 0
CentralRouters(3) 0
CentralRouters(4) 0
CentralRouters(5) 0
CentralRouters(6) 0
CentralRouters(7) 0
CentralRouters(8) 0
BeaconRS232 0
BeaconME 0
BeaconSDC7 0
BeaconSDC8 0
BeaconSDC10 0
BeaconSDC11 0
BeaconCOM1 0
BeaconCOM2 0
BeaconCOM3 0
BeaconCOM4 0
VerifyRS232 0
VerifyME 0
VerifySDC7 0
VerifySDC8 0
VerifySDC10 0
VerifySDC11 0
VerifyCOM1 0
VerifyCOM2 0
VerifyCOM3 0
VerifyCOM4 0
MaxPacketSize 1000
USRDriveSize 0
IPInfo MAC: 00d02c044a28
eth IP: 0.0.0.0
eth mask: 0.0.0.0
eth gw: 0.0.0.0
IPAddressEth 0.0.0.0
IPMaskEth 255.255.255.0
IPGateway 0.0.0.0
TCPPort 6785
pppInterface 0
pppIPAddr 0.0.0.0
pppUsername
pppPassword
pppDial
pppDialResponse CONNECT
IPTrace 0
Messages
CalGain(1) 0
CalGain(2) -0.6733208
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.6734008
CalGain(14) -0.3366455
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
The problem is likely with the card (which would seem to be confirmed since you have tried multiple dataloggers and multiple NL115/CFM100s with the same results).
CSI recommends the use of industrial grade cards with its dataloggers. We have seen good results with industrial grade cards from Silicon Systems.
Regards,
Dana W.
Hi Dana,
thanks for your fast answer. But maybe you mix things or my written english is not easy to understand.
Well, we tried with different modules with the same Logger, as we recognized that the error occurred. (errno 42) We use ONLY Silicion Systems industrial grade with extended temperature range, exactly what campbell recommended.
As we changed the logger the problem was solved! And both cards are working fine. (But with a differne logger)
What should we do?
Send to CS UK? or is there a chance to solve by ourself.
Greets Tim
* Last updated by: moho on 2/25/2009 @ 2:30 PM *
I'm sorry. I didn't read carefully.
If it seems isolated to only one datalogger, then yes, I would contact Campbell Scientific UK and seek their advice.
Regards,
Dana
Tim,
Please email me directly with your email address, to andrew . sandford @ campbellsci.co.uk (remove the extra spaces).
If the problem is specific to one wiring panel/logger combination this could be an obscure fault with the wiring panel assembly which affected a few batches of wiring panels. One symptom is problems with comms to the peripheral port to which the card module is connected.
I can send you a letter and instructions to test and rectify the fault. The fix is very simple and requires little more than a screwdriver to fix it.
Sorry you have a problem.
* Last updated by: aps on 2/25/2009 @ 4:44 PM *
Hi,
we are passing through the same problem here in Brazil. The interesting is we are facing it with a new CR1000 datalogger and an old CR3000 (both with OS 25).
We did change the NL115 and the cards and the problem continues. We are thinking that maybe could be the new version of the OS.. but some dataloggers with OS25 worked well with NL115 modules.
Please, Dana. Send me the same information about the wiring panel. To us will be very difficult to send the logger to you in another country: bureaucracy.
loliveira@inpa.gov.br
I have this very same issue with CR3000 S/N 6507, running OS 25. This device (CR3000/NL115 combo) was deployed in the field last winter with no issues. However I just experienced the same error:
"Unable to access Card. errno: 42"
Next week this system will be deployed in the field and need to resolve this issue ASAP.
Please help. Thank you.
Your problem could be due to any one of a number of problems:
A) the NL115 not being plugged into the wiring panel quite correctly this can be they are just loose but can be also
B) due to broken of bent pins in the connector to the wiring panel – visibly check both the NL115 and logger halves of the connector. Check for dirt or bits of paper too.
C) a hardware fault, e.g. a bad solder joint, in the NL115 or in the card itself. (Also check for moisture)
D) the type of card or format you are using.
E) Dirt in the card slot or even in the small holes of the socket of the card which is preventing proper contact being made when the card is plugged in.
In relation to (D), note that not all Compact Flash cards will work in all our logger. Generally all the cards we have sold ourselves will work in all ours logger when running OS25. We have sold industrial versions of Sandisk, Silicon Systems, Western Digital and FMJ over the years – no others. There are some other brands of cards that will not work reliably in the CR1000 and others will not work in the CR3000.
I would also recommend though that you format the card in the logger you want to try to use it in as we have changed to using the FAT32 format in more recent times. Early cards were formatted in FAT16 mode.
Dear Dana,
we have experienced in this days very similar behaviour of our system. We are using CR3000 with OS 25 and CFM100. We tested different cards brought from you, yet it don't want to work. Please, send us the instructions to test and rectify the fault. It would be quite urgent because we had to take back the datalogger from the field. Two weeks ago, everything was still working.
Regards,
Peter
torma.peter@epito.bme.hu