Weird homing issue

First off, this is probably in the wrong section, and probably something super simple but eh… I just spent almost 2 hours trying to upgrade from 1.18 to 1.21RC3... And that experience was utterly dreadful... So much misinformation or just simply LACK of info... First one site says to use S0 and then S1 and that bricks the entire board so it wont connect to wifi anymore... Then another place says to just use M997 without the S0 or S1 and it should just work... But nope! It took 7 different websites with a combination of different things to get it to work.... Wiping the SD Card, restoring the backed up data, changing file names of the bin files, adding an entire folder that just didn't exist, copying a zip file's contents to it, then setting up a macro to setup the wifi and password, another to connect to the wifi, and then tons of hope and praying..... ALL of that info should be posted somewhere in ONE LOCATION so that its easy and simple to follow... might end up just simply writing something to put it on the forum so some poor soul can get it all from one place....

ANYWAY That's not why I'm here in this section.. And yes, I'm super annoyed, salty, and on the verge of pissed... Which is nothing new when it comes to the Duet WiFi for me it seems...

I read the 'whats new' thing like the GitHub (one of two....) stated was probably a smart thing to do. Which yea, it made sense cause I do infact lift my Z up by 5-10mm so that I know I clear any possible failed print when homing. So I added the S2 like it stated to the end of the G1 command.

Well that sorta works. It still comes up at the bottom of the webpage as something like "Move could not be completed cause whatever axis was not homed"... Yet it still moved. Ok. But then when it tries to HOME the Z.... it homes, but then just keeps moving up and up and up and up and up!!! It won't stop no matter what I try! It doesn't have the S2 command because it 'should' be homed at this point! I tried adding it, but still nothing. It just keeps going up until it eventually nearly breaks my z-axis... It also moves my Y axis out, when there's NO COMMAND telling it to move.... So, is there yet ANOTHER webpage that I need to scour for info relating to how to get the printer to home without tearing itself to shreds?

Again, sorry for the salt and attitude... I'm just getting so tired of every time I try to do anything with this board, its like I'm fighting a mountain. "Oh you wanna do this? Well you gotta change this, flip this, kill this, assassinate this, murder this, and toss your soul into a pit! " Is what it feels like every time I've wanted to do something that should take less than 5 minutes..... like updating firmware Shoulda just taken a drag files to card, plug in laptop with pronterface, send two commands, DONE! But nope....

There's a pastebin of my homeall.g file… Where it does tell Y to move to 100, but it shoves it to something like 300 which is WAY out of its reach and luckily stops at 198 because of the 'software', but Z axis doesn't. No Idea why either of them are acting this way....

EDIT: And yes, I've taken the comments out at the "Move z down until the switch triggers" section. That just causes the nozzle to slam into the bed...

For some reason that "whatever could nto be completed because whatever axis was not homed" is actually stating that a G28 could not be completed.... But, NO WHERE in my homeall.g is there a G28.......

If following that guide anyway, if I leave the homeall.g in absolute mode after homing X and Y, it then moves to X144 Y95 But then says, yet again that G28 could not be completed.... and then starts to move the X towards the endstop slowly until eventually crashing and nearly breaking it off.......

Seriously wtf is going on here?!

EDIT: I added G4 S3 between each and every movement... It seems to go ok right until it is supposed to lower for a probe of the bed to determine Z endstop/height... At that point it says the G28 error, and just starts moving towards the X Endstop.

This pastebin is with the relative moves re-enabled, as its the only way to get the z axis to lower. It still tries to move back towards the X endstop but only for a few steps before going down to probe, then its climb back to the top of the Z Axis limits.........https://pastebin.com/EhHx41Nn

Its fixed by deleting the Deploy Probe and Retract Probe gcode files -.-

Seriously, Why is information for the Duet boards so fragmented and messed up? It only takes a little editing to correct things with the proper information people need........ Cause geeze, you can update the 'look' of the website all ya want, but if its HARDER to find the info, its not worth that pretty look...

I'm sorry you has such a frustrating experience. Here is some general advice to avoid having so many issues in future:

1. Don't upgrade to a beta or release candidate firmware version unless you are already running the latest stable firmware version, or an earlier beta/release candidate in the same series. So upgrading from 1.18 to 1.20 first and later from 1.20 to 1.21RC3 would have been more advisable. Otherwise you won't know whether any new issues are because you are running a beta (and may therefore not be widely known) or are known issues with upgrading between versions.

2. When upgrading, read all the upgrade notes between the version you are upgrading from and the version you are upgrading to. In your case that means the upgrade notes for releases 1.19, 1.19.2, 1.20, 1.21RC1, 1.21RC2 and 1.21RC3.

I had no real choice. The websites two links both took me to a 1.21RC3 page, and when I try to go back into the main channel, nothing would be there other than the normal deving files. So it was either stick with 1.18, or jump to 1.21RC3. Which is why I stated there is a serious lack of information/communication around the whole subject. You go to the website, and its harder than a walnut to find any info on the firmware. Once you find a link you THINK might be for the firmware, it just talks about the differences between the WiFi and non Wifi, and the Gen 2 vs Gen 1 boards… Then you see two links, which take you to two different firmwares which both state 1.21RC, and then normally, where most devs have their 'trees' set up, there is nothing for releases which take you directly to each numbered release, nor a beta/RC channel to directly get those releases...

So finding the 1.19, 1.19.2, 1.20, 1.21RC1, 1.21RC2 releases were not possible for me at the time. Although I DID read through the what's new section on each release after 1.18, but nothing I read stated that deploy probe and retract probe were also being called during a homing operation.... That sort of thing should prooooobably be documented somewhere obvious as well, and not just buried in forum posts... Almost 75% of the info I find that helps about the WiFi, tends to come from the Forum. Which don't get me wrong, is flipping AMAZING cause its one of the few forums that have actual people in it on a regular basis! Its simply awesome!!! But for a board that has the sheer amazing potential in it like the Duet boards, the vast amount of things it can do and be customized to do... the main pages/wiki for the boards should be kept up to date or at least organized TT-TT would prevent such things from happening. Although I do understand a vast majority of people who use these boards are usually electronic 'engineers' (dunno if thats the correct term or not) or programming savy people, so they're able to get the ins and outs pretty easily. lol.

Where have you been looking? I'm a bit puzzled by how and why you've been having such a hard time.

Click the "Documentation" link at the top of this forum, select "RepRap firmware" category, then in related pages select "Firmware overview", then in the left hand panel select "Where to get firmware, software and drivers". That's 4 mouse clicks. The first sentence you come across states - "It is highly recommended to read all the notes on the version of firmware you are looking to upgrade to." This is followed by a link to those notes. The next sentence states - "Stable releases of the dc42 build of main firmware and wifi firmware can be found at" and this followed by a link to the download.

That's the exact confusion though. Why would someone expect firmware to be in Documentation? Why would someone expect DUET firmware to be in 'reprap' firmware? Yes the machines that are using the Duet boards are basically repraps, and it is based on reprap firmware, but people going to the site are expecting DUET firmware. Then, further, 'firmware overview' is just as out of place because you go there to expect an overview of what the firmware is CAPABLE of…

All of which, yes that's where I went to get the firmware inevitably, but it was a chore to actually hunt down and locate after a complete site overhaul it seems.

The better, and by far easiest thing to have done... was at the top including a 'downloads' section, like just about every other website out there in existence that requires a download to take place in order to use their products (or at the very least, a 'support' link, which then contains a 'downloads' link)... Then a warning label of 'Attention! It is highly advised that you read through these notes!' and have the 'these notes' section clickable, or at least a link underneath the statement... Then followed by "Download this version here, and this version here" sort of things, and presto... you can find it all in one click…

I'm not trying to bash and such, just stating that man the organization structure is cumbersome to navigate, and multiple documents have conflicting information or straight up misinformation...

Also, as a plus note:
This version is WAY more stable (for me anyway) than 1.18 ever was... I don't have to power cycle the board 30 times to get it to connect to my Access Point, the sensors display proper information, fan sliders work without any weird tweaking, and the overall speed between navigating pages/tabs is alot quicker. Really do love the way it works now, even if it does typically take a long bit of work to get going.

Of which is another awesome note! Completely rebuilt the printer, and it printed perfectly the very first time with zero tweaks required! THAT I can say a RAMPS board would never be capable of doing lol. Good work! Seriously!