Debugging motors one by one might help you find if one particular motor is faulty, that’s a good start.
We’ve recently added a few more docs about debugging, reading them might also help you find the problem.
And finally, if you want to get the full logs (with that you’ll know for sure what is the problem, or you can send it to us and we’ll tell who what the logs really mean) :
– connect to the Raspberry Pi via ssh (tutorial here)
sudo systemctl stop niryo_one_ros.service to stop the current ROS stack
roslaunch niryo_one_bringup rpi_setup.launch to start the ROS stack, but in the current terminal, not in background, so you can see and print all the logs. When you spot a command problem, you can copy and paste the logs that have just been printed.