Posts made by milan.baca

@droftarts Thank you very much, it was it problem solved

@Phaedrux

Hi all, could anyone help me with my issue. I am trying printing with PLA and the speed when printing is very very slow, but travel move is fast as I expect. I do not know what I have wrong.
Speed is also slowing in time. At start it looks ok but it slowing down in time down to 20%. It is not caused by small object, I am printing large one. Fo example after 2 minutes of printing speed lower down from requested 105mm/s to 70 when it prints layer of big square. It looks like it takes to long when accelerating and then decelerating and I see pause(not big pause but noticeable) at end of the line. My second printer with duet3 has not this problem. Please help.

this is output from M122 command and below is my config

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.6 (2023-07-21 14:08:28) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NW4SS-6JKFD-3S86T-KAZHM
Used output buffers: 4 of 26 (24 max)
=== RTOS ===
Static ram: 23896
Dynamic ram: 76008 of which 64 recycled
Never used RAM 8584, free system stack 120 words
Tasks: NETWORK(ready,15.7%,211) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.2%,282) MAIN(running,83.9%,456) IDLE(ready,0.2%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:13:51 ago, cause: power up
Last software reset at 2024-06-08 09:36, reason: User, GCodes spinning, available RAM 8992, slot 1
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
Step timer max interval 0
MCU temperature: min 16.9, current 21.6, max 22.5
Supply voltage: min 21.8, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/88/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0
Driver 1: standstill, SG min 0
Driver 2: standstill, SG min 0
Driver 3: ok, SG min 0
Driver 4: standstill, SG min 0
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2024-06-09 11:11:39
Cache data hit count 4294967295
Slowest loop: 223.49ms; fastest: 0.19ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 6.7ms, write time 114.2ms, max retries 0
=== Move ===
DMs created 83, segments created 28, maxWait 387539ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 366, completed 361, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.3
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X185.802 Y186.672 E3.07944" 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: 210.26ms; 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
WiFi firmware version 1.27
WiFi MAC address 24:a1:60:2f:91:fb
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25048
WiFi IP address 192.168.0.153
WiFi signal strength -54dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E410.48 ; set steps per mm X, Y, Z correction

M566 X900.00 Y900.00 Z120.00 E249.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z2400.00 E6000.00 ; set maximum speeds (mm/min)
M201 X7200.00 Y7200.00 Z200.00 E9000.00 ; set accelerations (mm/s^2)
M906 X1700 Y1700 Z1200 E1700 I30 ; set motor currents (mA) and motor idle factor in per cent
M913 X80 Y80 E70 Z60 ; Set motor current reduction
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-2 Y-27 Z0 S1 ; set axis minima
M208 X296 Y271 Z250 S0 ; set axis maxima

; Orthogonality correction
M556 S1 X0.0060399 ; orthogonality correction

@dc42 thank you very much again R0.3 was the trick

@dc42 triangle lab (not genuine) - but this one I am using on my other printer (I took it from there) with duet2 wifi for years and it works well there

@dc42
G32 command now work well

still have a problem with G29
after few points I got
Error: Probe already triggered before probing move started

ps: should I make a new thread or can I continue here?

@dc42 thank you very much guys problem was in M671 command in numbers

I look at it many times but after you point to that command I saw the problem. It was decimal separator in coordinates

@jay_s_uk
I am using calculator from this project
https://miragec79.github.io/HevORT/firmwaresettings.html

@dc42 config.g

@phaedrux not helped, Error: This kinematics does not support auto-calibration is still there

@phaedrux
I removed G92 Z0 from homeall.g

but still same error

@phaedrux yes I change it to
M350 X16 Y16 Z16:16:16 E16 I1

I change it back to Z16 and now

M98 P"config.g"
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 516C

@phaedrux homeall.g

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3RC3 (2021-05-26 12:29:42) running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
Board ID: 08DJM-956BA-NA3TJ-6J9FJ-3S86R-1T96T
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 150784
Dynamic ram: 62052 of which 160 recycled
Never used RAM 141196, free system stack 126 words
Tasks: SBC(ready,5.2%,338) HEAT(delaying,0.0%,295) Move(notifyWait,0.0%,275) CanReceiv(notifyWait,0.0%,945) CanSender(notifyWait,0.0%,360) CanClock(delaying,0.0%,333) TMC(notifyWait,7.9%,59) MAIN(running,86.8%,922) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:38:42 ago, cause: software
Last software reset at 2021-06-13 15:27, reason: User, none spinning, available RAM 141196, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
Step timer max interval 133
MCU temperature: min 39.4, current 39.6, max 53.4
Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 66722, standstill, reads 27175, writes 23 timeouts 0, SG min/max 0/227
Driver 1: position -24410, standstill, reads 27175, writes 23 timeouts 0, SG min/max 0/227
Driver 2: position 28000, standstill, reads 27184, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 27176, writes 22 timeouts 0, SG min/max 0/228
Driver 4: position 0, standstill, reads 27176, writes 22 timeouts 0, SG min/max 0/233
Driver 5: position 0, standstill, reads 27177, writes 22 timeouts 0, SG min/max 0/246
Date/time: 2021-06-13 16:06:00
Slowest loop: 177.37ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 297675ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 43, completed moves 43, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
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 20904, send timeouts 20901, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 11614/0/0
Last cancelled message type 30 dest 127
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 16462/16462
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8bc
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3-rc3
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.35
Codes per second: 0.09
Maximum length of RX/TX data transfers: 2756/864

M98 P"config.g"
Error: M350: Driver 3 does not support x0 microstepping with interpolation
Driver 4 does not support x0 microstepping with interpolation
Driver 5 does not support x0 microstepping with interpolation
Warning: M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
Warning: M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 516C

@phaedrux
thank for explanation about Z-probe value.

because I have duet3 6HC

I changed line
M558 P9 C"^io7.in" H15 F100 T6000 R0.2 A5

to
M558 P9 C"io7.in" H15 F100 T6000 R0.2 A5

now I got different error

Error: This kinematics does not support auto-calibration

@veti I have 3 independent z motor configuration. I thought than G32 command should auto level the bed, without manual bed leveling.

Hello, I have this problem when I want to use G32 or G29 command.
When G32 it check 3 defined point end than stop and it show me this error "

G32
Error: Probe was not triggered during probing move
Error: Compensation or calibration cancelled due to probing errors".

When G29 common it check 2 points and then stop and show me this error.

bed.g
config.g

Could you help me what could be wrong?

I have tried stable release and also the newest rc release of firmware.
I have BLTouch instaled. It looks work well (stop bed when triggered), but when triggered it should show Z-probe value as 1000, but I have always 0.

garethky - do you have solved this issue?

I do not use Z hop. Also I have heavy bed and 8mm pitch lead screw. But I will try increase max Z speed to 12 mm/s.

After some attemps, I found out that the thing which has big impact on printing time is filament jerk. I set up the Default filament Jerk in Cura, but in the generated code, there were no "M566 Ex" anywhere. So I am thinking the Cura ignores this jerk setting.