MoffKalast

> Can the client try and see the performance using odom only, without map Hmm interesting idea, it would require a slight modification of sending the goals in the odom...

> see the perfomance using odom only, without map So, a follow up on that, I've attempted to set all frames to odom which I think forces internal transform of...

This is still an issue. With no examples one can take and try out this codebase is effectively useless to newcomers without a month to figure everything out by themselves.

Okay, well I can probably get someone from my team to look at it but from what I understand webrtc_ros is actually already up to speed and what remains is...

Hey @mjstn you should have sftp access for this now right?

Suggestion: once the motors stop running they should instead pwm beep in a recognisable way that can be described in the learn docs as a battery low alert.

Perhaps the real issue here isn't the lack of labels but the false sense of security that the main power switch provides, calling itself the "main power" switch while not...

Note: The pages are now live, so the actual page that should be edited is this one: ~~https://learn.ubiquityrobotics.com/noetic_magnisilver_mcb_revisions~~ There is the slight issue that we have a kinetic/noetic split for...

Okay I just went ahead and moved it, the definitive new file is now at: https://github.com/UbiquityRobotics/learn/blob/master/unlisted_pages/magnisilver_mcb_revisions.md And can be found on the wiki at: https://learn.ubiquityrobotics.com/magnisilver_mcb_revisions Only that one file needs...

For the robot model iirc you need to clone magni_robot into a local repo, maybe launching magni_description on the workstation itself, but but that may have some conflicts with something....