@wingtip said in Home Y wont home...:

That solved it. Thank you sir!

Now to decide whether to configure gcode for the bl touch or build the bed first... id rather test it without the bed so i dont smash anything lol.

Glad I could help.

Frederick

With variable declaration, I believe @chrishamm and anyone else can write their own push/pop routine and store/restore any variable they like?

Possibly, but they should have at least one release where they can test old and new version to make sure they behave identically.

Deprecation always is tricky.

@fcwilt That's perfect thankyou again

@Phaedrux I see, thanks for clarification.

Turns out it was a bad cable with it's brand new Slice Engineering thermistor and not an issue with the config.

@Garth_42 said in Extrusion Differences with Mixing Extruder:

For example, a single G1 E1500 command will extrude about half of the material compared to 30 G1 E50 commands.

Is this something you can model mathematically? That is, the actual material flow rate during a movement?

If so, you may solve the problem by preprocessing the slicer's output, transforming the extrusions and gantry movement to fit your model. And then disable the duet's acceleration and jerk restrictions such that it will execute exactly the program your post processor generated.

Just a thought.

@dc42 worked like a charm. Thanks!

@kzamani
Why would you want to (mis-)use the E-stop pins, when there are tons of other unused? GPIO pins on the expansion header? Or did you designate all the available pins already and desperately need some more?
If so, I'd be very interested to see what you are doing with this Duet2...

thanks @deckingman , sound like a good idea: have added T0 to the "clear heater errors" macro. Wasn't necessary in the past.

@Luke-sLaboratory
I can't say I've had a problem of putting a higher voltage than 3.3 volt on the end stop pins , But hate to know how many times I've shorted out the end stop 3.3v pin to ground .

@jay_s_uk i'm in sweden, roughly an hour inlands from gothenburg following E20 in a town called vårgårda

@oliof i honestly didnt think of that

@Shanian79 said in Need Insight! Y Axis Jumping - Cannot Find Cause:

M584 X0 Y1 Z2 E3 ; set drive mapping

next thing to rule out is a bad driver.

change to
M584 X0 Y4 Z2 E3 ; set drive mapping

and move the y connector to e1

The routine does not use the probe to measure. In the routine, I move the Z axis to get the nozzle to table clearance I want and set that to be the new Z0 position. I do find this changes based on bed temperature used. I find the probe OK but since doing this Z offset before every print, I have very few print failures cause by poor first layer.

Before a print I like to,

Bring bed to temperature
Do bed level
Do mesh level
Bring nozzle to temperature
Do Z offset

Then print

These steps have given me very good and repeatable results. Do I have to do this, maybe not, but it takes no time and the results are consistent.

And with these 5 photos I close the discussion.

Test_xyzCube_4_end-1.jpg Test_xyzCube_4_end-2.jpg Test_xyzCube_4_end-3.jpg Test_xyzCube_4_end-4.jpg Test_xyzCube_4_end-5.jpg

Thank you all

@Jordan_Miller41
if you can have it the other way round, with the switch on the tool itself, you'll be able to know which tool is installed and drop the tool off in the event of power loss etc.

You could query the input as part of the TPost file and flag accordingly.
You could also monitor the switches as part of the daemon file to ensure a tool hasn't dropped off mid print

I had read about some problems on RRF 3.2.2. As soon as I have a moment I update both of them and hopefully well.
Thanks everyone for the answers.

Thanks. I may implement the dual switches . Looks like there are solutions except for if 1 motor moves and the other doesn't say if it was at the bottom of travel going towards home. I think I have an idea that can take care of that mechanically/electrically. If it gets too far out of wack it will open/close a circuit that kills power or activates an emergency stop

@LB

One thing I use with the Nimble that others have used is a gimbal to allow the stepper to move which reduces pressure from the drive cable on the extruder assembly.

Overview.png

@resh said in Can't figure out axis limits with dual Z bed leveling:

Thanks guys, I got this working. Should I create a separate macro for this or just run it every time I do a home all? Also, I've seen a youtube video where it does the same probes twice (very fast) before it makes adjustments. Is this necessary?

I home my Z axis using endstop sensors.

I use the Z probe for setting the Z=0 datum, leveling the bed and creating the mesh compensation height maps.

I run the bed leveling procedure at the start of a print.

Check the A and S parameters of the M558 command for how to do multiple probing to improve accuracy.

Frederick

Well assuming 3.3 comes out of beta soon, I will close this for now. I have a workaround for 3.2.2 that always works... it's just weird an annoying is all 😉

@Oliver_Briggs said in Custom PID Controller:

@OwenD Thanks for the response! The M951 command looks like exactly the one. We want to control the current through the voltage without adjusting the height. We've designed a current limiter board, but we want to implement a closed loop controller on the gate voltage to adjust the current.
Goal is: put a voltage on the gate of a power transistor through a custom gate driver, pass the ground wire through a current transformer, transform that current to a voltage to read into the duet. Use that voltage and compare it to the expected voltage (therefore the current), and use a closed loop controller to adjust the gate voltage until the desired welding current is achieved.
Unsure about the electronics for now - there are a few potential solutions in the works. The key thing is to figure out whether we can implement a PID controller on the duet or whether it would require an external board. It says the default sample and correction frequency is 5Hz - do you know what the maximum frequency for this is?

Current transformers only work on AC, whereas I think the current produced by a MIG welder is DC. You can measure the current using a Hall effect current sensor. Most of them have 0-5V outputs, so you can step down the output to 0-3.3V and feed it into a thermistor input configured as a Linear Analog Sensor.

Whatever mechanism you use for passing a control signal from the Duet to the MIG welder should be optically isolated. Does the MIG unit provide an input for controlling the current?