Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yaml config file is updated too late in the installation process #375

Open
ted-miller opened this issue Feb 25, 2025 · 2 comments
Open

yaml config file is updated too late in the installation process #375

ted-miller opened this issue Feb 25, 2025 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@ted-miller
Copy link
Collaborator

We got up to installing the configuration file (.yaml) before we noticed differences between our system and the instructions. The instructions say that "Within 30 seconds of loading the config file, you should get alarm 8001[10]," but we never did.

Can you clarify whether the config yaml was loaded and whether you edited it? (Please post a copy here too.) @jimmy-mcelwain and I recently updated the readme steps. As I look this over right now, I fear we may have messed up. The current instructions tell you to load the file before updating it with the Agent IP address.

The 8001[10] alarm occurs until after MotoROS2 connects to the Agent for the first time. So, this would require that the configuration information is already in place.

Originally posted by @ted-miller in #374 (comment)

@ted-miller ted-miller added the documentation Improvements or additions to documentation label Feb 25, 2025
@ted-miller ted-miller self-assigned this Feb 25, 2025
@jimmy-mcelwain
Copy link
Collaborator

I agree that this should be changed. But also, your comment says

The 8001[10] alarm occurs until after MotoROS2 connects to the Agent for the first time.

But the README says

Within 30 seconds of loading the configuration file, you should get alarm 8001[10] Speed FB enabled, reboot now.
Reboot again and there should be no alarms.

Which one of these is it? The call site of this alarm is hidden, I'm not sure where to find it. Is it upon loading the configuration file, or upon connecting to the agent for the first time? Because the section describing connecting to the agent is also much later than the description of this alarm (and even was before we changed the README.md recently).

@ted-miller
Copy link
Collaborator Author

It is intentionally hidden. The alarm occurs within Ros_Controller_Initialize, which occurs after Ros_Communication_ConnectToAgent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants