We have noticed our BX-3105 modules sometimes return a disconnection reason 31, after which they stop RF activity. If scanning was active (using +SRBLESCAN command), it will stop. If advertising is enabled, the module cannot be seen. For example:
+SRBLE_IND: 1,1
+SRBLE_IND: 1,0,31
In most cases we get a reason code 19 (terminated by peer) when a client disconnects, in which case the advertising can be restarted ok. Reason code 31 is not listed, but it looks like we may need to restart the module to get it working again?
We are only using the module in BLE mode, and do not change modes after initial config.
I have just seen the same behaviour with disconnect reason 8 (connection timeout), where the module is not visible even though we restart advertising.
Most of the time the module works as expected. We get disconnect reason code 8 if the client goes out of range, or 19 if the client disconnects their app. We then restart advertising to allow the client to reconnect. The problem is that in rare cases the module is not visible even though it responds with an OK to our advertising command.
We also have BLE scanning enabled, which continuously sends scan results over the port. I notice that when this advertising issue occurs, the scan results also stop.
