Tk103 Engine Stop/Resume command not working in 60-70% of cases.
Even the IP address of the device remains the same and also updating the latest positions successfully. What can be a possible cause of this problem? Is there anything else I'm missing?
My guess is that it's either device issue or network issue.
OK, Thanks I'll check with other devices and will let you know.
Anyway I think that it's Circuit control signal command doesn't exist into the Traccar. Would you please implement it. It's already into the protocol documentation provided onto the List of Protocols page.
Dear Anton,
I can implement it my own and send a PR. Please confirm what would be the better name for the command?
Might be circuitOn / circuitOff ? Because device has two cords to control engine on/off.
Thank you.
What's wrong with existing commands?
The problem is that here most of the engineers are using circuit control cord.
Some are moving from other tracking platform to ours and old platforms were using circuit control cord as Engine On/Off
I still don't understand the issue.
Ok,
The existing Engine On/Off commands are working fine if oil wire is used to control Engine On/Off. There is no issue in that implementation.
The problem is that a manager type user is started using our platform ( Traccar ) and he already have Tk103 device deployed into the cars. He is using control circuit wire to get the Engine On/Off into the other platform (Server and App). So either we give them new command based on circuitOn / circuitOff or he had to manually change the wire one by one into the cars.
I can use custom commands but find it better to implement into the system.
There is output control command that you can use, specifically for this case.
I think it's not supported into the TK103 protocol. Is it?
Not yet, but isn't that you want to implement?
OK, Got you. You are asking about using control circuit command into the name of output control. Means If I'm sending this command then I have to select Output Control. Am I right?
I'm going to implement it.
Thanks you very much.
But one more thing how to identify On/Off via a single command?
Hi,
I have checked everything like commands queue ( whether it's into the queue ), protocol timeout ( by removing or adding like 120 seconds ) but it's not working. Other protocols like Gt06 working instantly. System logs showing commands sent. But if we try 3-4 times after some intervals then it works only for 2-3 times only.
It's only a problem with TK103 only. The device is working smoothly with another tracking platforms.