Understood and totally agree.
I am referring to HOW the Converse software gets updated.
I’m speculating that the omission of the MConnect method of updating Streamer firmware could be deliberate. I mean it’s a possibility, right?
Maybe it is preferred to do the Streamer updates via the AirLens? i.e. DIP 7 OFF + 15secWPS
which is controlled by the AirLens firmware. Maybe it is safer to update the Streamer (Converse) firmware the AirLens way rather than direct to the Converse board from the MConnect app?
After the experience I have just had, I can’t help this nagging feeling that had I updated the Server software from the AirLens itself rather than direct from MConnect, I may not have bricked by unit.
Also - I had previously done a Streamer firmware update the AirLens way and it worked fine.
FWIW, I have updated the Converse software twice via mconnect without incident.
What does concern me a bit (since mconnect is not my go-to server software) is there does not appear to be any communication from PSA when an update is available.
I have decided to check in via mconnect from time to time to see if updates are available.
Initial version: 2.6.4 (I had done the mconnect update)
Inserted the USB stick (Samsung 128GB, formatted FAT32 on MacBook) with image.bin
Power cycled as directed and the front logo behaved as indicated. When I got to the Flashing Orange condition, I used the “non responsive” directions - I removed the USB and then power cycled the unit. Viola! Came back Green.
First, the blue logo returned to solid blue from flashing status. Then after the power cycle I did the version check according to Aaron’s directions in the update file. I got 2 green, then 7 orange and 4 red flashes - 2.7.4
mconnect will allow you to read the AirLens status under device and get the firmware version for the streamer card.
I had done the mconnect streamer update to v4.3.95 before Aaron’s 2.7.0 main firmware preliminary update. So I had the later streamer version eg “4”. The main firmware update did not change that. It just did “2.6” to “2.7”. Aaron has clarified that all updates should could through the PSA OTA server to prevent the sorts of problems we had.
