ZA and ZB connections ?
-
-
@Rudy2A said in ZA and ZB connections ?:
If, I connect to E0 and ZA, it may be possible?
just use E1.
please read the page i posted earlier about this.
https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors -
@Veti said in ZA and ZB connections ?:
utilisez simplement E1
Frankly, I don't see how you manage to put the G32 or G29 in place ...
Even having connected my first Z to ZA and my second to E1, the result remains the same. I can see my Z engines running independently in my prints, except that the G29 or G32 correction does not work.
-
@Rudy2A
do read the article. you need to do more than just connecting it to e1. -
@Veti said in ZA and ZB connections ?:
lisez bien l'article. vous devez faire plus que simplement le connecter à e1
I read this very good article and especially I followed it to the letter! but unfortunately...
As I said above, I can see my motors running independently (apparently) during my tests, but it is as if the values obtained during G32 or G29 were not taken into account!
-
post your config, your bed.g and the output of multible G32
-
Thanks for your help...
The problem may be mechanical!
I use 4 guide rods (12 mm on linear ball bearings) at the four corners of the support of my bed and a motor in the center of the rods on each side to raise or lower my bed.
I think that the problem comes from there ... I have the impression that this system is not very stable and shifts slightly alone after leveling?
What do you think ?
-
those white belts a a very poor choice for a corexy printer.
see
https://reprap.org/wiki/Choosing_Belts_and_Pulleys -
I second that. Life of the 10mm white steel-reinforced belt was around 3kg of plastic on my CoreXY. However, they are stiffer than the 12mm 2GT belts sold by E3D. Still a good choice if you can use larger bend radii.
Regarding the Z-platform: that does not look too bad to me. Run a mesh calibration, so some movements, run it again, and see what shifted where.
-
@DaBit said in ZA and ZB connections ?:
Exécutez un étalonnage du maillage, donc certains mouvements, exécutez-le à nouveau et voyez ce qui a changé où.
I do a G29, at the beginning of all my impressions and the results are each time slightly different?
I no longer use my Bed.g but only G29 in my slicer.
Is there better for bed compensation, advice or a file to share (which I will adapt to my configuration)?
I also think that by dint of changing my configuration, I may have destabilized it with functions that are useless! -
post a picture of the g29 result.
-
@Veti said in ZA and ZB connections ?:
poster une photo du résultat g29.
Typically a great case ...
When we look at the photo of G29, we can see that the right front side of my bed is far too low and the rear left side of my bed is too high!
Even if I try to lay my bed as flat as possible, the test below remains essentially the same ... as if the height map was not taken into account and yet the motors (ZA and E1) are running much differently.
I print a 5 cm strip that goes around my bed 15 cm from its edge to do a test (with this height chart) and strangely the strip is very flattened only behind my bed in the middle. The rest acceptable and adheres to my bed despite the height map.
It’s as if every time my G29 does its job, except in the middle of the rear. -
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
-
@Veti said in ZA and ZB connections ?:
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 commandsThank 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) .
-
@Veti said in ZA and ZB connections ?:
j'attends toujours la sortie des commandes multibles G32
Is that what you want to talk about?
-
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 -
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. -
@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 !
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 !
-
@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.
-
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 neededM207 ; 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