Unknown device called Nems protocol?

TTRACK MOHSENa year ago

Hello everybody,
Can you help me decoding a GPS tracker frame coming from a clone called Nems Tracker:
Hexadecimal data frame I receive on the server is:

31333638313520414130303030303031303036303138304032332f30342f30392c32333a35323a33322b3034202c4943433a38393231363032303830323137313432373133462c20494d45493a3836323433303035303236313435380d0a414130314d46322d57303532312d4143492d464d532d322e302e302e315230304330322c204943433a38393231363032303830323137313432373133462c20494d45493a3836323433303035303236313435380d0a0a0d0a414141410d0a0a0d0a41413333303030303030303030303030303030303030303030303030303030303030303030303030303032333830303030303030303030303034303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030300d0a41413233303033373838303030303030303030303030303030303030303030303241303046463030303141303830303030303030303030303031303030303030303032314431303030303030303030303030303030303030303030303030303030303030303030430d0a41413233303030303030303030303030303030303030303030303030303030303030303030303030303032333830303030303030303030303034303030303030303030303030303030303030303030303030303030303030303030303030303030303030303030300d0a41413233303033394635303030303030303030303030303030303030303030303030303046464645303232303830303030303030303030303031303030303030303032314431303030303030303030303030303030303030303030303030303030303030303030300d0a41413233303033413335303030303030303030303030303030303030303030303030303046464645464532303830303030303030303030303031303030303030303032314431303030303030303030303030303030303030303030303030303030303030303030300d0a41413233303033413731303030303030303030303030303030303030303030303030303030314646303132303830303030303030303030303031303030303030303032314431303030303030303030303030303030303030303030303030303030303030303130300d0a41413233303033414144303030303030303030303030303030303030303030303030303046464646464532303830303030303030303030303031303030303030303032314431303030303030303030303030303030303030303030303030303030303030303030300d0a

coverted to text it give :

136815 AA00000010060180@23/04/09,23:52:32+04 ,ICC:8921602080217142713F, IMEI:862430050261458
AA01MF2-W0521-ACI-FMS-2.0.0.1R00C02, ICC:8921602080217142713F, IMEI:862430050261458


AAAA


AA330000000000000000000000000000000000000023800000000000040000000000000000000000000000000000000000000000
AA2300378800000000000000000000002A00FF0001A0800000000000010000000021D1000000000000000000000000000000000C
AA230000000000000000000000000000000000000023800000000000040000000000000000000000000000000000000000000000
AA230039F500000000000000000000000000FFFE0220800000000000010000000021D10000000000000000000000000000000000
AA23003A3500000000000000000000000000FFFEFE20800000000000010000000021D10000000000000000000000000000000000
AA23003A710000000000000000000000000001FF0120800000000000010000000021D10000000000000000000000000000000100
AA23003AAD00000000000000000000000000FFFFFE20800000000000010000000021D10000000000000000000000000000000000

What I see on the converted frame is IMEI, Date, ICCID... but I dont know how to decode GPS data and other input output data, it seems that they are also in hexadecimal after converting.

Please help to find the right protocol.

Anton Tananaeva year ago

Do you have the protocol documentation?

TTRACK MOHSENa year ago

Hello,
No I dont have documentation :(

Anton Tananaeva year ago

I don't think we support this protocol, but hard to tell for sure without the documentation.