Troubleshooting – Eagle Tree eLogger V3 User Manual

Page 9

Advertising
background image

Copyright © 2003-2007 Eagle Tree Systems, LLC

Page 9

The format of each line of data in the file is:

First Line: Model Name
Second Line: Data about your Model’s setup. This line is needed to allow sharing of your session log files with others.
Third line: header indicating what each of the data fields represents. These columns are:

If “IsEvent” is 1, the record contains event data as well as regular data. Typical events are power-up (restart), and servo glitches.
Ignore the non-event fields when IsEvent is set to 1.

Event Codes in the “EventCode” field are as follows. Note that codes other than those below should be reported to Eagle Tree
Systems:

9 = ERROR_RESTART: The eLogger has been started or restarted (power was applied)

18 = ERROR_GPS_DATA_PACKET: GPS Data was received from the GPS Expander,

27 = ERROR_SPEKTRUM_DATA_PACKET: Data was received from the AR9000 Interface

Milliseconds indicates when each record was collected, in Milliseconds since the eLogger was turned on.
Email us if you need more information on the file format.

Happy Modeling!!

Troubleshooting


Below is a list of problems that may be encountered, and steps to remedy them.

A good first step to troubleshooting, if you are able to connect your eLogger to your PC, is to download our latest software and update
the eLogger’s Firmware via “Hardware, Firmware Control.” Doing this will ensure that you have the latest software and firmware
available.

If your particular issue is not addressed by this update, or by the suggestions below, please visit our web support page for additional
support options, at

http://www.eagletreesystems.com/Support/support.html

.

Issue: My PC does not recognize the eLogger.
Solution: Try to eliminate the problem in the following ways:

o

Disconnect all other USB peripherals from your PC (if possible) and try the eLogger again.

o

Try the eLogger on a different PC. If it works, there may be a misconfiguration with your PC.

o

Try the eLogger with a different USB cable, if you have one. If this works, your cable has been damaged.

o

Try rebooting your PC – occasionally USB support gets disabled with some PCs.

o

Try the other USB connector on you PC if it has two.

o

Ensure that USB is enabled within your Operating System by checking in Device Manager. You’ll need to see your
Windows™ documentation to determine how to do this on your particular OS version.


Issue
: RPM is not working correctly (note: also see the Optical or Brushless RPM Sensor instruction manual if you are using the
Optical or Brushless RPM Sensor)
Solutions:

With the magnetic sensor, check to make sure your sensor to magnet gap is around 2mm or less.

Check the magnet polarity mounting. The magnet should have been glued so that the red line faces down, away from the
sensor, and the writing on the sensor faces the magnet. If you inadvertently glued the magnet so that the red line is facing
UP, flip the sensor over so the "non printed" side faces the magnet.

Make sure that under Choose What to Log in the app, you have checked RPM.

Make sure that the RPM sensor is plugged into the correct slot on the eLogger

Connect the eLogger to the computer and launch the Windows Application. Then, click the “Live Mode” button. Make
sure that the RPM gauge is displayed, and spin the magnets, or wave the magnets by hand in front of the sensor. Try both
sides of the magnets and both sides of the sensor. See if the RPM reading jumps.

Issue: I have a fully charged battery, but the eLogger frequently shows “Low Battery Restart” Notifications when playing back data.

Milliseconds IsEvent

EventError EventData Altitude Airspeed ServoCurrent*100 Throttle

PackVolt*100

Amps*100

Temp1*10

Temp2*10

Temp3*10

RPM

RPM2

GPSLat

GPSLon GPSAlt

GPSSpeed

GPSCourse GPSDist

GPSUTC

NumSats GPSFlags

Advertising