Part Number:CC3200
Hi All,
We're doing some range testing with our application using the CC3200 in P2P mode. The CC3200 is acting as the group client, and an android tablet is the group owner. Once we connect, I'm using a modified version of the UDP client demo to transfer data to the tablet. I've been getting the errors below quite often while testing. I want to understand their differences and ask if there are any ways to recover from them.
If we fail to connect, we typically see these events:
SL_GENERAL_ERROR_CON_MGMT_STATUS_UNSPECIFIED (-102)
SL_GENERAL_ERROR_CON_MGMT_STATUS_DISCONNECT_DURING_CONNECT (-109)
SL_GENERAL_ERROR_CON_MGMT_STATUS_SG_RESELECT (-110)
And if we connect, but then disconnect shortly after, we typically see these reasons:
SL_WLAN_DISCONNECT_ROAMING_TRIGGER_BSS_LOSS (109)
SL_WLAN_DISCONNECT_ROAMING_TRIGGER_BSS_LOSS_DUE_TO_MAX_TX_RETRY (110)
The reason codes, I understand. Since we're at range, we may have missed a beacon, and that triggers either of those disconnect reasons (though I don't know what the difference is between them).
I've also seen elsewhere in this forum that the error code -109 has to do with authentication failure during connection, so the parties disconnect from each other. I don't understand why that error would be thrown, and not the specific authentication failure code -103 (Auth reject). I have no idea what an SG Reselect is, and I can't find any information about it online. Error -102 doesn't provide much insight as to what's going on either.
Why are these different errors being thrown seemingly interchangeably? Am I missing some key info about each of them? Are there any parameters I can set to keep them from popping up so often? I ask this because we will get these errors, then move even further away, and connect/transfer data just fine on the subsequent test. I want to make sure our failures are actually failures, and not conditions that I could fix in code. The answers here will benefit me while I'm adding in some logic to switch channels if connections aren't working.
I'm running Service Pack 1.0.1.11-2.10.0.0, and this happens on both the LaunchXL and our custom designs.
Thanks for your time and assistance.
-Jason