Posts made by Excelon

@phaedrux said in X and Y surging / hesitant / pulsing while returning from homing:

I have a very slow Z axis with a heavy bed and I use a jerk and acceleration value of 60 for each. Seems to work out ok.

I like to use a lower jerk value for when the print requires supports since it's hardest to print supports. It's mostly just the first layer and sometimes the start of the second.

NOTE: I raised the Z jerk and it's not doing it now. Thanks guys. Sorry, I had to find out the hardway. I am hard headed!

@phaedrux

@excelon said in X and Y surging / hesitant / pulsing while returning from homing:

@dc42 and @Phaedrux

So, I wanted to change out the Duet 2 wifi board to see if I had a faulty board so I removed the one from the Ender 3 that hasn't been turned on in months.

Verdict? The steppers DID NOT jerk or hesitate while returning from homing, but as soon as I started a print it DID. Long story short ( I'll cut out how exactly I found this ) the steppers only jerk/hesitate when the mesh map is loaded and active.

WHY?

Ok.... for 'Z'... I don't think I changed the Z axis. Only X and Y since though were the only ones giving me issues. Let me try this! Thank you

@dc42 and @Phaedrux

So, I wanted to change out the Duet 2 wifi board to see if I had a faulty board so I removed the one from the Ender 3 that hasn't been turned on in months.

Verdict? The steppers DID NOT jerk or hesitate while returning from homing, but as soon as I started a print it DID. Long story short ( I'll cut out how exactly I found this ) the steppers only jerk/hesitate when the mesh map is loaded and active.

WHY?

@phaedrux

All the stepper motors are from E3D. Here is the link to the steppers.

https://e3d-online.com/motors-compact-but-powerful-motor

I do have to say that the pulsing and hesitation is getting worse. Now, instead of the steppers pausing once or twice while returning from home its doing it about every 15mm, or so... Could I have a bad board?

No, I believe those steppers are rated for 1.68amps (1680)and I have it set to 0.8 ( 800 ). Could that cause it?

I lowered the amps on everything because the steppers are too loud when @ rated amps

@phaedrux said in X and Y surging / hesitant / pulsing while returning from homing:

I can't really tell that it's hesitating.

Can you turn up the volume and hear the steppers? I did watch it also and thought the same thing. It's minor but its still not supposed to do that, right?

Here are two videos of the hesitation. Thanks again!

https://1drv.ms/f/s!AlKKGWMmM2j4xWSi3ZFVDpF6B_du

@phaedrux said in X and Y surging / hesitant / pulsing while returning from homing:

It might help to see a video of it in action.

Does the motion feel smooth if you disconnect the motor wires and move the carriage by hand?

I suspect binding or maybe a loose grub screw on a pulley.

That's what I thought also. I removed the whole bed and cleaned everything and re adj the tension.... same. I will upload a video tomorrow when I get home from work.

I tried values for 1000 for both instant and jerk speed and it does the same thing only faster. Any other idea's?

@deckingman said in X and Y surging / hesitant / pulsing while returning from homing:

@excelon IMO your instantaneous speed change (jerk) of 10mm/min is crazy low and accelerations of 90mm/sec^2 aren't much better unless your gantry weighs 20Kgs or so . Try setting both to something like 1,000.

@dpeckingman deckthank you as well for your input. Although, I didn't try 1000 for either i did try to increase both of those values because I had downloaded and printed a modified hotend with dual fans that were kind of loose and for that reason I had to lower the " jerk" value and then have come like the smoothness of the lower values. With that being said I did experience the hesitation from TOO LOW of the " jerk" value, but this is not the case, but I am willing to trying the 1000 value for both to see if it helps it for sure. I'm not opposed to trying anything if its recommended.

Thanks again!
Eric

@dc42 said in X and Y surging / hesitant / pulsing while returning from homing:

I don't see anything wrong with your config.g files, except for your rather unusual combination of two M208 commands. You set all the minima in the first one, then override the X and Y minima (but not the Z minimum) in the second one.

One possibility is that the VIN power is dropping below 9.5V when you move the motors. What PSU are you using? Try running M122 after the problem occurs and look for "under voltage events" in the report.

Thank you for the reply @dc42

I am running a Meanwell 24v 500watt PS. Pretty sure it's the RSP 24 500 but I can confirm if your truly think that's an issues. I will adj the dual M208 commands and also check the status of the M122 command after I "homeall".

This is my 2nd Duet build. This first one was more of a plug and play deal where this was more of a ground up, sort of... I am using a Creailty CR10S Pro from but changed all the steppers besides the dual Z's, changed the belts to Gates, installed the AC powered 1100 watt heated bed from E3D and using a direct drive setup via Bondtech>E3D V6.

For the most part everything is working fine, but when returning from homeall all the steppers hesitate and its almost like they're surging. So, I hit homeall and it goes to all the endstops and then the IR sensor travels to the center of the bed; Z lowers to home all without issue, but like I said... while returning from the center of the bed X and Y have a few moments where they almost come to a complete stop ( but never do ) and then continue only to do it again and again. I'm sure Z would be doing the same thing if it had to travel more than the 5mm that it does. I have tried a few things like adjust speeds and power current but nothing seems to improve this issue.

Any info, tips and/or tricks would be greatly appretiated. Thanking you in advance

I have included my config.g and homeall.g files

1_1551019819456_homeall.g 0_1551019819456_config.g

@dc42 said in IR sensor probe caused "diag LED" to come on:

@excelon said in IR sensor probe caused "diag LED" to come on:

Thank you for the reply, Dave. Is it correct to say that if there WAS a problem that the DIAG light would be lit and also some sort of DIAG error message within webserver?

No, the DIAG light isn't automatically lit. It's more of a debugging aid than a diagnostic light.

So, it is, or isnt normal for the DIAG light to remain lit 24/7 with the IR sensor coded in config.g?

You mentioned that some programming of M558 will trigger it which makes sense but I'm trying to make sure and understand that the board, even with the DIAG light lit is ok and functional 100%. Can you please explain how I would un-comment or program the duet 2 wifi in such a way where I could test the normal functionality of said DIAG light?

Thank you for the reply, Dave. Is it correct to say that if there WAS a problem that the DIAG light would be lit and also some sort of DIAG error message within webserver?

I am doing my final installation and just wired up the IR sensor and plugged it in. The red LED light on the IR sensor is on ( I don't think its working properly ) but was concerns me is the red diag LED light is on on the front of the Duet 2 wifi board just to the left of the SD card. Since, it came on I cannot get it to go off, nor can I get the IR sensor to work properly. I have the wires connected as follows.

GND / GND
VCC / +3.3V
out / Z Probe In

@dc42

@dc42 said in Not connecting with Blue and red lights displayed:

Looks like the green LED labelled "3.3V" is not lit. Can you confirm that? If so, turn the power off, disconnect the endstops from the Duet and try again.

@dc42 I disconnected the endstops and sure enough all the boards lights were on and I quickly ran command M587 S and P and then M552 S1.... working! Thank you @dc42

Now, the question is how do I connect the endstops correctly?

EDIT: I am working with a 2 pin endstop on the Y axis and had it plugged into the first 2 pins. Will I be able to use a 2 wire endstop?

@dc42 said in Not connecting with Blue and red lights displayed:

Looks like the green LED labelled "3.3V" is not lit. Can you confirm that? If so, turn the power off, disconnect the endstops from the Duet and try again.

Correct, no green light. I will try that tonight when I get home. Thank you

Blue and red are the colors posted

I will post a photo in 30 minutes or so when I get home. I thought they were blue and red but when you mentioned the blue light by the wifi module I second guessed myself.

Maybe in mistaken. Maybe it is green and red and not blue. The lights are not part of the wifi module but the LED lights to the right of it. Maybe the lights have no significance to my problem but I am unable to get connect via VAT, network or paneldue