Firmware Change Log

Afraid only Robo could provide that
They are not terribly open on that side, yet.

Mine also recently did this update.

 

@Jeff Uberstine you can become a GITHUB reader and see if you can decipher the changes made to the various parts Robo includes in RoboOS. I think you will find that the actual printer firmware changes very little from version to version, usually confined to configuration refinements, and that some other pieces change more.

 

I think the version displayed on the LCD for the C2 is the RoboOS version ... It may sync with the firmware version (but why they would rename marlin 1.10 to 1.14 is beyond me)

 

I have complained about this too! Marlin is still 1.1.0 and Robo only changes it because the Firmware Updater OctoPrint plugin is written to only see the M115 string and Marlin only uses 3 digits by default. It then checks against some server somewhere in the world to determine if an update is available.

Unfortunately the GIT fork is not up to date since the Updater code still has this line in it

Code:

  "update_service_url": "http://devices.bq.com/api/checkUpdate3D/{model}/{language}/{version}"

 

Still not software folks, eh?

 

My biggest complaints are little to no testing of changes, arbitrary code changes that add little to no value, almost no documentation on what or why changes are made. I am not even sure they have those conversations internally, but I would hope so. It makes it nearly impossible to follow the logic, if any, that is being used when the RoboOS is being pieced together.

I would love to see a spec document that outlines the goals for current and future RoboOS versions, my fear is that these things don't exist or are just a loose set of emails with no cohesive end goal.

 

Don't get me started on programmers! As a former Software Group Manager I know full well what happens when you put programmers in charge of complete software projects. I also understand what happens when you have a limited amount of resources (people in this case) and you are trying to design and code a UI. If I had a nickel for every time I had to ask a programmer to justify why code was changed.....

It's a good thing this isn't Linux kernel development and Linus isn't reviewing the code changes himself.

 

You're preaching to the choir, my friend.

 

Yeah and here is where it looks for updates
RoboLCD https://github.com/victorevector/RoboLCD/archive/{target_version}.zip
Firmware updater: https://github.com/Robo3D/OctoPrint-FirmwareUpdater/archive/{target_version}.zip

It won't help asking for changelogs, you are the consumer of an appliance as far as Robo is concerned so you don't need a changelog since you aren't supposed to change anything on an appliance by yourself.