search

aws-greengrass / aws-greengrass-cli

Provides a local command-line interface that you can use on Greengrass core devices to develop and debug components locally.
Apache License 2.0
14 stars 9 forks source link

Greengrass deployment rostopic list not same as EC2 rostopic list #138

Closed josephjoel3099 closed 3 years ago

josephjoel3099 commented 3 years ago

The rostopics after launching a launch file in the EC2 instance shows a aset of topics which the robot needs to run properly. After deploying the same stack on a RPi 4 (4 GB) using greengrass the list of rostopics reduces and while echoing the rostopic it give a warning saying "Is /clock being published."

The expected behaviour is to see the same rostopic list as listed in the EC2 instance after the greengrass deployment with the same launch file.

To add, we also checked the rosnode list for the same and it to had some of the node omitted from the actual list while deploying.

Due to the bug we are not able to launch rviz properly and see the topics on the romote machine running the same config.

Note: We are running Rasbian OS on the RPi where the bundle is deployed. Build and bundle is done on the EC2 instance running Ubuntu 18.04, ROS Melodic installed, ARM64.

MikeDombo commented 3 years ago

Hello Joseph, Have you contacted the ROS team about this issue? I am not clear on what the problem is and how it relates to Greengrass.

You note that the Greengrass version is Greengrass version 1, version 1 is not open source and our GitHub repositories do not apply to that software.

Please reach out to AWS support or the AWS forums for help in this matter.