-
RMF does not send the next command to my robot to board the lift My lift adapter is modified to manage multiple lifts. The requested lift by /adapter_lift_requests will start publishing its lift state once the lift's API is called. The lift state on rmf web and /lift_states are reflecting correct values Is there a list of requirements that RMF needs to have for it to understand that the lift has arrived and send the next command into the lift accordingly? Any specific functions that is a must to have on lift adapter? (i.e. follow_new_path equivalent) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hello! The LiftRequest and LiftState seem correct so far, could we get a clearer picture of what's happening with the robot fleet? It'd help to add some terminal logs from the fleet adapter, put them in a gist and link it here 😀 |
Beta Was this translation helpful? Give feedback.
-
after adding some logs into rmf_ros2 fleet adapter, the floor names are slightly different. modified it and it works now! |
Beta Was this translation helpful? Give feedback.
after adding some logs into rmf_ros2 fleet adapter, the floor names are slightly different. modified it and it works now!