@styler93gsx

Yes the 1.02 version boards can do homing by stall detection. Though, it will still be highly dependent on your motors and some fine tuning to get your sensitivity just right. If you have endstop switches already it's highly recommended to just use them.

It looks like you're still running some very old firmware. Now that you have access to the web control via wifi the easiest way to do a firmware upgrade is to upload it via the settings > general tab.

Here are the 3 files you'd need to update:

https://github.com/dc42/RepRapFirmware/releases/download/2.02/Duet2Firmware-2.02a.zip
https://github.com/dc42/RepRapFirmware/releases/download/2.02/DuetWebControl-1.22.6.ziphttps://github.com/dc42/RepRapFirmware/releases/download/2.02/DuetWiFiServer-1.22.bin

You may need to make a config change to get your homing working properly again.

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 I have dual lead screws (not independent) so unless I keep Z steppers on between prints, moving the bed or removing torque will tilt it between those two

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 ).

@bundesoberweber said in WiFi Problems after Firmware Update:

WiFi signal strength -91dBm, reconnections 0, sleep mode modem

That's the problem. The WiFi signal strength is outside the usable range.

I think user @biscuitlad has gone through the process. Perhaps they have a working config to share.

You can also search the forum for K8400. There have been a few discussions.
Here's one: https://forum.duet3d.com/topic/4145/using-the-reprapfirmware-configuration-tool

@stoop said in Duet Wifi 1.01 not detected after firmware upgrade:

But it was actually taking a long time to boot. Like 30 seconds.

That may indicate a problem with the SD card.

@macinyash, yes do that if you want the X=0 Y=0 position to be at one corner of the bed, but use negative values where appropriate. For example, if your printer has a X min endstop that triggers when the nozzle is 10mm off the edge of the bed, put -10 in the X minimum field. See https://duet3d.dozuki.com/Wiki/Centering_the_bed_or_setting_the_bed_origin. The values you select in the configurator are put in the M208 commands that it generates.

OK, I found it myself. The files deployprobe.g and retractprobe.g needed to be removed from the /sys directory. Now it works like it did before.

Tom Johnson

@dc42 Ok, the diag light on teh right is illuminated the diag is lit up. I canot ping the board from my router and the Samba is not working either, No speaking to the board at all. It did however speak before. Is there a way to "force feed" it? I will look at the routines and see if I see anything again.

@rastanser Here you have a complete example for dual Y-axis with separate end-stop for each motor, including some aspects related to gantry squaring. It works as it is with firmware 2.01.

Yes, that sounds sensible too.

@imrj Additionally to what @Phaedrux said: just putting the files on the SD card is not enough. They need to be installed. If you upload it via DWC it will ask you whether you want to perform this update or not. In case you uploaded them any other way (ftp or removing the SD card and copying the files onto it) then you need to run M997 S0:1 to update both RRF and DuetWifiServer.

@naqaj Thank you for the report, I could reproduce and fix the problem.

@yd14, to change the direction of the Z motor, find the M569 P2 command in config.g and change S0 to S1 or vice versa.

The other problem is likely to be caused by incorrect endstop switch configuration. Test the endstop switches as described at https://duet3d.dozuki.com/Wiki/Connecting_endstop_switches#Section_Test_endstop_switches.

On my list to investigate.

@chrishamm Thanks. 👍

What type of motor drives the rack and pinion system? Does the rack and pinion have any sort of endstop switch to indicate that it is in a particular position, or will you drive it into a hard stop to establish an initial position?

See the entry for M584 on the GCodes wiki page. The M584 command must come before some other commands, not after as you have it.

I do not know what happened, but it all works now.

I have tried several times with restart of both printer and PC in between. Maybe it comes back.
When upload from slicer failed I still could upload from DWC.

No errors, except within Slic3r when trying to upload.

I have installed latest DWC but I am not using it. I had failures without connecting with the DWC to the Duet since bootup of the Duet. So I do not thing the new DWC is the cause of this.

I will post again if this problem occurs again.

Just a FWIW. I traced the circuit out a bit further down, to R75 on the board. With the SDCard ejected I get no resistance. With the card inserted I get resistance. I'm assuming that directly relates to the CD as it closely matches the resistance when I measure directly to the ground PIN.