A dated record of the main changes to the
system. Entries are taken from the repository history, so each date is the date the work
was committed.
RoboCommand support and readiness evidence
The operator console now speaks the full RoboCommand protocol, and the readiness
rehearsal reads the submission directory directly, so the run start drawn on screen
uses the team id, course, tiers and sequence numbers from the log that was actually
sent. Scripts were added to regenerate both the log and the screencast against a
local copy of RoboNation's test server.
Readiness packages submitted
The mandatory window closed. Packages for the boat, the ROV, the aircraft and
communications were submitted. The communications evidence was produced the same day:
a run start sequence against RoboNation's test server, recorded with our console on
one side of the screen and their decoder on the other.
3D course model
The Marina Bay course was built in the browser, with every task element from the
build specifications at true scale, five camera modes, and a visual settings panel,
added because the low sun over the bay washes out the part of the water the buoys are
in. The readiness rehearsal followed, with the four handbook courses and the 63 item
checklist.
RoboCommand client and mock shore server
The RoboCommand client and a mock shore server were added together, so the run
start handshake could be tested offline. Telemetry streams were trimmed to the
messages the ground station uses, which reduced the radio load to a few packets per
second per vehicle.
Software in the loop and link emulation
Software in the loop was added: ArduRover, ArduSub and Copter running the same
firmware as the vehicles, behind an emulator for the WiFi HaLow link with latency,
jitter, loss, a bandwidth cap and periodic outages. The fringe profile found the
telemetry load problem described in the entry above.
First mission logic
The three state machines, the orchestrator, the health monitor and the terminal
console were written, with simulated vehicles behind them. This was enough to run a
mission end to end on a laptop while the hardware was still being specified.
Planned before November
Water sessions for the pipeline survey, the docking approach and the delivery
mechanism, then one session with all three vehicles autonomous at the same time.
The test record lists what is planned.