problèmes duet 3 mini5+ coreXY

droftarts

@foukouda said in problèmes duet 3 mini5+ coreXY:

RepRapFirmware for Duet 3 Mini 5+ version 3.2-beta3.2+1

This is the firmware version you are currently on. It would be worth updating to the current 3.3 release. From https://github.com/Duet3D/RepRapFirmware/releases/tag/3.3 download the "Duet2and3Firmware-3.3.zip" file, and upload it to the Duet, as a zip file, in DWC on System > Upload a system file.

Your motors are rated at 1.7A, and you are running them at 1.6A. We recommend running motors at 80% to 85% of their rated current maximum, so you should run them at 1.4A. So change

M906 X1600 Y1600 Z1600 E800 I30 ; set motor currents (mA) and motor idle factor in per cent

to

M906 X1400 Y1400 Z1400 E800 I30 ; set motor currents (mA) and motor idle factor in per cent

Reducing the current will reduce the noise, and the stepper motors shouldn't get hot at this setting.

Can you send M569 P0.3 and post the response? This will show how the X drive is set up. Most likely it is changing modes of operation from stealthChop (quiet) to spreadCycle (noisy) at the default speed, which may cause a bang and be noisy when moving.

At the moment, your homing is using a Z endstop at maximum Z, not the probe, for homing:

G1 H1 Z505 F360 ; move Z up stopping at the endstop
G90 ; absolute positioning
G92 Z500 ; set Z position to axis maximum (you may want to adjust this)

But you need to check the probe works first, before changing this. To test the probe, see https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

Then change the lines in homeall.g (and homez.g) to:

G90                     ; absolute positioning
G1 X200 Y200 F6000        ; go to first bed probe point and home Z
G30                     ; home Z by probing the bed

Ian

foukouda

@droftarts said in problèmes duet 3 mini5+ coreXY:

et téléchargez-le sur Duet, sous forme de fichier zip

M569 P0.3
Drive 3 runs forwards, active low enable, step timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, pos 8, tpwmthrs 2000 (2.3 mm/sec), pwmScaleSum 15, pwmScaleAuto 0, pwmOfsAuto 36, pwmGradAuto 14

foukouda

here is a video that can help you
https://youtu.be/4i8183o3-NU

droftarts

@foukouda I can't really tell what's happening in the video. It looks like you are clicking Home X? It sounds like the motors are trying to move very fast. Have you tried testing the motors disconnected from the machine? Have you checked that the motor phases are connected correctly? See https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Using_the_internal_drivers and https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Identifying_the_stepper_motor_phases

Ian

foukouda

I think I'm going to start from zero take it into account your note.
do you think you can provide me some kind of schema code for coreXY 3d printer on which i can base myself?

Thanks for your help

Phaedrux

This may help: https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter

First step would be to identify the motor phase pairs first to ensure the motors are wired correctly. Then in that corexy setup link there are motor tests to perform to determine the correct configuration.

foukouda

hello I just did what you told me and I could see the problem
when I run a command only 1 motor is running. suddenly I checked that the driver was not broken by exchanging the cables is not that. in addition to that I checked the polarity of my motor and it is well done

I will try to make a video to show you

something else my printer is a BLV mgn Cube this can help

foukouda

Hell I have the impression that the printer thinks to be a Cartesian printer yet in the config it is marked

Phaedrux

Are you getting any errors when you try to command the motor that doesn't work?

Which motor/driver isn't working?

foukouda

This post is deleted!

foukouda

This post is deleted!

foukouda

no I have no error message when I execute the command
and it is motor for X that does not work

Phaedrux

So if driver3/X motor isn't working, can you swap X and Y and change the driver mapping in config.g as well and retest? Does the problem follow the motor, or stay with the driver?

foukouda

@phaedrux suddenly I did what you ask me and I stink noticed that it is always the engine designed as the X engine that has problems and I can certify that all my engines are well connected and that all my drivers are working correctly

Phaedrux

@foukouda said in problèmes duet 3 mini5+ coreXY:

M350 X256 Y256 Z256:256 E64 I0 ; configure microstepping without interpolation
M92 X2560.00 Y2560.00 Z12800.00:12800.00 E409.00 ; set steps per mm

Using x256 microstepping for all axis is not recommended because it can exceed the capabilities of the CPU to keep up with step generation. Best to use x16 with interpolation.

@foukouda said in problèmes duet 3 mini5+ coreXY:

@phaedrux suddenly I did what you ask me and I stink noticed that it is always the engine designed as the X engine that has problems and I can certify that all my engines are well connected and that all my drivers are working correctly

Do you mean it's working correctly now?

foukouda

@phaedrux hello. It's been two weeks since I try anything and everything. and I can confirm that the problem comes from the programming and not from the wiring or the mechanical side (motor, driver, ext belt)

for more precision
when I run the G91 command
G1 H2 X10 F3000 this one runs as it should.
but not the command
G91
G1 H2 X10 F3000
and it does the same as in the video that I stink sent

foukouda

@foukouda suddenly I would like to ask you if you can make me a customized program I think you are the best for that

(if you don't mind) thank you very much for taking the time to help me

Phaedrux

@foukouda said in problèmes duet 3 mini5+ coreXY:

for more precision
when I run the G91 command
G1 H2 X10 F3000 this one runs as it should.
but not the command
G91
G1 H2 X10 F3000
and it does the same as in the video that I stink sent

Those are the same commands...

https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter#Section_Testing_motor_movement

It describes what you should do based on how the motors respond to the commands. Have you followed this yet?

foukouda

@phaedrux already sorry I made a mistake in the second order it is not (G91
G1 H2 X10 F3000)
but (G91
G1 H2 Y10 F3000)
it is the motor called Y which does not work constantly.

and yes I followed what you gave me 3 weeks ago.

I will specify when I execute (G91
G1 H2 X10 F3000) this one is executed normally and in the right direction, i.e. + Y + X

when I execute the command (G91
G1 H2 Y10 F3000) the "bug" command and this one makes a loud noise and seems to want to go in a direction except that it seems to be blocked by something (like in the video I posted)

Phaedrux

@droftarts said in problèmes duet 3 mini5+ coreXY:

@foukouda I can't really tell what's happening in the video. It looks like you are clicking Home X? It sounds like the motors are trying to move very fast. Have you tried testing the motors disconnected from the machine? Have you checked that the motor phases are connected correctly? See https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Using_the_internal_drivers and https://duet3d.dozuki.com/Wiki/Choosing_and_connecting_stepper_motors#Section_Identifying_the_stepper_motor_phases

Ian

@foukouda Did you address these questions?

Did you update the firmware to 3.3?