| Problem | Reason/Diagnosis | Solution |
|---|---|---|
| An attached USB device isn’t working properly. | Cerebrum’s host operating system is based on the Linux armhf kernel, and therefore has limited driver availability. However, this does not mean that the device will not work, but rather might need some additional software to be installed. | Please contact Symbiomech help services for assistance, or check for software updates. |
| Cerebrum is ignoring commands commands. | Much like humans, Cerebrum can only “listen” to one source at a time, and has a set of built-in priorities. | Check if there are multiple sources connected to Cerebrum. Some sources may be streaming data, which will “talk” over any other source. |
| The status LED is stuck as white or green; software is unresponsive. | Cerebrum’s firmware has frozen. There could be several varying causes. | Power cycling Cerebrum is the only way to really get out of this situation. If it persists, there may be electrical damage. |
| A connection to Bluetooth was established but software claims there is no valid connection. | Bluetooth hasn’t been labeled as “trusted” or “paired”; or you have selected the wrong device. | Ensure your adapter has been paired; On Mac, Bluetooth adapters have varying names such as cu.Bluetooth-PDA-Sync, tty.Bluetooth-Modem, or cu.Bluetooth-Modem. On Linux, you should see a device name containing “rfcomm”. This may be set up using this tool. |
Reference
Troubleshooting