ROVIK-1 / ROVSSA · Case study · 2026
I was responsible for software development for ROVIK-1. I built ROVSSA, the ground control station connecting the operator to the rover and displaying telemetry. The data transmission system worked during the competition.
01 / The challenge
A remotely operated vehicle needs an interface that brings its data together and helps the team monitor its state. The challenge was to integrate software, communications and hardware in a prototype built by a multidisciplinary team from UNSa and UCASAL in Salta, Argentina.
Telemetry transmission was successfully used during the competition. The console brings together camera views, orientation, sensors, mapping and rover controls.
AI navigation was not implemented. Later experimental modules are not part of the results demonstrated in competition.
02 / Architecture
The interface receives telemetry through Server-Sent Events (SSE), sends HTTP commands and displays MJPEG video. On the Jetson, Python coordinates communication with sensors and devices. The Pico integration uses serial communication.
This architecture describes the reviewed code. Competition telemetry is the confirmed operational result; the experimental repository version requires separate validation.
03 / Process
The work extended beyond the screen: software development had to support vehicle construction, component assembly and team testing. These images document the working environment and prototype development.
04 / Results and demonstrations
ROVIK-1 earned second place in the Pro category of the International Astromobile Rover Competition, held during the 2nd Latin American Conference on Space Science of the International Academy of Astronautics (IAA). This was a team achievement; my responsibility was software development.
05 / Coverage
Institutional and media coverage of the recognition. These visual summary cards open the original articles.
06 / Lessons and next steps
The integration provided hands-on experience in web development, Python, Linux and hardware communications. It also opened a next stage of security review: the prototype code uses HTTP to transport commands and telemetry over the local network.
IMPROVEMENT PLAN · IMPLEMENTATION AND VALIDATION PENDING
The next proposed improvement is to add TLS and verify server certificates to protect data in transit. Authentication, access to control channels and behavior during connection loss also need review.
These changes have not yet been implemented or tested on the rover. Hardware validation is pending until the equipment becomes available again.
