-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Previously generated INFORM job detected as invalid on next boot #166
Comments
Hi @rsaintobert |
Slightly off-topic, but on the FS100 branch I have gavanderhoorn@578a610 which would print the 'offending' line during the check. I might cherry-pick that to See #167. |
Hi, here are the files. INIT_ROS.JBI
PANELBOX.LOG
I rebooted the controller several time today and so far I can see the ros node, but the alarm for invalid job still appears. |
There is a difference here: job MotoROS2 expects/generates:
job it 'sees' on your YRC1000m @rsaintobert:
@ted-miller: this is a similar difference to what I saw on the FS100 and I worked around/fixed with gavanderhoorn@6a79f9b. Would something similar be needed for the YRC1000m? |
I tried to update the job manually and I confirm the YRC1000m adds a trailing 0 when entering 0.05 value. |
Yes, that's also why I didn't suggest editing it. It wouldn't have worked. |
What if we simply change motoros2/src/InformCheckerAndGenerator.c Line 263 in 4ab13e9
|
Hm, could do that. It wouldn't be the same though. I personally like being specific about things. Edit: but I won't block a PR if you decide to submit one. |
@rsaintobert motoros2/config/motoros2_config.yaml Line 270 in 4ab13e9
To update the config file: |
Thanks for reporting the issue @rsaintobert 👍 This should be fixed in |
ROS2 Version: Humble
MotoROS2 Version: Latest (0.1.1)
MicroROS Version: Latest
YRC1000u
GP7
Hi. I am having trouble to make the driver work.
I followed the installation procedure and I let MotoROS2 generate the INIT_ROS job.
I started the micro ros agent using the docker image and executed the "ros2 node list" cmd into the container (docker exec -it) but no ros node was visible.
After reboot of the controller, the INIT_ROS job is detected as invalid and the alarm 8014 is raised. No ROS node is visible.
The weird thing is that I turns out to work one time without changing anything apparently. I was able to see the node and listen to the /joint_states topic, but after a reboot the problem appeared again.
Here are the logs of the agent
The logs of the debug after first boot
The logs of the debug at reboot indicating that the job is invalid
The config file
The text was updated successfully, but these errors were encountered: