-
Notifications
You must be signed in to change notification settings - Fork 5
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
Save robot configuration with dataclasses #254
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can convert the other configs
m0_can_address=config.external_mower.m0_can_address, | ||
m1_can_address=config.external_mower.m1_can_address, | ||
m2_can_address=config.external_mower.m2_can_address, | ||
m_per_tick=self.M_PER_TICK, # TODO: this is a different value than in external_mower.m_per_tick!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Johannes-Thiel do you know why the mower uses M_PER_TICK
and not the 0.01 from the config?
I merged main into this branch and added a gnss configuration |
This PR introduces a new format to save robot configurations.
Changes
thooth_count
totooth_count
FieldFriendConfiguration
dataclass with more configurations as propertiesfield_friend_hardware.py
to use the newFieldFriendConfiguration
check_pins
functionLedEyesHardware
since it's not used anymoretornado.py
and othersToDos
get_config
to dynamically load configurationm_per_tick
is used correctly in all hardware elements