
Description: Displays the current app version for troubleshooting.
Notes: Shows the version number in numeric format.
Description: Displays the firmware version of the device.
Notes:
Description: Displays the hardware version of the device’s head component.
Notes:
Description: Displays the hardware version of the device’s body component.
Notes:

The Network module provides details about the network connection status, helping to evaluate connectivity and diagnose issues.
Used to test the network connection's availability and response time. It also helps evaluate network latency. The response time is displayed in milliseconds (e.g., 200ms).
Checks the connection status between two devices or servers. Disconnected indicates the connection is not active, while Connected means the connection is normal.
Indicates whether the app's local server is connected. A value of 0 means disconnected, and 1 means connected.
Displays the automatic scheduling status to improve efficiency. The status is represented as a numerical array in the format [0,0,0], where the values correspond to plan, recharge, and pause respectively.

The Cellular module provides information about cellular connectivity, signal strength, and SIM card details to help monitor and diagnose network performance.
Displays the current 4G network status.
Indicates the received signal strength, commonly used to evaluate cellular signal quality.
Measures signal quality in LTE networks.
Indicates signal quality in GSM networks.
Displays the overall signal strength, including RSSI and other metrics.
Measures LTE signal power.
Shows the current network technology code used by the device.
Displays the unique SIM card identifier for the device.
Indicates if the current SIM card is an internal card.

Refers to the RTK module inside the Yarbo Core.
If the issue still persists, please keep the DC installed in the same physical location and perform Reinstall DC in the app.
Represents the number of shared satellites visible to both the left and right antennas.
You typically want this to be greater than 10 and ideally at least 15. The lower the number, the more likely you are to have a loss of GPS and the rover will pause. This is normal so that the rover can wait for a better signal and get a solid fix on its position. Usually it will resume on its own. If after 30 mins it doesn’t, you can move Yarbo out into the open and resume.
There are 4 possible Status values: 1 / 2 / 4 / 5
When performing Correct Map Drift, please also make sure:
- Status = 4
- Quality > 0.9
Quality represents the RTK positioning quality, with a value range from 0 to 1.0.
A value higher than 0.9 indicates high positioning quality.
Indicates initialization success of sensor fusion positioning:
RTK angle output status:
The lower the number is to zero the better. Anything close to 2 is poor and over 2 is unusable.
At 2 the rover switches to internal sensors like the IMU and wheel odometers to try and compensate for loss/poor GPS. It can only compensate for so long and then it will pause and wait for a good RTK status (4).
The number is impacted by noise, reflections, absorption, etc of GPS signal. For instance, placing your docking station under the eves of your home and up against the foundation can cause the HDOP to be high and result in poor to no GPS conditions when docked or docking. Satellites are always moving along with a number of other environmental factors that can affect this.
It is normal for this number to fluctuate wildly, but generally you don’t want it to continually be near or above 2.
This value represents the number of shared satellites visible to both the Data Center (DC) and the left antenna of the Yarbo Rover.
This number isn’t important. As long as it is generally above 20, it is fine. L2 is the more important satellite count to pay attention to.
Data Latency Indicates the time elapsed since the Rover last received valid RTCM data.
This should be 1-2 normally. Anything higher than that reboot the DC or the rover and see if it gets better. If not, reboot your home router. Anything more than 15 is unusable.
Indicates whether multiple DCs are broadcasting RTCM to the Core.
Shows the server location used for RTK/NTRIP communication (e.g., US).
Rover's real-time location info:
The device containing the RTK base module.
Serial number of the Data Center.
Connection has 5 possible status values: 0 / 1 / 2 / 3 / 4
It represents how RTCM data is transmitted from the Data Center (DC) to the Yarbo Core:
Note: Normally, the status should display as 2. However, if it switches back and forth between 2 and 3, this is considered normal behavior. It means the DC is transmitting RTCM data through both the local network and NTRIP at the same time, while Yarbo automatically uses whichever RTCM data arrives fastest.
DC output GPS data:

The Status module provides details about the device's operational state and automatic scheduling.
Indicates the status of automatic scheduling for improving efficiency and diagnosing internal scheduling issues.
The status is displayed as a numerical array in the format [0,0,0].The three values correspond to plan, recharge, and pause respectively.
Displays the current operational status of the device.The specific status codes and details can be found in the below documentation or additional references.
| Status Code | Status Explanation |
|---|---|
| 0 | RunningNormal |
| 1 | PedestrianAnimalDetect |
| 2 | RotateHumpDetect |
| 3 | InStuck |
| 4 | SerialLoss |
| 5 | GetAngleError |
| 6 | WaitForRTK |
| 7 | WaitForChuteArrive |
| 8 | CameraError |
| 9 | HumpAdjustDetect |
| 10 | HumpFinishBack |
| 11 | WaitForPushRodArrive |
| 12 | ChuteOverCurrent |
| 13 | WaitForRollerArrive |
| 14 | VisionBypassing |
| 15 | RunningError |
| 16 | WaitForBladeArrive |
| 17 | WaitForBladeSpeed |
| 18 | CollisionAdjust |
| 19 | IsDeadendObstacle |
| 20 | WaitForBladeTemp |
| 21 | BypassingReturnAction |
| 22 | NodeError |
| 23 | WaitForBlowerArrive |

The Main module provides details about the machine's operational parameters, including battery, CPU, memory, and motor statuses.
Displays the temperature of the battery to check if it is too low or too high.Data shown as a numerical value.
Shows the current status of the battery.
States include: Charging, Discharging, or Heating.
Displays the percentage of CPU currently in use.
Shows the memory utilization percentage to diagnose potential issues.
Displays the disk usage percentage for diagnosing storage-related issues like log file management. Data shown as a percentage.
Displays the current usage of the left drive motor to evaluate its performance. Data shown as a numerical value.
Shows the current usage of the right drive motor for performance assessment. Data shown as a numerical value.
Displays the current power usage of the auger (snow blower). Data shown as a numerical value.
Displays whether the emergency-stop system has been triggered on the rover’s main body or front module. The value shown represents the current detection state:

The HaLow module provides details about the wireless HaLow connection, including the network name, connection status, and signal strength.
Displays the name(SSID) of the Data Center.
True is working normal. False indicates a problem and could be because the rover is out of range or the DC needs to be rebooted.
Indicates the signal strength of the HaLow connection.
If the HaLow signal falls to –82 dBm or below, the system will automatically switch to 4G.
When operating over 4G, if the HaLow signal rises to –77 dBm or above, it will automatically switch back to HaLow.

The Sensor module provides data from various sensors, including rain and ultrasonic sensors, to monitor environmental and operational parameters.

The Camera module provides details about the camera's version, status, and MAC address for all camera modules (LC: Left Camera, RC: Right Camera, FC: Front Camera, BC: Back Camera).
Description: Displays the current state of the camera.
Usage: Helps determine the operational status of the camera.
Notes:
Additional explanation:
Displays the MAC address of the camera.