• State Not Answered
  • Replies 12 replies
  • Subscribers 77 subscribers
  • Views 1960 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 287560
Options

SLM UDP arbitrary received data size by #XRECV and #XRECVFROM

Michal Mühlpachr

Hi,

I do not know how to reliably get size of arbitrary UDP data received by #XRECV or #XRECVFROM.

It is clear for text data, but for binary data both #XRECV and #XRECVFROM do not report size of received data in advance before data.

Because arbitrary binary data can contain <CR><LF> or even "#XRECV: <any number>", how size of received data reported by SLM can be distinguished reliably?

Why #XRECV and #XRECVFROM do not report size of received data BEFORE data (that would work fine)?

Thank you.

Regads,
Michal

Parents
  • 0

    Hi Michal,

    Thanks for your advice. We really appreciate your contributions.

    I have a discussion with our developer, and the conclusion is that we can adjust the URC timing but not in a short time. The reason is that it will affect not just UDP but TCP as well, and lots of doc updates. We also have some high priorities works to do before the next NCS release.

    I will keep monitoring the state and give you an update if necessary.

    Thanks again and have a nice day!

    Best regards,

    Charlie

Reply
  • 0

    Hi Michal,

    Thanks for your advice. We really appreciate your contributions.

    I have a discussion with our developer, and the conclusion is that we can adjust the URC timing but not in a short time. The reason is that it will affect not just UDP but TCP as well, and lots of doc updates. We also have some high priorities works to do before the next NCS release.

    I will keep monitoring the state and give you an update if necessary.

    Thanks again and have a nice day!

    Best regards,

    Charlie

Children
Related
Terms of service