Topics created by pixelpieper

@pixelpieper I'm going to adjust the minimum of the temperature chart dynamically in the next build. It will be the lowest value of the configured temperature presets or heaters[].min.

@dc42 Its a bit of a tradeoff, I want to cover a range from -20ºC to 120ºC, have to compare whether a 10k thermistor would still work well on the upper end - thanks for the suggestion!

@pixelpieper said in Low effort Duet controlled air filter: IKEA Förnuftig:

@jay_s_uk here you go. Note that the VOC activated carbon filter is sold separately.

There are some reports in the Voron forums about activated carbon that is acidic and corrodes the printer, so pick carefully.

I am using this one based on recommendations.

https://envirosupply.net/products/4mm-pellet-virgin-coal-activated-carbon-charcoal-for-vapor-filtration-1-lb-bag?variant=14036431372323

@SputnikOC3d

Hi,

would you share the stl from your umbilical-1lc-mount-combination?

Thank you very much,
Pierre

@bearer said in Duet 2 Maestro and FYSETC Mini12864:

Could you just add which of the two chipsets that display uses? ST7920 or ST7565 iirc.

The Mini12864 uses the ST7565. Displays with the ST7920 such as the reprep discount one are natively supported without the need of a dedicated wiring loom.

Configuration needed:

; Enable LCD M918 P2 E-4

Nevermind, Fixed it - Problem was the order of my commands, I now moved the M140 and M307 to before the M143 definition:

;; thermal ------------------------------------------------- ; Sensors -------------------------------------------------- M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 A"Bedmat"; configure sensor 0 as thermistor on pin temp0 M308 S1 P"e0temp" Y"pt1000" A"Hotend" ; configure sensor 1 as thermistor M308 S2 P"ctemp" Y"thermistor" T100000 B3950 A"Chamber" ;Chamber fan M308 S3 Y"mcu-temp" A"Board" M308 S4 P"e1temp" Y"thermistor" T100000 B3950 A"Bedplate" ; Heaters -------------------------------------------------- ;Bed M950 H0 C"bedheat" T4 ; create bed heater output on out0 and map it to sensor 4 M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M140 H0 ;PID Settings M307 H0 A301.0 C845.3 D1.4 S1.00 V23.6 B0 M307 H1 A482.6 C291.7 D5.5 S1.00 V23.6 B0 ;V6 ; Monitors & Limits M143 H0 P1 T0 A2 S110 C0 ; Regulate (A2) bed heater (H0) to have pad sensor (T0) below 110°C. Use Heater monitor 1 for it M143 H0 P2 T0 A0 S120 C0 ; Fault (A0) bed heater (H0) if pad sensor (T0) exceeds 120°C. Use Heater monitor 2 for it M143 H0 P0 S110 ; Set bed heater max temperature to 120°C, use implict monitor 0 which is implicitly configured for heater fault M143 H1 S400 ; set temperature limit for heater 1 to 275C

@pixelpieper thanks for confirming the cause in the end. And also thanks for taking the plunge and testing 3.2 beta!

Thanks! I enabled that option, I will rather not try it for now since I have a running print...

But that would be pull instead of push, I would like the printer to be able to communicate events at the point of time when they happen. Push whenever an event happens would consume much less resources than contineously pulling...

@dc42 I understand that there are limitations, but I would have assumed that it would be possible to run the interpreter as an rtos tasked with a fixedly preassigned memory budget, enforced by the mpu of the cortex m4. The micropython web page lists a minimum of 8kB of ram, I don’t know however how much pressure there is on the 128 kB available.