@fcwilt
It's for a Duet 2 ethernet (1.04)

Fans used for thermal regulation of the printer chamber.

The fan datasheet is requesting 25kHz. I will try a lower frequency, as the command was working in RRF2 with the default PWM frequency.

The fans have a tacho output, but never used it (even cut the wire). Is it needed in RRF3 ?

I tried with and without commenting the M563, no effect.

Ok, I managed to perform the downgrade.

I used the Duet2CombinedBinary.bin from 2.03, and the Duet2CombinedIAP.bin from the 3.1.1.

Ok, looks like a wiring issue on the PWM wire between the Duet and the fan.

Thanks for the support!

Ok, looks like a wiring issue on the PWM wire between the Duet and the fan.

Thanks for the support!

Ok, I managed to perform the downgrade.

I used the Duet2CombinedBinary.bin from 2.03, and the Duet2CombinedIAP.bin from the 3.1.1.

@phaedrux
Thanks.

I'm using the Duet in standalone mode (with printcore link to a RPI 3B+).
Do I put directly the zip file in the /sys folder ?

@fcwilt
It's for a Duet 2 ethernet (1.04)

Fans used for thermal regulation of the printer chamber.

The fan datasheet is requesting 25kHz. I will try a lower frequency, as the command was working in RRF2 with the default PWM frequency.

The fans have a tacho output, but never used it (even cut the wire). Is it needed in RRF3 ?

I tried with and without commenting the M563, no effect.

Hi,

I'm trying to update a config.g (working in 2.03) to a new Duet in RRF3.1.1

All axes are working fine, but impossible to have my fans controlled by the PWM command. (ebm-papst 4-wire fans, with 25kHz PWM command)
The M106 has no effect. The 24V is supplied externally, I only use the Duet to generate the PWM signal (wired to FAN0- pin).

The LED command is working fine, I expect then to not be too far from the truth.

Concerning the sx1509 outputs, can you confirm I need to declare them first with M950 ?
Is my config OK for those ? I receive an error message when trying to use a P value >10 (would have loved to keep the old P120-126 to keep the same slicer/gcodes)

Below my config.g file, with the old RRF2 commands, and my try at updating them to RRF3.

;config.g file hopefully compatible with RepRapFirmware 3.1.1
; Communication and general
M111 S0 ; Debug off
M550 My_new_printer ; Machine name and Netbios name (can be anything you like)

;*** Networking
M552 S0 ; Turn network off

M555 P2 ; Set output to look like Marlin
G21 ; Work in millimetres

;Define axis
M584 X0 Y1 Z2 U3 E4

;Set drive current an idle current at 20%
M906 Z1500 X1500 Y1500 U1500 E1500 I20

;Set inactive time before idle to 5s
M84 S5

; set microstepping with interpolation
M350 X16 Y16 Z16 U16 E16 I1

;Set axis step/unit
M92 Z3200 X3200 Y3200 U44.4 E460

;Set acceleration
M201 Z200 X500 Y500 U10000 E3000

;Set max feedrate (unit/min)
M203 Z600 X600 Y600 U108000 E10000 I1

;Set instant speed changes mm/minute (Jerk)
M566 X1200 Y1200 Z1200 E1200

; Z probe definition
;M558 P5 I1

; Axis and motor configuration
M569 P0 S1 ; Drive 0 X goes forwards
M569 P1 S1 ; Drive 1 Y goes forwards
M569 P2 S1 ; Drive 2 Z goes forwards
M569 P3 S1 ; Drive 3 U goes forwards
M569 P4 S0 ; Drive 4 E goes backwards

;define min and max travel
;RRF2: M208 X-25 Y-25 Z0 u-1000000000000 S1; min travel
;RRF2: M208 X25 Y25 Z92.5 u1000000000000 S0; max travel
;RRF3:
M208 X-25:25 Y-25:25 Z0:92.5 U-1000000000000:1000000000000

;Endstop configuration
;RRF2:M574 X1 Y1 Z1 U2 S1
;RRF3:
M574 X1 S1 P"xstop"
M574 Y1 S1 P"ystop"
M574 Z1 S1 P"zstop"
M574 U2 S1 P"e0stop"

; Disable heat bed to use as command of the LED light
;RRF2:M307 H0 A-1 C-1 D-1
;RRF3.1:
M950 P0 C"bed_heat"
;light ON
M42 P0 S1

; Set Fan : H0
;RRF2: M106 P0 I1 H-1
;RRF3:M950 needed
M950 F0 C"!fan0" Q25000
M106 P0 S0.5

; Set Fan : H1
;RRF2: M106 P1 I1 H-1
;RRF3:M950 needed
M950 F1 C"!fan1" Q25000
M106 P1 S0.5

;set SX1509 outputs
M950 P9 C"sx1509b:0" ;P0 already used by the LED
M950 P1 C"sx1509b:1"
M950 P2 C"sx1509b:2"
M950 P3 C"sx1509b:3"
M950 P6 C"sx1509b:6"

;Tool definition : still necessary in RRF3 to activate the PWM fan command?
M563 P0 D0 F0:1
;Tool selection
T0

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

@fcwilt we always have bad reason for not upgrading

I have a first (exotic architecture) printer still in 2.03, everything working well.
I try to commission a 2nd printer (same hardware than the first), with a new Duet in 3.1.1. I have some issues with a couple of I/O (PWM command to fans, link to a SX1509, ...). I want to be sure not to have a hardware or wiring issue, by testing it with RRF2 and the same config.g than the first printer.
Then if everything is working well, I may explore the new capabilities of 3.x ...

Hi,

Trying to downgrade a fresh Duet2 ethernet currently in 3.1.1, to RRF 2.03
(I tried first to upgrade my config.g to comply with RRF3, but many changes are not working on this new printer, and I want first to test with a known valid version of config.g if the issues are on hardware or config side).

The M997 S0 command is asking for the following files :
Duet2CombinedFirmware.bin
Duet2CombinedIAP.bin

However, the repo for version 2.03 has the following files:
Duet2CombinedFirmware.bin -> OK
iap4e.bin
iap4s.bin

Should I rename one of these iap files to "Duet2CombinedIAP.bin" ?

Hello,

I have some issues reading a SD-card (and then the config.g file) from my freshly received mini 5+, with up-to-date firmware.
In tried several SD cards, 8 or 16GB, all freshly formatted in FAT32, and they are all either not detected or can't be read (M122 P104 S10 report a write error).
Looks then I may have this SD card reader soldering issue?
Can the issue be physically verified by testing continuity on specific pin(s) or else?

Nevertheless, I would like to test it anyway in a degraded configuration as I can't spend weeks of warranty for the moment (it's for a very simple but short term project, just using the bed heater + a thermistor to control it, no driver or other IO used).
I tried to connect the Duet by USB to a RPI 3B+, and using Printrun/pronterface (via pronsole command tool), I was able to send the few config.g gcodes lines I need, one-by-one "by hand" and correctly configure the Duet.
I tried then to automate this "external" configuration by using a python script with printrun python library, which would be executed at the Duet startup. The Duet connection seems to be successful, but then the printrun status never goes to clear=True, which prevents any gcode to be sent.

The Duet STATUS LED blinks nominally (once per second), but is there any internal behaviour that may put it in a specific error mode if no SD card can be read or no config.g file can be loaded?

Do you have any other recommended tool to make this automatic configuration via the RPi ?