Topics created by SANJR

@SANJR said in INTEGRATING WIRE FEEDER TO THE DUET CONTROLLED WELDER:

Configure the WIRE FEEDER as an extruder and use Open Source Slicer to predict the profile/geometry of the bead.
Limitation : for the below code
G1 X100 E2000 F80
for this code the X axis moves 100 mm at a feedrate of 80mm/min. The WIRE FEEDER extrudes wire at a rate of 80 mm/min for the 2000 mm that is the extruder would be feeding the wire even after the X axis would have stopped. This means that the motion of X axis and the WIRE FEEDER would be coordinated and synchronized at the beginning but not at the end. Is my understanding of this option correct?

Not correct. When a move has both axis motion and extrusion, the feed rate refers to the overall axis motion. The extruder feed rate will be adjusted automatically so that the extrusion starts and stops at the same time as the axis motion, with the specified amount having been extruded..

Thanks dc42

Below is the picture of 22 AWG 2 Core + Shield cable from Amazon. Previously used 24 AWG, hope this 22 AWG wouldnt be a issue.

22 AWG 2 Core + Shield Cable.jpg

The updated REVISED SHIELD Cable for reference. Is it okay?
GND (Duet) -> Pin 3 (Endstop)
3.3V (Duet) -> Pin (Endstop)
io.in (Duet) -> Pin4 (Endstop)

REVISED SHIELDED CABLE.png

@SANJR please supply a link to the technical data for the welder and explain how you have connected it to the Duet.

@o_lampe

Thanks for the feedback

Removed the M106 code and changed the Q value to 3000.
Using the macros with M42 CODE now and increased the S parameter value to 255.

The issue persists.

@Phaedrux

Well said..... in a clear and polite manner. Agreed

@oliof said in Multiple motion system homing malfunction:

@SANJR

daemon.g while (true) M596 P1 G91 while (global.weldtorchstate == 1) ; maybe an if-condition would be better here? G1 H4 U99999 F1000 ;selects the U axis & sets the feedrate G4 S0.2 ; this delay should be related to the while(true) loop

Thanks Oliof

Its good now

@o_lampe

Thanks

Will update the same

@dc42

Ur insights on this would be very helpful for us

Ideas to proceed further for the asynchronous movement plzzz

@o_lampe

Thanks, the second motion system is working.

This requirement is completed. Hence can be closed

This setup is completed. Hence can be closed

Hello,

If any additional information needed for the requested above. Please let me know, I would be glad to provide.

@deckingman

Thanks for the feedback

@droftarts Thanks

I will do tryout on both conditions and select the most suitable one.

@SANJR

It seems I organize my system code and my "macros" code differently from most.

In my setup the items in the macros folder are only there to provide access, from the DWC interface, to items in the system folder.

If other words items in the macros folder invoke, via M98, items in the system folder but no items in the system folder invoke items in the macros folder.

There are some items in the macros folder that have a line or two of code but nothing that I ever would need to invoke from the system folder.

Just FYI.

Frederick

@SANJR Order dependencies are listed in the Gcode dictionary, where relevant.
M208

Order dependency

If this command refers to any axes other than X, Y and Z then it must be later in config.g than the M584 command that creates those additional axes.

M671

Order dependency

M671 must come later in config.g than any command that changes the kinematics, e.g. M667 or M669.

So it shouldn't matter if M208 is before M671, or vice versa.

Your M671 does look a bit strange, though.

M671 X5:5:545:545 Y70:455:455:70 S5.0

This effectively says that the leadscrews are within the bed area, at (X,Y) 5,70 and 5,455 and 545,455 and 545,70. As it says in M671:

M671 is used to define the pivot points of the bed or gantry where it connects to the Z axis. These pivot points are often at each leadscrew, but may also be offset from the leadscrews, if the bed/gantry rests on a carriage extending out from the leadscrew, for example on a kinematic mount.

Generally with 4 Z axis motors, I'd expect the pivot points to be where the leadscrews are, rather than on Kinematic mounts under the bed.

Ian

@droftarts Thanks

I have connected the two boards via twisted RJ11 cable now both the boards are communicating.

I have also uptaed the versions of both the boards to 3.4.6. Below is the DWC details of the same.

For Mainboard
M115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.6 ELECTRONICS: Duet 3 MB6HC v1.02 or later FIRMWARE_DATE: 2023-07-21 14:11:38

For Expansion Board
M115 B1
Duet EXP3HC rev 1.02 or later firmware version 3.4.6 (2023-07-21 14:15:46)

@SANJR Yes, you are correct, it should be M308, not M307. I will correct the Gcode dictionary. Thanks!

Ian