Posts made by moth4017

in the above dialogue box can there be an option to add number of measurements in x and y , instead of distance.
eg, X=5 y =8

from the settings above i ran an auto tune to see how long it would take , ambient air 18C
M303 H0 P1 S100
the PID tune took 37 minutes and i got back this response

Warning: heater behaviour was not consistent during tuning
Auto tuning heater 0 completed after 4 idle and 25 tuning cycles in 1620 seconds. This heater needs the following M307 command:
M307 H0 R0.812 K0.268:0.000 D3.35 E1.35 S1.00 B0
Edit the M307 H0 command in config.g to match this. Omit the V parameter if the heater is not powered from VIN.

My first auto tune took much longer

so my bed has been working fine with those settings above and the results were not much different .

previous settings working ok "M307 H0 R0.838 K0.331:0.000 D3.08 E1.35 S0.90 B0"
settings after the PID tune "M307 H0 R0.812 K0.268:0.000 D3.35 E1.35 S1.00 B0"

@DonStauffer the bed PID tune does take a long time i have a 340mm x 340mm x 8mm thick Keenovo 700W /220Vac , if you have a heated or insulated chamber even longer .
here is my PID tune if it helps

My sensor is in a hole drilled in the edge of the aluminum bed . not using the one on the silicone heater

M307 H0 R0.838 K0.331:0.000 D3.08 E1.35 S0.90 B0

if you send M307 H0 in the console you will get a report
Heater 0: heating rate 0.838, cooling rate 0.331, dead time 3.08, max PWM 0.90, mode PID
Predicted max temperature rise 198°C
PID parameters: heating P69.2 I2.156 D149.1, steady P69.2 I6.103 D149.1

@mirellehgf something as simple as a silicon sock on the heater block can help , especially if your part cooling fan is blowing on it .

@gloomyandy i did look , great

When there is an error in a Macro file the error message in the console is like this
Error: in file macro line 32 column 33: meta command: unknown variable

Can it also name the macro file instead of just "Macro" it would make tracking down the issue much easier .

cheers

@dc42

have i done this correctly to capture the "Time out"

M291 R"Do you want to Run G29" P"your choice" S4 T5 J2 K{"Yes", "Reuse height map" ,"clear heightMap"} F5
    if input = 0
        echo input
        G29    ; use saved height map
    elif input = 1
        echo input
        G29 S1 P"/sys/heightmap.csv"; load previous height map   
    elif input = 2
        echo input
        G29 S2 ; clear height map
    elif input = -1 
        echo "no selection pressed" ;G29 S1 ; load previous height map 
        echo input

When using the M291 with a T value for time out , i carnt seem to capture this event .

M291 R"Do you want to Run G29" P"your choice" S4 T5 J1 K{"Yes", "Reuse height map" ,"clear heightMap"} F5
    if input = 0
        echo input
        G29    ; use saved height map
    elif input = 1
        echo input
        G29 S1 P"/sys/heightmap.csv"; load previous height map   
    elif input = 2
        echo input
        G29 S2 ; clear height map
    else 
        echo "no selection pressed" ;G29 S1 ; load previous height map 
        echo input

selection 1 returns this:-
8/31/2024, 4:02:19 PM M292 R{1} S21
1
time ouit selection nothing returned

@Zoltan3D you should beable to put this in a macro to turn it off

M591 D0 S0 ;D = extruder number S0 =off

@droftarts What is the maximum current that each FET can handle using an external power supply?

@Kiwi3D im core XY , , you are core Xz
but you should still be able to use my home x , you need to modify it for your core XZ

something like this

; homex.g
echo "home the X axis"
M400                                 ; make sure everything has stopped before we make changes
G91                                  ; relative positioning
M915 P0.0 S5 H200 F0 R0              ; Configure Stall Detection
M906 X550                            ; set homing motor current
G1 F8000
G1 H1 X-350                          ; Home X-Axis independently
M906 X1000               	     ; set homing motor current
M915 P0.0 S35 H500 F0 R1             ; Configure Stall Detection
M400                                 ; make sure everything has stopped before we make changes
G90                                  ; absolute positioning
G1 F12000 X152.5

@Kiwi3D up your homing speed to F8000 ,

here is my x homing, your need to change out my motors numbers for yours

; homex.g
echo "home the X axis"
M400                                 ; make sure everything has stopped before we make changes
G91                                  ; relative positioning
M915 P0:1 S5 H200 F0 R0              ; Configure Stall Detection
M906 X550 Y550                       ; set homing motor current
G1 F8000
G1 H1 X-350                          ; Home X-Axis independently
M906 X1000 Y1000               		 ; set homing motor current
M915 P0:1 S35 H500 F0 R1             ; Configure Stall Detection
M400                                 ; make sure everything has stopped before we make changes
G90                                  ; absolute positioning
G1 F12000 X152.5

@Kiwi3D is your steps/mm correct, move the x axis 20 mm does it move 20mm?

What type of printer do you have as in make? ,
has it been working before?
have you made any chages?

they are not fuses they are jumper links
https://www.aliexpress.com/item/1005005414075962.html

(admin: removed tracking data from link)

@Phaedrux i tried viewing DWC in Prusa slicer in their "physical printer" it works ok in that , so i guess its an orca slicer problem.

issues submitted to orca team, please close

@Phaedrux

BROWSER GOOGLE CHROME
ZOOM 100%

BUT the DWC window is viewed in Orca slicer Device

when the speed goes 0ver 99.0mm/s the mm/s drops to a lower line increasing the status box size .

In DWC if you use M141 it will auto set this for Chamber

Is there an option to set "Dry Box temperature M14?

@deckingman Hi im not trying to measure the RH at the HT but i need the sensor to survive the higher temperature , when drying filament at high temperatures the humidity sensor is in the same enclosure . also use it to dry desiccant.