@jay_s_uk

Connected the Duet to the computer. Thanks for the support provided

@Phaedrux Thanks

I would start testing the motors movement very soon, after that i would test the G30 as well.

@Phaedrux Hi,

The X Axis Stepper Motor is being tested when the Emergency Push Button is pressed.

The Y And Z Axis Motor were working fine after the EPB usage.

Since the Other Axes were having multiple motors i was not able to test them with X Axis driver.

However after a brief time with a shutdown and restart the X Axis was working fine.

@jay_s_uk Thanks for the update provided

Thanks

The last line for the drivers of expansion board M307 G-Code is used is this correct? Should i replace it with the M308.

In the documentation it is mentioned as M307. But on referrring the G-Code M307 is to set the heater process parameters.....

It´s very disturbing to see a post with the words ¨offended, our cultural surrounding, common sense owning the probelm¨. Sorry to say these reflect the state of mind.

Not sure the messages where i have posted was refering the forum to balme. Definitely that was not i meant, then why was it taken like this? This is not a matured way of communication in a well respected forum..... I just wanted to make sure the same problem is not repeated by others elsewhere. And the spoken and unspoken are really hard and difficult to understand as per what ever the standards is being refered too......

What is the point of contextion here? Accepting the error was...really.....???

Word Civilized itself represent the members of the forum are well respected.....

Really think either the choice of words and the whatever is really being taken out of the context.......

And personally i have nothing against to anyone with an cultural inquisitive thought

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.

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)

@deckingman

Thanks Everyone

I will try the code and update in this post

@OwenD

Thanks Owen

The Video explanation was really helpful in understanding few areas where I was sceptical. So once again thanks very much.

Now as rightly said in the video and explained in this post, In order to have a either a droplet transfer or bridge transfer at any cost the wire plunging to be avoided. In addition, unlike an extruder the wire is feed at an angle to the torch. Finally as Owen rightly pointed out the issues of omnidirectionality is a key issue.

So in order to control these issues one of the way is to play with the WIRE FEED RATE.

Based on the discussions in this post summarized the possible option each with their limitations

1. 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?

2. Configure as an U axis by multiple motion system
   Limitation : A) daemon.g file needs to rename as .PART to update the F parameter and the machine needs to switched
   OFF and ON for a certain time like 15-20 mins for the feed rate to update.
   B) Not able to vary the WIRE FEEDER FEED RATE in a continuous tool path.
   C) Not able to expand for 2nd WIRE FEEDER, only 2 multiple motion systems are possible

3. Install separate WIRE FEEDER systems and configure as IO through a 5V relay to control the ON/OFF operation through DUET. And the speed can be adjusted by WIRE FEEDER Potentiometer. By this option additional WIRE FEEDERs could be added if required.
   Limitation : -

Coordinated and Synchronized movement at the beginning and end are required. In such a scenario option 1 doesn´t suit the purpose. Option 2 has limited flexibility

Any corrections or suggestion would be most welcome plz........

@deckingman

Thanks

For a better understanding, lets consider for example

G1 X100 E2000 F50

As per the above the code the X axis moves 100 mm at a rate of 50 mm/min, the extruder feeds the wire for 2000 mm but at a higher feed rate since the 2000 has to be completed at the same time of X100.

Is my understanding correct?

@OwenD

Hi Owen,

Good to hear from you

Separate Wire feeder is not used for the designed setup.

I have built an custom wire feeder using a stepper motor and configured it as an U axis, hence using multiple motion system

@dc42

Apologies dc42, hope my explanation is not clear. I will try to explain with the below code which i am currently using for welding.

The below code switches the WELDER ON @ X250 and travels until X360. The line 5 parameter F80 represents the WELD TORCH TRAVEL speed (torch mounted on the X axis bundle). If i try to input the WIRE FEEDER configured as U axis in the same line 5, unable to change the feed rate separately for the WIRE FEEDER, instead only a single feed rate is followed by both the axis i.e., X & U.

M98 P"0:/macros/WELD TORCH OFF+SM"
G1 X250 Y345 Z150 F2000
G1 Z123.10 F2000
M98 P"0:/macros/WELD TORCH ON+SM"
G1 X360 F80
M98 P"0:/macros/WELD TORCH OFF+SM"
G1 Z150 F500
G1 X250 Y345 Z150 F2000
M98 P"0:/macros/WELD TORCH ON+SM"
G1 Z151 F2000
M98 P"0:/macros/WELD TORCH OFF+SM"

@dc42

Greetings dc42

Herewith attached REVISED END STOPPER WIRING LAYOUT.

In the existing plan, the io.in pin of duet is connected to the S pin of the end stopper (PIN:4). In the REVISED Layout this S pin (PIN 4 of end stopper) left blank and from the shielded Wire Signal cable, the shield cable is connected to GND (DUET) and central conductor is connected to io.in pin (DUET).

Is this layout correct. Requesting for any corrections or suggestions plz

@dc42

Thanks dc42

@dc42

Thanks dc42, Its always good to hear from you

I was planning to configure the wire feeder like an extruder. But the WELD TORCH travel speed is much lesser when compared to an WIRE FEEDER.

Lets say for example
Torch Travel Speed : 100 mm/min (Torch is installed on the X axis bundle, so its feed rate is controlled by the X axis motor)
Wire feed rate : 1000 mm/min (Wire feeder configured as U Axis)

So during welding, torch travel speed would be slower and the wire feed rate is significantly higher by almost 10 times. In order to achieve this independent feed rate control the MULTIPLE MOTION SYSTEM was incorporated by integrating the TORCH ON/OFF with WIRE FEEDER ON/OFF.

Yes as you rightly said, torch is SWITCHED OFF during travel moves and so the wire feeder.

If there is any other alternative to achieve this kind of independent feed rate control apart from the multiple motion system. I would like to try it as in the future i may have to add up more wire feeder which would have independent feed rate with the other wire feeders and torch.

Greetings,

I am using a welder On/Off CONTROLLED Via 5V Relay by Duet 6HC Main board. Planning to separate the existing wire feeder (configured as multiple motion system so as to have an independent feed rate/control to the 3 axis motion system) to an SEPERATE WIRE FEEDER SYSTEM.

The current system WELD ON/OFF and WIRE FEEDER ON/OFF is integrated through an daemon.g. On separating the wire feeder the daemon.g may not be required, but would like to retain the current coordinated action/command of the WELDER and WIRE FEEDER.

The Wire Feeder has an TRIGGER CONTROL unit, planning to connect this with a 5V relay to IO Port of the Duet 6HC mainboard and control the On/Off of the feeder through a macro file similar to the the welder operation. Does this idea workout? Is there any other details i have to look on......

Requesting the suggestion/feedback plz....