The updater.py script is configured to use /dev/ttyS0, the serial port for the HAT v1 hardware, /dev/ttyS0. It should be configured to use the serial for the HAT v2, /dev/ttyAMA1. This misconfiguration is only apparent when updating. The updater.py script is NOT able to use screen 4 on the HAT v2.
The RoboQuest application software is still able to communicate with the HAT because updater.py runs the rq_core container in privileged mode, so the incorrect /dev/ttyS0 is irrelevant.
To reproduce, verify you have HAT v2 hardware, HAT firmware v6.1, updater.py v6, rq_core v13rc4, and rq_ui v14rc1. Boot the RaspPi and connect the browser. Verify HAT screens 2 and 3 are populated. Switch the HAT to screen 4 and leave it there. Use the RoboQuest browser page to start an UPDATE. Watch /opt/updater/updater.log to confirm the UPDATE is running. Observe the absence of update status messages on HAT screen 4 and the appearance of only "HAT setup" after the application software starts.
This will be updater VERSION 7.
The updater.py script is configured to use /dev/ttyS0, the serial port for the HAT v1 hardware, /dev/ttyS0. It should be configured to use the serial for the HAT v2, /dev/ttyAMA1. This misconfiguration is only apparent when updating. The updater.py script is NOT able to use screen 4 on the HAT v2. The RoboQuest application software is still able to communicate with the HAT because updater.py runs the rq_core container in privileged mode, so the incorrect /dev/ttyS0 is irrelevant.
To reproduce, verify you have HAT v2 hardware, HAT firmware v6.1, updater.py v6, rq_core v13rc4, and rq_ui v14rc1. Boot the RaspPi and connect the browser. Verify HAT screens 2 and 3 are populated. Switch the HAT to screen 4 and leave it there. Use the RoboQuest browser page to start an UPDATE. Watch /opt/updater/updater.log to confirm the UPDATE is running. Observe the absence of update status messages on HAT screen 4 and the appearance of only "HAT setup" after the application software starts.