WIKIABOUT

FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

4167 questions

4739 answers

3460 comments

0 members

Most popular tags

fmb920 fmb120 configurator fmb640 sms-commands firmware fmb125 fmb001 configuration unlock-code fmb204 bluetooth canbus fmb140 fota-web fmc640 fmc130 firmware-upgrade fmb130 sms
We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.

7275: Setting keyword via SMS

0 votes
1,568 views
in Vehicle tracking by anonymous
Hello! I'm trying to set keyword on our devices via sms with comand like "setkey<space><old keyword><space><new keyword>" but we don't have an "old password", so command transforms to "setkey<3 spaces><new keyword>" and our sms manager compress "3 spaces" to "one space" and devices don't recognise command. Is there some trick to avoid these problem? Maybe use instead of spaces some other symbols?

1 Answer

0 votes
by anonymous

Hello,

There is no option to unlock without old keyword. After 5th try device should be locked then as an response you should receive IMEI number and Lock Code . Contact your sales manager and send IMEI+LockCode. The sales manager will confirm that the device is really yours and will send you an Unlock Code, which you can use to unlock the configuration.

Thank you.

by anonymous

I'm sorry. I put it wrong. There are our devices with NO keywords. We have access to them, but we can't set keywords on it because "old keyword" is empty. So command is "setkey<space><EMPTY KEYWORD><space><new keyword>" is transforms to "setkey<3 spaces><new keyword>"

by anonymous

No worries. Can you try with two spaces?

<Space><Space>setkey<space><space><NewKeyWord>

Also try this, might help: https://wiki.teltonika.lt/view/FMB_setkey

Usual command line looks like this: SMS_login<space>SMS_password<space>setparam...
 

by anonymous

Two spaces also doesn't work. Answer from device is: Wrong keyword simbols.

If command will succesfull should i receive any answer from device?

by anonymous
Tested example When command is sent:

<space> <space> setkey <space> <space> 1234

Response: Keyword saved:1234

Try sending <space> <space> delkey <space>

and then again:

<space> <space> setkey <space> <space> 1234

Reminder:

Min. keyword length is 4 symbols and max. length is 10 symbols. Only uppercase, lowercase letters and numbers are supported.
by anonymous

Ok, i tried to send setkey command via TCP from our server and the result is:

1) FMB125 set keyword succesfully

2) FM5300 send answer #ERROR

3) FM1100 send answer Wrong keyword simbols.

I'm tried to emulate this situation on FM1100 that connected to my computer via USB and watch Terminal, so TCP answer from device is Wrong keyword simbols. and terminal log is:

[2019.07.03 10:35:07]-[OP.SEARCH] GPRS Detected. Search on hold
[2019.07.03 10:35:08]-[AppSend] Task status: TCP1 1, TCP2 0, UDP1 0, UDP2 0
[2019.07.03 10:35:08]-[AppSend] Server 1 data sending task running, wait...
[2019.07.03 10:35:08]-[MODEM] Entering Data Mode
00000000000000160C01050000000E7365746B65792020373339310D0A0100005037[2019.07.03 10:35:08]-[DataProcTCP] Write_idx: 0 Length: 34
[2019.07.03 10:35:08]-[DataProcTCP] Data copied to buffer
[2019.07.03 10:35:08]-[DataProcTCP] Pass: 2000a278 - 2000a256
[2019.07.03 10:35:08]-[DataProcTCP] Codec12 command length: 22
[2019.07.03 10:35:08]-[DataProcTCP] Data: c-1-5-0-0
[2019.07.03 10:35:08]-[DataProcTCP] Command received
[2019.07.03 10:35:08]-[DataProcTCP] Single command received
[2019.07.03 10:35:08]-[DataProcTCP] write: 2000a278 read: 2000a278
[2019.07.03 10:35:08]-[DataProcTCP] Done
[2019.07.03 10:35:08]-[MODEM] Exiting Data Mode
Received events: [, , GPRS_COMMAND]
[2019.07.03 10:35:08]- [CONF.SECURITY]-> Wrong keyword simbols.
[UBUF general info] Free space: 1024 / 1024 (total), stored cmds: 0, write idx: 624, read idx: 624
[2019.07.03 10:35:08]-[U.GPRS] Added to index: 9, start: 624, end: 647, len: 24, type: GPRS, C12 type: 06, CID: 12
Received events: [UNIVERSAL, , ]
[2019.07.03 10:35:08]-[CODEC12] Commands available for sending: 1
[UBUF cmds info] Index: 9, cmd type: GPRS, cmd start: 624, cmd end: 647, len: 24, cmd type: 0x06
cmd 9 data:
57726F6E67206B6579776F72642073696D626F6C732E0D0A
[2019.07.03 10:35:08]-[DataSend] Attempting to send GPRS, cmds found: 1
[2019.07.03 10:35:08]-[DataSend] Read table entry: len: 32 | NOD: 1 | CID: 12 | Type: 6 | Nofdata: 24
[2019.07.03 10:35:08]-[U.GPRS] ubuff cleared from 624 len 24
[2019.07.03 10:35:08]-[DataSend] Packed 24 B to avl send data buffer from 15 to 38 idx. Read idx 624 => 648
[2019.07.03 10:35:08]-[DataSend] Table idx 9 cleared
[2019.07.03 10:35:08]-<< AT+TIPCLOSE?
[2019.07.03 10:35:08]->> +TIPCLOSE: 1
[2019.07.03 10:35:08]->> OK
[2019.07.03 10:35:08]-[MODEM] ok got after 11942 ms cmd event after 11941 ms
[2019.07.03 10:35:08]-[MODEM] RetVal: 1
[2019.07.03 10:35:08]-<< _DATA_
[2019.07.03 10:35:08]->> +TIPSEND: 1,0,2700
[2019.07.03 10:35:08]->> OK
[2019.07.03 10:35:08]-[MODEM.SEND] Data Left:0 bytes
[2019.07.03 10:35:09]-<< AT+TIPSEND?
[2019.07.03 10:35:09]->> +TIPSEND: 1,2700
[2019.07.03 10:35:09]->> OK
[2019.07.03 10:35:09]-[MODEM.SEND] Bytes in modem buffer:44 bytes
[2019.07.03 10:35:09]-<< AT+TIPPUSH=1
[2019.07.03 10:35:09]->> +TIPPUSH: 1,0,165
[2019.07.03 10:35:09]->> OK
[2019.07.03 10:35:09]-[MODEM] ok got after 11882 ms cmd event after 11881 ms
[2019.07.03 10:35:09]-[MODEM] RetVal: 1
[2019.07.03 10:35:09]-[DataSend] Packet sending succeeded
[2019.07.03 10:35:09]-[DataSend] Result: send success, avlbuf mutex released
[2019.07.03 10:35:09]-[MODEM] Entering Data Mode
00000000[2019.07.03 10:35:09]-[DataProcTCP] Write_idx: 0 Length: 4
[2019.07.03 10:35:09]-[DataProcTCP] Data copied to buffer
[2019.07.03 10:35:09]-[DataProcTCP] Pass: 2000a25a - 2000a256
[2019.07.03 10:35:09]-[DataProcTCP] Unexpected answer from server. Clear buffer.
[2019.07.03 10:35:09]-[DataProcTCP] write: 2000a25a read: 2000a256
[2019.07.03 10:35:09]-[DataProcTCP] Resume
[2019.07.03 10:35:09]-[MODEM] Exiting Data Mode

But there is no keyword on device! I succesfully connect to it with configurator!