Posts made by ander

@CVMichael i can´t see the video

@o_lampe
I was referrig to a pretty expensive machine that exist already, they use it to measure acurately. it has a sensor where the extruder would go, and touches the part, for measuring.

Hi there everyone!
I´ve been using duet boards for some years now(i already have 3 of them on 3 custom printers).
and i was wondering that technically this machines can be used as a measuring tool.
One of my printers is retired now but, if anyone could give me a hand with the development of the firmware, i could modify it to use it a n automatic three coordinate measuring tool.
What are your thoughts about the idea?

@droftarts
Can anyone help me? it is still giving me the same error.
i run m303 several times, then m500 and still same error when powering on the printer.
Thanks

@droftarts
You are rigth, all the problems started when i upgraded the firmware.
It was giving me errors when heating up the bed. i runned m303 several times, try to do some changes and didn´t work and i changed the heating element for a more powerfull 220v silicon one. the bed itself is 460 in diameter, and yes, it takes a while to heat up.
i run m303 back again to show the results, and see if we can get someting out of it.
m303 h1 s220
Auto tuning heater 1 using target temperature 220.0°C and PWM 0.50 - do not leave printer unattended

Auto tuning heater 1 completed after 3 idle and 5 tuning cycles in 386 seconds. This heater needs the following M307 command:
M307 H1 R5.033 K0.424:0.000 D7.16 E1.35 S0.50 B0 V23.8

m303 h0 s90
Auto tuning heater 0 using target temperature 90.0°C and PWM 1.00 - do not leave printer unattended

M307 H0 R0.175 K0.111:0.000 D15.43 E1.35 S1.00 B0
Send M500 to save this command in config-override.g

Hi there!
Every time i power on my delta printer puts "bad model parameters" on the screen.
And a warning that says heater 1 predicted maximun temperature at full power is 660C.
This is my output of m115 :
m115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2023-07-21 14:08:28
And this is my config.g
config(1).g
Can someone please give me a hand?

@droftarts said in Bed heating problems:

M98 P"config.g"

M98 P"config.g"
Error: Accelerometer not found on specified port
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Endstop configuration:
X: high end switch connected to pin xstop
Y: high end switch connected to pin ystop
Z: high end switch connected to pin zstop
U: high end switch connected to pin e0stopError: bad model parameters
Warning: Heater 1 predicted maximum temperature at full power is 656°C
Warning: Heater 1 predicted maximum temperature at full power is 660°C

@deckingman I just changed the "T" parameter and looks like it is working fine no. thanks so much

By the way, every time i power the duet it says "bad model parameters".

@droftarts there you have it :
config.override.g
config.g

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Feb 27 2020 08:16:33 GMT+0100 (hora estándar de Europa central)

; General preferences
G90                                                 ; send absolute coordinates...
M83                                                 ; ...but relative extruder moves
M550 P"Muxar 3.1"                                  ; set printer name
M584 X0 Y1 Z2 U4 E3 F5                                ; set drive mapping
M665 R228.6 L407.8:407.8:407.8:340 B200 H440        ; Set delta radius, diagonal rod length, printable radius and homed height
M669 X0 Y0                                          ;esto especifica el ofset de la salida del extrusor referente al centro de la mesa
M666 X0 Y0 Z0 F0                                      ; put your endstop adjustments here, or let auto calibration find them
M575 P1 B57600 S1
M955 P0 C"spi.cs2+spi.cs1"
M593 P"mzv" F27


; Network
M552 S1                                             ; enable network
M586 P0 S1                                          ; enable HTTP
M586 P1 S0                                          ; disable FTP
M586 P2 S0                                          ; disable Telnet

; Drives
M569 P0 S1                                          ; physical drive 0 goes forwards
M569 P1 S1                                          ; physical drive 1 goes forwards
M569 P2 S1                                          ; physical drive 2 goes forwards
M569 P3 S0 
M569 P4 S0                                         ; physical drive 3 goes backwards

M350 X16 Y16 Z16 U16 E16 I1      ; Configure microstepping with interpolation
M92 X80 Y80 Z80 U400 E415        ; Set steps per mm

M566 X1200.00 Y1200.00 Z1200.00 U1200 E1200.00            ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z12000.00 U3000.00 E12000.00        ; set maximum speeds (mm/min)
M201 X2000.00 Y2000.00 Z2000.00 U1500.00 E2000.00            ; set accelerations (mm/s^2)
M906 X1200 Y1200 Z1200 U1200 E1200 I30                     ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                             ; Set idle timeout

; Axis Limits
M208 S1 Z-2                                           ; set minimum Z
M208 S0  U1000                                          

; Endstops
M574 X2 S1 P"xstop"                                 ; configure active-high endstop for high end on X via pin xstop
M574 Y2 S1 P"ystop"                                 ; configure active-high endstop for high end on Y via pin ystop
M574 Z2 S1 P"zstop"                                 ; configure Z-probe endstop for low end on Z
M574 U2 S1 P"e0stop" 
M574 F2 S1 P"filamentstop"                                      

; Z-Probe
M558 P8 C"E1stop" H5 F1200 T6000                     ; set Z probe type to effector and the dive height + speeds
G31 P500 X0 Y0 Z-0.26                                ; set Z probe trigger value, offset and trigger height/cuanto mas negativo mas separado de la mesa
M557 R175 S80                                        ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B3950      ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                               ; create bed heater output on bedheat and map it to sensor 0
M143 H0 S120                                        ; set temperature limit for heater 0 to 120C
M307 H0 R0.083 K1.473:0.000 D5 E1.35 S1.00 B0 ;M307 H0 A215.5 C661.6 D5.8 S1.00 V24.0 B1 ;M307 H0 R0.905 K2.126:0.000 D1.06 E1.35 S1.00 B0   ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                                             ; map heated bed to heater 0
M308 S1 P"e0temp" Y"thermistor" T100000 B4725       ; 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               
M143 H1 S250                                        ; set temperature limit for heater 1 to 280C
M307 H1 R3.841 K0.319:0.000 D7.07 E1.35 S0.50 B0 V23.9;disable bang-bang mode for heater  and set PWM limitM307 H1 A346.2 C140 D5.3 B0 S0.8 V23.8
M570 H0 P15 T1 
; 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
M591 D0 P1 C"exp.e2stop" S1                   ; filament monitor connected to E2 endstop

; Miscellaneous
M501                                                ; load saved parameters from non-volatile memory

; config-override.g file generated in response to M500 at 2020-10-01 11:18
; This is a system-generated file - do not edit
; Delta parameters
M665 L407.800:407.800:407.800:340.000 R228.301 H447.033 B200.0 X-0.618 Y-0.603 Z0.000
M666 X0.660 Y-0.395 Z-0.265 A0.00 B0.00
; Heater model parameters
M307 H0 A72.8 C413.7 D0.2 S0.80 V24.4 B0
M307 H1 A933.6 C181.4 D1.5 S0.5 V24.0 P0.2 B0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00 U0.00
G10 L2 P2 X0.00 Y0.00 Z0.00 U0.00
G10 L2 P3 X0.00 Y0.00 Z0.00 U0.00
G10 L2 P4 X0.00 Y0.00 Z0.00 U0.00
G10 L2 P5 X0.00 Y0.00 Z0.00 U0.00
G10 L2 P6 X0.00 Y0.00 Z0.00 U0.00
G10 L2 P7 X0.00 Y0.00 Z0.00 U0.00
G10 L2 P8 X0.00 Y0.00 Z0.00 U0.00
G10 L2 P9 X0.00 Y0.00 Z0.00 U0.00

Hi there!have a delta printer running on a duet2 wifi and was running fine until i changed the firmware to a newer one.
This is what i have rigth now: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.6 (2023-07-21) .
The bed heating started to report errors. i commented in this forum and the suggestion was that the bed was very underpowered, so i put a bigger power supply with an ssr for the bed, was heating faster but not enough, so it was reporting errors of heating too slowly. (i runned m303 in several ocations with m500 afterwards).
So, now i took it a step further, and i put a 220v bed heating element, and run m303. When do in so, i put a value of 60 degrees and when reching it it passes up to 61.6 but no more.
everything kind of normal so far, but if i try to heat it up to 60 and when passes up to 61 it gives an error because it passed the target temperature.
I don´t know what to do at this point

@droftarts
Thanks for the help, it worked beautifly!!

The goal was 70 and failed at almost 60

@Phaedrux

@Phaedrux
After i made all the changes to the bed, and making calibration several times, i´m still in the same spot.
If i try to heat it up, the error pops out.
And yes, i put m500 after doing the calibration process

@dc42
Hi there!
I´m back with my Delta printer. i changed the bed and isolated a bit better, the sensor now is in between the heater and the bed, then i put an isolating foil, and underneath there is a really strong composite material.
I made some tunning procceses back and i couldn´t fix it.
The weird thing is that everything started when i updated the firmware. the one before was 2-3 years old and it wasn´t having any issues with the same bed system.
i also tried to change the sensor but the result was exactly the same
config(6).g
config-override(2).g
i´ll add some pics to see how is built.

I forgot to mention, the screen is telling : "accelerometer not found in specified port" when starting

Hi there!
I have installed an accelerometer LIS3DSH on my duet wifi V1.2.
I was using an ethernet wiring to do the conection but the console was telling me that the accelerometer wasn´t found. I read in this forum that the wiring could be important so i changed the wire with a usb 3.0 cable.
The problem persists.
Sending the M955 P0 : Error: M955: Accelerometer not found
Here is my config.g:
config(5).g
Also, this is my wiring:

Can someone give me a hand please?
This is my 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: 08DGM-917Q9-GLMS8-6JTD2-3SD6P-9YD0B
Used output buffers: 1 of 26 (22 max)
=== RTOS ===
Static ram: 23896
Dynamic ram: 75136 of which 44 recycled
Never used RAM 13004, free system stack 184 words
Tasks: NETWORK(ready,11.4%,242) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) MAIN(running,83.4%,436) IDLE(ready,5.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:17 ago, cause: software
Last software reset at 2024-01-17 16:42, reason: User, GCodes spinning, available RAM 12800, slot 0
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 36.2, current 36.8, max 37.2
Supply voltage: min 23.4, current 23.4, max 23.5, 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: 2024-01-17 16:42:38
Cache data hit count 663459077
Slowest loop: 12.20ms; fastest: 0.18ms
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: 20.0MBytes/sec
SD card longest read time 0.7ms, 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 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.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 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: 25.59ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8

@dc42
Hi there, i´ll try to do those changes and try, and maybe try with another sensor too.
that will be next year maybe. i´ll keep you informed with the results.
thanks

@droftarts
I put the M307 in both( config.g and override)
as wasn´t working fine i made the tunning back again, and send M500 again:
Auto tuning heater 0 completed after 3 idle and 5 tuning cycles in 1133 seconds. This heater needs the following M307 command:
M307 H0 R0.950 K1.299:0.000 D1.36 E1.35 S1.00 B0
Send M500 to save this command in config-override.g
and still doesn´t work
The error i saw was the same as always:
Heater 0 fault: temperature rising too slowly: expected 0.47°C/sec measured 0.10°C/sec
by the way, when switching of and on again the console in the screen says Error: bad model parameters.
Doesn´t say anything in the DWC console but it does in the machine screen (i dunno if could be related)
This is the tunning picture, this time i made it until 80 degrees

@droftarts
Thanks for the help
The tunning has been from cold, you can see that the blue line matches the red line in the beggining .
I tried the m307 you suggested and it did not work either.
the heating element is this style 400mm in diameter and works at 24v.

this heating element is attached to an aluminum plate 450mm in diameter and 4mm thickness.
Under the heating element is a material that covers all made out of trespa.
The output of the duet is attached to an SSR and then goes to the bed.
on top of the aluminum is a magnetic bed but the sensor goes all in one with the heating element as shown in the picture.
The weird thing is this problem started when updating to the latest firmware. before this was working fine.
I dissasembled the bed to check some things but everything is as it was before.