By default the startup sequence is that the MCU turns the 12V bus on, and waits for 50s for Up2 to boot up and communicate with it (systemd-analyze shows startup time of 34s to userspace and this is true when measured while rebooting).

This sometimes works but Up2 does not always startup properly. Sometimes it takes >90s to boot up, and sometimes it does not turn on all (blue LED next to power socket stays off). I can see that te voltage is supplied ( I do have indicator LED, and voltage measurement on Up2's 5V bus), but the board itself remains dark. The monitor connected to the board, turns on for a second and then goes to standby (indicating that 'something' triggering HDMI is happending).

I haven't noticed this when powering the Up2 for a regular ACDC power supply. Below there is a oscillogram of 12V bus when powering on:
As you can see the voltage rise time is ~10ms to 12V, which is rather long.

If anyone has any clue why the board does not turn on i would be thankfull for sharing.

I've got UP Squared 6000 with UP Xtreme i11 Robotic Kit installed on it and I'm trying to run an example of motor control. I'm on step 3 in section Calibrate your Robot’s IMU, and I have to save data from /amr/imu/raw topic to a file. The problem is that no messages are published in this topic.

Steps 1 and 2 were successful, I got the expected output:

[INFO] [1660834785.348021058] [IoContext::IoContext]: Thread(s) Created: 2
[INFO] [1660834785.349719311] [AMR_node]: Serial opened on /dev/ttyUSB0 at 115200
[INFO] [1660834786.366661024] [AMR_node]: Hardware is now online

Robot is assembled according to the instructions, Motor Control Board and Intel Real Sense camera are connected to UP 6000 Board via USB. Motor Control Board is powered up and ON/OFF switch is set to ON (not sure if it matters, it wasn't mentioned anywhere).

Topics displayed after ros2 topic list command (no messages are published in any of them):

/amr/battery
/amr/imu/raw
/amr/initial_pose
/amr/odometry
/cmd_vel
/parameter_events
/rosout
/tf

Nodes displayed after ros2 node list command:
/AMR_node

Even if I try to publish something on /cmd_vel topic, there is no motor movement.

In step 2, parameter port_name:=/dev/ttyUSB0 seems to be correct, because ls /dev | grep USB displays only ttyUSB0.

What could be the reason of missing messages in topic /amr/imu/raw and other topics? The Motor Control Board should work right away, or do I need to setup it somehow?

Thanks!

Issue is observed on 2 different Up Squared 6000 systems.
Issue is observed with both Linux and Windows.
Same RM510Q-GL card works fine in different system (Supermicro board with M.2 B-key slot and USB 3.0 lanes provided).

Basically device is seen on the USB bus but it fails to set configuration:

[ 1430.217568] usb 2-4: new SuperSpeed Plus Gen 2x1 USB device number 2 using xhci_hcd
[ 1430.239261] usb 2-4: New USB device found, idVendor=2c7c, idProduct=0800, bcdDevice= 4.14
[ 1430.239264] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1430.239266] usb 2-4: Product: RM510Q-GL
[ 1430.239268] usb 2-4: Manufacturer: Quectel
[ 1430.239269] usb 2-4: SerialNumber: 125b5122
[ 1430.243869] usb 2-4: can't set config #1, error -32

And device stays in unconfigured state and drivers are not bound. I tried to use external USB 2.0 adapter on the same Up Squared 6000 and card works OK (in USB 2.0 mode).

BIOS version is 2.0.

Any help appreciated.