@dc42 Yes, I do use M556. It should be in the config I posted earlier, but I just realized I copied the wrong one, sorry! I'll update it right now.

Posts made by cichaczech
-
RE: [3.6.0 RC1] MultiMotor Z bed leveling
-
RE: [3.6.0 RC1] MultiMotor Z bed leveling
@dc42 Today, I noticed an issue when using G30 the print head with the probe shifts a few millimeters to the right (+X axis) between multiple probing actions and after probing the reported X position in DWC is lower.
Example:
G28 X Y G0 X113 Y200 ;move to bed center G30 ;probe
- The first probe is at X113 Y200 as expected.
- When the bed moves away from the probe, the toolhead slightly shifts to +X before probing again.
3.After probing, DWC updates the X position incorrectly—showing X111.3, even though physically, the tool is still past X113.
2 problems - probe moves between multiple probing and DWC reports wrong axis movment.
This happens on both of my CoreXY printers running firmware 3.6.0.
@Phaedrux I didn't have time to probe it manually today, but I'll try it tomorrow.
-
RE: [3.6.0 RC1] MultiMotor Z bed leveling
@dc42 yes and same configuration. One is just bigger and one smaller. I remember that one time I had some problems with Duet 2 in bigger printer and flash FW with bossa helped me. (I completly forgot abou it)
Update:
No change after BOSSA. Bed is still drifting away.May there be problem with Bltouch? I do not know.
-
RE: [3.6.0 RC1] MultiMotor Z bed leveling
@dc42 so on 2nd printer both firmwares (3.5.4 and 3.6.0 RC1+3) works same, 3.6. mayby bit better. I suspect some problem with Duet2 board on 1st printer. Tomorow I will try flash it with BOSSA.
Sorry for bothering you whole week.
-
RE: [3.6.0 RC1] MultiMotor Z bed leveling
@dc42 still the same with G4 S1 after last G30. I have another printer with 3x Z motors and bed 240x240mm, but it still printing. I will post update when it finishes.
-
RE: [3.6.0 RC1] MultiMotor Z bed leveling
@dc42 leadscrews moves after last G30 P..... S command normaly in 3.6.0 RC1.
Here are my test first 3.6.0 RC1:
then I run 3.5.4 just to test it again:
and then 3.6.0RC1+3:
same printer, gcodes and same conditions - bed 70C hotend 230C.
-
RE: [3.6.0 RC1] MultiMotor Z bed leveling
@dc42 Yes, first I did 3.5.4 -> 5x auto adjust and than G29. immediately after I upload 3.6.0 and run same 5x auto adjust and than G29. I am using same printer, Duet2, config and all gcodes in both examples.
-
[3.6.0 RC1] MultiMotor Z bed leveling
Hello,
I have problem with auto bed levelig with 3 independent motors in FW 3.6.0. In version 3.5.4 it worked well, but with new FW rear motor keeps moving away from ideal plane with every auto leveling pass.
M561 ; Vymaz predchozi zakriveni podlozky G28 X Y ; Home X Y axis G0 X115 Y215 ; G30 ; G4 S1 ; G30 P0 X20 Y400 Z-99999 ; Zjisti vysku Leveho Zadniho rohu G30 P1 X245 Y400 Z-99999 ; Zjisti vysku Praveho Zadniho rohu G30 P2 X245 Y5 Z-99999 ; Zjisti vysku Praveho Predniho rohu G30 P3 X20 Y5 Z-99999 S3 ; Zjisti vysku Leveho Predniho rohu a vyrovnej podlozku G29 ; Zmer zakriveni podlozky
in 3.5.4 :
heightmap(3.5.4).csvin 3.6.0 RC1
heightmap(3.6RC1+2).csvEDIT-
Config:;########################### Komunikace ##################################### M552 S1 ; Aktivuj Wifi modul, pripoj se na znamou Wifi M586 P1 S1 ; Enable FTP M575 P1 B57600 S0 ; Nastav seriovy port Baud 57600, no checksum ;_________________________________________________________________________ ;####################################General preferences########################################## M669 K1 ; Select CoreXY mode M550 P"CichyCore" ; Nastev jméno tiskarny ;M929 P"log.txt" S1 ; Start logging informations ;__________________________________________________________________________________________________ ;###################################Drives########################################################## M584 X0 Y1 Z5:6:7 E3:4:2 ; Set Divers mapping Z-Front Left:Rear Center:Front Right, E-Left, Right, Head M569 P0 S1 ; Physical drive 0 goes forwards M569 P1 S1 ; Physical drive 1 goes forwards M569 P2 S0 ; Physical drive 2 goes backwards M569 P3 S0 ; Physical drive 3 goes backwards M569 P4 S0 ; Physical drive 4 goes forwards M569 P5 S0 ; Physical drive 5 goes forwards M569 P6 S0 ; Physical drive 6 goes forwards M569 P7 S0 ; Physical drive 7 goes forwards M451 ; Nastav FFF Mod M671 X-68.8:131.2:331.2 Y-55.0:540.0:-55.0 S5 ; leadscrews at Front left, Rear center and Front right M593 P"ei3" F54 S0.05 ; Input Shaping M350 X16 Y16 Z16 E16:16:16 I1 ; Configure microstepping with interpolation M92 X100.000 Y100.000 Z3200.000 E96.55:96.55:96.55 ; Set steps per mm (16) [E=(microstep)*200/(pi*gear_dia)] M350 E64:64:64 I0 ; Set extruders microstepping to 64 no interpolation M566 X900 Y900 Z100 E2000.00:2000.00:2000.00 ; Set maximum instantaneous speed changes (mm/min) M201 X10000 Y10000 Z120 E15000:9000:15000 ; Set accelerations (mm/s^2) M203 X30000 Y30000 Z280 E30000:30000:30000 ; Set maximum speeds (mm/min)) M906 X1800 Y1800 Z1000 E1000:1000:600 I30 ; Set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout M556 S1 X0.0044693 Y0.0013474 Z0.0051741 ; Orthogonal axis compensation with M556 M579 X1.003827 Y1.003116 Z0.998213 ; Scale compensation ;_______________________________________________________________________________________________________ ;##############################Limity pohybu######################################## M208 X0 Y0 Z0 S1 ; Set axis minima M208 X269 Y445 Z320 S0 ; Set axis maxima M564 H0 S0 ; Axis Limit H0 = allow movement of axes that have not been homed, S0 = allow movement outside boundaries ;________________________________________________________________________________________________________ ;####################################Endstops##################################### M574 X1 S1 P"xstop" ; X min active high endstop switch M574 Y2 S1 P"!ystop" ; Y max active high endstop switch M574 Z2 S1 P"!exp.e3stop" ; Z max active high endstop switch M591 D0 P1 C"e0stop" S1 ; Extruder 0 Filament sensor, D- Drive, P-type of probe, C-pin name, S- filament monitoring M591 D1 P1 C"e1stop" S1 ; Extruder 1 Filament sensor, D- Drive, P-type of probe, C-pin name, S- filament monitoring M591 D2 P1 C"zstop" S1 ; Extruder 2 Filament sensor, D- Drive, P-type of probe, C-pin name, S- filament monitoring ;_________________________________________________________________________________ ;################################## Vstup/Výstupy - výhrev/PWM ############################## M950 F2 C"FAN2" ;ventilator chlazeni Z Driveru a Elektroniky M106 P2 S0 ;Vypni chladici ventilatory ############Hotend/Bed Heater################## .... ...... ;##########################BLTouch############################ M558 P9 C"^zprobe.in" F200 H5 R0.5 T6000 A5 S0.03 B1 ; Defien Probe - P-BLTouch, C-pin name&pin status, F-Probing speed mm/min, H-Dive height (mm), R-0,2 sec pause after probe, T-100mm/s move betwen probe points, A-Probe 5x or until 2 similar, B1-turn off heaters M950 S6 C"!exp.heater6" ; create servo/gpio 0 on heater 6 pin on expansion connector G31 P80 X20.0 Y3.0 Z1.685 ; Offset BLTouch od tiskove hlavy, P-Citlivost mereni .. M557 X21:245 Y5:395 P4:5
Am I missing something?
Thank you, -
RE: 3.6.0 beta1 - RC1 - Laser not working
@dc42 it is working now. Thank you.
-
RE: 3.6.0 beta1 - RC1 - Laser not working
@dc42 , @jay_s_uk I managed to get it work.
In whole Gcode, even in the end script, there cannot be my M42 P10 S0 for disabling power supply to laser module and before first G1 command there must be G4 command.
Examples that not working:
;Custom GCode device profile, user origin ;Bounds: X69 Y193 to X105 Y210 ;USER START SCRIPT M42 P10 S1 ;USER START SCRIPT G00 G17 G40 G21;Restore metric mode G54 G90;Restore absolute mode G0 X-1.001 Y-1.001 G91;Restore relative mode ;Cut @ 5001 mm/min, 21% power ; ; G0 X1 Y-18 ;Layer C02 G4 P1 G1 X-37 S50 F5001 G1 Y18 G1 X37 G1 Y-18 ; ; G90;Restore absolute mode ;USER END SCRIPT M42 P10 S0 ;USER END SCRIPT
or
;Custom GCode device profile, user origin ;Bounds: X69 Y193 to X105 Y210 G00 G17 G40 G21;Restore metric mode G54 G90;Restore absolute mode G0 X-1.001 Y-1.001 G91;Restore relative mode ;Cut @ 5001 mm/min, 21% power ; ; G0 X1 Y-18 ;Layer C02 ; G1 X-37 S50 F5001 G1 Y18 G1 X37 G1 Y-18 ; ; G90;Restore absolute mode
And this one works:
;Bounds: X69 Y193 to X105 Y210 G00 G17 G40 G21;Restore metric mode G54 G90;Restore absolute mode G0 X-1.001 Y-1.001 G91;Restore relative mode ;Cut @ 5001 mm/min, 21% power ; ; G0 X1 Y-18 ;Layer C02 G4 P1 G1 X-37 S50 F5001 G1 Y18 G1 X37 G1 Y-18 ; ; G90;Restore absolute mode ;
or
;Bounds: X69 Y193 to X105 Y210 G00 G17 G40 G21;Restore metric mode G54 G90;Restore absolute mode G0 X-1.001 Y-1.001 G91;Restore relative mode ;Cut @ 5001 mm/min, 21% power ; M5 G0 X1 Y-18 ;Layer C02 G4 P1 G1 X-37 S50 F5001 G1 Y18 G1 X37 G1 Y-18 ; M5 G90;
with Sticky Laser it fires independently on M3 S0 (M3 S255) before move or M5 after so I choose to run without them, for now.
-
RE: 3.6.0 beta1 - RC1 - Laser not working
@jay_s_uk I am using diode laser and M42 is just switching On/Off power supply to laser module for safety (when handling object inside laser machine). For switching laser output there is S command.
In Lightburn I am using Custom Gcode (experimental) profile to get rid off M3, M5, M7, M8 ... commands.
-
RE: 3.6.0 beta1 - RC1 - Laser not working
;Custom GCode device profile, user origin ;Bounds: X69 Y193 to X105 Y210 G00 G17 G40 G21;Restore metric mode G54 G90;Restore absolute mode G0 X-1.001 Y-1.001 G91;Restore relative mode ;Cut @ 5001 mm/min, 101% power ; M42 P10 S0 ;Vypni napajeni Laseru G0 X37 Y1 ;Layer C02 M42 P10 S1 ;Zapni napajeni Laseru G1 X-37 S254 F5001 G1 Y18 G1 X37 G1 Y-18 ; M42 P10 S0 ;Vypni napajeni Laseru G90;Restore absolute mode ;
-
RE: 3.6.0 beta1 - RC1 - Laser not working
@dc42 Ok, yesterday I tried it only from consele via DWC simple G1 command with S parameter and it was working.
Now I am trying to run program from Lightburn via USB and laser not fires again. If I export gcode from Lightburn a go command by command in DWC Console it fires ok, but not from USB or exported .gcode to Job jist in DWC. -
RE: 3.6.0 beta1 - RC1 - Laser not working
@dc42 with new firmware RC1+2, it works flawlessly. Thank you for the solution
.
-
3.6.0 beta1 - RC1 - Laser not working
Hello, it is me again.
Laser not firing in any release 3.6.0 from beta1 to RC1. Last working stable FW where laser works normally is Release 3.5.4.
I tried
G1 S0 G1 S254 M3 S254 and with or without M563 P0 C"Laser" T0
before any laser movement and also S parameter in G1, but laser not works.
My laser setting in config (Duet2 WiFi)
;#############LASER################ M308 S0 P"e0temp" Y"thermistor" A"LASER Temp" T100000 R4700 B3950 H0 L0 ; Definice temp. senzoru LASERu M452 C"!exp.heater6" R255 F400 S1 ; Enable Laser mode, on out6, with max intensity being 255, and a PWM frequency of 400, S1 - Sticky parameter laser M950 P10 C"e0heat+e1heat" ; Vytvor pin on/off 24V (napajeni regulatoru); Q - frekvence spinani M42 P10 S1 G1 S0 ; NASTROJ ;M563 P0 C"Laser" ; Definuj nastroj 0 LASER ;T0 ; Aktivuj nastroj 0
Thanks for investigating.
-
RE: Command to verify FFF, CNC, LASER
@OwenD Thanks, is there any list with all possible commands or variations of commands? Original Duet manual is a bit limited in informations. ( https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands )
-
Command to verify FFF, CNC, LASER
Hello,
is there a way to verify in which mode the printer is by Gcode metacommand?
I build a 3D printer with changeable tool heads and I have currently running daemon.g
var first_start = true while true if var.first_start == false if heat.heaters[0].current < -250 M999 if var.first_start == true M118 P2 S"HHD" L2 ; Zjisti typ osazene nove Hlavy set var.first_start = false ; Zmena promenne na False G4 S1 ; Vyckej 5s G4 S5 ; Spomaleni smycky 5 sec
which communicates with tool head via UART and is dependent on hotend temperature and it works flawlessly. For CNC and LASER there is no temp sensor so the printer keeps resetting.
I would like to change the dependency from temperature to Mode selected, is it possible?Thank you.
My project - https://www.cichr.com/cichycore.html
-
RE: 3.5.0-B3 Reboot in Laser mode
@dc42 Both of your solutions work.
3.5.0-beta4 -> you have to send G1 S0 after switching laser mode
3.5.0-beta4+ -> works normally in laser mode, without any additional commandsThank you.
-
RE: 3.5.0-B3 Reboot in Laser mode
@dc42 Today I tried delete old FW and instal beta4 with BOSSA, but it still keeps rebooting when I try to home it.
For now I am moving back to last stable releasethis is my latest M122
=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-beta.4 (2023-06-08 23:39:39) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6M2-NW4SS-6JKDD-3S86R-KAZ7L Used output buffers: 13 of 26 (20 max) === RTOS === Static ram: 23236 Dynamic ram: 74836 of which 244 recycled Never used RAM 14828, free system stack 186 words Tasks: NETWORK(2,nWait,12.5%,238) HEAT(3,nWait,0.0%,383) Move(4,nWait,0.0%,364) MAIN(1,running,78.8%,819) IDLE(0,ready,8.7%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:10 ago, cause: software Last software reset at 2023-06-12 09:11, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 14328, slot 2 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x0041f803 BFAR 0x6b4bddd0 SP 0x20003f60 Task Move Freestk 379 ok Stack: 20008d28 00000001 00000270 6b4bd870 a5a5a5a5 004291c3 0043c218 a1000000 00000000 00000000 00000000 00000000 3f800000 00000000 00000000 00000000 2000c168 00000000 00000001 2000c16c 20004bb4 00000000 00000000 a5a5a5a5 004291c3 a5a5a5a5 a5a5a5a5 Error status: 0x00 Aux0 errors 0,0,18 MCU temperature: min 22.2, current 22.7, max 23.0 Supply voltage: min 23.7, current 23.7, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes 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: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2023-06-12 09:11:56 Cache data hit count 397729243 Slowest loop: 9.39ms; fastest: 0.19ms 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: 12.0MBytes/sec SD card longest read time 1.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled === DDARing 0 === 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 === Movement locks 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 assembling a command 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 Q0 segments left 0 Code queue 0 is empty === Filament sensors === Extruder 0 sensor: ok === Network === Slowest loop: 114.56ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(2) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 3 of 8 = WiFi = Interface state: active Module is connected to access point Failed messages: pending 0, notready 0, noresp 0 Firmware version 2.1beta3 MAC address bc:ff:4d:45:e0:c1 Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 38084 WiFi IP address 10.0.0.120 Signal strength -54dBm, channel 1, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0
-
RE: 3.5.0-B3 Reboot in Laser mode
@dc42 still the same
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-beta.4 (2023-06-08 23:39:39) running on Duet WiFi 1.02 or later Board ID: 0JD0M-9P6M2-NW4SS-6JKDD-3S86R-KAZ7L Used output buffers: 1 of 26 (15 max) === RTOS === Static ram: 23236 Dynamic ram: 74836 of which 244 recycled Never used RAM 14828, free system stack 184 words Tasks: NETWORK(2,nWait,12.2%,238) HEAT(3,nWait,0.0%,385) Move(4,nWait,0.0%,364) MAIN(1,running,81.7%,819) IDLE(0,ready,6.1%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:00:15 ago, cause: software Last software reset at 2023-06-09 17:27, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 14328, slot 0 Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x0041f803 BFAR 0x6b4bddd0 SP 0x20003f60 Task Move Freestk 379 ok Stack: 20008d28 00000001 00000270 6b4bd870 a5a5a5a5 004291c3 0043c218 a1000000 00000000 00000000 00000000 00000000 3f800000 00000000 00000000 00000000 2000c168 00000000 00000001 2000c16c 20004bb4 00000000 00000000 a5a5a5a5 004291c3 a5a5a5a5 a5a5a5a5 Error status: 0x00 Aux0 errors 0,0,18 MCU temperature: min 22.9, current 23.5, max 23.6 Supply voltage: min 23.6, current 23.7, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes 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: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2023-06-09 17:28:13 Cache data hit count 558914657 Slowest loop: 8.27ms; fastest: 0.19ms 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: 12.0MBytes/sec SD card longest read time 1.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled === DDARing 0 === 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 === Movement locks 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 assembling a command 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 Q0 segments left 0 Code queue 0 is empty === Filament sensors === Extruder 0 sensor: ok === Network === Slowest loop: 111.94ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 1 of 8 = WiFi = Interface state: active Module is connected to access point Failed messages: pending 0, notready 0, noresp 0 Firmware version 1.27 MAC address bc:ff:4d:45:e0:c1 Module reset reason: Power up, Vcc 3.39, flash size 4194304, free heap 27096 WiFi IP address 10.0.0.120 Signal strength -59dBm, channel 0, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0