Topics created by Ntrack

Spelled tty wrong*, but yes.

*)could be auto carrot perhaps

I redid the wiring that way and it works now. I left both the positive and negative 12cm short.Thank you.

I’ll have to wait for variables then.I think I have an idea how to do it using a variable.

This is a bug in 3.01beta2. It is fixed in the internal builds at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0.

I am almost there with the homing file using conditional code.

if sensors.endstops[4].triggered && state.status.idle M291 P"MMU loaded. Selector homing not allowed.Please unload MMU manually." S2 if sensors.endstops[4].triggered && state.status.printing M25 M291 P"MMU loaded. Selector homing not allowed.Please unload MMU manually." S2 else M913 U50 ; reduce motor current to 50% to prevent bad noises M915 U S5 F0 ; set stall parameters G91 ; use relative positioning G1 H1 U5 F2000 ; move out 5mm G1 H1 U-100 F1000 ; move carriage to home G90 ; back to absolute positioning M400 ; make sure everything has stopped before we reset the motor currents M913 U100 ; motor currents back to normal

But , obviously is not working because state.status.idle is not the correct way of expressing the value of state.status.

Here is the state tree. Surely this is trivial for anyone who is used to any type of coding, not for me unfortunately.

Edit: state.status == "Idle" .

Thank you, didn't expect it to be TBH. Otherwise it would have been used in power recovery

@dc42 said in Servo question:

@Ntrack said in Servo question:

@smece said in Servo question:

@Ntrack you are talking about R

Yes, a micro servo. I have some 10V 220uF capacitors. Do I need bigger capacitance or voltage rating ?

How micro? My suggestion of 220uF was for a MG996R, which isn't exactly micro.

Hey,

would I need that capacitor for a MG996 on a Duet 3? Better safe than sorry?
Thanks.

M25 during tool change works now, thank you.

Hmmm... I actually thought it remembered this itself. Because this has caused me some problems on a toolchanging printer where I've yanked power to stop it from harming itself, and I thought I'd seen it assume it had the tool after I powered back up.

But... I could be wrong!! It could be the problem is it is NOT persisting this.

Let me do a couple of tests later today.

@dc42 said in M574 usage on RRF 3:

Thanks for reporting this. S0 is handled correctly for endstops on Duet 3 expansion boards, but S0 is currently treated the same as S1 for endstop switches connected to a main board. I will fix this in the next release.

There is a new build at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0 which should fix this. It also fixes file upload issues when running in standalone mode.

Yeah, I might have the answer there. According to that A axis endstop should work if connected to E3.
A axis is controlled by E3 endstop.Problem solved.

More drugs less thinking 😛
(No kids, dont do drugs!)

But if you describe what you want to achieve instead of how you (think you) want to achieve it, you'll get to the finish line faster.