- Thu Sep 21, 2023 8:12 am
#244020
I'm working on a project that counts the number of times a wheel spins in a complete circle using a proximity sensor controlled by UART, and sends that data to an application on a phone or computer via BLE. The device should be counting the data regardless of whether or not a central device is connected, but should be able to connect to said central device at any time to show the current data.
I'm constantly running into an error that's really hard to diagnose since I can't tell for sure when it's occurring, only that it at some point happened. Basically, after several minutes of running the device perfectly fine, I write to a characteristic to update the number of rotations, and after that the connection is terminated and the device becomes undiscoverable. I've checked with nRF Connect on Android and Apple devices, and it happens on both. The Artemis Nano isn't showing a hard-fault, so my best guess is that it's still running fine and thinks that it's still connected to a central device, even though the connection dropped out prior to or at the exact moment I wrote to that characteristic.
I don't have a lot to go on right now, so I'll come back with more information as I keep troubleshooting. That said, I wanted to know if anyone had any similar experiences and/or possible solutions.
I'm constantly running into an error that's really hard to diagnose since I can't tell for sure when it's occurring, only that it at some point happened. Basically, after several minutes of running the device perfectly fine, I write to a characteristic to update the number of rotations, and after that the connection is terminated and the device becomes undiscoverable. I've checked with nRF Connect on Android and Apple devices, and it happens on both. The Artemis Nano isn't showing a hard-fault, so my best guess is that it's still running fine and thinks that it's still connected to a central device, even though the connection dropped out prior to or at the exact moment I wrote to that characteristic.
I don't have a lot to go on right now, so I'll come back with more information as I keep troubleshooting. That said, I wanted to know if anyone had any similar experiences and/or possible solutions.