• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 521 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SPP Port Status Indication Issues - Break Status: 0x0010, Length: 0x255e1.

Sheldon Blackshire
Intellectual 985 points

I have been working with a heavily modified  "automatic" version of  NOOS/SPPDEMO for a while. When opening a SPP port with a device, the etPort_Open_Confirmation callback case occurs. Under normal conditions, the SPP Port Status Indication would read something like this:

SPP Port Status Indication: 0x0001, Status: 0x0000, Break Status: 0x0000, Length: 0x0000.

For this situation, data transfer works correctly. My issue arises when the following occurs. (LOG)

atAuthenticationStatus:OpenRemoteServer() -> MyPC

SPP_Open_Remote_Port: success.

****************************************************
etPort_Open_Confirmation
****************************************************
etPort_Open_Confirmation 00027281d26a
SPP Open Confirmation, ID: 0x0002, Status 0x0000.
SPP Port Status Indication: 0x0002, Status: 0x0000, Break Status: 0x001c, Length: 0x24be5.

I was wondering if the Status, Break Status, and Length could be explained a bit more in depth. Also has anyone received this kind of information, why does it occur and how to avoid it?