Firmware upgrade from 1.15b fails
-
@frontrange said in Firmware upgrade from 1.15b fails:
After walking away from this for a bit it occurred to me that following those directions may have wiped my network configuration out without happening to mention that tidbit.
Thanks for pointing this out. Yes, upgrading from pre-1.19 to 1.19 or later firmware requires you to re-enter the WiFi access point details. I'll add this to those instructions.
-
Just adding that note isn't a fix for this. The documentation is a cross between a train wreck and a boiler explosion, I've honestly never seen anything like it. You don't give an end user and endless list of if..then..else conditions to get through a firmware upgrade, then leave out a third of the steps.
In the end I went form 1.18.1 to 2.04 in one step, but first I had to scavenge all the files from different places, and then make copies of some with different names to satisfy the initial firmware, etc, not knowing except by trial and error what release of what would work with the other files I collected. Why can't there be one damn image with the latest stuff, and any additional renaming, duplication, whatever in one SD image? That is exactly what I did but it took hours of misdirection to get there...
And then maybe have someone actually run through all the steps and make sure they ARE ALL WRITTEN DOWN...
This board cost me under $200 to buy, and nearly 10X that in my time just to get the stupid firmware update done.
-
https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md under version 1.20
When uploading firmware to the WiFi module, the system parameter is cleared
@bearer said in Firmware upgrade from 1.15b fails:
but you really should read the whatsnew section for every release.
You were given all the information you needed, but due to attitude it wasn't spoon-fed.
-
Oh that's really rich. There are over 30 releases between where I started and the latest, and you think everything I needed to know could have been found by reading each and every set of release notes on every one of them huh? You pretty sure about that??
And I'm sure you also read all the terms and conditions on every web site you visit before checking OK?
Of course your suggestion make MUCH more sense that doing it my way and making one sd image and one set of complete instructions, why do that?
-
So you dug it out of the trash and got it working?
Good.
Based on my time here your experience is fairly unique.
I've got five sets of Duet2 WiFi/Duex5 boards and have never had the problems upgrading that you encountered.
Most folks don't wait so long to between firmware upgrades.
Frederick
-
It was only 3 years man. I've been in the industry for 40 years and I've seen decade old firmware as many times as current firmware in customer equipment.
-
ALL of the changes are relevant for your upgrade, thats why they're listed. If you choose to save up
twothree years worth of releases and not bother checking whats changed its asking a bit much to expect someone to maintain a one-click upgrade path for every version under the sun imo.ESPECIALLY since you would still have to adapt your configuration file to any changes there, I recall one of the earlier versions have the motor direction swapped for instance, the manufacturer cannot maintain yours and everyone elses config file for any permutation of upgrades for years on end.
-
BS, I made a single image that covered everything back all the way to the beginning, but I had to scavenge the files from different places and fix the directions. If I'd known what I was doing I could have had it done in no time and all that would be involved in maintaining that image is updating files and re-linking names.
This is just your bullshit excuses to cover for bullshit process.
-
@frontrange said in Firmware upgrade from 1.15b fails:
I made a single image that covered everything back all the way to the beginning,
Single image for both the ESP8266 and the SAM4E8E? You're clearly a better man than me. I shall leave you to bask in your glory
-
MY beginning if you'll read the title of this post was 1.15, I have no idea what you're talking about.
-
I suggest everyone should calm down a bit. @frontrange does have a point and I can understand his frustrations. We should all be aware that not all users are as keen as we are in keeping our systems up to date. "If it ain't broke don't fix it" is a reasonable adage. The fact that he hadn't upgraded his system for 3 years should not be construed as negligence on his part.
Unfortunately for him, the pace of Duet updates is far faster than just about any other firmware that he might have come across. This is because firmware features are driven by users and implemented quickly. Which is a good thing but the unfortunate side effect is that there can be very many changes after only a few months. So if some people do not have the time or inclination to keep abreast of developments as we do, when they do eventually come to upgrade, they can have a lot of catching up to do. But because they haven't been able to keep abreast of developments, they aren't intialy aware of that fact. Hence their frustration.
-
Just to be clear, I finished the machine work on my printer 3 years ago but it sat next to my workbench for all that time unused because I've been kind of busy.
Does anyone think I'm the only guy who has a Duet printer project on the shelf waiting to be finished?
Like I said, in the end my solution was simple and covered updating my 1.18 all the way to current in one step. I'm pissed because I had to spend so much time figuring out the steps and locating the files. Is it really unreasonable to expect that someone on the other side of the equal sign for this monetary transaction do a little due diligence and clean up the awful documentation because I've read the comments by others and I'm not the only one who's had to just suffer through a firmware upgrade when dealing with older code releases.
-
@frontrange said in Firmware upgrade from 1.15b fails:
It was only 3 years man. I've been in the industry for 40 years and I've seen decade old firmware as many times as current firmware in customer equipment.
Well this firmware is a work in progress and they add new features in addition to fixing things that are broken.
Of course the new stuff may end up needing fixing in the next release.
dc42 is very responsive to user input and thus the rate of change is faster than most firmware.
Frederick
-
I'm done. So just keep the process of upgrading a NOS board at least 10X more complicated than it has to be with the current docs and repo organization. It's not my problem anymore...
