Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
user:kluong:feature_idea_-_onboard_xbee_diagnostics [2021/03/24 17:14] kluong created |
user:kluong:feature_idea_-_onboard_xbee_diagnostics [2021/09/19 21:59] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Feature Idea - Onboard XBee Diagnostics ====== | ====== Feature Idea - Onboard XBee Diagnostics ====== | ||
| - | If you take a look at apple's spring 2021 PDR presentation, one thing they mentioned was not "XBEE not able to send or receive packets on board". I'm not sure what the debug steps they took or how long it took to resolve but my gut says this kind of debugging is painful for hardware teams at the moment. If you're a hardware person, you should be able to check voltage/etc. but you might not know where to continue beyond that. | + | If you take a look at apple's spring 2021 PDR presentation, one thing they mentioned was not "XBEE not able to send or receive packets on board". |
| + | |||
| + | I'm not sure what the debug steps they took or how long it took to resolve but my gut says this kind of debugging is painful for hardware teams at the moment. If you're a hardware person, you should be able to check voltage/etc. but you might not know where to continue beyond that. | ||
| One thing that can be added is on on-board diagnostic mode in the firmware, which will set the XBee into command more and attempt to read some parameters from it like panid, nodeid, api mode, etc. If the XBee doens't even respond with these things, the diagnostic is a failure, and at least you know something else is wrong and the XBee is not broken. It could be the XBee is completely broken. Or the wiring is broken, or something else. | One thing that can be added is on on-board diagnostic mode in the firmware, which will set the XBee into command more and attempt to read some parameters from it like panid, nodeid, api mode, etc. If the XBee doens't even respond with these things, the diagnostic is a failure, and at least you know something else is wrong and the XBee is not broken. It could be the XBee is completely broken. Or the wiring is broken, or something else. | ||
| Line 13: | Line 15: | ||
| Some of the code would look like: | Some of the code would look like: | ||
| - | <code> | + | <code C++> |
| xbee_port.write("+++\r"); | xbee_port.write("+++\r"); | ||
| Line 28: | Line 30: | ||
| </code> | </code> | ||
| + | |||
| + | In the serial console, the user would see something like this, after entering command mode and typing XBEE_DIAG: | ||
| + | |||
| + | <code> | ||
| + | Entered command mode: | ||
| + | XBEE_DIAG | ||
| + | |||
| + | Running XBEE Diag Mode... | ||
| + | PANID 8888 | ||
| + | SUCCESS | ||
| + | Exiting weatherbox command mode. | ||
| + | </code> | ||
| + | |||
| + | Would be good to start basic and extend the functionality as needed. But it might be possible to check other things as well with AT command that could be worth exploring: | ||
| + | |||
| + | * if the xbee is connected to a network at all | ||
| + | * signal strength | ||
| + | * might be more here as well | ||