ZA and ZB connections ?

Rudy2A

without special instruction G32 will not correct for that missalignment. and it cant to some extend.
get the bed flat first, then continue testing.
i am still waiting for the output of multible G32 commands

Thank you for your involvement, it's very honorable of you ...

what do you mean by "i am still waiting for the output of multible G32 commands"... i didn't understand, sorry (google translator) .

Rudy2A

@Veti said in ZA and ZB connections ?:

j'attends toujours la sortie des commandes multibles G32

Is that what you want to talk about?

Capture d’écran 2019-12-29 à 12.33.19.png

DIY-O-Sphere

Hi Rudy2A,
my experience is, that the Z-axis of the hypercube isn't rigid enough. The frame of the bed bends to much. I would suggest you to improve that fist.
Try to find z-carriages witch connect the beams by plates.

For my modification you will need new bearings. But I have seen similar parts for the standard bearings on thingiverse.
You should also replace the springs by silicon dampers.
After that, the Z-Axis is absolutely reliable. Forget about levelling before every print.
Auto bed leveling can't compensate mechanical weakness.

Regards
Frank

Veti

@Rudy2A

Is that what you want to talk about?

yes. that means your bed is so bad that it does not do any adjustment.
you will need to manual get the bed close to a flat area before you can do normal G32 adjustment.

Rudy2A

@Veti said in ZA and ZB connections ?:

yes. that means your bed is so bad that it does not do any adjustment.
you will need to manual get the bed close to a flat area before you can do normal G32 adjustment.

Even with these values (I can not do better ), nothing happens !

Capture d’écran 2019-12-29 à 15.12.22.png

I'm starting to get lost because I don't understand something!
If the limits of the correction points must not exceed 0.00 mm, what is the point of making an automatic correction with G32, since the limits being at 0, there will be no automatic correction?

I post my files, if a charitable soul can take a look and correct it would be great!

Thank you !

config.g

bed.g

Rudy2A

@DIY-O-Sphere said in ZA and ZB connections ?:

mon expérience est que l'axe Z de l'hypercube n'est pas assez rigide

Thank you for this advice.

Veti

M671 X-10: 240 Y0: 0 S0,5; vis à plomb à gauche (connectées à Z) et à droite (connectées à E1) de l'axe X

duet uses . and not , for decimal, so this command does not work.

M584 X0 Y1 Z2: 4 U4 E3 P3 ; deux moteurs Z connectés aux sorties pilote Z et E1

there should be no spaces in a lot of your commands.
also you should delete the u axis. it is not needed

M207 ; Paramétre de rétraction

thats not a command for the config. it has no parameters.

M558 P1 X0 Z0

bltouch is P9, and this config line is missing a lot of parameters.

G31 P500 Z1.48

you are missing the offset of your probe

Rudy2A

@Veti said in ZA and ZB connections ?:

Thank you for being so kind to watch ...

However, I didn’t understand everything.

M671 X-10: 240 Y0: 0 S0,5; vis à plomb à gauche (connectées à Z) et à droite (connectées à E1) de l'axe X

utilisations en duo. et non, pour la décimale, donc cette commande ne fonctionne pas.

S0,5 Is he the problem?

M584 X0 Y1 Z2: 4 U4 E3 P3 ; deux moteurs Z connectés aux sorties pilote Z et E1

il ne devrait pas y avoir d'espace dans beaucoup de vos commandes.
vous devez également supprimer l'axe u. ce n'est pas nécessaire

OK

M207 ; Paramétre de rétraction

OK

ce n'est pas une commande pour la config. il n'a pas de paramètres.

M558 P1 X0 Z0

This is not an order for the mini IR probe?

bltouch est P9, et cette ligne de configuration manque beaucoup de paramètres.

G31 P500 Z1.48

il vous manque le décalage de votre sonde

I do not use BLTouch, but a mini IR probe ... It seems to me that there is no lag? (to check)

Veti

@Rudy2A said in ZA and ZB connections ?:

S0,5 Is he the problem?

yes

This is not an order for the mini IR probe?

i assumed you have a bltouch because of this
M307 H3 A-1 C-1 D-1 ; Désactiver le chauffage sur le canal PWM pour le BLTouch

but even the mini ir probe has an offset. without the offset you probing will be wrong

Rudy2A

@Veti said in ZA and ZB connections ?:

S0,5 Est-ce le problème?

It’s with people like you that we move forward!

As I start and sometimes I am a little stupid ... if it is not S0.5 what to put, I simply copied from a previously cited example.

For the rest I understood ...

Veti

@Rudy2A

you have to write S0.5
you wrote S0,5

notice , and . duet does not use , for decimal representation.

Rudy2A

@Veti said in ZA and ZB connections ?:

vous devez écrire S0.5
vous avez écrit S0,5

Ok ... frankly, I was far from that mistake . Thank you !

Rudy2A

Hello, thanks to the members of this forum and more particularly to Veti.

I solved my problem and my current tests are very good. I only have a few small adjustments left and everything will be on top!

I still have a question ... I would like to get the best out of G32 and G29 in my impressions. How do you go about your settings?

You make a G32 in your slicer and you included in your Bed.g G29 or G29S1 file or else, you put G32 and G29 (S1) or vice versa in your slicer or do you use another method?

I take your advice once again.

Veti

if you run G32 then you need to run a G29 and not a G29 S1.

Rudy2A

@Veti said in ZA and ZB connections ?:

si vous exécutez G32, vous devez exécuter un G29 et non un G29 S1.

Very good, but in what order? G29 followed by G32 (or vice versa in my slicer or G32 in my slicer and G29 in my Bed.g or other file?

The best solution...

Phaedrux

You can put everything in your slicer gcode if you want it to run before the print every time.

You can use G32 for the leveling tilt first, and then do a g29 to map the surface of the bed. The g29 could be within bed.g and called as part of G32 (which just calls bed.g) or you could have it as a separate command in the slicer start gcode. Up to you. But it is important to correct for tilt before doing the mesh compensation.

Phaedrux

More simply:

Slicer start gcode:

G28 ; home the printer
G32 ; level for tilt
G29 ; mesh bed compensation mapping

Rudy2A

@Phaedrux said in ZA and ZB connections ?:

Vous pouvez tout mettre dans votre gcode slicer si vous voulez qu'il s'exécute à chaque fois avant l'impression.
Vous pouvez d'abord utiliser G32 pour l'inclinaison de mise à niveau, puis faire un g29 pour cartographier la surface du lit. Le g29 peut être dans bed.g et appelé dans le cadre de G32 (qui appelle simplement bed.g) ou vous pouvez l'avoir comme une commande distincte dans le slicer start gcode. Dépend de vous. Mais il est important de corriger l'inclinaison avant de faire la compensation de maillage.

Thank you, quick and precise !!!

This forum is like Duet material, that is to say of quality !!!

dc42

@Veti said in ZA and ZB connections ?:

if you run G32 then you need to run a G29 and not a G29 S1.

It's quite in order to run G32 to correct for loss of sync of the Z motors, followed by G29 S1 to load a height map to compensate for gantry sag and any undulations in the bed surface.

Rudy2A

Happy New Year everyone !

I spoke too quickly ... I realized that when I wanted to print large pieces the leveling of the bed did not work finally!

While searching the forum, I found a case very close to mine, but unfortunately that has apparently not been resolved!

https://forum.duet3d.com/topic/725/still-having-problems-with-bed-compensation-with-the-dc42-probe?_=1578077431668

However, I would point out that before my mini IR probe, I had a BLTouch and the problem was the same!

Thank you.