I am experiencing very long time periods between sending a UDP message from a server to a BC660K-GL module. I have measured multiple occasions where it took ~20 seconds from sending to receiving. If multiple messages are sent right after another, the reception time can be faster sometimes (~3 seconds), but not always; sometimes it takes ~20 seconds for messages sent right after another.
Test messages are only one byte long, and power saving is completely disabled on the module.
Hello @herbert.pan-Q,
thank you for the manual. I conducted the test with logging today.
Regarding your manual: You did not provide the comdb.txt file for BC660K, so the output showed a lot of hex data. Also the button Log->Log control did not exist for me.
Otherwise it worked fine.
I measured the time from sending a udp message until receiving the +QIURC message on the main UART. It took 16 seconds.
I did the test again. This time the message was received 3 seconds after sending, which is fine.
But i could observe another problem, which happens very often. The device takes a very long time (2 minutes and 50 seconds) to connect to the network. Could you take a look whats wrong in the logs?
Since our product moves a lot (multiple cells), and NBIoT does not support cell handover, we are not using any powersaving at all. We completely disable the NBIoT module and restart it once we need to communicate. It will only be active for a very short time to send a single message, then be disabled for multiple hours/days.
Does eDRX enable cause long connection time? This seems unlikely. Does it cause long message reception time? If so, how can it be completely disabled?
