Problem with J16 connection

Auto Rastreio19 days ago

I configured the J16 device with port 5023, it is connecting, cutting off fuel, location and everything else.

However, it is entering a state where the ignition icon does not appear and when I turn on the vehicle, no notification is sent.

Then, if I turn off the vehicle and wait for the engine icon to turn off and then turn on the vehicle, the notification is sent.

I have already reinstalled the traccar server without any changes.

No server log is saved

Cristian19 days ago

First you say that the power icon does not appear and then that you wait for it to turn off.
Does the icon appear or not at any point?

Did you try adding ignition to the attribute copy?

Auto Rastreio19 days ago

When I turn on the car, the icon appears and turns green (on). As soon as I turn it off, it still appears gray (off). During the period that the icon is appearing, if I turn on the vehicle, a notification is sent.

After a period of time, the icon disappears and if I turn on the vehicle, the green icon appears again, but no notification is sent. Only if I do the same process as mentioned above

Cristian19 days ago

then the problem is with the power-on notification?

Anton Tananaev19 days ago

If the ignition icon doesn't appear, it probably means your device didn't report it. Check logs and protocol documentation for your device.

Auto Rastreio19 days ago

O dispositivo utiliza o protocolo gt06, está configurado corretamente.
Ele identifica a ignição, mas o ícone desaparece. Quando desaparece não é enviado notificação

Cristian19 days ago

I insist on the copy of attributes then.

I use those devices and they work perfect for me

Auto Rastreio19 days ago

What commands do you use to configure?

Cristian19 days ago

GMT,E,0,0#
SZCS#SERVIP=tudominio.com#SERVPORT=5023
SZCS#APN=tuapn

SZCS#GT06IEXVOL=2 vehicle voltage

then the TIMER

https://we.tl/t-vgZ3vxvQOD

RastreameMX18 days ago

Your problem is on the protocol you are using. On J16 ignition is not reported on every position.

J16 can be configured to report using GT06, Huabao and H02 protocol. I don't remember exactly how, but GT06 can be configured to use some as "extended" protocol where it reports more complete attributes.

Other solution could be configure device to report as H02 with "new" version. Commands for J16 devices to change protocols are these :

SZCS#PTL_SEL=
0 for H02, 1 for Huabao and 2 for GT06

SZCS#GT06SEL=
0 and 1, don't remember exactly but maybe 1 is extended GT06 format (it reports better ignitions)

SZCS#808SEL=
0 for 2011 version of 808 protocol (Huabao), 1 for 2013 version of huabao protocol (as far as i remember, 2013 is most complete and it reports better on ignitions)

Not necesary to say that depending on what format you configure on PTL_SEL, you must to change SERVPORT too according.

Greets.

RastreameMX18 days ago

Sorry, i forgot to mention : Indeed attribute copy could be an option to fix trouble, but it's safer to configure a protocol that reports complete attributes, because even if you configure attribute copy of "ignition", if your device is not able to report position where "ignition=false" was set, your device never is going to report ignition off, and even it would keep reporting ON until next position with attribute "ignition=false" arrives.

Always is better to configure complete attribute protocols. It uses more carrier fees, but it's safer, because on each position you have full attributes and can manage better when it changes.

Greets

4574789554758 days ago

Did you manage to solve the problem? my j16 does not turn off the engine when the command is assigned to a notification