CyberDog encountered an exception it can be restored later

● cyberdog_ros2.service - "cyberdog Deamon"
Loaded: loaded (/etc/systemd/system/cyberdog_ros2.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2025-03-23 14:44:46 CST; 47s ago
Main PID: 10040 (ros2)
Tasks: 237 (limit: 4915)
CGroup: /system.slice/cyberdog_ros2.service
├─10040 /usr/bin/python3 /opt/ros2/foxy/bin/ros2 launch athena_bringup lc_bringup_launch.py
├─10048 /opt/ros2/cyberdog/lib/athena_decisionmaker/decisionmaker --ros-args -r __ns:=/mi0017073 --params-file /tmp/tmprt_vvtlm
├─10049 /opt/ros2/cyberdog/lib/athena_cyberdog_app/app_server --ros-args -r __node:=athena_cyberdog_app -r __ns:=/mi0017073
├─10050 /opt/ros2/cyberdog/lib/athena_cyberdog_app/app_action_client --ros-args -r __node:=app_action_client -r __ns:=/mi0017073
├─10051 /opt/ros2/cyberdog/lib/athena_bms/bms_recv --ros-args -r __ns:=/mi0017073
├─10052 /opt/ros2/cyberdog/lib/athena_bms/bms_ctrl --ros-args -r __ns:=/mi0017073
├─10053 /usr/bin/python3 /opt/ros2/cyberdog/lib/wifirssi/talker --ros-args -r __node:=wifirssi -r __ns:=/mi0017073
├─10055 /opt/ros2/cyberdog/lib/athena_audio/athena_audio --ros-args -r __ns:=/mi0017073
├─10079 /opt/ros2/cyberdog/lib/athena_camera/maincamera --ros-args -r __node:=camera_server -r __ns:=/mi0017073
├─10088 /opt/ros2/cyberdog/lib/athena_obstacle_detection/service_obstacle_detection --ros-args -r __node:=obstacle_detection -r __ns:=/mi0017073
├─10090 /opt/ros2/cyberdog/lib/athena_scene_detection/service_scene_detection --ros-args -r __node:=scene_detection -r __ns:=/mi0017073
├─10091 /opt/ros2/cyberdog/lib/athena_body_state/service_athena_body_state --ros-args -r __node:=bodystate_detection -r __ns:=/mi0017073
├─10092 /opt/ros2/cyberdog/lib/athena_led/service_athena_led --ros-args -r __node:=led_server -r __ns:=/mi0017073
├─10093 /opt/ros2/cyberdog/lib/athena_touch/service_athena_touch --ros-args -r __node:=touch_publisher -r __ns:=/mi0017073
├─10157 dbus-launch --autolaunch 7b98bf708f2d4c499a536f25f4fc5d45 --binary-syntax --close-stderr
└─10170 /usr/bin/dbus-daemon --syslog-only --fork --print-pid 5 --print-address 7 --session

Mar 23 14:45:32 lubuntu ros2[10040]: [decisionmaker-1] [INFO] [1742712332.434451625] [mi0017073.motion_manager]: [State_Detection] Locking state & Error state detected. Checking to passive
Mar 23 14:45:32 lubuntu ros2[10040]: [decisionmaker-1] [INFO] [1742712332.634236312] [mi0017073.motion_manager]: [State_Detection] Locking state & Error state detected. Checking to passive
Mar 23 14:45:32 lubuntu ros2[10040]: [decisionmaker-1] [INFO] [1742712332.816561073] [mi0017073.motion_manager]: [Offline] Odom state response is offline. Clear Velocity & Pose
Mar 23 14:45:32 lubuntu ros2[10040]: [decisionmaker-1] [INFO] [1742712332.830560010] [mi0017073.motion_manager]: [State_Detection] Locking state & Error state detected. Checking to passive
Mar 23 14:45:33 lubuntu ros2[10040]: [app_server-2] [INFO] [1742712333.028457461] [mi0017073.athena_cyberdog_app]: set_status
Mar 23 14:45:33 lubuntu ros2[10040]: [decisionmaker-1] [INFO] [1742712333.030396411] [mi0017073.motion_manager]: [State_Detection] Locking state & Error state detected. Checking to passive
Mar 23 14:45:33 lubuntu service_scene_detection[10090]: 111 gps fixtpye is 0,lat is 0.000000,lon is 0.000000 flag is 1,111
Mar 23 14:45:33 lubuntu ros2[10040]: [decisionmaker-1] [INFO] [1742712333.230801345] [mi0017073.motion_manager]: [State_Detection] Locking state & Error state detected. Checking to passive
Mar 23 14:45:33 lubuntu ros2[10040]: [decisionmaker-1] [INFO] [1742712333.316527641] [mi0017073.motion_manager]: [Offline] Odom state response is offline. Clear Velocity & Pose
Mar 23 14:45:33 lubuntu ros2[10040]: [decisionmaker-1] [INFO] [1742712333.424565399] [mi0017073.motion_manager]: [State_Detection] Locking state & Error state detected. Checking to passive

i cant understand what is happenin

Start with the reported cyberdog_ros2.service status and ROS 2 logs, especially the decisionmaker messages about error state, passive mode, and offline odometry. Reproduce the failure and collect the relevant component logs; the issue is done when the triggering component and recovery path are identified and documented.