-
Notifications
You must be signed in to change notification settings - Fork 24
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
Unexpected error #23
Comments
Hello, have you known why those " unknown message type " errors occurred? |
Unfortunately No I don’tOn Jan 14, 2024, at 8:58 AM, randydom ***@***.***> wrote:
Hello, have you known why those " unknown message type " errors occurred?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@AgentVicman007 sorry for late reply The other unknown message type 160 (0xA0) was also not sent by my tracker. Is the lib otherwise working for you? Are you getting location updates? |
@vondraussen 0x7979 is the format for some GT06 devices like Concox GT08. It's used as start indicator for Location messages. Here more info about this protocolo https://www.traccar.org/protocol/5023-gt06/S20WanWayProtocol2021.03.22V21.pdf |
Hello,
I'm hoping you can help me out. I have a GT06 and it's sending requests to my server using your code. and I'm seeing
client connected
started server on port: 64459
client connected
{
expectsResponse: true,
imei: 352672107482515,
serialNumber: 1,
responseMsg: <Buffer 78 78 05 01 00 01 d9 dc 0d 0a>,
event: { number: 1, string: 'login' },
parseTime: 1703714944097
}
err {
error: 'unknown message type',
event: { number: 138, string: 'unknown' }
}
err {
error: 'unknown message header',
msg: <Buffer 79 79 00 08 94 00 04 8f 00 d2 48 15 0d 0a 79 79 00 20 94 0a 03 52 67 21 07 48 25 15 03 10 24 02 01 37 35 57 89 01 24 02 04 11 37 35 57 4f 00 9a 43 00 ... 2 more bytes>
}
{
expectsResponse: true,
terminalInfo: {
status: false,
ignition: false,
charging: true,
alarmType: 'normal',
gpsTracking: false,
relayState: false
},
voltageLevel: 'high',
gsmSigStrength: 'good signal',
imei: 352672107482515,
responseMsg: <Buffer 78 78 05 13 00 01 e9 f1 0d 0a>,
event: { number: 19, string: 'status' },
parseTime: 1703714946096
}
{
expectsResponse: true,
terminalInfo: {
status: false,
ignition: false,
charging: true,
alarmType: 'normal',
gpsTracking: false,
relayState: false
},
voltageLevel: 'high',
gsmSigStrength: 'good signal',
imei: 352672107482515,
responseMsg: <Buffer 78 78 05 13 00 01 e9 f1 0d 0a>,
event: { number: 19, string: 'status' },
parseTime: 1703715246401
}
err {
error: 'unknown message type',
event: { number: 160, string: 'unknown' }
}
err {
error: 'unknown message type',
event: { number: 160, string: 'unknown' }
}
err {
error: 'unknown message type',
event: { number: 160, string: 'unknown' }
}
err {
error: 'unknown message type',
event: { number: 160, string: 'unknown' }
}
Would you be able to help me out with what the error above means?
The text was updated successfully, but these errors were encountered: