search

goodrobots / maverick

UAV Autonomous Systems Management
https://goodrobots.github.io/maverick/
MIT License
173 stars 61 forks source link

Create a set of port ranges for known and unknown services #941

Closed fnoop closed 4 years ago

fnoop commented 4 years ago

There will be a set of fixed/known services, for example:

Then there will be sets of variable/unknown services, eg.:

Define:

Within the set of known services, we should define fixed ports for the various services. This is particularly important for services such as -discovery, which need to be consistently available on the same port at all times. eg:

fnoop commented 4 years ago

Port 6000 is blocked by most browsers as it's standard X11 port, so start from 6001. https://superuser.com/a/188070

fnoop commented 4 years ago

This is a new list of fixed/known ports:

Dev:

fnoop commented 4 years ago

Docs for mavlink need to be updated to reflect new port ranges; https://goodrobots.github.io/maverick/next/#/modules/mavlink

fnoop commented 4 years ago

Refactor mavlink ports. Current the ports are all over the place, depending on the service which are usually unrelated, eg. for FC:

For SITL/default dev instance:

fnoop commented 4 years ago

New FC ports:

New Dev SITL ports:

In addition, maverick_dev::apsitl creates instance clusters based on an instance number, and numbers ports based on a multiple of the instance number. Currently the starting ports are:

Instead create a set of grouped ports per instance, eg.:

so..

fnoop commented 4 years ago

OK, now document.

fnoop commented 4 years ago

Also need to refactor px4 sitl. Currently on: ROSmaster: 6131 maverick-api: 6132 mavlink-tcp: 6133-6135 maverick-udp: 6136-6141