Open bjost2s opened 5 years ago
This issue refers to the change in update procedures of all robots that require HAL updates: EV3 (all versions), NAO v5 & v6, raspberry pi and possible others.
This refactoring should include the development of automatic update procedures for the openroberta-connector program.
The idea is to separate the main openroberta server and the update server into two parts and make a change in the robot-server protocol.
The update could be executed as follows:
Current implementation of REST endpoints could be reused for this separate update server.
Another server has to be discussed in detail because of the costs, maintenance, man power, ...
By the server I mean a separate software piece, not another machine. Anyway, I made a sketch of the sequence diagram for the update process:
Or maybe like this:
todo