Box Car

Common Errors

Error 0

Logger not supported or undefined error, customer must upgrade software or install software patch.

Error 4

Weak battery - remove and reinsert battery - is the LED blinking?  If not, replace battery.

Dead battery - same

Cable not fully inserted into logger or computer.

Wrong COM port.

Bad COM port on computer (usually Gateway or Micron have weak serial communications).  Installing 3rd party card will solve problem.

(Optic loggers)

Is the Optic Base Station end clean?

If downloading in the sun, it can cause interference with infrared communications.

A dirty coupler, or a coupler with the magnet missing can cause a problem.

A coupler is inserted the wrong way.

Error 6

Weak battery (can appear full, however, when a load is placed upon it, battery will drain rapidly).

W98 & W2K - If you are getting an Error 6 or 9, try this: go to start/Settings/Control Panel and double click the System icon.  Click on the Performance tab, then click on the Graphics button near the bottom center of the screen.  Under Advanced Graphic Settings, move the Graphics Acceleration slider over one notch to the left--usually to the 3/4 mark (note the original position of the slider in case you want to change it back later).   Click OK, then click CLOSE.  The computer should ask you to restart--say Yes.  After the computer has restarted, open BoxCar and retry.

XP - If using a serial port (not USB adapter), go to start/Settings/Control Panel and double click the System icon.  Click on Hardware/Device Manager/Ports-COM & LPT and double click the Port being used.  Click on Port Settings/Advanced and remove the check from "Use FIFO buffers" and click OK.  Retry BoxCar.

Error 7

Creator Checksum error.  Remove and reinsert battery (will sometimes clear it up), else, logger has to be returned for programming.

Error 9 - The COM port chosen to run BoxCar is the same as the modem COM port.

If you receive an Error 9 on a laptop, and the laptop is running on battery power, try plugging it in, and re-download the logger or shuttle.

If the customer buys a Palm and installs the HotSync software on the computer, you will receive an Error 9 until the HotSync Manager is disabled (right click on the HotSync icon in the System Tray, left click on Exit).

If the customer buys PC Anywhere (or any other program that uses the serial port), the program must be disabled before BoxCar can communicate.

A low or weak battery will cause an error 9.

If you are getting an Error 6 or 9, try this: go to start/Settings/Control Panel and double click the System icon.  Click on the Performance tab, then click on the Graphics button near the bottom center of the screen.  Under Advanced Graphic Settings, move the Graphics Acceleration slider over one notch to the left--usually to the 3/4 mark (note the original position of the slider in case you want to change it back later).   Click OK, then click CLOSE.  The computer should ask you to restart--say Yes.  After the computer has restarted, open BoxCar and retry.

XP - If using a serial port (not USB adapter), go to start/Settings/Control Panel and double click the System icon.  Click on Hardware/Device Manager/Ports-COM & LPT and double click the Port being used.  Click on Port Settings/Advanced and remove the check from "Use FIFO buffers" and click OK.  Retry BoxCar.

Error 11 -model number has changed, logger or shuttle has to be sent in for reprogramming.  Model number changed means that the logger has lost its programming in its header (which identifies it as a specific logger with a specific serial number).  What causes this?  If the logger gets disconnected prematurely from the shuttle (or the computer during launch, relaunch, or readout), it could cause the logger to have an error 7 or 11.  Error 7 is usually recoverable, however, error 11 can be fatal.  What happens is that the logger is either being programmed with an instruction set, and communication is broken off before it has received the entire set of instructions from the computer or the shuttle.  Dependent upon where the break occurs and where the hexadecimal numbers land will determine the error message and resultant corruption. 

Corrosion to the EEPROM is also another cause of error 11.