Track My Order
Frequently Asked Questions
International Shipping Info
Mon-Fri, 9am to 12pm and
1pm to 5pm U.S. Mountain Time:
November 1, 2008
about 12 years ago
this morning I received the Lpc2148. I just tried to power it via USB and the NXP chip becomes after few seconds extremely hot. I also tried to use two different power supply (6v and 5 V) and the capacitor close to the power supply and the chip become hot as well. Is it normal? Is it drawing too much current?
about 13 years ago
ok, how do I send you the code?
FYI the code contains the following fixes:
1)Current data in buffer was discarded when Usb cable was connected
2)problem when an interrupt occurred when the data was being saved (device froze)
3)if the '\n' was lost when parsing nmea str no check for buffer overrun, memory was corrupted
In addition, I added the following:
1)if configured save data in binary mode to save space/improve speed
2)(attempt to) recognize doubleclick to stop/restart recording data
3)add fields in the config file to change the freq of gps recording and accel recording; save nmea commands,add accel calib
4)In the text file, gps data is recorded in a decimal format directly usable in google maps/earth
5)added a tool to create kml files from the binary data for Google earth (drag&drop) to display the recorded gps path
6)added a tool to generate txt file with accel data from the binary data (accel data recorded w/ RTC)
Thanks for the help.
I fixed a few problems in the firmware and added a couple of features that I needed.
If you are interested I can write a simple readme and give you the code.
Hope it helps
Hopefully I'm not taking (too much) advantage of your patience but I have another question. I see the following file on the logical disk (3,491,536 bytes; apparently created September 08, 2008, 1:03:37 PM):
03 Turn the Lights Out.m4p
I haven't find any description on your web site. What's the use of that file?
thanks for the prompt response. Yes I had waited long enough. This is another exzample (from a different location), after more then 100 readings there was an error of more than 25 miles from the physical position of the device.
Forgive me for the second naive question.
I left the kinetamap horizontal for several minutes. The log contains the following entries for the steady period:
The GPS is putting me in the middle of the Arizona desert; however, what is really confusing me are the accelerometer readings. I was expecting to see 1g on the z axis and 0 on x and y. I'm not sure why y is always reporting 255 and what's the default scale.
When in the user guide you say "it?s up to you to decipher what they mean!", I didn't expect to be this cryptic.
Forgive me for asking a naive question. In the Kinetamap Firmware 1.1 I see these defs:
However, if I check the the datasheet (KinetaMap v14 8/1/2008) I see STAT1 pointing to Port 16 P1.16 (as in the define) while STAT0 points to port 12 P1.17. Should these match?
No public wish lists :(