Stepper motors ports Duex5 seem to not respond anymore
-
you will use port 5 & 6 on your duex but the m569 p5 & p6 is missing and you write as commend that you have 4 Z motors there are only 3 configured
-
Actually at the begginning we were working with ports 7 and 8 for the other motors, and now we are back to it (so the M569 P7 and P8 code).
Isn't it normal that only 3 motors appear, as on the drive 2 you can have two different motors ? The total is 4 motors...
We think that the problem is linked to an update on the Firmware (in september 2019?)... The Duex is recognized but the information is not driven into the motors.
-
@PaulineC said in Stepper motors ports Duex5 seem to not respond anymore:
2
is it possible that you update your firmware to the latest 2.5.1 (not 3.0!) and then post the result of m122 again
-
I don't see 2.5.1 in the possibilities. We updated the firmware to 2.0 yesterday and it changed nothing :
-
-
you'll find the firmware here
https://forum.duet3d.com/topic/14310/reprapfirmware-2-05-1-duet-2-and-1-26-1-duet-06-085-released/1?_=1581494521559and for the configurator 2.03 to 2.05 would be the one to use after updating the firmware first.
-
@bearer Thank you yes, we downloaded the firmware from here yesterday.
I'll do the M115 command as soon as I get back to the printer in some minutes, and will update the situation.Actually we didn't work on the firmware since june 19, so we were working with 1.21 and everything was ok. I believe now we need to update
-
Okay so did the M115 command, and even if i downloaded the file of the new firmware and put it into the sys file, but it still returns that :
Reprapfirmware for Duet2 Wifi/Ethernet Version 2.0 (RTOS) running on Duet Wifi 1.02 or later + DueX5 Board ID...The update is in a way that I don't get, not working
-
@PaulineC said in Stepper motors ports Duex5 seem to not respond anymore:
so we were working with 1.21
@PaulineC said in Stepper motors ports Duex5 seem to not respond anymore:
The update is in a way that I don't get, not working
there are a few files that have changed names along the way, so either search the forum for the details, read the whats new file or update the board using usb and bossa.
-
@PaulineC Just downloading the file and putting it in the sys folder may not update the firmware. If it doesn't, you need to send command
M997 S0
to install the firmware.Ian
-
@droftarts also hasn't the IAP File changed between 2.0 and 2.05 (not sure but I believe it has I have moved to V3 a fair while ago now).
Doug
-
@Dougal1957 May have done, but will only need to update that if @PaulineC wants to downgrade back to earlier firmware from 2.05.1. We'll see if they get an error trying to update, as they were on 1.21 before, updated to 2.0.
Ian
-
@PaulineC For your config.g, you should define all the motors with M569 and set them for each axis with M584, before setting motor speeds and accelerations. Below is a version of your config.g done like this, without the 'Custom settings' section at the end. Also, it would be best to put motors that are on the same axis on the same board (Duet or DueX), eg
M584 X0:1 Y:2 E:3, Z:5:6:7
. I have not done this below.; Configuration file for Duet WiFi (firmware version 1.21) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Tue Feb 11 2020 18:16:38 GMT+0100 (Central European Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"BigPrinter 2.10" ; set printer name M564 H0 ; allow motors to move without homing first ; Network M551 P"1234" ; set password M552 P0.0.0.0 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; 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 S1 ; physical drive 5 goes forwards M569 P6 S1 ; physical drive 6 goes forwards M569 P7 S1 ; Change direction of Z motor M569 P8 S1 ; physical drive 8 goes forwards M569 P9 S0 ; Change direction of one motor ; Old settings ;M584 X0 Y1 Z2 E3 ; set drive mapping (original) ;M584 X0:9 ; Two X motors on driver 0(default) and 9 of duex ;M584 Z2:5:6 ; Set 4 motors on Z M584 X0:9 Y1 Z2:5:6 E3 ; M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X88.89 Y88.89 Z1600.00 E420.00 ; 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 Y800 Z1200 E800 I0 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X200 Y160 Z0 S1 ; set axis minima M208 X600 Y620 Z700 S0 ; set axis maxima ; Endstops M574 X1 Y1 S1 ; set active high endstops M574 Z2 S2 ; set endstops controlled by probe ; Z-Probe M307 H7 A-1 C-1 D-1 ; disable heater on PWM channel for BLTouch M558 P9 H5 F120 T3000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y52 Z1.6 ; set Z probe trigger value, offset and trigger height M557 X250:550 Y210:580 S75 ; define mesh grid ; Heaters M140 H-1 ; disable heated bed M305 P1 T100000 B4138 R4700 ; set thermistor + ADC parameters for heater 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M106 P0 S1 I0 F500 H-1 ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off M106 P1 S1 I0 F500 H1 T50 ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on ; Tools M563 P0 S"test" 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
Try this, let me know what works.
Ian
-
@droftarts Thanks for the information about the M997 command, it worked perfectly fine and now we're running 2.0.5. Unfortunately, it changed nothing. I'll try using the rework of the config.g file that you just sent, thank you !
Pauline
-
@PaulineC Can you check if the Duex is getting power at the screw terminals with a voltmeter? Check the connections; see: https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring
The Duet is seeing the Duex, because in the response to
M115
you get:
Reprapfirmware for Duet2 Wifi/Ethernet Version 2.0 (RTOS) running on Duet Wifi 1.02 or later + DueX5 Board ID...
So it may just be a power issue. Also check jumpers on the DueX; see https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_JumpersOtherwise, please can you post a picture showing the Duet, Duex and wiring.
Ian
-
@droftarts Your code worked. Thank you so much, I guess it was the fact that the motors were not defined. But I'm kind of puzzled, we never touched the gcode directly, only using the reprapfirmware config tool online. So do you know why it's not working anymore like this ?
-
@PaulineC There's a limit to what the RRF config tool can do, and one of the limits is that it doesn't do custom motor mapping with more than one motor per axis (yet). You can define the Duex; on the 'I/O Mapping' page, click '+ Add Duex 5', and this will give you the option to use the outputs on the Duex. But you can still only map one motor per axis.
Because you added the motor mapping on the end, it meant that those motors did not have their motor settings (jerk, accelerations etc). The M584 command that maps motors to each axis needs to come before this. If not, the motors will usually use default values, but I'm actually not sure if this applies to motors connected to the Duex.
Anyway, glad it's working now!
You may want to update the WiFi Server firmware, and Duet Web Console (DWC) software, too, as I expect yours will be old versions. To do this, upload the following files from https://github.com/dc42/RepRapFirmware/releases/tag/2.05.1 to the sys folder on the Duet:
DuetWiFiServer-1.23.bin
DuetWebControl-SD-2.0.7.zipWhen uploaded, these should ask you if you want to install them. If not, send
M997 S1
to update the Duet WiFi server, andM997 S2
to update Duet Web Control.Ian