Error after firmware upgrade to 2.02
-
When upgrading firmware, you should always read the upgrade notes for the new version and any versions you skipped, to see what changes you may need to make to config.g, homing files etc.
-
I Followed them to letter.
I have made no config changes at all.
Web control, wifi and main firmware all updated and report ok, as per the file above.
I'm at a loss.
-
Too tired to check this all again now... It's 4.21 am.
I'll try again tomorrow. Maybe there will be people with some constructive hints.
-
I'm not going to spoon feed you, nobody would read the upgrade notes if I did that for everyone. Read the version 1.21 upgrade notes. https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md
-
Good Morning.
Oh, you meant the individual release notes. Now I understand what you meant. After wading through the one page listing what to do in what order depending on what revision of software you're upgrading from and too, and it being late ( for me ) it didn't occur to me that each release had it's own readme file. My bad.
Dave, the Duet is a great product. The Duet info wiki is expansive. And comprehensive. ....
My two cents though, less words and more pictures / flow charts.
Yes, the Duet is a technical product. But, page after page of 'do this IF, and in this order IF, else do this' doesn't always suit the audience.
I am always happy to read and learn/self help, and I hope I don't need spoon feeding (for a few years yet).
I have 5 original (non clone) Duet Wifi in machines with different setups that I have to upgrade. So, there is a point where it becomes a chore to read page after page of info. Last night it became exactly that.
All this, combined with lack of sleep and the late hour caused my snippy response. My apologies.
.....now, off to go find the reading glasses.
Keith
-
I get this error message: "Error: G0/G1: insufficient axes homed"
Recent firmware versions do not allow axes to be moved before they have been homed. The only movements allows are homing moves (G1 moves with S1 or H1 parameter) and individual motor moves (G1 moves with S2 or H2 parameter). So any Z movements that your homing files make before Z is homed should use the S2 parameter. Alternatively, add M564 H0 to config.g to allow axis movement before homing. -
@phaedrux said in Error after firmware upgrade to 2.02:
I get this error message: "Error: G0/G1: insufficient axes homed"
Recent firmware versions do not allow axes to be moved before they have been homed. The only movements allows are homing moves (G1 moves with S1 or H1 parameter) and individual motor moves (G1 moves with S2 or H2 parameter). So any Z movements that your homing files make before Z is homed should use the S2 parameter. Alternatively, add M564 H0 to config.g to allow axis movement before homing.Thanks, I forgot that we had an FAQ entry about this too.
-
Thank you for this.... I was just reading, changing and testing.
I am concerned though. I have not moved this machine physically, and with the new firmware the WiFi keeps dropping out mid saving of config files. The router is maybe 30 ft away ( up one floor ). Signal level is -62db.
Thoughts ?
-
Which DuetWiFiServer version were you using before, and which version are you using now?
-
I am using 1.22 now ... was 1.20 prior ( I think ... I didn't check the revision. But, machine h
as not been upgraded since July last year ).
