Duet2 wifi RRF3 homing mixture

[Pertti]

Here´s the result. I´m new with the RRF3 .
Config.g
M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop

;M574 Z0 S0 ; set active low and disabled endstops RRF2.
;M574 X1 Y1 S1 ; set active high endstops RRF2.
;
Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop

---

M119
Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: at min stop

-I do not use z probe

[Pertti]

Meanwhile I updated RRF3.0 to 3.3 by the "Duet2and3Firmware-3.3.zip" -file
The wifi connection disappeared, this did not happen when uppdating from RRF2 to RRF3.0 . Did I do something wrong?
I have had many problems with this board, should I get a new one or should I buy a Duet3? I´m aiming to build a duex printer some day.

[Phaedrux]

@pertti said in Duet2 wifi RRF3 homing mixture:

The wifi connection disappeared,

Occasionally the wifi server update can fail. To get it back, you need to reflash it by sending M997 S1 over the USB terminal.

https://duet3d.dozuki.com/Wiki/FAQ#Section_Cannot_start_wifi_after_a_firmware_update

@pertti said in Duet2 wifi RRF3 homing mixture:

I have had many problems with this board, should I get a new one or should I buy a Duet3? I´m aiming to build a duex printer some day.

I think you're just having some growing pains updating the firmware.

You can send M98 P"config.g" in the gcode console to check for syntax errors.

[Pertti]

@phaedrux
I sent M997 S1 over the USB , and it returned:
Error: M997: File 0:/firmware/DuetWiFiServer.bin not found<LF>ok<LF>
Ok, now the wifi connection was established.
The LCD screen shows up but does not pass any commands and the console does not tell the IP or anything else.
The x and y axes are engaged so that if You move x then x and y move and if You move y then x and y move.

[Phaedrux]

@pertti said in Duet2 wifi RRF3 homing mixture:

Error: M997: File 0:/firmware/DuetWiFiServer.bin not found<LF>ok<LF>

In RRF 3.3 it will look for firmware bin files in the new firmware folder in the root of the SD card. This is to clean up the sys folder that was getting a bit crowded with bin files and config files. Manually placing the bin files into the firmware folder might be needed if they didn't get transferred over during the update. For that to happen, the update would need to be performed using DWC and uploading the full zip file.

But it sounds like you got the wifi updated and working now. But just to confirm, you can send M122 and check the main firmware version at the top of the report. It should be 3.3. The wifi firmware version is found near the bottom of the report and should be 1.26. DWC version should be 3.3 as well.

If you have a connection to DWC now, and you want to make sure you have all the needed files in the right place you can upload the full zip file again.

https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip

@pertti said in Duet2 wifi RRF3 homing mixture:

The LCD screen shows up but does not pass any commands and the console does not tell the IP or anything else.

If you mean for the PanelDue, you need to have a command in config.g to enable it. M575 P1 B57600 S1 near the top of config.g will do it.

@pertti said in Duet2 wifi RRF3 homing mixture:

The x and y axes are engaged so that if You move x then x and y move and if You move y then x and y move.

Is your printer a corexy?

@pertti said in Duet2 wifi RRF3 homing mixture:

M669 K1 ; select CoreXY mode

It's configured as if it is. But is it actually?

You can send M98 P"config.g" in the gcode console to check for syntax errors.

[Pertti]

@phaedrux Many thanks again!
Unfortunately I´m occupied by my employer for a while. Coming back later.

[Pertti]

@pertti
My printer is xy printhead and z bed (built on ruins of a Leapfrog Creatr)
I´m not 100% sure is it a Corexy. I commented M669 and now x and y move correctly! Maybe two z motors and drives are in Corexy, but I have only one.
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Bad command: Endstops (at the moment no endstops connected)

M122

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later

WiFi firmware version 1.26

[Pertti]

@pertti
I commented M669 and now x and y move correctly! Maybe two z motors and drives are in Corexy, but I have only one.

[Pertti]

@pertti
Now things get better . The thermistor H1 came back(!) and H0 bed starts warming but gives a fault message of too slow temperature rising, same with H2. All thermistors seem to get power from the board.
Axes move nicely. There is still hope with this project, after all.

[Pertti]

@pertti
I copied S values from my previous RRF2 configuration, now all heaters work fine!
; Heaters

M307 H0 B1 S120 ; S1.00 ; enable bang-bang mode for the bed heater and set PWM limit

M308 S1 P"e0temp" Y"thermistor" T100000 B3950; B4138 ; configure sensor 1 as thermistor on pin e0temp

M308 S2 P"e1temp" Y"thermistor" T100000 B3950; B4138 ; configure sensor 2 as thermistor on pin e1temp

[Phaedrux]

Sound slike you've got most things working now. That's great.

Can you send M98 P"config.g" once more and report any errors? Also post your current config.g again.

[Pertti]

@phaedrux
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: bad model parameters

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.0 on Mon Aug 16 2021 09:36:00 GMT+0300 (Itä-Euroopan kesäaika)
; Z-Probe commented by user
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name
;M669 K1 ; select CoreXY mode PPremoved thus

; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet
M575 P1 B57600 S1

; Drives
M569 P0 S0 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M569 P4 S1 ; physical drive 4 goes forwards
M569 P5 R0 T10:10:10:10 S0 ; T10:10:10:10 T2.5:2.5:5:5
M584 X1 Y2 E3:4 Z5 ; set drive mapping z TM 6600

M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
M92 X66.67 Y66.67 Z640.20 E837.00:144.00 ; set steps per mm (titan aero)
M566 X900.00 Y900.00 Z60.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z1600 E800:800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X270 Y270 Z180 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop

; Z-Probe
; M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
; G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
; M557 X15:215 Y15:195 S20 ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S120 ;S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B3950;B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M308 S2 P"e1temp" Y"thermistor" T100000 B3950;B4138 ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2
M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S280 ; set temperature limit for heater 2 to 280C

; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1:2 T45 ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 D0 H1 F0 ; 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
M563 P1 D1 H2 F0 ; define tool 1
G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C

; Custom settings are not defined

[Phaedrux]

@pertti said in Duet2 wifi RRF3 homing mixture:

M308 S1 P"e0temp" Y"thermistor" T100000 B3950;B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M308 S2 P"e1temp" Y"thermistor" T100000 B3950;B4138 ; configure sensor 2 as thermistor on pin e1temp

You may need to add a space between the B3950 and ;B4138

Send M308 S1 and M308 S2 in the console by itself to see what it reports.

[Pertti]

@phaedrux said in Duet2 wifi RRF3 homing mixture:

M308 S1

M308 S1
Sensor 1 type Thermistor using pin e0temp, reading 18.6, last error: sensor not ready, T:100000.0 B:3950.0 C:0.00e+0 R:4700.0 L:0 H:0
M308 S2
Sensor 2 type Thermistor using pin e1temp, reading 20.9, last error: sensor not ready, T:100000.0 B:3950.0 C:0.00e+0 R:4700.0 L:0 H:0

[Phaedrux]

@pertti said in Duet2 wifi RRF3 homing mixture:

Error: bad model parameters

Does that error still occur after fixing that missing space?

[Pertti]

@phaedrux
Yes, I´m afraid.
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: bad model parameters

[Phaedrux]

@pertti said in Duet2 wifi RRF3 homing mixture:

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S120 ;S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"thermistor" T100000 B3950;B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M308 S2 P"e1temp" Y"thermistor" T100000 B3950;B4138 ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2
M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S280 ; set temperature limit for heater 2 to 280C

I'm not sure which of these commands is sending that error message.

Can you copy and past each of those lines one at a time to the gcode console? The offending line should produce the bad model parameters error.

[Pertti]

@phaedrux
I got it. This is the one and only line that sends the error message.

M307 H0 B1 S120 ;S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
Error: M307: bad model parameters

[Phaedrux]

@pertti said in Duet2 wifi RRF3 homing mixture:

M307 H0 B1 S120

Ah yes, ok. It's the S120 that is invalid.

That should be S1. It's specifying the PWM power factor in a range from 0.0 to 1.0, not a temperature.

Once that is solved I suggest you re-run the PID tuning process and save the new values with M500 so that it gets written to config-override.g.

M303 H0 S60 will tune the bed heater to 60c
M500 to save the results
M303 T0 S220 will tune the hot end heater to 220c
M500 after to save the results

And make sure you have added M501 at the end of config.g so that config-override.g gets loaded at startup.

[Pertti]

@phaedrux
Thanks for this day, I´ll be back tomorrow.