936 réponses à ce sujet

[mikelikesrobots]

Hi all, has anyone got a downloadable version of the SD card image? I can't sign up for an account to download it - apparently some security issue.

[mikelikesrobots]

Hi @:robot:Lisa , I'm still stuck on my issue. Could you please take a look?

[drobo_community]

@Qiaolong Li @Seth Please help to assist the problem.

[qiaolongli_30839]

Ok:fullwidth_comma:we will push an image to Google Drive and release it later.

[cute_peacock_32095]

originbot_sd_image_x5_v3.0.1.rar
https://drive.google...iew?usp=sharing

[drobo_community]

@MikeLikesRobots please download from here.

[mikelikesrobots]

Got the image - will get to testing it soon. Thanks!

[mikelikesrobots]

Hi @:robot:Lisa - I'm afraid that image didn't work. When I run it, the board fails to load the device tree. Some of the logs:
```
bootargs = console=tty1 console=ttyS0,115200 rootfstype=ext4 rw rootwait root=/d ev/mmcblk2p2 mtdparts=spi7.0:0x700000@0x0(miniboot),0x180000@0x700000(ubootenv)
Loading fdt file: /boot/hobot/x5-rdk.dtb
144506 bytes read in 9 ms (15.3 MiB/s)
Apply device tree overlay
Unknown command 'dtoverlay' - try 'help'
Unknown command 'setpin' - try 'help'
Loading kernel: /boot/Image
23216136 bytes read in 1022 ms (21.7 MiB/s)
Boot kernel from 0x200000, devices tree from 0x3C00000
## Flattened Device Tree blob at 03c00000
Booting using the fdt blob at 0x3c00000
Loading Device Tree to 0000000003c00000, end 0000000003c1ffff ... ERROR: fdt move failed - must RESET the board to recover.
FDT creation failed! hanging...### ERROR ### Please RESET the board ###
```
After a few seconds, the board reboots and the same thing happens.

I also tried to install Ubuntu server on it from this image: https://drive.google...Vqvm-LK78KLsJeO
Following the instructions, I start it up (which works) and log in (which works), then get stuck on the apt update method. The repositories from d-robotics aren't available, so the update fails and I'm unable to `apt install tros`.

[mikelikesrobots]

Could you provide any info on how to proceed, please?

[dd2mf]

Hello I'm not an official D robotics staff or anything but I might be able to help you. Can you share the ouput of "sudo apt update"? I'm tryna check something.

[mikelikesrobots]

Let me reflash to the Ubuntu image and try - it'll be a few minutes

[mikelikesrobots]

Okay, here's my log:  update_log.txt   3,22 Ko   0 téléchargement(s)

[dd2mf]

It looks like your system clock is way off-several repositories are being rejected because their release files appear to be "from the future" (371 to 446 days ahead).

Fixing the Clock Issue

Try manually setting the correct time:
1. Check the current system time:

date

If it's incorrect, proceed to fix it.

2. Set the correct time manually (temporary fix):

sudo date -s "YYYY-MM-DD HH:MM:SS"

Replace with the actual current date and time.

3. Sync time via NTP (better fix):

sudo apt install ntpdate -y
sudo ntpdate ntp.ubuntu.com


4. Enable NTP service to keep time updated:

sudo timedatectl set-ntp on
sudo systemctl restart systemd-timesyncd



Once the time is corrected, try running sudo apt update again. Let me know if you hit any other issues!

[dd2mf]

@MikeLikesRobots sorry for the late reply mate

[mikelikesrobots]

Nice one! It's updated and upgrading. Hopefully should be good from here. Cheers.

[dd2mf]

Alrighty

[mikelikesrobots]

Hi folks, has anyone got the lidar working successfully? I've [installed the sensor drive](https://www.originbo...he-sensor-drive) and [configured the port](https://www.originbo...dar-port-number), then rebooted, but no `/dev/ydlidar` appears. Power is on to the lidar, it's spinning, and the ~~serial cable is plugged in to the base board~~. Running `ros2 launch originbot_bringup originbot.launch.py use_lidar:=true` gives me:

```
[ydlidar_ros2_driver_node-4] [2025-02-13 18:52:21][info] SDK initializing
[ydlidar_ros2_driver_node-4] [2025-02-13 18:52:21][info] SDK has been initialized
[ydlidar_ros2_driver_node-4] [2025-02-13 18:52:21][info] SDK Version: 1.2.11
[ydlidar_ros2_driver_node-4] [2025-02-13 18:52:21][error] Error, cannot bind to the specified [serial port:/dev/ydlidar] and [baudrate:115200]
[ydlidar_ros2_driver_node-4] [2025-02-13 18:52:21][error] Error initializing YDLIDAR check Comms.
[ydlidar_ros2_driver_node-4] [ERROR] [1739443941.362491212] [ydlidar_ros2_driver_node]: Unknown error
[ydlidar_ros2_driver_node-4]
[ydlidar_ros2_driver_node-4] [INFO] [1739443941.399600106] [ydlidar_ros2_driver_node]: [YDLIDAR INFO] Now YDLIDAR is stopping .......
```

Maybe it's a controller firmware issue, but I did flash it with the [v1.0.5 hex from the repository](https://gitee.com/gu...master/firmware). Any help would be great!

Edit: not serial cable to the base board, I was looking at the wrong cable. I meant the USB cable from the lidar is plugged into the RDK USB3.0 port.

[mikelikesrobots]

@:robot:Lisa tagging for visibility!

[mikelikesrobots]

As a follow-up to that, the IMU is also giving all 0s. I can run `ros2 launch originbot_bringup originbot.launch.py use_imu:=true` with some extra log statements enabled and get this:
```
[originbot_base-1] Frame raw data: 55 02 06 ff 00 00 ff 00 00 fe bb
[originbot_base-1] Frame raw data: 55 03 06 00 00 00 00 00 00 00 bb
[originbot_base-1] Frame raw data: 55 04 06 00 00 00 00 00 00 00 bb
[originbot_base-1] Frame raw data: 55 05 06 00 00 00 00 00 00 00 bb
[originbot_base-1] Frame raw data: 55 06 06 0a 49 00 00 00 00 53 bb
[originbot_base-1] [INFO] [1739450498.211831770] [originbot_base]: Acceleration data: x=0.000000, y=0.000000, z=0.000000
[originbot_base-1] [INFO] [1739450498.212074806] [originbot_base]: Angular data: x=0.000000, y=0.000000, z=0.000000
[originbot_base-1] [INFO] [1739450498.212205511] [originbot_base]: Euler data: r=0.000000, p=0.000000, y=0.000000
```
And it's always 0s, no matter how much I move the robot. Is there something I'm meant to do to enable the IMU? Thanks.

[rdk_wuchao]

Hello:fullwidth_comma:please update STM32 frameware:fullwidth_comma: it may fix the imu