So i need to manually babystep to 0.1mm each print. How do i save the value? There is no save button 
️
After using klipper and mainsail i just cant stand the lack of features in rrf. I love the quick interface and the hardware. But not even being able to save something like babystepping from the UI is lacking if you ask me.
What are wrong in my configs for individual home x and y? I have not used this printer in like over 1.5 years. I had it apart and just reassembled it. Homeall works just fine but i wanted to home idividual axis.
@dc42 said in Duet 3 mini+ red/green led keeps flashing card unresponsive:
@alucardi I'm glad you sorted it out.
If you get flashing LEDs again, please tell us which LEDs are flashing. There are two red and two or three green ones. I guess in this case it was the red +5V and green +3.3V ones that were flashing, not the red Status LED which flashes during normal operation.
One of our support staff is currently not working, so response to forum questions is slower than usual.
Eventually i found this link https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond After using that one i figured out that it must be the power supply. It was a bit hard to find, had to use google.
not much help here but i figured out it was the powersuply.
I came down and saw that my bl touch was flashing and printer just stopped mid print. Now i cannot get it to connect to wifi. Red and green keep blinking but stops for a few seconds and the red led by it self blink a few times then they are back to flashing. What could have happend? Running it on USB red and green are solid and i can connect through wifi.
@tomkamin I cant find a calibration rutin for stealthchop in your homeall. You are also doing 2 passes which are only needed for switches. Here are my homeall.g that works for me with my mini 5+. I know it is messy, i need to clean this up but it works atleast.
M400 ; finishes all current moves and and thus clears the buffer
M913 X60 Y60 ; drop motor current to 33%
M569 P0.0 D3 V60 ; reduce V to ensure stealthChop is enabled
M569 P0.1 D3 V60 ; reduce V to ensure stealthChop is enabled
M915 P0 S0 R0 F0 H400 ; sensitivity X, don’t take action, don’t filter -4
M915 P1 S0 R0 F0 H400 ; sensitivity Y, don’t take action, don’t filter -4
M400 ; finishes all current moves and and thus clears the buffer
G91 ; relative positioning
G1 H1 Z10 F5000 ; lift Z relative to current position
G1 H1 X5
G4 P300
G1 H1 X20 F3000
G1 H1 X-400 F3000 ; move to X
G1 H1 Y-5
G4 P200
G1 H1 Y-20 F3000
G1 H1 Y400 F3000 ; move to Y
M913 X100 Y100 ; return current to 100%
G90 ; absolute positioning
G1 X167.5 Y167.5 F5000
G30 ; home Z by probing the bed
M402 ; retract probe
G1 Z5 F5000
M400 ; finishes all current moves and and thus clears the buffer
M569 P0.0 D2 ; restore default for motor
M569 P0.1 D2 ; restore default for motor
M913 X100 Y100 ; return current to 100%
M400 ; finishes all current moves and and thus clears the buffer
Have you dsone this?
"You need to run the stealthChop tuning procedure first. You can do this is the homing files.This is what I suggest:
Execute a tiny move (1 or 2 microsteps) away from the homing direction.
Pause for 100ms using G4.
Execute a small move away from the homing direction, e.g. 10mm.
Execute the homing move.
Don't forget to reduce current for the homing move (M913)."
@dc42 no could that help? I’ll give it a try right now. But that don’t explain the difference in measured sensitivity.
@Phaedrux i ordered another sensor that is not the duet sensor. This one seem to be to much trouble. It is all fancy but it keeps slipping or reporting false values when it should not.
@Phaedrux it have not. It does this at random and it a pain in the but. I have ordered another sensor that most likely will work 100%. I am disappointed of this super expensive sensor that will not work.
I cannot for my life get this sensor tuned. It keep reporting to little movement. I have sern min movement as low as 10%. Measured sensitivity can also jump from 26 to 36mm/rev.
The Bowden tube cannot move and the sensor is firmly in its place.
I had it active for like a month but never use it cause it just randomly stops my long prints.
Adding a picture on how it can look. Values are all around the place.
@dc42 Well i can't be more excited. I run klipper on one machine but love my duet cards and the magnetic filmaent sensor. I assume there will be use of some accelerometer. Is it same as klipper? would be nice to have it home when 3.4 beta comes.
@dc42 I will give it a try tonight and reslice something. The same gcode did work on 3.2.2 though. I did reslice using same settings but that did not help.
@dc42 just me getting excited. I know it is meant for 3.4 but seeing it made me want to try it out 
@Phaedrux not sbc but we control. Tried to downgrade webcontrol first but made no difference.
I seem to remember seeing a post where it accruals did make a difference when the guy changed to the different modes. Also according to the gcode wiki it should work.
I am unable to upload gcodes in 3.3 Beta2. I get Network error, it keep trying to reupload but after several tries i get a error.
Going back to 3.2.2 and it works fine.
Trying out input shaper, i use same Hz as with DAA which completely removes my ringing. Input shaper P1/2/3 have terrible ringing. Changing the damping factor make no difference.
You can clearly tell on the picture when DAA is active. No ringing.
