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.

11199: FMB120 Reponse Timeout issue

0 votes
1,114 views
in Vehicle tracking by anonymous

Hi,

The FMB120 can not receive the ACK from the AVL server it is waiting 30 secondes (default Reponse Timeout ). After that the link timeout occur.

After cheking, the AVL server make response in less than 5 secondes (tested with Hercules tool ).  When i change the param  GPRS > Records Setting > Reponse Timeout to 120 secondes, i can receive  all the records. But when i set  Reponse Timeout to 30s or 60 the  problem occurs : the records are sent again and again because no ACK received by the module i guess.

Could you please help me ?

This a small peace off logs

[2019.10.27 10:45:28]-[REC.SEND.1] records packed: 10, waiting 30 sec for answer

[2019.10.27 10:45:28]-[REC.SEND.1] link timeout reset for server: 0

Below the complete logs :

In your case its not happening, So the device is thinking server didn't get the data.

Then device is cancelled its record sending procedure and will start it again with the same data.

Please find the above mentioned details below from your log

[2019.10.27 10:45:21]-[REC.SEND.1] Caller: 1139, queueing recsend1 task job type: 0/records

[2019.10.27 10:45:21]-[REC.SEND.1] [CHANGE.STATE.0163] Server: 0, finished => check rec no

[2019.10.27 10:45:21]-[REC.SEND.1] check rec no

[2019.10.27 10:45:21]-[REC.GEN] Server: 0, not all min records send: 1/1

[2019.10.27 10:45:22]-[CODEC.APP] Rec found at 0x00000471, sort:1

[2019.10.27 10:45:22]-[CODEC.APP] 0x00000471 skipped, due to packing High prios

[2019.10.27 10:45:22]-[CODEC.APP] Rec found at 0x00000472, sort:1

[2019.10.27 10:45:22]-[REC.SEND.1] Have enough records to send!

[2019.10.27 10:45:22]-[REC.SEND.1] [CHANGE.STATE.0260] Server: 0, check rec no => check gprs

[2019.10.27 10:45:22]-[REC.SEND.1] check gprs

[2019.10.27 10:45:22]-[REC.SEND.1] gprs is open

[2019.10.27 10:45:22]-[REC.SEND.1] gprs settings the same -> check link

[2019.10.27 10:45:22]-[REC.SEND.1] [CHANGE.STATE.0300] Server: 0, check gprs => check link

[2019.10.27 10:45:22]-[REC.SEND.1] check link

[2019.10.27 10:45:22]-[REC.SEND.1] link is closed, try to open

[2019.10.27 10:45:22]-[NETWORK] [SOCKET.OPEN.0425] Socket target: 0, attempt: 1/3

[2019.10.27 10:45:22]-[NETWORK] Connecting to 52.29.190.209:31123@TCP

[2019.10.27 10:45:22]-[NETWORK] [SOCKET.OPEN.0425] Waiting for create conn result, waiting: 160 sec

[2019.10.27 10:45:23]-[NETWORK] connection established! acc id: 52, socket id: 1, evt sending: enabled

[2019.10.27 10:45:23]-[NETWORK] VR socket 0 open! real socket id: 1

[2019.10.27 10:45:23]-[REC.SEND.1] link timeout reset for server: 0

[2019.10.27 10:45:23]-[REC.SEND.1] launching link monitoring

[2019.10.27 10:45:23]-[SCH] Task eM2M_Tid_link_tmo_checking[11] has been scheduled. Period: 1s

[2019.10.27 10:45:23]-[REC.SEND.1] [CHANGE.STATE.0485] Server: 0, check link => send imei

[2019.10.27 10:45:23]-[REC.SEND.1] send imei

[2019.10.27 10:45:23]-[NETWORK] attempting to send data by VR socked id: 1, data len: 17

[2019.10.27 10:45:23]-[NETWORK] [SEND.DATA.0512] Waiting for socket send result, waiting: 10 sec

[2019.10.27 10:45:23]-[NETWORK] data send to socket: 1, successfull! evt sending: enabled, VR socket: 0

[2019.10.27 10:45:23]-[REC.SEND.1] imei send OK, waiting 30 sec for imei answer

[2019.10.27 10:45:23]-[NETWORK] [IND] received data from socket!

[2019.10.27 10:45:23]-[NETWORK] notification, socket id: 1 has data which must be read!

[2019.10.27 10:45:23]-[NETWORK] VR socket 0, real socket id: 1, attempt automatic data reading for application

[2019.10.27 10:45:23]-[NETWORK] attempting to read data from socked id (real): 1

[2019.10.27 10:45:23]-[NETWORK.PARSER] Parsing data from 0 socket, data len: 1

DUMP DATA START:

01 

DUMP DATA END

[2019.10.27 10:45:23]-[NETWORK.PARSER] imei answer received!

[2019.10.27 10:45:23]-[REC.SEND.1] server accepted imei

[2019.10.27 10:45:23]-[REC.SEND.1] [CHANGE.STATE.0519] Server: 0, send imei => send records

[2019.10.27 10:45:23]-[REC.SEND.1] send records

[2019.10.27 10:45:23]-[REC.GEN] Server: 0, not all min records send: 1/1

[2019.10.27 10:45:23]-[CODEC.APP] Rec found at 0x00000471, sort:1

[2019.10.27 10:45:28]-[NETWORK] attempting to send data by VR socked id: 1, data len: 705

[2019.10.27 10:45:28]-[NETWORK] [SEND.DATA.0589] Waiting for socket send result, waiting: 10 sec

[2019.10.27 10:45:28]-[NETWORK] data send to socket: 1, successfull! evt sending: enabled, VR socket: 0

[2019.10.27 10:45:28]-[REC.SEND.1] records packed: 10, waiting 30 sec for answer

[2019.10.27 10:45:28]-[REC.SEND.1] link timeout reset for server: 0

[2019.10.27 10:45:28]-[MODEM.ACTION] GSM Update Reason:Periodic

[2019.10.27 10:45:28]-[MOD.TSK] SMS Read Map:0,0,0,0 Index:32

[2019.10.27 10:45:28]-[MODEM.ACTION] SMS Not Found

[2019.10.27 10:45:28]-[MODEM.ACTION] status done

[2019.10.27 10:45:35]-[WD.FUNC] WARNING @ 172:counter:2 Cnt:4568 Limit:10800

[2019.10.27 10:45:37]-[REC.SEND.1] Mode: 0/Home on Stop. Time for next periodic data sending: 16 / 120

[2019.10.27 10:45:42]-[SYS.DIAG]

[2019.10.27 10:45:58]-[REC.SEND.1] WARNING @ 735:No server response to sent records [45], rec sending canceled

[2019.10.27 10:45:58]-[REC.SEND.1] [CHANGE.STATE.0736] Server: 0, send records => finish

[2019.10.27 10:45:58]-[REC.SEND.1] finish

Best regards

1 Answer

0 votes
by anonymous

Hello,

Thank you for your query.

Wireshark will help you out to investigate what server actions are while this happens. Also take logs with hercules  to see what device does at the same time when server gives no response.

Could you take Log using wireshark? instructions I've uploaded below:

https://wiki.teltonika.lt/view/File:How_to_take_log_from_the_server_wireshark.pdf

Hope this will help.

Best Regards,

Teltonika support.

Best answer
by anonymous
Hi

I captured some with wireshark, the server respond in 2 secondes ( including ACK).

I think that this issue is caused by link timeout according to log :

1- Records packed:10, waiting 30 seconds for response

2- Link timeout reset for server:0

The server respond in 2 seconds, why there is timeout in the module ?

There is 800 records in flush memory. Maybe he module has trouble to manage the sending process.

Best regards