FMC920 not sending back data

TELEMATICS
1

Hello, recently I bought FMC920 and I managed to make web server that accepts IMEI from my device but after that device does not send any data. Below are logs. Any help is appreciated but please have in mind I am beginner in this :slight_smile:

[2025.02.16 15:37:07]-[ATCMD] >>[199] ERROR
[2025.02.16 15:37:07]-[AT.RSP] in error handler:
[2025.02.16 15:37:07]-[AT.SEND] ERROR @ m2m_at_cmd_api.c(616):Evt @ATCI ERR
[2025.02.16 15:37:07]-[AT.SEND] ERROR @ m2m_at_cmd_api.c(355):CMD failed. Try:2
[2025.02.16 15:37:07]-[ATCMD] >>[228] +QIURC: “closed”,0
[2025.02.16 15:37:07]-[AT.RSP] WARNING @ 1804:[Test QUIRC] Socket:0, State:3
[2025.02.16 15:37:07]-[NETWORK] [IND] unexpected close soc detected!
[2025.02.16 15:37:07]-[NETWORK] WARNING @ 1505:detected socket close! socket id: 0 res:1 data:0
[2025.02.16 15:37:07]-[REC.SEND.1] Caller: 1383, queueing recsend1 task job type: 2/close link
[2025.02.16 15:37:07]-[NETWORK] VR socket 0 closed! Real:0
[2025.02.16 15:37:08]-[ATCMD] <<AT+QISEND=0,223

[2025.02.16 15:37:08]-[ATCMD] >>[228] ERROR
[2025.02.16 15:37:08]-[AT.RSP] in error handler:
[2025.02.16 15:37:08]-[AT.SEND] ERROR @ m2m_at_cmd_api.c(616):Evt @ATCI ERR
[2025.02.16 15:37:08]-[AT.SEND] ERROR @ m2m_at_cmd_api.c(355):CMD failed. Try:1
[2025.02.16 15:37:08]-[ATCMD] <<AT+QISEND=0,223

[2025.02.16 15:37:08]-[ATCMD] >>[228] ERROR
[2025.02.16 15:37:08]-[AT.RSP] in error handler:
[2025.02.16 15:37:08]-[AT.SEND] ERROR @ m2m_at_cmd_api.c(616):Evt @ATCI ERR
[2025.02.16 15:37:08]-[AT.SEND] ERROR @ m2m_at_cmd_api.c(355):CMD failed. Try:0
[2025.02.16 15:37:08]-[SCH] Task eM2M_Tid_link_tmo_checking[10] dropped

2

Hi,

Good day, are you using the latest firmware for FMC920? It seems that the network socket is closing.

Please try to connect your device to flespi: www.flespi.io
In case you have a server issue please find this link: Help with Server FAQ - Teltonika Telematics Wiki

If the issue is regarding the device you need to send the logs to us, please contact your sales manager or create an HD ticket to investigate the issue.

Best Regards
Maynard C

4

Hello Maynard, seems this was the issue. Fixed now and it works great! Thanks!