Error after upgrade

belgianguy

Hi All,

I just upgraded my firmware to the latest release and after startup, I get an error in line 24: " M350: array too long for parameter 'E' ".

In my config.g, line 24 looks like this:

M350 X16 Y16 Z16 E16 I1

It always worked before. Anyone knows what's wrong?

Thanks for the answer.

jay_s_uk

@belgianguy can you post your full config please

belgianguy

This is my config.g file:

; Configuration file for Duet WiFi
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2 on Mon Feb 25 2019 09:02:50 GMT+0100 (Midden-Europese standaardtijd)

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

; Network
M550 P"3D-Printer Gert" ; Set machine name
M552 S1 ; Enable network
;
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet

; Drives
M569 P0 S1 ; Drive 0 goes backwards
M569 P1 S1 ; Drive 1 goes backwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S1 ; Drive 3 goes forwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z800.00 E145.0 ; Set steps per mm
M566 X900.00 Y900.00 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; Set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; Set accelerations (mm/s^2)
M906 X800.00 Y800.00 Z800.00 E800.00 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 X350 Y350 Z400 S0 ; Set axis maxima

; Endstops
M574 X2 Y2 S1 ; Set active high and disabled endstops

; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2.682 ; Set Z probe trigger value, offset and trigger height
M557 X30:350 Y15:350 S100

; Heaters
; M307 H0 B0 S1.00 ; Disable bang-bang mode for the bed heater and set PWM limit
M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S290 ; Set temperature limit for heater 1 to 290C

; Fans
M106 P0 S0.3 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

; 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

; Filament sensor
M591 D0 P1 C3 S1 ; Filament Sensor (Extruder0)

; Automatic saving after power loss is not enabled

; Custom settings are not configured
M501

jay_s_uk

@belgianguy you're missing an M584 to set the driver mapping. https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m584-set-drive-mapping
No M584 means no extruder driver
Something like M584 X0 Y1 Z2 E3 assuming those are the drivers you are using for each axis

belgianguy

@belgianguy Thanks, that did it. All is working again. Thank you for the fast solution

droftarts

@belgianguy FYI the reason for this error was because of a change in the firmware. I guess you were on RRF 3.2.2 or earlier, and updating to a version later than RRF 3.3, because (from the M584 Notes):

VERY IMPORTANT! From RRF 3.3, X (driver 0), Y (driver 1) and Z (driver 2) are assigned by default. There are no default extruder drives; all extruder drives must be declared explicitly using M584. Changing an existing drive (i.e. X, Y or Z) to a different driver with an existing assignment will result in two axes using the same driver, e.g. M584 X1 results in 'Driver assignments: X1 Y1 Z2'. Changing a drive to an unassigned driver results in the drive moving to the new driver, e.g. M584 Z3 results in 'Driver assignments: X1 Y1 Z3'. This may result in unexpected behaviour. It is best practice to define all drives explicitly as in the above example, if you are not using the default drive/driver assignments.

This is also mentioned in the changelog: https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-33

We always advise reading the changelog when updating firmware. There is rather a lot of it to plough through, but things do change! There is also @MintyTrebor 's ReleaseMgr DWC Plugin: https://github.com/MintyTrebor/ReleaseMgr which can highlight changes.

Ian

belgianguy

@belgianguy Correct, I was indeed on an earlier version where this problem didn't occur. Thanks for the extra information.