- 5005 - Radio control joystick data -
pixrc
process on the Solo listens to this for rc joystick messages - 5010 - Config Stick Axes Msg
- 5011 - Param Stored Values Msg
- 5012 - sysDestPort?
- 5013 - pairReqPort -
stm32
process on Artoo listens to pair requests from the pair_server process - 5014 - pairReqDestPort -
stm32
process on Artoo sends to this port on the pair_server process - 5015 - mavDestPort -
stm32
process receives telemetry from the telem_ctrl process here - 5016 - buttonEventPort (TCP) - Subscribe to button events on the Artoo (pause, home, A, B, etc) by connecting to this port on the Artoo.
- 5017 - buttonFunctionConfigDestPort
- 5018 - setShotInfoDestPort
- 5019 - updaterDestPort (update status screens)
- 5020 - lockout_msg - port on stm32, controls whether the "need update" screen is shown.
- 5021 - status info (TCP) - Subscribe to status information (battery life, etc) on the Artoo
- 5022 - config sweep time on Artoo
- 5024 - set telem units (metric / imperial) on stm32
- 5026 - control when app connected message is displayed on stm32
- 5501 - controller link port (communication between pair_server on the Artoo and pair_solo on the Solo)
- 5502 - app server port (TCP) - Port on the Artoo where the Solo app connects. Merely connecting to this port triggers the app_streamer process to stream video from the Solo to app on UDP port 5600.
- 14560 - mavlink on solo - When the telem_forwarder app is running on Solo, it allows processes (such as shot manager) to communicate with the flight controller.
- 14550 - telemetry solo <--> controller. When Solo is connected to the Artoo, it sends a combination of Mavlink (and some other data) to this port. The first 56 bytes are unknown data type, the rest appears to be Mavlink packets.
-
-
Save courtarro/2aeb3ddc4a90a8ac93bfb5e474259cd6 to your computer and use it in GitHub Desktop.
Solo Network Services / Ports
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment