I'm glad it all worked out for you.

I was also getting stops on power fail pause, which I wasn't getting before. I was using quite tight parameters for Vin voltage, which I have backed off by 0.5v but it was more apparent with B4 than B1.

P3 correspond to Heater 3 (pin 8).? Orange wire?

You need to generate config.g and homing files to match your printer characteristics, and upload them to the SD card. See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer. You can use this tool https://configurator.reprapfirmware.org/ to generate them.

No problem, if I saw "Tools / Heaters / Extra" mentioned, I would assume that the"/" meant a sub-menu. But in this case, it didn't.

As it says on the wiki in several places, latest stable firmware is always at https://github.com/dc42/RepRapFirmware/releases.

@dc42:

Black wire should be connected to the GND pin on the Z probe connector, as described in the wiki.

When the probe is deployed but not triggered, the Z probe reading should be zero, or close to zero,

Its the same…. too i have try
....

solved…

Was this, bad wiring

Yes, see https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Delta_printer#Testing_the_motors_individually.

The DuetWiFiFirmware.bin file gets deleted from /sys after is has been successfully installed.

M122 will show you the signal strength.

It reconnects by pressing "Connect", of course. All the server apps (web UI, ping, telnet, ftp) start to work by magic when the print is done.

I don't remember, but I'm pretty sure it is a timeout message. The printer's IP is not reachable on any port and protocol. I am and IT guy at the core, so I am 100% about "unreachable". It simply stops being there from the network point of view.
What I didn't check is if the AP still sees it joined at all during the down time. I will do that next time.

I've remembered a maybe important bit: it didn't happen on short prints (<1 hour) and I don't know when it happens on longer prints because I find it dead when I check occasionally.

Well dc42 I think it was definitely me having slightly larger soldering blobs where I couldn't push them in and even more directly related to me pushing those connectors in "Forcing Them" with a tool of mine and messing up the end part. wish I had done all this with a crimp tool, but I don't have one for it. I had been checking out the barbs that they had engaged.

Hey jlegere if you don't have a zprobe like I don't go to config.g file and actually dc42's words on my thread "use P0 in the M558 command in config.g to say that you have no Z probe. At each probe point, the web interface will present some buttons for you to jog the nozzle down until it just touches the bed, then you press OK."

hope that helps, you could always turn it back to "p1" after installing your probe with the new part you print..

Yes, the pre-production boards will run the latest firmware.

Version 1.19+1 has been superseded by 1.19.2 which is an official release on github.

That would almost certainly be an issue between Chrome and DWC, so a firmware change won't help. I mostly use FireFox to access my Duets these days, because Chrome on my Win64 PC had a frequent habit of become completely unresponsive (on all tabs) for about 30 seconds before recovering - even when I wasn't connected to a Duet.

See https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_Cartesian_printer. At the end of the first paragraph it provides a link to a web site that will help you generate the configuration files.

I'm sorry to hear that you are having problems getting connected. Please see https://duet3d.com/wiki/What_to_do_if_your_Duet_or_Duet_WiFi_won%27t_respond.

Yes, it took me a while to work out what the correct acceleration and speed limits should be for other than pure X and pure Y moves! And then there was CoreXYU to do as well…