Mictrack 4G GPS Tracker MT600 Feedback

Hi Mictrack, Anton

Have you tested the MT600 Plus-E on Traccar?
I see it connecting in the logs, but its not doing anything else (no data getting to DB / UI)

here are my logs

2018-10-25 11:46:26  INFO: [5b33d19b: 9030 < 31.210.232.51] HEX: 23383637393632303430313631393535234d54363030233030303023302330233133372334312330234155544f23310d0a233030303139303233343032244750524d432c3038343730322e30302c412c333232382e363737322c532c31313534352e393638342c452c2c3135392e38302c3235313031382c2c2c412a35360d0a23230d0a
2018-10-25 11:46:56  INFO: [5b33d19b: 9030 < 31.210.232.51] HEX: 23383637393632303430313631393535234d54363030233030303023302330233133372334312330234155544f23310d0a233030303139303233343032244750524d432c3038343733322e30302c412c333232382e363737322c532c31313534352e393638352c452c2c3135392e38302c3235313031382c2c2c412a35340d0a23230d0a
2018-10-25 11:47:26  INFO: [5b33d19b: 9030 < 31.210.232.51] HEX: 23383637393632303430313631393535234d54363030233030303023302330233133372334312330234155544f23310d0a233030303139303233343032244750524d432c3038343830322e30302c412c333232382e363737322c532c31313534352e393638352c452c2c3135392e38302c3235313031382c2c2c412a35380d0a23230d0a
2018-10-25 11:47:56  INFO: [5b33d19b: 9030 < 31.210.232.51] HEX: 23383637393632303430313631393535234d54363030233030303023302330233133372334312330234155544f23310d0a233030303139303233343032244750524d432c3038343833322e30302c412c333232382e363737342c532c31313534352e393638362c452c2c3135392e38302c3235313031382c2c2c412a35450d0a23230d0a
2018-10-25 11:48:26  INFO: [5b33d19b: 9030 < 31.210.232.51] HEX: 23383637393632303430313631393535234d54363030233030303023302330233133372334312330234155544f23310d0a233030303139303233343032244750524d432c3038343930322e30302c412c333232382e363737332c532c31313534352e393638352c452c2c3135392e38302c3235313031382c2c2c412a35380d0a23230d0a

here is an example decoded message

#867962040161955#MT600#0000#0#0#137#41#0#AUTO#1
#00019023402$GPRMC,084702.00,A,3228.6772,S,11545.9684,E,,159.80,251018,,,A*56
##

I've tried version 3.15, 3.17 and the latest version 4.1 but neither work
Any ideas?

Looks like it doesn't match old documentation. Please ask vendor for updated one.

Hi,

MT600 Plus is a upgrade version of MT600. It will report some new data such as Door status, Fuel voltage, Car battery voltage, Backup battery voltage , temperature, other are the same as MT600 Protocol.

For example the report sentence is:
#861108034748748#MT600 Plus#0000#1#47#118#39#269#AUTO#1

1--> Door status (1=Door close, 0=Door open)
47-->Fuel Voltage (47 means 4.7V)
118-->Car battery voltage (118 means 11.8V)
39-->Backup battery voltage (39 means 3.9V)
269-->Temperature (269 means 26.9℃)

This is the protocol: https://www.mictrack.com/downloads/protocols/Mictrack_Communication_Protocol_For_MT600_Plus_V1.0.pdf

Thanks,
Mictrack

Thanks Both for the quick response

So to confirm, traccar doesn't support the newer model since it has additional parameters?
Anton is the documentation MicTrack provided sufficient?

I have fixed the problem.

Thanks Anton, that was quick!

I assume this will be in 4.2, but since 4.1 is quite new I presume that will take some time

If I wanted to run this code base how can i install it from a packaged windows install?

We plan to release 4.2 relatively soon because there were many issues with 4.1. You can just wait.

Oh wow, I have just received my MT600-Plus E from NZ POST and I was wondering why my logs in tracker-server.log weren't decoding, and then I was wondering why the decoded HEX wasn't matching up with the tlt2h protocol in your troubleshooting guide.

Guess I'll be looking through "Upgrading Traccar" in the days ahead aye :D

Hi Anton

Is the protocol decoder for the MT600Plus vehicle tracker from Mictrack included in the 4.2 update?

I have upgraded but Im still getting...

2018-11-13 13:54:11 DEBUG: [5F70D36C: 5030 < 118.149.245.246] HEX: 23383637393632303430313733333135234d54363030233030303023302330233131382334312330234155544f4c4f5723310d0a2330303234313866323034244750524d432c3030353431302e30302c412c343535322e373539322c532c31373033302e313734352c452c312e38302c2c3133313131382c2c2c412a35320d0a23230d0a

...in my logs.

This hex converts to:

#867962040173315#MT600#0000#0#0#118#41#0#AUTOLOW#1
#002418f204$GPRMC,004409.00,A,4552.7369,S,17030.1957,E,0.90,,131118,,,A*54
##

The closest match I can find is with the tlt2h protocol but its still different and I can't find anything that matches my message format exactly.

'tlt2h' : '#123456789012345#V500#0000#AUTO#1\r\n#$GPRMC,123000.000,A,6000.0000,N,13000.0000,E,0.00,0.00,010112,,,D*70\r\n##\r\n'

I saw your GitHub post 2-ish weeks ago saying that code was added to handle the MT600Plus message format.

Have I missed an item in the list of protocols? Where am I going wrong? and do you need any further information from my server? I'm fairly new to Linux CLI and I'm a software engineering novice.

Just tested. Your sample works fine on version 4.2.

Inspecting the post from @Quade dennis I see that in the second line he has at the end of the line a letter, followed by two commas and a number. where as I have a letter followed by a number, followed by two commas. not sure what this means or why I have a discrepancy.

@Quade dennis MT600Plus message

#867962040161955#MT600#0000#0#0#137#41#0#AUTO#1
#00019023402$GPRMC,084702.00,A,3228.6772,S,11545.9684,E,,159.80,251018,,,A*56
##

My MT600Plus message

#867962040173315#MT600#0000#0#0#118#41#0#AUTOLOW#1
#002418f204$GPRMC,004409.00,A,4552.7369,S,17030.1957,**E,0.90,,*131118,,,A54
##

Thanks for the super quick response Anton.
I think I have just found the problem, I may have installed the wrong version twice by way of typos

-__-

Thanks Anton, we also test the MT600 Plus and it works fine.

yahoo! Things are working beautifully and have been reliable for the last 3 days.
Thanks for all your quick feedback guys

Does the MT825 tracker utilize "Communication Protocol V3.5"?

https://www.mictrack.com/downloads/protocols/Mictrack_HSPA&GPRS_Communication_Protocol_V3.2.pdf