Duet Wifi will not connect via web control

[A Former User]

@dc42 said in Duet Wifi will not connect via web control:

M552 S1

When I send the M552 command it just says WiFi module is being started.
It never goes past that.
When I ping it this what I get. The 192.168.1.92 used to be the ip for that printer, not sure wy it says 192.168.1.72 Destination host unreachable.
I did try the M552 S-1 and then the M552 S1 command. It just says sending M552 S1....nothing happens after that.

PS C:\Users\Richard> ping 192.168.1.92

Pinging 192.168.1.92 with 32 bytes of data:
Reply from 192.168.1.72: Destination host unreachable.
Reply from 192.168.1.72: Destination host unreachable.
Reply from 192.168.1.72: Destination host unreachable.
Reply from 192.168.1.72: Destination host unreachable.

Ping statistics for 192.168.1.92:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
PS C:\Users\Richard>

[A Former User]

@chichirod said in Duet Wifi will not connect via web control:

not sure wy it says 192.168.1.72 Destination host unreachable

likely your computer (and its IP address) tellig you it cannot reach the printer/target

[dc42]

I think you may be running an old version of Duet WiFiServer that is incompatible with the newer Duet2CombinedFirmware. Download DuetWiFiServer 1.23, put the SD card into a PC and copy DuetWiFiServer.bin into /SYS (it must be called exactly that on the SD card). Safely remove the SD card, put it back in the Duet, start the Duet, and send M997 S1 from USB or PanelDue to install it. Watch the installation progress messages to check that it is installed successfully.

[A Former User]

@dc42 said in Duet Wifi will not connect via web control:

M997 S1

Worked like a charm, Thank you I Love this board. Problem solved. Now back to printing!

[A Former User]

@dc42
Hi DC42 sorry one more issue, now that I can connect via web control when I power on my printer my BLTouch no longer works. It just starts flashing and says G28 Z probe already triggered. It was working flawlessly before the update. Suggestions?

[Phaedrux]

What firmware version were you using before the update? And can you post your config.g?

[A Former User]

@phaedrux Hi here is my config.g file:
It was 1.21 but now its 2.03

; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Thu Nov 08 2018 21:43:50 GMT-0700 (Mountain Standard Time)

; General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves

; Network
M550 PRED Rodriguez Black Widow ; Set machine name
M552 S1 ; Enable network
M587 S"RCMP Surveillance 2.4" P"241428433" ; Configure access point. You can delete this line once connected
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P0 S1 ; Drive 0 goes forwards
M569 P1 S0 ; Drive 1 goes forwards
M569 P2 S0 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z1600 E415 ; Set steps per mm
M566 X420 Y420 Z20 E120 ; Set maximum instantaneous speed changes (mm/min)
M203 X10000 Y10000 Z1200 E1200 ; Set maximum speeds (mm/min)
M201 X1000 Y1000 Z20 E500 ; Set accelerations (mm/s^2)
M906 X1100 Y1100 Z1200 E400 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; Set axis minima
M208 X370 Y241 Z400 S0 ; Set axis maxima

; Endstops
M574 X1 Y1 S0 ; Set active high endstops

; Z-Probe
M574 Z1 S0 ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 F200 H3 R0.2 T12000 A5 B0 ; Set Z probe type to bltouch and the dive height + speeds
G31 P25 X-11 Y57 Z0.4

                             ; Set Z probe trigger value, offset and trigger height

M557 X10:370 Y10:240 S60 ; Define mesh grid

; Heaters
M305 P0 T100000 B4725 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4388 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C

; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off

M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on

M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C

; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss
G1 Z0 F6000 S2 ; lower Z again
M564 H0

; Custom settings are not configured

; Miscellaneous
T0 ; Select first tool

[dc42]

@chichirod said in Duet Wifi will not connect via web control:

@dc42
Hi DC42 sorry one more issue, now that I can connect via web control when I power on my printer my BLTouch no longer works. It just starts flashing and says G28 Z probe already triggered. It was working flawlessly before the update. Suggestions?

A flashing BLTouch means it is in an error state. There is an M280 command that you can send to reset it.

When does it start flashing: the first time the firmware tries to deploy it, or at some other time?

If you have any M401 or M402 commands in any of your homing of bed probing files, remove them. Likewise any M98 commands that invoke deployprobe.g or retractprobe.g.

[A Former User]

@dc42 Hi, its starts flashing within 5 seconds of turning the power on. I had no M401 or M402 codes but I did delete the M98 command. I still have the same thing. Within in seconds of powering up it starts flashing

[Phaedrux]

what does it do if you send the servo command to clear the error state and retract the probe?

M280 P3 S160 I1

[A Former User]

@phaedrux said in Duet Wifi will not connect via web control:

M280 P3 S160 I1
That seems to have fixed. Ill play with it for a bit but it seems perfect now. Thank you

[Phaedrux]

At power up the probe does it's self test where it drops and retracts the pin a few times to get that it's working. If the pin gets blocked somehow it will error out.

Does the pin actually drop and retract? Is it far enough away from the bed to do so?

I've added M280 P3 S160 I1 to the end of my config.g to clear any errors. It was left over from original testing and I never removed it. If the probe seems to work otherwise, and clearing the error seems to work, maybe you could add it to config.g as well.

[A Former User]

@phaedrux It seems to work fine now but I might just do that anyways. Thanks again

[dc42]

I'm marking this as solved, because the original problem in the title is.