uCAM III-application (including TCP- and HTTP transfer)

Any idea why on a Boron LTE the tcp sending would fail after package 11?

Below are the trace logs. It always gets to package 11 and then nothing, it just hangs.
The image arrived so far is valid. Sending it through serial is no problem, the image arrives in full.

0000032771 [app] TRACE: getJpegData
0000032772 [app] TRACE: sendCmd
0000032773 [app] INFO: sendCmd: AA 0E 00 00 07 00
0000032821 [app] INFO: Package 8 (506 Byte) -> TCP x.x.x.x:port
0000032824 [app] TRACE: getJpegData
0000032825 [app] TRACE: sendCmd
0000032827 [app] INFO: sendCmd: AA 0E 00 00 08 00
0000032874 [app] INFO: Package 9 (506 Byte) -> TCP x.x.x.x:port
0000032878 [app] TRACE: getJpegData
0000032880 [app] TRACE: sendCmd
0000032881 [app] INFO: sendCmd: AA 0E 00 00 09 00
0000032928 [app] INFO: Package 10 (506 Byte) -> TCP x.x.x.x:port
0000032931 [app] TRACE: getJpegData
0000032932 [app] TRACE: sendCmd
0000032933 [app] INFO: sendCmd: AA 0E 00 00 0A 00
0000032981 [app] INFO: Package 11 (506 Byte) -> TCP x.x.x.x:port

And then after about 60 seconds:
0000087671 [gsm0710muxer] ERROR: The other end has not replied to keep alives (TESTs) 5 times, considering muxed connection dead

This might be a Boron connectivity problem, so I have also raised this as a separate thread under Boron LTE connectivity problem

1 Like