LE TORRI NEL GRAFICO

alankilian

It looks like I have my endstops adjusted a little better than yours as well as the angle of the rails.

Maybe you could spend some time getting those adjusted better and see if it makes your bed probing produce a flatter heightmap.

rjenkinsgb

@luca-massimiliano said in LE TORRI NEL GRAFICO:

ECCO LE CORDINATE E LE TORRI SULLA STAMPANTE

Ok, the "front" is -Y, between XT and YT.
XT is the corner of the graph with the red-green-blue axis indicators.

As alankillian says, try to get the mechanical setup as accurate as possible first.

Create a bed.g with settings 10-6-6 and as large a radius as you can, without the probe missing the bed:
http://www.escher3d.com/pages/wizards/wizardbed.php

Then run G32 several times! Each should improve the compensation values in the M665 and M666 lines.

Then use M500 to save the final ones, and add M501 at the end of your config to load the config-override file, if you do not already have it.

Hopefully that will give a better heightmap result!

luca Massimiliano

@alankilian GRAZIE , CON LAIUTO TUO E DI TUTTI ,SONO RIUSCITO AD OTTENERE NOTEVOLI MIGLIORAMENTI DEL GRAFICO, QUESTO MI HA FATTO CAPIRE IL POSSIBILE PROBLEMA , LA DEFORMAZIONE NEL TEMPO NON HA PIU' UNA CORRETA GEOMETRIA NELLA PARTE SOPRA , PROVVEDERO' A SISTEMARLA.

luca Massimiliano

@alankilian DOVE SI MODIFICA LA RAPPRESENTAZIOE GRAFICA DA QUADRATA A CIRCOLARE ?

alankilian

@luca-massimiliano

What software are you using to make that image?

luca Massimiliano

@alankilian Elettronica
Diagnostica
Scheda: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware per Duet 2 WiFi/Ethernet 3.2.2 (2021-02-11)
Duet WiFi Server Versione: 1.23

luca Massimiliano

@luca-massimiliano ciao ora ho ottenuto un risultato accettabile ,inserendo modificando co i vari comandi M665 R LB130 H ,M303 per heater , eccetera , salvai con m500 quindi la stampante si accende bene con tutti i dati , ma nel config .g non vengono riportati questi nuovi dati, e' possibile trasferire i dati nella memoria della scheda di Duet . in un file ? grazie cordiali saluti

Phaedrux

@luca-massimiliano said in LE TORRI NEL GRAFICO:

hello now I have obtained an acceptable result, inserting by modifying with the various commands M665 R LB130 H, M303 for heater, etc., I saved with m500 then the printer turns on well with all the data, but in the config .g they are not given these new data, it is possible to transfer the data to the memory of the Duet card. in a file? thank you

M500 saves the data to config-override.g. You must then add M501 to the end of config.g to load the values at startup.

luca Massimiliano

@phaedrux said in LE TORRI NEL GRAFICO:

M500
grazie. ora ho stampato ma il pezzo e' fuori scala , ho modificato M665 L306.17 e ho con un nuovo valore calcolato, ora stampa in scala , ma se do il comando G0 Y-130,X0,Z0, non parte proprio se do G0 Y-125,X0,Z0, ci va (le braccia Z della torre sono al Limite non vanno oltre . ma se riporto M665 L306.17 il comando G0 Y-130,X0,Z0 funziona . come posso risolvere ?

Phaedrux

thank you. now I have printed but the piece is out of scale, I have modified M665 L306.17 and I have with a new calculated value, now it prints to scale, but if I give the command G0 Y-130, X0, Z0, it does not start just if I give G0 Y-125, X0, Z0, it goes there (the Z arms of the tower are at the Limit they do not go beyond. But if I carry M665 L306.17 the command G0 Y-130, X0, Z0 works. How can I solve?

I think you need to redo your calibration.

https://docs.duet3d.com/en/User_manual/Tuning/Delta_calibration

luca Massimiliano

@phaedrux RIFORMULO LA DOMANDA LE MIE ASTE MISURATE SONO M665 L 335 , MA L OGGETTO STAMPATO E' PIU PICCOLO DEL REALE. COME POSSO RISOLVERE?

Phaedrux

@luca-massimiliano said in LE TORRI NEL GRAFICO:

@phaedrux RIFORMULO LA DOMANDA LE MIE ASTE MISURATE SONO M665 L 335 , MA L OGGETTO STAMPATO E' PIU PICCOLO DEL REALE. COME POSSO RISOLVERE?

I REFORM THE REQUEST MY MEASURED RODS ARE M665 L 335, BUT THE PRINTED OBJECT IS SMALLER THAN THE REAL. HOW CAN I SOLVE?

Have you done an auto calibration? G32?

https://docs.duet3d.com/en/User_manual/Tuning/Delta_calibration#auto-calibration

luca Massimiliano

@phaedrux si ho ricevuto il messaggio G32 Error: Auto calibration failed because probe point P3 was unreachable using the current delta parameters. Try a smaller probing radius. ho provato a diminuire il raggi fino 90 da b130 originale ma da sempe lo stesso errore.

Phaedrux

I'm not a delta user myself, so I'm afraid I'm not much help here. Typically though the way forward is to start from the beginning with the calibration of the machine.

luca Massimiliano

@alankilian Ciao, ho modificato m665 l premetto che la stampante stampa ma ecco i problemi, per stampare nelle le dimensione corrette tutto ok , ho lanciato un G0 Y-130 dove 130 e' il raggio bed e non arriva fisicamente con le braccia ( mi sembra che sia tutto piu' grande) e se lancio un G32 lo esegue mi dice di diminuire il raggio bed ,lho fatto nessun risultato . G32
Error: Auto calibration failed because probe point P3 was unreachable using the current delta parameters. Try a smaller probing radius.

alankilian

@luca-massimiliano

What's your M665 and M666 say?

luca Massimiliano

@alankilian said in LE TORRI NEL GRAFICO:

M666

GRAZIE ECCOLE M665
Diagonals 306.170:306.170:306.170, delta radius 182.280, homed height 565.800, bed radius 130.0, X 1.246°, Y -1.600°, Z 0.000°
M666
Endstop adjustments X-1.26 Y0.75 Z0.51, tilt X0.00% Y0.00%

alankilian

@luca-massimiliano

OK, now we need to see bed.g to see where your probing points are located.

I have a smaller delta than you do:

m665
Diagonals 291.060:291.060:291.060, delta radius 144.000, homed height 400.186, bed radius 132.5, X -0.223°, Y -0.216°, Z 0.000°

Here's my bed.g

; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Mar 09 2021 13:21:23 GMT-0500 (Eastern Standard Time)
M561 ; clear any bed transform
; Probe the bed at 6 peripheral and 6 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y109.9 H0 Z-99999
G30 P1 X95.18 Y54.95 H0 Z-99999
G30 P2 X95.18 Y-54.95 H0 Z-99999
G30 P3 X0 Y-109.9 H0 Z-99999
G30 P4 X-95.18 Y-54.95 H0 Z-99999
G30 P5 X-95.18 Y54.95 H0 Z-99999
G30 P6 X0 Y54.9 H0 Z-99999
G30 P7 X47.54 Y27.45 H0 Z-99999
G30 P8 X47.54 Y-27.45 H0 Z-99999
G30 P9 X0 Y-54.9 H0 Z-99999
G30 P10 X-47.54 Y-27.45 H0 Z-99999
G30 P11 X-47.54 Y27.45 H0 Z-99999
G30 P12 X0 Y0 H0 Z-99999 S6
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)

luca Massimiliano

@alankilian ECCOLI
G30 P0 X0 Y84.2 H0 Z-99999
G30 P1 X66.01 Y38.11 H0 Z-99999
G30 P2 X66.01 Y-38.11 H0 Z-99999
G30 P3 X0 Y-84.2 H0 Z-99999
G30 P4 X-73.61 Y-42.5 H0 Z-99999
G30 P5 X-73.61 Y42.5 H0 Z-99999
G30 P6 X0 Y41.05 H0 Z-99999
G30 P7 X29.84 Y-17.23 H0 Z-99999
G30 P8 X-36.81 Y-21.25 H0 Z-99999
G30 P9 X0 Y0 H0 Z-99999 S6

QUINDI IL PUNTO 3 SAREBBE G30 P3 X0 Y-84.2 H0 Z-99999 LHO MANDATO IN CONSOL ,NON DA NESSUN PROBLEMA NE ERRORE

alankilian

@luca-massimiliano

OK, let's make sure your bed.g is being used.

Backup your old bed.g and then use this one.

G30 P0 X0 Y0 H0 Z-99999
G30 P1 X0 Y0 H0 Z-99999
G30 P2 X0 Y0 H0 Z-99999
G30 P3 X0 Y0 H0 Z-99999
G30 P4 X0 Y0 H0 Z-99999
G30 P5 X0 Y0 H0 Z-99999
G30 P6 X0 Y0 H0 Z-99999
G30 P7 X0 Y0 H0 Z-99999
G30 P8 X0 Y0 H0 Z-99999
G30 P9 X0 Y0 H0 Z-99999 S6

You should see:

g32
Error: Unable to calculate calibration parameters. Please choose different probe points.

It should tap ten times at the center of your bed.

If it taps ten times at (0,0) we know you are using this bed.g and we can then start to move on to getting you a good bed.g

LE TORRI NEL GRAFICO

Robert J.