Brand new duet 3 mini, 2 issues
-
@T3P3Tony Here is the information requested
- RRF version: 3.4.5 (2022-11-30)
- PanelDue Version : 3.4.1
- config.g file:
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.15 on Sun Jan 08 2023 17:56:19 GMT+0000 (Greenwich Mean Time) ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"duetPrinter" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E95.00 ; set steps per mm M566 X900.00 Y900.00 Z60.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 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 X220 Y220 Z300 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io0.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io0.in M574 Y1 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in M574 Z1 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin io2.in ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"temp1" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp1 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; disable 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"temp0" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin temp0 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 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"out5" Q500 ; create fan 0 on pin out5 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out6" Q500 ; create fan 1 on pin out6 and set its frequency M106 P1 S1 H1 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 ; Custom settings M501 ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first toolI've also got some images of the various versions for reference aswell:
-
@deamonata can you confirm how paneldue and mini 5+ are wired together?
-
@jay_s_uk I'm using the ribbon cable that was supplied with the PanelDue. I can try the 4 wire though if that might be the issue.
-
@deamonata if you don't need the external sd card on the screen i'd definitely go for the 4 wire. even if you do need the sd card, get started with the 4 wire and we can go from there
-
@jay_s_uk I was just about to try this and check the documentation to see where to connect it to and noticed it wanted to connect to IO0. Are the same pins also used on the ribbon cable as I currently have IO0 configured as on of my endstops.
Could that be the issue?
Obviously I'll need to change the config for the 4 wire option but if it's the same signals on both connectors that that could be the issue.
-
@deamonata yes. io0.in and io0.out are shared between the paneldue port and the io0. That may be causing the issues you're seeing.
I would move your endstop to another io and see if that fixes things first. and if you don't need to external sd card i would switch to the 4 wire cable anyways as its just UART rather than carrying the sd SPI connection and allows you to have much longer runs so it makes it easier to install the screen where you want. -
@OwenD said in Brand new duet 3 mini, 2 issues:
However you will need to update by USB
"From RepRapFirmware version 3.2 (beta 4.1), you can flash the PanelDue firmware from the Duet itself, provided you have a V3/5i/7i PanelDue running firmware 3.2.2 or later"Actually any version 3 PanelDue can be updated from RRF, although if the existing PanelDue firmware is old then you need to press Erase and Reset on the PaneDue.
-
@deamonata said in Brand new duet 3 mini, 2 issues:
Are the same pins also used on the ribbon cable as I currently have IO0 configured as on of my endstops.
Could that be the issue?Yes, that will definitely prevent the PanelDue from connecting.
If you want to use the SD card on PaneDue then depending on the version, you may need to install a jumper on the Duet. See the Duet 3 Mini tab at https://docs.duet3d.com/en/User_manual/Connecting_hardware/Display_PanelDue#card-detect-signal.
-
Excellent. I couldn't find my crimps to change over the wires to the 5 pin connector rightn now But I redid the config anyway and it now works it might be worth adding a note about this to here, as you might notice if you're using the 4wire connector but if you are using the ribbon cable it is an easy thing to do.
-
@deamonata Maybe I spoke too soon. I just powercycled it after uploading the new config and now it's dead. It's not talking to the PanelDue again and now it doesn't connect on the web interface either. The status light is still blinking correctly and the most of the LEDs look right too, however the ESP32 light is off now.
My config.g is now:
; Configuration file for Duet 3 Mini 5+ (firmware version 3.3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.3.15 on Mon Jan 09 2023 17:26:18 GMT+0000 (Greenwich Mean Time) ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"duetPrinter" ; set printer name ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E95.00 ; set steps per mm M566 X900.00 Y900.00 Z60.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 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 X220 Y220 Z300 S0 ; set axis maxima ; Endstops M574 X1 S1 P"io3.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io3.in M574 Y1 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in M574 Z1 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin io2.in ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"temp1" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp1 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M307 H0 B0 S1.00 ; disable 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"temp0" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin temp0 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 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"out5" Q500 ; create fan 0 on pin out5 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out6" Q500 ; create fan 1 on pin out6 and set its frequency M106 P1 S1 H1 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 ; Custom settings M501 ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool -
@deamonata can you connect to the board over USB and get an M122 output?
sounds like its not reading the config correctly -
I've copied the output of M122
M122<CR> === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.4.5 (2022-11-30 19:41:16) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: HBVW7-3096U-D65J0-40KMN-MK03Z-ZXA36 Used output buffers: 1 of 40 (1 max) === RTOS === Static ram: 103652 Dynamic ram: 108776 of which 0 recycled Never used RAM 29284, free system stack 132 words Tasks: NETWORK(ready,7.1%,509) HEAT(notifyWait,0.0%,374) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,341) TMC(notifyWait,0.0%,124) MAIN(running,92.0%,614) IDLE(ready,0.1%,30) AIN(delaying,0.8%,272), total 100.0% Owned mutexes: USB(MAIN) === Platform === Last reset 00:03:05 ago, cause: power up Last software reset at 2023-01-09 17:27, reason: User, GCodes spinning, available RAM 27552, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 186006, completed 186006, timed out 0, errs 0 Step timer max interval 730 MCU temperature: min 21.5, current 25.6, max 25.9 Supply voltage: min 0.4, current 0.9, max 0.9, under voltage events: 0, over voltage events: 0, power good: no Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0 Date/time: 1970-01-01 00:00:00 Cache data hit count 356769640 Slowest loop: 10.33ms; fastest: 0.12ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 3.3ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === 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 ready with "M122" 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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === CAN === Messages queued 930, received 0, lost 0, boc 0 Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 930/0/0 Tx timeouts 0,0,929,0,0,0 last cancelled message type 30 dest 127 === Network === Slowest loop: 0.25ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 0 of 8 = WiFi = Network state is disabled WiFi module is disabled Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485 Socket states: 0 0 0 0 0 0 0 0 ok -
@deamonata said in Brand new duet 3 mini, 2 issues:
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.3ms, write time 0.0ms, max retries 0it seems to be detecting the SD card ok. Can you make sure that config.g is in the correct place and not empty?
-
@jay_s_uk Thats the issue config.g appears to be missing when I plug the SD card in to my laptop. Assuming that it should be in sys/
-
@deamonata yes, it should be.
Can you replace it with the one you posted a couple of posts above? that should get you up and running then we just need to monitor if it goes missing again.
Did you edit it, press save and then restart mainboard? -
@jay_s_uk I used the config tool and uploaded a new file and then restarted the mainboard and initially it all seemed to work, but then I powercycled it and then rebooted it and then I had the problem.
I didn't edit anything else though.
It all seems to be working again now though.
Only thing to figure out now is the random pauses but I'll try having a bit of a play on my own, and gather more information, unless there are any obvious things to check that you already know of.
-
@deamonata when do the random pauses happen?
-
@jay_s_uk all the way through printing, I'm not 100% sure on a pattern but looking at a test print I did it looks like they tended to happen on 90degree turns.
-
@deamonata So I just checked my cura settings I'm guessing that having my gcode flavour setting as Marlin is probably not right. so I'll correct that but could that be causing this behaviour?
-
@deamonata could be. are you using a bed mesh as well?
