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

Integrate the m2m2 lidar into sensors package #24

Open
DingoOz opened this issue Dec 19, 2024 · 1 comment
Open

Integrate the m2m2 lidar into sensors package #24

DingoOz opened this issue Dec 19, 2024 · 1 comment
Assignees
Labels
20-software General software issue, not specific to any one area 21-ros Involves ROS code 52-autonomy Issue relates to autonomous navigation or mapping 70-hardware This is a hardware issue

Comments

@DingoOz
Copy link
Contributor

DingoOz commented Dec 19, 2024

Using the newly developed test code as a base, we need to integrate the m2m2 into the sensors package: https://github.com/DingoOz/m2m2_test

Since the m2m2 uses port 1445 and nothing else does it might improve resiliency to have code that monitors which ip address has port 1445 open and selects the ip address that way. Or at least have a tool that can find the ip address based on the port so as to have a backup if static IP address fails.

@DingoOz DingoOz added 70-hardware This is a hardware issue 21-ros Involves ROS code 20-software General software issue, not specific to any one area 52-autonomy Issue relates to autonomous navigation or mapping labels Dec 19, 2024
@DingoOz DingoOz self-assigned this Dec 19, 2024
@RandomSpaceship
Copy link
Contributor

I'm not a huge fan of running a port scanner full-time just to detect the lidar, and that's also not bulletproof (plus it's quite expensive) - and if we do have to use it, I'd rather it be streamlined and manual than automatic. A good option (if it supports it) would be to do lookup based on either its hostname or mDNS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
20-software General software issue, not specific to any one area 21-ros Involves ROS code 52-autonomy Issue relates to autonomous navigation or mapping 70-hardware This is a hardware issue
Projects
None yet
Development

No branches or pull requests

2 participants