I’m not able to log any acceleration values. I have tried with original firmware, 1.1.2 and 1.2 versions and each one logs only static values for X,Y,Z -axels. Resolution or sample rate change does not change the situation or values. GPS logging is working just fine.
Is this hardware related issue? My KinetaMap is brand new and purchased via one of SparcFun’s distributor.
Please help
-Teemu
edit: terminal output
----------- KinetaMap Config Menu -----------
FW Version 1.2
SparkFun Electronics
-
Read directory
-
Read file
-
Delete file
-
Format SD card
-
Listen to GPS (press any key to stop)
-
Check Accelerometer(press any key to stop)
-
Change settings in the config file
-
Exit menu and start logging
Current Settings:
Menu: 1
GPS Logging: 1
Accel Logging: 1
GPS over BT: 0
Battery Logging: 1
NMEA Logging: 1
WAAS Enabled: 0
Accel Range: 1
RMC Messages: 0
GGA Messages: 1
Accelerometer Frequency: 20
Option = 6
X=-14 Y=0 Z=0
X=-1 Y=0 Z=0
X=-1 Y=0 Z=0
X=-1 Y=0 Z=0
X=-1 Y=0 Z=0
X=-1 Y=0 Z=0
X=-1 Y=0 Z=0
X=-1 Y=0 Z=0
Just from sitting at my desk and looking at your data, it looks like there’s either a problem with the accelerometer and/or communication with it.
I would only expect readings like those from a stationary accelerometer in 0g or with the high pass filter enabled.
By the way there are a number of bugs in the KinetaMap software. The importance of them to you depends on what it is you’re trying to do. I sent a bunch of fixes to SFE, but they haven’t done anything with them.
None of the bugs I found would cause you to get the accelerometer readings that you’re seeing. You should probably e-mail SFE’s tech support. I had an accelerometer that was out of spec on one axis and SFE’s tech support was very responsive. They helped me exchange it for a device that was in spec.
-Michael
mdipperstein:
Just from sitting at my desk and looking at your data, it looks like there’s either a problem with the accelerometer and/or communication with it.
I would only expect readings like those from a stationary accelerometer in 0g or with the high pass filter enabled.
By the way there are a number of bugs in the KinetaMap software. The importance of them to you depends on what it is you’re trying to do. I sent a bunch of fixes to SFE, but they haven’t done anything with them.
None of the bugs I found would cause you to get the accelerometer readings that you’re seeing. You should probably e-mail SFE’s tech support. I had an accelerometer that was out of spec on one axis and SFE’s tech support was very responsive. They helped me exchange it for a device that was in spec.
-Michael
Thx for fast response. At first I'd like to see this working as described. My idea is place it to big RC helicopter and collect flight data. GPS to draw flightpath with alt. and Accelerometer to measure G's. Later on my plan is to customize firmware to provide more accurate speed information by combining GPS and accelerometer data and send it realtime to ground station by using Bluetooth.
Hopefully SFE’s tech support will help you get you KinetaMap working. My experience with them was very positive.
It’s been a few months since I used our KinetaMap, but there’s one bug I remember that might be a problem for you. The code that verifies the checksum of GPS sentences doesn’t handle A-F in hex correctly. As a result any sentence that contains at least one A-F in its check sum will be thrown out.
-Michael