JM-VL01 Device - Protocol?
Have you tried asking them? It's probably using the same protocol or one of the other common protocols that are supported.
Can someone confirm that the JM-VL01 is working with traccar?
Hello, this is Jessie from JIMI&Concox, anyone from traccar can contact me for VL01, VL03 integration?
The 4G GPS trackers are not using the same protocol as 3G or 2G which traccar has integrated.
Looking forward to your reply, thanks.
You can contact support email address.
Did the JM-VL01 or JM-VL03 ever get integrated?
having same need :(
This new protocol is now supported?
My bad, sorry about that, for the record VL03 works correctly
Salvador
Which port number did you use?
Thanks
Geoff
for the record VL03 DOES NOT WORK CORRECTLY. At least with CONCOX protocol port 5023
it does not send SOS ALARM
Other functionalities works fine but for some reason traccar does not recognice SOS Alarm
Hi,
You need to add some changes to file Gt06ProtocolDecoder.java on the method hasStatus, just add on the switch statement the event 0xA4, and the sos command will be recognized.
Hello Anton, I have version 5.0 that works perfectly for me with various devices, except that the JM-VL03 device does not receive SOS and battery cut alerts, I would like to know if it is possible to fix this protocol (gt06) for this version of Traccar without affect the operation of the other Concox that use the protocol and that work correctly. Is this arrangement possible? Obviously paying the professional fees to which there is place
Should be possible. Send us an email to discuss.
Hi, is there an update on this issue? I'm trying to get my JM-VL01 to work with a local traccar server. As far as I can see, router/firewall settings are ok; the traccar log shows that there's incoming traffic on the gt06 protocol. But the device shows as offline on the map. Here's a part of my log file (to check, I also set up a traccar client app which works without any problem.
Thanks & regards,
Sven
2023-02-20 11:01:50 INFO: Operating system name: Linux version: 5.15.84-v8+ architecture: aarch64
2023-02-20 11:01:50 INFO: Java runtime name: OpenJDK 64-Bit Server VM vendor: Debian version: 17.0.6+10-Debian-1
2023-02-20 11:01:50 INFO: Memory limit heap: 950mb non-heap: 0mb
2023-02-20 11:01:50 INFO: Character encoding: UTF-8 charset: UTF-8
2023-02-20 11:01:50 INFO: Version: 5.6
2023-02-20 11:01:50 INFO: Starting server...
2023-02-20 11:01:51 INFO: HikariPool-1 - Starting...
2023-02-20 11:01:53 INFO: HikariPool-1 - Added connection conn0: url=jdbc:h2:./data/database user=SA
2023-02-20 11:01:53 INFO: HikariPool-1 - Start completed.
2023-02-20 11:01:53 INFO: Set default schema name to PUBLIC
2023-02-20 11:01:53 INFO: Clearing database change log checksums
2023-02-20 11:01:54 INFO: Successfully acquired change log lock
2023-02-20 11:01:54 INFO: Successfully released change log lock
2023-02-20 11:01:54 INFO: Successfully acquired change log lock
2023-02-20 11:01:58 INFO: Reading from PUBLIC.DATABASECHANGELOG
2023-02-20 11:01:59 INFO: Reading from PUBLIC.DATABASECHANGELOG
2023-02-20 11:02:00 INFO: Successfully released change log lock
2023-02-20 11:02:05 INFO: jetty-10.0.13; built: 2022-12-07T20:13:20.134Z; git: 1c2636ea05c0ca8de1ffd6ca7f3a98ac084c766d; jvm 17.0.6+10-Debian-1
2023-02-20 11:02:05 INFO: Started o.t.w.@3e9beef2{/,null,AVAILABLE}
2023-02-20 11:02:05 INFO: Session workerName=node0
2023-02-20 11:02:07 WARN: JAXBContext implementation could not be found. WADL feature is disabled.
2023-02-20 11:02:09 INFO: Started o.e.j.s.ServletContextHandler@319b1c77{/,null,AVAILABLE}
2023-02-20 11:02:09 INFO: Started ServerConnector@8c0a23f{HTTP/1.1, (http/1.1)}{0.0.0.0:8082}
2023-02-20 11:02:09 INFO: Started Server@cf01c2e{STARTING}[10.0.13,sto=0] @21164ms
2023-02-20 11:02:09 INFO: Health check enabled with period 480000
2023-02-20 11:03:48 INFO: [T2beb65d7] connected
2023-02-20 11:03:48 INFO: [T2beb65d7: gt06 < 89.183.13.xxx] 1603010200010001fc03038f7f9cd0094e00ac00e33403ef4b77127784707f5919fcdd233f347a945795be20e96804d4dd2b2bd7d7baeef1e02ba2b42baf1f9ef7100ce90c4b7ff98>
2023-02-20 11:03:57 INFO: [T2beb65d7] disconnected
2023-02-20 11:03:57 INFO: [T3b363373] connected
2023-02-20 11:03:57 INFO: [T3b363373: gt06 < 89.183.13.xxx] 1603010200010001fc0303e0636f50a1499f41818e278f99a83b8297d26a0907a6dfdb55f2737b49d55b6a203a9d0c5cfd46e526a7355ceb842c67e98052bcc5cc72512c8173e661a>
2023-02-20 11:04:06 INFO: [T3b363373] disconnected
2023-02-20 11:04:06 INFO: [Td8ce8906] connected
2023-02-20 11:04:06 INFO: [Td8ce8906: osmand < 89.183.13.xxx] 1603010200010001fc03036ac5d59c20df5f665ef3f94081d31853df8e65e12a884e1f4ee7b45a1440e40520c4895efa1af958be1c0f0848c99cb407e674d9bae46cbad9270ec21>
2023-02-20 11:04:06 INFO: [Td8ce8906: osmand > 89.183.13.xxx] 485454502f312e31203430302042616420526571756573740d0a636f6e74656e742d6c656e6774683a20300d0a0d0a
2023-02-20 11:04:07 INFO: [Td8ce8906] disconnected
2023-02-20 11:04:12 INFO: [T266e5855] connected
2023-02-20 11:04:13 INFO: [T266e5855: gt06 < 89.183.13.xxx] 1603010200010001fc03039b9d3ed65d514c10123ae97edfcf0ea674c5cf28e177b9f2332c02b267179fb220f592d0a60354a0b0c2fce56342111fc539fecdf5d64d06f82b57590b7>
2023-02-20 11:04:43 INFO: [T266e5855] disconnected
Hi there,
Does anyone use the JM-VL01 Device(https://www.jimilab.com/products/jm-vl01-lte-vehicle-terminal.html) ? It’s the successor of the GT06E Device from Jimi iot. I haven’t found which Protocol it uses, the predecessor uses the GT06 Protocol.
Does anybody know if the Device is supported, and which Protocol it does use? I don’t want to order one and cannot use it.
Thanks for your Help!
Frank