When possible could you post your current MCU version of your active RS130.
You can find it under:
System Info > System Version Information > View Details > Scroll until you see MCU. (this is done from the rs130 directly not via remote software or apps.)
Mine is 1.0.16 after the early beta access from today.
Thank you in advance.
@duffer5
The MCU version applied to the E/A version is 1.0.16.
Are there any issues after the current update?
Can you confirm all version of what I posted below are correct with the newest early access version.
For your information here is what is currently installed after the attempted update:
System Information: 5.12 (early access)
Xmos: 3152
MCU: 1.0.16
Kernal: 4.4.83
SDK: eng.rose.20260610.145311
Device Version: 5.12
RoseOS: 5.12.04
RoseWare: 5.12.01.1
RoseService 5.12.01.1
@duffer5
Yes, the version numbers you wrote down are correct. It looks like you experienced some issues during the update based on the post in the link below—has your system been successfully restored to normal now?"
Everything appears to be working normally now, but I wanted to document an issue I experienced immediately after updating my RS130 to the latest Early Access Rose OS.
The problem occurred right after the MCU update completed and the RS130 automatically rebooted. Following the reboot, the display remained completely black. I couldn’t determine whether the unit was actually powered on or off because there was no image or other visual indication on the screen.
I waited several minutes and then pressed the power button. I could hear the normal audible relay “click,” indicating the unit was responding, but the display remained black. I then attempted a hard restart by holding down the power button, again hearing the relay click, but the screen still never came back on.
The solution was to completely disconnect the RS130 from AC power and leave it unplugged for approximately 30 minutes. After reconnecting power and restarting the unit, it booted normally and has been operating without issue since.
@Rose_love, do you have any idea what might have caused this behavior? It almost seemed as though the MCU update completed successfully, but the unit became stuck in a state where the display would not initialize properly until all residual power had been discharged.