You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/troubleshooting/index.md
+31-2
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
layout: single
3
3
title: MBot Troubleshooting Guide
4
4
toc: true
5
-
last_modified_at: 2024-09-20
5
+
last_modified_at: 2024-11-04
6
6
---
7
7
8
8
Got a problem with your MBot? You're in the right place! This section has detailed guides to help you troubleshoot and fix the most common MBot problems.
@@ -22,6 +22,7 @@ Here are some common issues and how to fix them:
22
22
*[My robot is not driving](#my-robot-is-not-driving)
23
23
*[My robot is driving crooked](#my-robot-is-driving-crooked)
24
24
*[I can't flash the MBot Control Board](#i-cant-flash-the-mbot-control-board)
25
+
*[My MBot Control Board keeps disconnecting](#my-mbot-control-board-keeps-disconnecting) (you periodically lose the ability to drive the robot or lose access to odometry)
25
26
*[My robot won't connect to WiFi](#my-robot-wont-connect-to-wifi)
26
27
*[Mapping isn't working](#mapping-isnt-working)
27
28
@@ -83,6 +84,35 @@ If you see this error, the firmware *did not flash correctly*. Here are some thi
83
84
84
85
---
85
86
87
+
### My MBot Control Board keeps disconnecting
88
+
89
+
**Note:** This section is specifically for *intermittent* disconnections, meaning sometimes you can control the robot, and sometimes you can't. If your MBot Control Board is *never* connecting (you can never drive the robot or read odometry), see [My robot is not driving](#my-robot-is-not-driving).
90
+
{: .notice--info}
91
+
92
+
Here are some signs that your MBot Control Board is periodically disconnecting:
93
+
* Your robot occasionally loses access to odometry,
94
+
* Your robot sometimes stops being drivable,
95
+
* Your robot gets stuck driving at some velocity you sent it but then loses control and can't be controlled.
96
+
97
+
If you are experiencing these issues, you may have a **low battery** or a **bad battery**.
98
+
99
+
**How do I fix it?** You should replace your battery with a new, fully charged one. If your battery is very old (multiple years), you may consider retiring it and replacing it with a brand new battery.
100
+
101
+
**How do I check if my MBot Control Board is disconnecting?** Monitor the LCM channels and check to see whether the channels published by the MBot Control Board (these are the IMU data, encoder data, and odometry) *stop publishing data* when the problem is occurring. There are two ways to look at the channel:
102
+
1. Use the LCM Monitor web tool by going to `http://<MBOT-IP>/spy` in your browser, replacing all of `<MBOT-IP>` with your MBot's IP (see [What's my MBot's IP?](/docs/tutorials/get-ip) if you don't know your IP).
103
+
104
+
**Not seeing the LCM Monitor App?** It may not be installed. You can install it following [these instructions](https://github.com/mbot-project/mbot_lcm_monitor/?tab=readme-ov-file#installing-from-the-latest-release-recommended){:target="_blank"}.
105
+
{: .notice--info}
106
+
107
+
2. If you are [connected in NoMachine](/docs/tutorials/no-machine/), open a terminal and type `lcm-spy`.
108
+
109
+
The MBot Control Board channels (IMU, encoder, odometry) will stop coming in if the board is disconnected (you can look at the "count" property to see if the data is coming in).
110
+
111
+
**Note:** This is much more likely to happen with MBots that use the Raspberry Pi 5 (instead of the Raspberry Pi 4). The Raspberry Pi 5 draws much more power, so you may see this happen when more power is demanded, like when driving the motors and while the Lidar is spinning.
112
+
{: .notice--info}
113
+
114
+
---
115
+
86
116
### My robot won't connect to WiFi
87
117
88
118
If your robot is not connecting to WiFi or not reporting its IP, check the [Networking Troubleshooting Guide](/docs/troubleshooting/networking).
@@ -101,4 +131,3 @@ Lidar spinning and Robot Control Board working but SLAM still isn't working? Try
101
131
3.**Restart your robot.** If any program got into a funny state or crashed, a reboot will fix it. If the problem persists, follow the next steps.
102
132
4.[**Check the logs and services**](/docs/troubleshooting/software/#checking-service-status). These instructions also tell you how to get a log to send to course staff for help if your problems persist.
103
133
5.[**Check LCM channels**](/docs/troubleshooting/software/#viewing-lcm-channels). If you can't find the issue in the services, you might check that all the correct data is being published. Do you see the Lidar scan and odometry data coming in?
0 commit comments