Posts made by cichaczech

@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 )

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

@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 commands

Thank you.

@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 release

this 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

@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

@dc42 Ok, will do.
Thank you.

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-beta.3 (2023-04-14 11:27:37) 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: 22192
Dynamic ram: 74716 of which 244 recycled
Never used RAM 15992, free system stack 184 words
Tasks: NETWORK(nWait,11.0%,238) HEAT(nWait,0.0%,386) Move(nWait,0.0%,364) MAIN(running,80.9%,559) IDLE(ready,8.1%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:11 ago, cause: software
Last software reset at 2023-06-09 12:21, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 15492, slot 2
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x0041f803 BFAR 0x6b4bd9b0 SP 0x20003b38 Task Move Freestk 379 ok
Stack: 20008908 00000001 00000270 6b4bd450 a5a5a5a5 0042a6e3 0043cee0 a1000000 00000000 00000000 00000000 00000000 3f800000 00000000 00000000 00000000 2000bcf8 00000000 00000001 2000bcfc 2000487c 00000000 00000000 a5a5a5a5 0042a6e3 a5a5a5a5 a5a5a5a5
Error status: 0x00
Aux0 errors 0,0,19
MCU temperature: min 23.8, current 24.1, max 24.4
Supply voltage: min 23.6, current 23.7, max 23.8, 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 12:21:49
Cache data hit count 418033720
Slowest loop: 8.31ms; 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, comp offset 0.000
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.47ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is 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 27176
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

Hi, with new beta update I have problem in laser mode. When I try home axis or move axis from DWC Duet2 Wifi (Standalone) reboot itself.

Commands like G0 X10 works normaly, but G28 in console -> reboot.
FW 3.4.5 works good.

@Veti said in G30 start Gcode:

you are missing
M574 Z1 S2

this will home to Z MIN with probe after G28, but in homeall is to home to MAX and I wold like to home to MAX
problem was G30 and why if the printer thinks it is in Z0, it trigger BLtouch automaticaly even if Z axis was disconnected

sorry, I forgot. Printer works with multiple tools so config is just generic definition of machine.
For 3D printing I am using macro Hv6BS60.g .

Yesterday I thing I found the problem. I set Home Z max to 250mm but actualy it was 250.8mm, so when I started G30 bed raised to 250 and BLTouch somehow automaticaly click itself even if the bed was still 0.8 below triggering. ???? I don't know. ( I tried disconnect Z stepper an run G30, after the printer was thinking it raised bed 250mm BLTouch clicked and printer was displaing Z = 0.0)
Now I defined Z Max 260 and it seems working fine.

bed.g
config.g
Hv6BS60.g
homeall.g

Board is Duet2 Wifi with firmware 2.04RC3.

Hi,
I have problem to keep righr nozzel distance from bed.
After power up printer it homes all axes and perform bed compensation

G28   ;Z max, X & Y min
G0 X150 Y150
G30 ;find real Z0
G29 S0

When I start printing now without starting script it prints perfectly, but if I use G30 (starting script) it starts printing 0,8mm above bed.

do you know why? thank you

Thank you, finaly yesterday I had a time to work on my printer I was confuzed by the mixing extruders.

the M140 worked, thank you
In my mycro file I already have similar definition of extruder

M563 P1 D0:1 H1 F0 S"Hlava 0.30"  

but it does not work.

Hi,
I will start with my BED heater problem . I have printer with multiple exchangable tools so after power on, I just configure basics parameters same for all tools. After that I select Macro with specific configuration for tool (some of them include heated bed).

After power on I would like to see no heater in Web interface. Heaters shouls be activated after I run macro, but now It seems I somehow configure Bed heater in config.g or it is self configure.
My question is how to remove BED Heater0, from WEB interface, before Macro is run.

First BED Heater 0 is always there, Heater 1 and second Heater 0 shows after my macro.

Second question, I can not run 2 extruders with only one hotend (dual color, one nozzle)
I think my configuration is correct, but E0 wont feed material.

Thank you

Wow, you are really the best thank you.
So for me is the best to stick with the conventional origin front-left, mainly for compatibility with slicers or some controlling softwares.
The thing is that printer will be working with multiple tools. Some larger, some smaller, longer..... And the only point which will be unaffected with tool change is rear-left.
I will change the config.g and home__.g
Thanks again.

Hi,
I am currently building CoreXY printer and I have problem with mesh bed leveling.
I personaly like origin (0:0) to be at rear and left. My setup is:

Endstops - Xmin, Ymin, Zmax (X left from fron view, Y rear)
When I move X+ gantry moves right, Y+ to the front (so when the head is in most forward position X reads +250)

OK my problem - after runing auto bed level, printer thinks that origin (point 0:0) is in forward left so bed compensation is inverted for Y axis.
Is there any way to flip the Y axis and still maintain origin 0:0 at rear-left.
Only solution I found was to set the Ymin to -250 but this will make origin 0:0 in front-left.

Sorry for bothering, but you are my only hope :D.
Thank you.

Hi,
from reviews and HW parameters Duet3D WiFi looks like The best controller board for printers. I am using 3D printers in industrial enviroment and for easy maintenance and overall informations about printers, I am looking for features like logging of all axis distance movements (like odometer in car), total extruded filament, Total hours power on, Last service in (hhhh), Next service in (hhhh with alert), .......
Is it now or will it be avialible in future?

Thank you