Historical track data reading of Holux m1200-e Bluetooth GPS track recorder

HOLUX M1200-E bluetooth GPS The historical track data of the track recorder is read

The picture is too bad to upload   primary Word File download address   Click to open the link http://download.csdn.net/download/cp459584547/9950331

 

This blog doesn't talk about how to read GPS Historical track data and interest point data of the equipment . How to parse GPS Real time data received by the device , Just say more , There are many on the Internet , Search a lot of

Hardware environment ：HOLUX M1200-E

development language ：C#

The idea of capturing data comes from , First, through the official client HOLUX ezTour for Logger Connecting device , And then use AccessPort137 The serial port packet grabbing tool grabs The client is reading GPS Some commands sent when equipment track data , First, let's preview these commands

Some of the previous commands are useless , until $PMTK182,2,8*33,

inquiry RCD Address , Namely The address to which the next data of the current device will be recorded , The device answers

$PMTK182,3,8,000508D4*63, The answer means The device has recorded 508D4（16 Base number ） So many bytes of data

Then what we have to do next is Call the command to read all these bytes , The command to read device data is

Express From address 0 Start reading , The read direct length is （8000H） Bytes , The effect of this official program to read data in batches , Of course, in order to save trouble, I read all the data at one time So order Namely $PMTK182,7,0, 508D4*（ XOR check bit ）, Think like this, after the device sends a command The device will return a lot of 16 The string of the base , that Where is the historical trajectory data we need ,

After some research, my younger brother found that , The historical trajectory data is here 16 In hexadecimal string characters , The middle item is continuous AAAAA、FFFFF BBBBB Wait, these are bad data , I don't know what the equipment is stored . But there is one law That's it   These useful data are based on 20 Store one in bytes GPS Coordinate point information , After sorting out the following

among Yes 484F4C55584D31323030574159504E5420202020 Such a string appears many times , After some research, this is a few letters ASCII code Which translates as HOLUXWAYPNT, Interest point means , Then there are those arrays left That's the historical track , One point 20 Bytes , The first three data bytes are time - longitude - latitude -【】-【】, The last two haven't been studied . Please let me know when a friend finds the rule ！

such as FF217859, You need to turn it upside down 597821FF And then convert to 10 Base number 1501045247 It's a time stamp , In the conversion to time is

E693F441 Namely Float Data storage 16 Base form , Just change it ,

The last two haven't been studied , How to analyze

That's it Can handle GPS All the track data of the device has been read out .

What needs to be noted is , These data are not arranged neatly Every time the switchgear produces a lot of bad data . use hexOnly.Split(newstring[] { "BBBBBBBBAAAAAAAAAAAAAA0702010000BBBBBBBB","FFFFFFFF2ABFBBBBBBBB" },StringSplitOptions.RemoveEmptyEntries); After the explosion Each array is divided into 40 A string is parsed at a time then Judge Whether the longitude and latitude are within the scope of China , Basically, there will be no mistakes .

 

The appended drawings

HOLUX ezTour for Logger The trajectory data read by the official program

Red Just the point of interest , After zooming in

 

My program The track read out And points of interest

 

Source code ？ The principles are posted , Just write the code yourself , If you're too lazy to write and really need source code , I believe you Can find my mailbox ！