3.4.0beta2 - delta printer prints crooked in y-direction
-
@caijonas please run a few layers of that print and then send M122. Look for "step errors" under the heading Main DDA Ring. If the figure is nonzero, then please connect a laptop running YAT or another terminal emulator to the Duet via USB, and send:
M111 S1 P4
This will enable Move debugging. Then continue the print and watch out for debug info on the laptop. anticipate that you will see one or more blocks of debug data per layer. When you have collected a few, please post them here along with your config.g file and the GCode file you are printing.
-
@dc42 I also get this issue on 3.4b2 on the STM32 port.
Unfortunately nothing shows up in an M122=== Diagnostics === RepRapFirmware for STM32F4 based Boards (fly_e3_pro) version 3.4.0beta2_2 (2021-08-10 16:09:22) running on STM32F4 Used output buffers: 3 of 40 (13 max) === RTOS === Static ram: 21252 Dynamic ram: 77444 of which 28 recycled Never used RAM 31320, free system stack 214 words Tasks: NETWORK(ready,26.2%,225) ACCEL(notifyWait,0.0%,348) HEAT(delaying,0.0%,341) Move(notifyWait,1.7%,292) FSWRITE(notifyWait,0.0%,566) MAIN(running,71.9%,138) IDLE(ready,0.2%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 02:13:36 ago, cause: [software] Last software reset details not available Error status: 0x00 Step timer max interval 0 MCU temperature: min 29.2, current 37.9, max 47.8 Supply voltage: min 18.1, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/86/86, gc cycles 0 Driver 0: position 122979, 2209 standstill, reads 37139, writes 15, error r/w 0/1, ifcnt 38, timeout 0, SG min/max 0/416 Driver 1: position 122979, 2209 standstill, reads 37139, writes 15, error r/w 0/1, ifcnt 38, timeout 0, SG min/max 0/428 Driver 2: position 122979, 2209 standstill, reads 37139, writes 15, error r/w 0/1, ifcnt 38, timeout 0, SG min/max 0/434 Driver 3: position 0, 2209 standstill, reads 37141, writes 13, error r/w 0/1, ifcnt 34, timeout 0, SG min/max 0/48 Driver 4: position 0, 2209 standstill, reads 37144, writes 9, error r/w 0/1, ifcnt 19, timeout 0, 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 Date/time: 2021-08-25 18:41:44 Slowest loop: 21.88ms; fastest: 0.06ms === Storage === Free file entries: 10 SD card 0 detected SD card longest read time 2.7ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 21, maxWait 433006ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 94096, completed moves 94096, 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, chamberHeaters = -1 Heater 0 is on, I-accum = 0.3 Heater 1 is on, I-accum = 0.9 === GCodes === Segments left: 0 Movement lock held by null HTTP 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: 29.17ms; fastest: 0.00ms Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) HTTP sessions: 1 of 8 Uploads/Errors: 0/0 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 Bad header: 0/0 WiFi firmware version 1.26-05S-D WiFi MAC address 70:3a:cb:2a:71:1b WiFi Vcc 3.42, reset reason Turned on by main processor WiFi flash size 4194304, free heap 31888 WiFi IP address 192.168.1.28 WiFi signal strength -64dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00004002 Socket states: 0 4 0 0 0 0 0 0
The issue doesn't occur on 3.3.0
-
-
; Configuration file for Fly-E3-Pro (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.1-LPC+17 on Wed Jun 30 2021 09:24:28 GMT+0100 (British Summer Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Predator" ; set printer name M665 R227 L450 B185 H400 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 D3 V40 ; physical drive 0 goes forwards using TMC2209 driver timings M569 P1 S1 D3 V40 ; physical drive 1 goes forwards using TMC2209 driver timings M569 P2 S1 D3 V40 ; physical drive 2 goes forwards using TMC2209 driver timings M569 P3 S1 ; physical drive 3 goes forwards using TMC2209 driver timings M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X160.00 Y160.00 Z160.00 E415.00 ; set steps per mm M566 X1500.00 Y1500.00 Z1500.00 E1000.00 ; set maximum instantaneous speed changes (mm/min) next try 3000 M203 X18000.00 Y18000.00 Z18000.00 E10000.00 ; set maximum speeds (mm/min) M201 X1100.00 Y1100.00 Z1100.00 E3000.00 ; set accelerations (mm/s^2) next try 6000 M906 X1344 Y1344 Z1344 E560 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; set minimum Z ; Endstops M574 X2 S1 P"e1stop" ; configure active-high endstop for high end on X via pin e1stop M574 Y2 S1 P"pson" ; configure active-high endstop for high end on Y via pin pson M574 Z2 S1 P"e0stop" ; configure active-high endstop for high end on Z via pin e0stop ; Z-Probe M558 P8 C"probe" H5 R0.4 F1200 T6000 A9 ; set Z probe type to switch and the dive height + speeds G31 P100 X0 Y0 Z-0.25 ; set Z probe trigger value, offset and trigger height M557 R180 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"e1heat" T0 ; create bed heater output on e1heat 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 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.060000e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat 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 M308 S2 P"boardtemp" Y"thermistor" T100000 B4092 ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 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 are not defined M207 S5.0 F2400 Z0.5 M572 D0 S0.4 M955 P0 C"B.1+E.8" I50 ; Miscellaneous M501 T0 ; select first tool
AP_Voron_Design_Cube_v7.gcode
The left is 3.4b2 and the right is 3.3.0 -
-
@dc42 Was that using beta2 or beta3?
-
@gloomyandy said in 3.4.0beta2 - delta printer prints crooked in y-direction:
@dc42 Was that using beta2 or beta3?
Beta3.
-
@dc42 Thanks, I should have a build for jay to try of beta3 shortly, just testing it at the moment.
-
@jay_s_uk are you still having this issue with the 3.4b3 build the @gloomyandy did for you?
@CaiJonas which Duet are you using and can you share the gcode that causes the issue. please
I have tested this using 3.4b3 and do not get a leaning issue.
-
@t3p3tony yes, I am.
The left one is 3.4b3 and the right one is 3.3.0
Only change is the firmware version -
@jay_s_uk can you post your config please. Also if possible try a simple hollow cube to see if that also displays the issue please.