Please enable JavaScript.
Coggle requires JavaScript to display documents.
Launch different RMF env. - Coggle Diagram
Launch different RMF env.
msi_3h2f.launch.xml
[incl.] msiRobot_adapter.launch.xml
做車隊的設定,如可以執行哪些任務、速度等等
[incl.] fleet_adapter.launch.xml
[node] {full_control}
(以下的值是 hard coding 在 hpp)
subscribe LaneRequest
'/lane_closure_requests'
subscribe InterruptRequest
'/robot_interrupt_request'
subscribe ModeRequest
'/action_execution_notice'
subscribe FleetState
'/fleet_states'
publish ClosedLanes
'/closed_lanes'
publish PathRequest
'/robot_path_requests'
publish ModeRequest
'/robot_mode_requests'
7878 由 cmd [ ros2 launch rmf_demos msi_lobby_sim.launch.xml server_uri:="ws://localhost:7878" ]帶入
connect to [ws://localhost:7878] :red_flag: :red_flag: :red_flag:
-- used to publish tasks and robot state
[arg] control_type = full_control
[incl.] robot_state_aggregator.launch.xml
備援機制 / 目前設定 false
failover_mode == true
[incl.] robot_state_aggregator.composition.launch.xml
failover_mode == false
[node] robot_state_aggregator
[node] free_fleet_server_ros2 (值 from parent xml)
rmf <-> ServerNode (ros2)
-- subs
'/robot_mode_request'
from rmf
-- subs
'/robot_path_requests'
from rmf
-- subs
'/robot_destination_requests'
from rmf
-- publish
'/fleet_state'
to rmf
Server <-> Client (pure dds used)
-- subs
'/robot_state'
from client
-- publish
'/mode_request'
to client
-- publish
'/path_request'
to client
-- publish
'/path_request'
to client
office.launch.xml
[incl.] office.launch.xml
[incl.] common.launch.xml :recycle:
[noed] rmf_traffic_blockade
[node] building_map_server
map path: /home/rc1/amrpoc/FMS/install/rmf_demos_maps/share/rmf_demos_maps/office/office.building.yaml
發送 map :red_flag: :red_flag: :red_flag: :red_flag:
[incl.] visualization.launch.xml
[node] schedule_visualizer
TrajectoryServer.cpp
-- Websocket server started on port: 8006
ScheduleMarkerPublisher 接收 map data :red_flag: :red_flag: :red_flag: :red_flag:
[node] rmf_visualization_fleet_states
[node] rmf_visualization_building_systems
rviz2
[node] door_supervisor
[node] lift_supervisor
[node] rmf_task_dispatcher
-- subs
'/task_api_requests'
-- pubs
'/task_api_responses'
-- pubs
'/rmf_task/bid_notice'
-- subs
'/rmf_task/bid_response'
-- pubs
'/dispatch_states'
-- pubs
'/rmf_task/dispatch_request'
-- subs
'/rmf_task/dispatch_ack'
-- service
'/cancel_task'
-- service
'/get_dispatches'
-- service
'/rmf_task_dispatcher/describe_parameters'
[incl.] dashboard.launch.xml
[node] simple_api_server :star:
Set Server port to: localhost:8083
Set RMF Websocket port to: localhost:7878 :red_flag: :red_flag: :red_flag:
server_ip: 0.0.0.0
server_port_num: 8083
<== used for restful api
ws_server_port_num: 7878
dashboard_config_file: ""
[node] rmf_traffic_schedule_monitor
[node] rmf_traffice_schedule
[incl.] fleet_adapter.launch.xml
[node] fleet_manager
[node] fleet_adapter
Successfully added new robot: tinyRobot1
BroadcastClient unable to connect to [ws://localhost:8000/_internal]. Please make sure server is running. Error msg: invalid state :red_cross:
[incl.] simulation.launch.xml
gzserver
gzclient
rmf-web/
package.json
rmf-server
api-server
for browser used.
[Settings for api-server]
default_config.py
"port": 8000:red_flag::red_flag::red_flag::red_flag::red_flag:
route: _internal
react
[settings where to find server]
~ dashboard/.env
REACT_APP_TRAJECTORY_SERVER=ws://localhost:8006
REACT_APP_RMF_SERVER=
http://localhost:8000
:red_flag::red_flag::red_flag::red_flag::red_flag:
dashboard-e2e/scripts/config.js
REACT_APP_TRAJECTORY_SERVER = ws://192.168.171.168:8006
REACT_APP_RMF_SERVER =
http://192.168.171.168:8000
E2E_DASHBOARD_URL =
http://192.168.171.168:5000
packages/dashboard/rmf-launcher.js
server_uri:=ws://localhost:8001
[unknow the effect area]
packages/api-client/examples/listen.ts
client = new SioClient('
http://localhost:8000
')
rmf_panel
service.tsx
API_SERVER = "
http://localhost:8083
" :red_cross: