@jay_s_uk

Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Thu Mar 04 2021 02:49:06 GMT+0100 (Mitteleuropäische Normalzeit) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; set printer name ; Network M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S0 ; physical drive 0.0 goes backwards M569 P0.1 S0 ; physical drive 0.1 goes backwards M569 P0.2 S0 ; physical drive 0.2 goes backwards M569 P0.3 S0 ; physical drive 0.3 goes backwards M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping M350 X32 Y32 Z32 E128 I0 ; configure microstepping without interpolation M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm M566 X900.00 Y900.00 Z60.00 E60.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min) M201 X3000.00 Y3000.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 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 S1 P"io0.in" ; configure active-high endstop for high end on X via pin io0.in M574 Y2 S1 P"io1.in" ; configure active-high endstop for high end on Y via pin io1.in M574 Z2 S2 ; configure Z-probe endstop for high end on Z ; Z-Probe M950 S0 C"io4.out" ; create servo pin 0 for BLTouch M558 P9 C"^io3.in" H5 F1800 T6000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X-44 Y-9 Z29 ; set Z probe trigger value, offset and trigger height M557 X10:350 Y10:350 S20 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T988801 B4185 C2200 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S110 ; set temperature limit for heater 0 to 110C M308 S1 P"temp1" Y"thermistor" T98801 B4185 C2200 ; configure sensor 1 as thermistor on pin temp1 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S260 ; set temperature limit for heater 1 to 260C ; Fans M950 F0 C"out6" Q20 ; create fan 0 on pin out6 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out7" Q20 ; create fan 1 on pin out7 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"out8" Q20 ; create fan 2 on pin out8 and set its frequency M106 P2 S1 H1:0 T45 ; set fan 2 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 ; Custom settings are not defined ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue M501 ; load saved parameters from non-volatile memory

but do i still need to split the axis during homing, the M584 command? homeall.g homex.g

@Phaedrux said in Tevo Little monster crashes at enstop: G1 H2 X-10 3/3/2021, 5:18:33 PM m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6B2-NJ4S8-6JKDJ-3S46K-TS6QM Used output buffers: 3 of 24 (13 max) === RTOS === Static ram: 23460 Dynamic ram: 72436 of which 24 recycled Never used RAM 16160, free system stack 191 words Tasks: NETWORK(ready,169) HEAT(blocked,308) MAIN(running,451) IDLE(ready,20) Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:19 ago, cause: software Last software reset at 2021-03-03 17:18, reason: User, GCodes spinning, available RAM 16124, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU temperature: min 24.9, current 25.4, max 25.9 Supply voltage: min 24.0, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes Driver 0: position 70856, standstill, SG min/max not available Driver 1: position 70856, standstill, SG min/max not available Driver 2: position 70856, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-03-03 17:18:32 Cache data hit count 22939044 Slowest loop: 5.47ms; fastest: 0.21ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 3.4ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is idle in state(s) 0 Aux is idle in state(s) 0 Trigger is idle in state(s) 0 Queue is idle in state(s) 0 LCD is idle in state(s) 0 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 16.17ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.25 WiFi MAC address 48:3f:da:88:8a:06 WiFi Vcc 3.36, reset reason Turned on by main processor WiFi flash size 4194304, free heap 24400 WiFi IP address 10.0.0.33 WiFi signal strength -44dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 3/3/2021, 5:19:04 PM M98 P"config.g" HTTP is enabled on port 80 FTP is disabled TELNET is disabled Awesome! ok i am homing properly now. Thank you for your time and help im going to follow the Delta calibration you sent me and hope all goes well from here. Thanks again!

It sounds like the Duet is on a different subnet than your computer. The RE450 is probably creating a new network and not bridging between the existing network and it's own wifi network. There might be some settings you can change to allow that. Running the Duet in access point mode might be an option, but isn't as convenient.

maybe try M303 H2 P0.5 S220

@Zerocool1703 said in Connecting multiple heated beds to Duet 3 6HC: ...want to save on power costs... If cost is an issue than 3D printing may not be something for you to invest in. The amount of money I have spent on filament dwarfs the cost of running the printers. I suggest you follow the advice to connect both to the board via the SSRs and use a separate temp sensor for each one. I would also suggest you re-consider using line voltage units. Good luck.

@DocTrucker Hello all, and thanks to @T3P3Tony for the shout out. I'm doing clay printing just about every day, using a dual syringe printer. However, my refilling process is quite straightforward compared to what is proposed here. I pause the print, retract the syringe, insert a fresh tube of clay, extrude a bit to prime the nozzle, and return to printing. If I do this quickly it doesn't show in the print. If I get distracted and make the switch slowly, the object being printed shrinks a little and the first fresh layer stands a bit proud of the others. In these pandemic times I have been documenting what I do more vis video rather than in the classroom (I'm a teacher (of Art)). So if anyone cares to see some clay printing fairly up close with the occasional explanation of process/material/art etc. have a look here: https://www.youtube.com/channel/UCeyNCJtCUtwsq2dWv26BmRA

Sounds like a bad connection to the stepper motor. Check your cable and crimps. Are you getting any error messages along with it? Send M122 and M98 P"config.g" and post the response here. Also post your config.g

This might help: https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview

@deckingman said in Poor print quality with RRF3 - especially 3.2.2.: How do you explain the print to print variability when nothing changes between prints - not even the filament? firmware also didn't change between those prints . i'm not saying the firmware is perfect . I'm just starting with duet3 and i can say that so far with all the various (minor) issues i had , the diagnostics (m122) was pretty much useless in my case . i also didn't like the default homing files , which mark axis as homed even if i dont have a sensor attached to the board (no sensor = NO = HOMED...) . this could potentially cause damage as i'm using large high current motors . back to topic , your print has no layer shifts , so i guess the problem is extrusion related . if i were you , the first thing i would change is the filament . if you didn't print for 19 months , i guess that pla is more then 19 months old . pla degrades over time and its the easiest thing to change .that curling is good indication of degraded filament (if temps were ok). next i would test extrusion / retraction (including firmware ) for example extrude 11mm and retract 1mm 10 times , measure if total is 100 . do this with various feed rates until you reach approx 1.5x your max printing feed rate. if you think its something related to multi axis/ stepper movement then you can add movements during this test . your test print is pretty large , i would use something smaller for tests , even benchy would be better .

Problem solved, the D0 D1 solved it. Thank you very much. You have saved me a lot of time and effort.

check how "proper printing" did it , pretty amazing . https://www.youtube.com/watch?v=OBB5WuhNhWk

Thanks. Have you seen this? https://duet3d.dozuki.com/Wiki/Laser_PWM_control

@AndiG85 said in Duet Wifi Motors wont work after update to RRF3: Warning: motor phase A may be disconnected reported by driver(s) 0 1 Warning: motor phase B may be disconnected reported by driver(s) 0 1 Well that error would indicate that there may be a bad connection on drivers 0 and 1. So double check your wiring. As a quick test you could connect the motors from another axis, like 2 of the Z motors to X and Y and see if it gives the same error. If it does, that may mean the problem is with the driver itself. Can you also provide the results of sending M122? Were you up and running before updating to RRF3?

@dc42 said in Duet Maestro Struggling to Produce Smooth Curves: Thanks, it looks like there is scope to increase the maximum segments/sec for G2/G3 moves then. I'm guessing that on your end steps/sec might be more important, these are 0.9* steppers with the following configuration: M92 X159.93 Y159.75 ; set steps per mm M350 X16 Y16 I1 ; configure microstepping with interpolation

@bernardomattiucci said in Duet2 wifi + Duex5 for large printer with 4 Z motors: I connected the power supply as shown in the photo to the link you suggested (even if the power supply was 30 cm from the boards). there is a big warning on the page Do not run separate ground wires from each terminal block back to the power supply unless the power supply is very close (less than 100mm) to the Duet 2 and Duex. so 30 cm is more than 10cm

@oliof it looks like each G2/3 move has the centre point (cp) in the comment after the command, so you could run a post processing script to use those as I and J values, rather than using R. Ian

He means to use a multimeter to check the 3.3v and 5v pins on the expansion header to see if they are getting power. See the pinout for the expansion header here:

From DC42: Currently we don't support CANopen or any other plain CAN protocol. As the 6HC has dual CAN ports, it may be that we will support plain CAN on the second port in future. However, 3D printing often involves printing several hundred or even a thousand short segments per second, and it's unlikely that any protocol using plain CAN could support that command rate.

Send M552 by itself. It should respond with an IP address If not, send M552 S1. @3dpnut said in Duet 2 wifi not connecting to Paneldue 7i: MCU temperature: min -72.1, current -67.6, max -65.6 Supply voltage: min 16.3, current 16.3, max 16.7, under voltage events: 0, over voltage events: 0, power good: yes Seems like an off temperature for the MCU and odd voltage?

@Phaedrux Thanks! I did this and my return package is already on its way. Thanks for the great service and help.

hey guys sorry off topic but i cant get any help trying to set my laser up on duet 2 wifi with rrf 3.2 its the 12v ali express 40 watt laser can i use buck converter to step down and hook directl y to my fan pins?

Ok, so I received my new Duet 2 Ethernet board today and the first thing I did was flashed firmware 3.2.2 on it. It is working without a glitch so far (fingers crossed). I guess the ethernet module on the other board was bad. I have ordered a replacement for it, so hopefully that fixes my problem.