-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fiducial Follow is reported as not working on Noetic image #34
Comments
In the log he posts and in his comment it looks like fiducial_follow/follow.py is not found process[raspicam_node-1]: started with pid [763] |
If I recall, the follow script is in the old 'demo' folder on GitHub. It
needs to be copied over and catkin_make on the pkg. I did get it to work on
Noetic, I also got partybot and object detection working. The old python
nodes need to be patched to work with Python 3.
…On Thu, Dec 16, 2021, 6:56 PM Mark Johnston ***@***.***> wrote:
In the log he posts and in his comment it looks like
fiducial_follow/follow.py is not found
process[raspicam_node-1]: started with pid [763]
process[aruco_detect-2]: started with pid [764]
ERROR: cannot launch node of type [fiducial_follow/follow.py]:
fiducial_follow
—
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHZ375PDEBLUMI4AD7AKELURKRFTANCNFSM5KHZ5MIA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
It seems like a lot of demo stuff is not working on noetic because they arent proted to python 3 yet:
If we plan to keep demos on noetic someone should get them up to date. Untill then they are out of the noetic image |
This is the corrected python to get the follow.py to work in Noetic. for some reason I can't create a pull request for this node: """
""" import rospy def degrees(r): class Follow:
if name == "main": |
@anfederman which branch are you trying to create a pr from? |
In demo didn't give me permission to create a new branch for the follow.py.
the launch in magni_nav is already ok.
…On Tue, Mar 29, 2022, 7:23 AM Janez Cimerman ***@***.***> wrote:
@anfederman <https://github.com/anfederman> which branch are you trying
to create a pr from?
—
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHZ375JUMSFWWNF3RTYRNTVCMG47ANCNFSM5KHZ5MIA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Forum post of https://forum.ubiquityrobotics.com/t/fiducial-follow-not-working-in-ros-noetic/920/2 was entered by forum user murpht2 and this is the 'bug report' from murpht2
I recently obtained a Magni with ROS Kinetic on the Raspberry Pi. I am able to run fiducial_follow in this configuration and the robot functions as expected. After consulting with the Ubiquity team I downloaded the beta ROS Noetic image and got the robot up and running with this. When I run the fiducial_follow demo on the Noetic setup the robot does not move. Full text from the terminal window is below, but I can see that the raspicam_node and aruco_detect are both working but fiducial_follow is not. The output changes as expected when I move a fiducial into and out of the field of view, which confirms that the robot sees the fiducial but is not able to execute any commands to follow.
FWIW I double-checked that I am up to date on all the ROS packages including ros-noetic-magni-demos and I was unable to locate a follow.py file anywhere on the system, though I’m not sure if this is relevant or not.
The text was updated successfully, but these errors were encountered: