flexbe_app icon indicating copy to clipboard operation
flexbe_app copied to clipboard

[ROS][Noetic]Flexbe_app not running on Jetson Orin

Open hs0747 opened this issue 1 year ago • 1 comments
trafficstars

SUMMARY

PARAMETERS

  • /behavior/enable_clear_imports: False
  • /behavior/log_enabled: False
  • /behavior/log_folder: ~/.flexbe_logs
  • /behavior/log_level: INFO
  • /behavior/log_serialize: yaml
  • /rosdistro: noetic
  • /rosversion: 1.16.0

NODES / behavior (flexbe_onboard/start_behavior) behavior_launcher (flexbe_widget/be_launcher) behavior_mirror (flexbe_mirror/behavior_mirror_sm) flexbe_app (flexbe_app/run_app)

auto-starting new master process[master]: started with pid [71945] ROS_MASTER_URI=http://localhost:11311

setting /run_id to 1ec80bf8-d2e3-11ee-a880-2cf7f120f4b7 process[rosout-1]: started with pid [71962] started core service [/rosout] process[behavior_mirror-2]: started with pid [71968] process[flexbe_app-3]: started with pid [71971] process[behavior_launcher-4]: started with pid [71973] process[behavior-5]: started with pid [71975] [0224/123545.043446:WARNING:chrome_main_delegate.cc(569)] final extension:

(nw:72004): Pango-ERROR **: 12:35:45.088: Harfbuzz version too old (1.4.2)

/home/jetson/catkin_ws/src/flexbe_app/bin/run_app: line 16: 72004 Trace/breakpoint trap (core dumped) "$NW" --password-store=basic $ROOT_PATH "$@" [flexbe_app-3] process has died [pid 71971, exit code 133, cmd /home/jetson/catkin_ws/src/flexbe_app/bin/run_app __name:=flexbe_app __log:=/home/jetson/.ros/log/1ec80bf8-d2e3-11ee-a880-2cf7f120f4b7/flexbe_app-3.log]. log file: /home/jetson/.ros/log/1ec80bf8-d2e3-11ee-a880-2cf7f120f4b7/flexbe_app-3*.log [INFO] [1708758346.712538]: 2 behaviors available, ready for start request. [INFO] [1708758347.545796]: --- Behavior Engine ready! --- [INFO] [1708758347.546662]: No onboard behavior is active.

hs0747 avatar Feb 24 '24 07:02 hs0747

Given that the app is intended to run as the "Operator Control Station" separate from the robot "onboard" software, do you need to run on Jetson hardware?

I do not expect to spend time on this as I don't have access to that hardware. It sounds like an issue with the nwjs. You might try editting the "nwjs_install" script to download a newer version. Of course this is untested.

dcconner avatar Apr 08 '24 14:04 dcconner