You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The paparazzi server is a central piece in Paparazzi, however it lacks some important features, and probably no one knows everything it does.
Can we start specifying what features a software would need to replace the current server, and to keep up with the new needs ?
Existing features
be a central hub for up to date data about all ACs
data interpretation and "translation" (telemetry-> ground, e.g. local frame to LLA)
manage aircrafts "sessions", and configuration coherence (md5sum checking)
data logging
new features
configuration aggregation: resolving include and procedures.
configuration files serving (e.g. through a Rest API)
Web ready (HTTP, websocket, ...)
I also think that we should reduce our dependency from Ivy as it's not very adapted in some situations.
There should be new options to connect the server to clients, including links (seen as privileged clients?)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The paparazzi server is a central piece in Paparazzi, however it lacks some important features, and probably no one knows everything it does.
Can we start specifying what features a software would need to replace the current server, and to keep up with the new needs ?
Existing features
new features
include
andprocedures
.I also think that we should reduce our dependency from Ivy as it's not very adapted in some situations.
There should be new options to connect the server to clients, including links (seen as privileged clients?)
Beta Was this translation helpful? Give feedback.
All reactions