Unable to connect to Reachy 2023's mobile base

jyau · November 6, 2025, 12:17am

Hi Pollen Robotics team,

We’ve been having some trouble connecting to Reachy 2023’s mobile base. We’re not sure yet if it’s a software or hardware issue, but when Reachy 2023 is turned on, we can connect to the ReachySDK without the mobile base, like running the below code is fine:

reachy = ReachySDK(host=f'{ip_addr}')

However, if we try to include the mobile base, then there’s an error:

reachy = ReachySDK(host=f'{ip_addr}', with_mobile_base=True)

Traceback (most recent call last):

  File "/home/reachy/dev/reachy-sdk/reachy_sdk/reachy_sdk.py", line 78, in __init__

    self.mobile_base = MobileBaseSDK(self._host)

  File "/home/reachy/dev/mobile-base-sdk/mobile_base_sdk/mobile_base_sdk.py", line 56, in __init__

    self._drive_mode = get_drive_mode().lower()

  File "/home/reachy/dev/mobile-base-sdk/mobile_base_sdk/mobile_base_sdk.py", line 49, in get_drive_mode

    mode_id = self._stub.GetZuuuMode(Empty()).mode

  File "/home/reachy/.local/lib/python3.10/site-packages/grpc/_channel.py", line 946, in __call__

    return _end_unary_response_blocking(state, call, False, None)

  File "/home/reachy/.local/lib/python3.10/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking

    raise _InactiveRpcError(state)

grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:

status = StatusCode.UNAVAILABLE

details = "failed to connect to all addresses; last error: UNKNOWN: ipv4:10.192.8.157:50061: Failed to connect to remote host: Connection refused"

debug_error_string = "UNKNOWN:failed to connect to all addresses; last error: UNKNOWN: ipv4:10.192.8.157:50061: Failed to connect to remote host: Connection refused {grpc_status:14, created_time:"2025-11-05T17:57:50.202295886-06:00"}"
>
During handling of the above exception, another exception occurred:
Traceback (most recent call last):

  File "<stdin>", line 1, in <module>

  File "/home/reachy/dev/reachy-sdk/reachy_sdk/reachy_sdk.py", line 80, in __init__

    raise IOError('Failed to connect to mobile base!')

OSError: Failed to connect to mobile base!

And from the dashboard, these are the logs for the reachy_mobile_base.service:

● reachy_mobile_base.service - Mobile base SDK server service
     Loaded: loaded (/home/reachy/.config/systemd/user/reachy_mobile_base.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2025-11-05 17:59:05 CST; 26s ago
    Process: 62178 ExecStartPre=/bin/sleep 10 (code=exited, status=0/SUCCESS)
   Main PID: 62593 (bash)
      Tasks: 12 (limit: 9054)
     Memory: 78.0M
        CPU: 3.163s
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/reachy_mobile_base.service
             ├─62593 /usr/bin/bash /home/reachy/reachy_ws/src/reachy_2023/mobile_base_controller/mobile_base_sdk_server/launch_mobile_base.bash
             ├─62693 /usr/bin/python3 /opt/ros/humble/bin/ros2 launch mobile_base_sdk_server run_mobile_base_sdk_server_and_hal.launch.py
             └─62731 /usr/bin/python3 /home/reachy/reachy_ws/install/mobile_base_sdk_server/lib/mobile_base_sdk_server/mobile_base_sdk_server --ros-args

nov. 05 17:58:55 reachy-2023-0001 systemd[1547]: Starting Mobile base SDK server service...
nov. 05 17:59:05 reachy-2023-0001 systemd[1547]: Started Mobile base SDK server service.
nov. 05 17:59:06 reachy-2023-0001 reachy_mobile_base[62593]: Starting mobile base launch file.
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [INFO] [launch]: All log files can be found below /home/reachy/.ros/log/2025-11-05-17-59-07-476815-reachy-2023-0001-62693
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [INFO] [launch]: Default logging verbosity is set to INFO
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [INFO] [rplidar_scan_publisher-1]: process started with pid [62727]
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [INFO] [hal-2]: process started with pid [62729]
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [INFO] [mobile_base_sdk_server-3]: process started with pid [62731]
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [rplidar_scan_publisher-1] [INFO] [1762387147.677299289] [rplidar_scan_publisher]: RPLIDAR running on ROS2 package rplidar_ros2.ROS2 SDK Version:1.0.1, RPLIDAR SDK Version:2.0.0
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [rplidar_scan_publisher-1] [INFO] [1762387147.726423197] [rplidar_scan_publisher]: RPLIDAR S/N: E880EC95C1EA9ED0B2E29FF96B5A467D
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [rplidar_scan_publisher-1] [INFO] [1762387147.727275765] [rplidar_scan_publisher]: Firmware Ver: 1.01
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [rplidar_scan_publisher-1] [INFO] [1762387147.727339441] [rplidar_scan_publisher]: Hardware Rev: 18
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [rplidar_scan_publisher-1] [INFO] [1762387147.778627045] [rplidar_scan_publisher]: RPLidar health status : 2
nov. 05 17:59:07 reachy-2023-0001 reachy_mobile_base[62693]: [rplidar_scan_publisher-1] [ERROR] [1762387147.778723415] [rplidar_scan_publisher]: Error, rplidar internal error detected. Please reboot the device to retry.
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [ERROR] [rplidar_scan_publisher-1]: process has died [pid 62727, exit code 255, cmd '/home/reachy/reachy_ws/install/rplidar_ros2/lib/rplidar_ros2/rplidar_scan_publisher --ros-args -r __node:=rplidar_scan_publisher --params-file /tmp/launch_params_m_7_eyfh'].
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2] [INFO] [1762387148.724573687] [zuuu_hal]: Starting zuuu_hal!
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2] 1.2
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2] [ERROR] [1762387148.848426083] []: Traceback (most recent call last):
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2]   File "/home/reachy/reachy_ws/build/zuuu_hal/zuuu_hal/zuuu_hal.py", line 1156, in main
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2]     node = ZuuuHAL()
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2]   File "/home/reachy/reachy_ws/build/zuuu_hal/zuuu_hal/zuuu_hal.py", line 156, in __init__
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2]     self.zuuu_model = check_output(
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2]   File "/usr/lib/python3.10/subprocess.py", line 421, in check_output
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2]     return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2]   File "/usr/lib/python3.10/subprocess.py", line 526, in run
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2]     raise CalledProcessError(retcode, process.args,
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2] subprocess.CalledProcessError: Command '/home/reachy/.local/bin/reachy-identify-zuuu-model' returned non-zero exit status 1.
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2]
nov. 05 17:59:08 reachy-2023-0001 reachy_mobile_base[62693]: [hal-2] [ERROR] [1762387148.848856880] []: Failed to init ZuuuHAL
nov. 05 17:59:09 reachy-2023-0001 reachy_mobile_base[62693]: [ERROR] [hal-2]: process has died [pid 62729, exit code 1, cmd '/home/reachy/reachy_ws/install/zuuu_hal/lib/zuuu_hal/hal --ros-args -r __node:=zuuu_hal --params-file /home/reachy/reachy_ws/install/zuuu_hal/share/zuuu_hal/config/params.yaml'].
nov. 05 17:59:09 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387149.360928203] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:10 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387150.363085397] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:11 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387151.365475017] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:12 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387152.367669040] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:13 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387153.370170787] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:14 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387154.371897563] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:15 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387155.374903134] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:16 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387156.377512576] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:17 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387157.379536665] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:18 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387158.381497996] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:19 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387159.383328116] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:20 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387160.385333700] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:21 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387161.388038150] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:22 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387162.390259252] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:23 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387163.393629299] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:24 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387164.396043047] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:25 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387165.398473048] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:26 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387166.400661552] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:27 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387167.402924132] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:28 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387168.405537343] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:29 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387169.407966718] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:30 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387170.412218921] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:31 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387171.414294335] [mobile_base_server]: service SetSpeed not available, waiting again...
nov. 05 17:59:32 reachy-2023-0001 reachy_mobile_base[62693]: [mobile_base_sdk_server-3] [INFO] [1762387172.416190552] [mobile_base_server]: service SetSpeed not available, waiting again...

We had also tried looking into the mobile base and tested parts with a multimeter and it seems that at least one issue we found is that we are not getting any output voltage out of the silver box (converter?) for Reachy.

The serial number on our Reachy 2023 base is MB-0005.

We would really appreciate any suggestions or support, thank you very much!

Claire · November 6, 2025, 2:57pm

Hi @jyau,
Thanks for your detailed feedback. Could you please measure the voltage between the + and - terminals of parts n°1, 2 and 10 (see image)?
You should get 26V on n°1 and 2, and 5V on n°10.

In the meantime, you can continue to use your robot by deactivating the mobile base. To do this, you have to modify the configuration file.
On the robot, you do nano ~/.reachy.yaml
You modify zuuu_version : instead of its number, you enter None and you save the file.
Then you’ll have to start back the robot.

We will make sure to resolve this issue as quickly as possible!

jyau · November 6, 2025, 4:30pm

Hi Claire,

Thank you for the reply! We checked n1, 2, and 10 and yes for n1 and n2 we get 27V and for n10 we got 5V. Would you have other suggestions on places to look?

jyau · November 7, 2025, 9:25pm

Here are some more images of the base, not sure if they would be helpful for debugging, thank you!

jyau · November 12, 2025, 6:00am

This error also appears occasionally:

Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22] Traceback (most recent call last):
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/home/reachy/reachy_ws/install/reachy_sdk_server/lib/reachy_sdk_server/reachy_sdk_server", line 33, in <module>
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     sys.exit(load_entry_point('reachy-sdk-server', 'console_scripts', 'reachy_sdk_server')())
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/home/reachy/reachy_ws/build/reachy_sdk_server/reachy_sdk_server/reachy_sdk_server.py", line 249, in main
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     sdk_server = ReachySDKServer(
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/home/reachy/reachy_ws/build/reachy_sdk_server/reachy_sdk_server/reachy_sdk_server.py", line 42, in __init__
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     self.body_control_node = BodyControlNode(
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/home/reachy/reachy_ws/build/reachy_sdk_server/reachy_sdk_server/body_control_ros_node.py", line 100, in __init__
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     self.wait_for_setup()
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/home/reachy/reachy_ws/build/reachy_sdk_server/reachy_sdk_server/body_control_ros_node.py", line 118, in wait_for_setup
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     rclpy.spin_once(self)
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/__init__.py", line 206, in spin_once
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     executor.spin_once(timeout_sec=timeout_sec)
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 751, in spin_once
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     self._spin_once_impl(timeout_sec)
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 748, in _spin_once_impl
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     raise handler.exception()
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/task.py", line 254, in __call__
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     self._handler.send(None)
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 447, in handler
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     await call_coroutine(entity, arg)
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 372, in _execute_subscription
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     await await_or_execute(sub.callback, msg)
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/opt/ros/humble/local/lib/python3.10/dist-packages/rclpy/executors.py", line 107, in await_or_execute
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     return callback(*args)
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]   File "/home/reachy/reachy_ws/build/reachy_sdk_server/reachy_sdk_server/body_control_ros_node.py", line 213, in _on_joint_state
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22]     d = getattr(self, self._device_type[name])
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [reachy_sdk_server-22] KeyError: 'front_left_wheel_joint'
Nov 11 23:58:06 reachy-2023-0001 reachy_sdk_server[1892]: [ERROR] [reachy_sdk_server-22]: process has died [pid 2460, exit code 1, cmd '/home/reachy/reachy_ws/install/reachy_sdk_server/lib/reachy_sdk_server/reachy_sdk_server full_kit --ros-args'].

Maybe this could be related to the mobile base not starting properly? Thank you!

Claire · November 12, 2025, 10:49am

Hi @jyau,

Sorry for the delayed response! Thank you very much for your prompt reply and photos. In terms of power supply, everything seems fine, so we will check if there is a problem with the electronics.

Several checks:

Could you check that once the mobile base is switched on, you have a blue LED behind each wheel?
On the black USB hub: Could you disconnect the USB extension cable (which connects the mobile base to the robot body) from the mobile base, disconnect USB port 1 (see the image), and reconnect this port to the extension cable. Then, when connecting to the robot, check that you can access ls /dev/vesc_wheels,
Do the same with USB port 2, and check that you can access ls /dev/rplidar_s2

If both do not work, it is probably a problem with the USB extension cable. If one does not work, it is probably a problem with a connector upstream of the hub. If both work, it is probably a problem with the hub or the USB cable connecting the hub to the extension cable.

Could you also send me an email at claire.houziel@pollen-robotics.com with your address, in case we need to send you replacement equipment, please ?

Thanks a lot and have a nice day!

jyau · November 12, 2025, 8:04pm

Hi Claire,

Thank you so much for the next steps! For the checks mentioned:

When we turn on the mobile base, we don’t see a blue LED behind any of the three wheels.
We could not find the /dev/vesc_wheels directory, it does not appear on Reachy’s computer.
We are able to access /dev/rplidar_s2

Since one of them does work (the LiDAR) but the wheels do not work, would you have any suggestions on how to check the connector upstream of the hub?

Thank you!

Claire · November 14, 2025, 10:52am

Hi @jyau ,

We checked on our end on a mobile base to try to find the configuration that could cause your symptoms.

The fact that none of the VESC LEDs are lit points us toward the power supply. A disconnected cable between the VESC and the hub would not cause this.

Could you remove the fuse (after activating the emergency stop, turning off the mobile base, and disconnecting the battery power supply) and check with an ohmmeter to see if you have anything?

Can you also tell us if, when you turn on the mobile base, the button lights up blue and the interface above the button lights up with a percentage > 0%? And is there a blue led on the hub ?

If the fuse is OK, it is probably the mobile base’s electronic board that is faulty. We will send you a replacement, along with instructions on how to change it!

I have received your email, so I have all the information I need to proceed!

jyau · November 15, 2025, 7:59am

Hi Claire,

Thank you for all your help! For the checks mentioned:

About removing the fuse (I followed the directions but just confirming, is the fuse the white cylinder on the electronic board?): I’m not sure which pins to check so I just checked all the pins following the pin numbering diagram from the first reply:

~45kOhm
~45kOhm
~74Ohm
~4kOhm
~74Ohm
~5kOhm
~78Ohm
~5kOhm
0Ohm
~23kOhm
~6kOhm

About turning on the mobile base: the interface turns on with more than 0% but the button doesn’t light up and the USB hub does not have the blue LED lighting up.

I’m not sure if the checks above help confirm if the fuse is OK, but thank you very much! Please let us know if there is anything else needed from our side!

Claire · November 17, 2025, 9:01am

Hi @jyau,

I’m sorry, my last message was not clear : could you measure the resistance value of the fuse with the ohmmeter, placing a probe on each side of the fuse?

Ok, so it seems that the electronic card of the mobile base is faulty, we are going to send you a new one as soon as possible ! (But we still need to know if the fuse has blown as well)

I will send you an email as soon as it is shipped, with the tutorial on how to change the circuit board.

Once again, thank you for your responsiveness and cooperation !

jyau · November 17, 2025, 5:34pm

Hi Claire,

No problem, this is the resistance value from the fuse: ~1.3Ohm

Not sure if that means the fuse has blown, but thank you for all your help and support with the mobile base! Please let us know if there’s anything else needed from our side!

Claire · November 19, 2025, 8:39am

Hi @jyau, thanks a lot !
That means the fuse is ok ! I’m gonna send you the electronic card today, I will confirm with you by mail.