Open compunited opened 5 years ago
@compunited It's not clear to me where the 3 minutes timeout you mention is in the library I'm looking GSMUdp::endPacket and there is no 3 minute timeout.
Can you please share a file and line number for what you are referring too, as well as a minimal sketch to reproduce this issue.
i can't resolve it to a line of code, otherwise i could fix it myself. It happens if there is bad reception. My workarround is to reset it by the watchdog but loosing data
I don't think the problem is with the library itself. This is probably a setting in the GSM chip, but in the thousand pages of documentation there are plenty of timeouts
I don't think the problem is with the library itself.
@compunited ok, I suggest we follow up with u-blox support on this then. Would you be able to contact them?
hi, @compunited. did you get any support from u-blox?
I have an unrelated issue with the U201. considering the quasi-abandonment of their forum, I have little faith it can provide any meaningful help from u-blox themselves. well, at least some customers do provide some help.
As you can see the UDP Timeout is 3 Minutes. That's far too long and needs to be changeable. If the message isn't transferred within a few seconds it'll never be transferred successfully.
00:32:37.794 -> AT+USOST=0,"iot.blafasel.de.... 00:32:38.918 -> +USOST: 0,112 00:32:38.918 -> 00:32:38.918 -> OK 00:35:37.853 -> AT+CSQ 00:35:37.853 -> +CSQ: 8,1