-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not send commands #659
Comments
Attached you also will find traccar config files |
The reason of this issue is that such command is not supported by the device:
|
Thank you very much Please let me know, what should I do to solve this problem |
You need to implement this particular command for the protocol your device is using. All commands sending is implemented on the "backend" project: https://github.com/tananaev/traccar According to this particular file the "Position periodic" is actually implemented: https://github.com/tananaev/traccar/blob/master/src/org/traccar/protocol/H02Protocol.java However, it's support is not yet released, i.e. it is not included in traccar 3.5. So you should either build it yourself from sources or wait until traccar 3.6 is released. |
Thank you very much I'm new using traccar, what the tab ¨ import¨ is for |
You can import positions for device from a GPX file. |
Thank you very much |
@inghenryh message from your screenshot is completely different from the message from @Ruben1966 It actually means that command has been sent successfully. |
and because only appears {}? should not appear "the command has been sent"? 2016-05-31 13:38 GMT+08:00 Vitaly Litvak [email protected]:
|
I install the traccar-windows-32-3.5.zip (date 17-Apr-2016), but when I sent a command it show me the next error:"{"reason":"java.lang.reflect.InvocationTargetException: null","success":false}", please see the attached image.
You will find attached the traccar config files and logs files
Please help me to fix this trouble
Best regards
Ruben
services wrapper logs .docx
traccar server logs.docx
The text was updated successfully, but these errors were encountered: