@deckingman Yes, you are right. Totally forgot about the video.
Here's the old video: https://www.youtube.com/watch?v=oXsFLG7AMug&feature=youtu.be
The extruders are commanded so erratically, that they end up moving backwards. While digging through the firmware I've observed that this can be tipped one or the other way (overextrusion or underextrusion) depending on how factors are mathematically rounded in PA computations, but I couldn't find which one and by how much as the results were not perfect in all cases. Thus I think me or the implementation is missing something other than just rounding.
I've done major upgrades to the printer but the basic setup is still the same. I just ran the same test script and the same thing still happens.
@veti You're absolutely correct! No wonder that my homed height seemed higher than it should have been.
Thanks a lot! Case closed - I've configured steps per mm for 20-tooth pulleys while running 16-tooth ones.
@paulhew said in Warning Light for Bed temp:
I could move one of my fans, like the case fan.
I was going to ask in the rrf3 forum, but can I take a decent ssd card, format it and drop rrf3 on it an keep my original card and swap if need be?
Thanks again David and all, it is appreciated.
Ask me a network question or something about model helicopters and I could help back!
The firmware doesn't reside on the SD card itself, rather, the bin file for the firmware is written onto the board itself, so to swap between firmwares you would need to reflash each time.
@fr4nc3sco Well, not all fans play nicely with PWM and it sounds like yours might be that type. You said that you had tried a frequency of 0.18Hz which is really too low. That's why I thought you might have been confusing the F and S parameters because 0.18 would be a valid number for S (although many slicers use the 0 to 255 range rather than the 0 to 1.0 range).
I have some very small part cooling fans that I've managed to get working by using a PWM frequency of 10 Hz. Try that, or a frequency close to it.
@phaedrux said in Duet Wifi - G29 causes extremely rapid Z movement and head crash:
Are you running a G30 before doing G29?
Bingo. That fixed it.
Thanks for the help. Got a new heightmap generated and printing away.
Titan with a 1.8 stepper should be in the 400-420 step range and double that if using a 0.9 degree stepper motor with the 16x microstepping. I have a bondtech BMG clone extruder on my ender 3 with a 0.9 degree pancake stepper motor...my esteps after calibration are 846.90. Also your acceleration is very high for your extruder which could also be causing issues. I have the max speed and acceleration for my extruder at 3000.
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E846.90 ; Set steps per mm (gregs wade was 604 steps)
M566 X500.00 Y500.00 Z30.00 E600.00 ; Set maximum instantaneous speed changes (mm/min)
M203 X10800.00 Y9000.00 Z300.00 E3000.00 ; Set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z500.00 E3000.00 ; Set accelerations (mm/s^2)
M906 X700.00 Y700.00 Z700.00 E960.00 I30 ; Set motor currents (mA) and motor idle factor in per cent
EDIT: I see you commented out those high speeds...I didn't see the semi-colons at first glance.
As already suggested, it very much depends on the machine. It could be anywhere from 0.1 to 1.0. After running some calibration from these forums, pay attention to your prints. Blobby corners -> increase PA. Rounded corners -> decrease PA. Make sure the Bowden tube sits as firmly as possible.
@chriskimbr said in Need help! please! Duet2wifi and bltouch ZOffset:
Question: on the duet2wifi if i change the config.g g31 zvalue and save it.
Do i need to reboot device to take effect?
Yes. It will prompt you to restart the board for it to take effect.
If you wanted to configure it on the fly, you could send the command in the console and it would take effect immediately without a restart.
@philipp-r said in Mesh Bed Compensation, doesn't change Z-Height during Print:
But don't you think it's a little suspicious that the values of the Bed probe heights are all zero?
No, those probe heights have NOTHING TO DO with mesh bed compensation. After you run auto calibration, they will be the height errors of the first 5 probed points.
And also when i start a print it, the nozzle height is clearly not constant above the Brinting bed. More than 0.1mm. So i expacted the Mesh bed compensation to compensate this offset.
If your probe is offset from the nozzle, then that's almost certainly caused by the effector tilt varying with XY position. See https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer.
@bearer said in Y baby step insted of Z baby step on display:
I followed the instructions and it sort of just-worked(tm)
Think I got creative&lazy with just downloading make and putting it in the same path as the cross compiler though, as I couldn't get it to work with the internal as suggested. (possibly v2.11 from here)
So it's working now?
You will find the objcopy step in the Build Steps tab.
@aidar Thanks, that solves the problem for me!
@phaedrux I set the dive height to 50 mm. It gives me a lot of failure tolerance. It is working fine for me. So far no problems and much safer than just the 5 mm default. The mentioned error while probing (which I now avoid with a higher dive height) was due to mechanical tolerances in my extruder / laser mount.
It is working fine for single probes using G30. Wasn't aware that this would affect the dive height of G29, too. Haven't tried G29 in a while now as I still don't know if it resets z=0 when called AFTER G30.
I got the problem that whenever G29 after G30 the printer prints with different z=0 heights. It is always a way too high and it is different every sequence! Trigger height of BLTouch probe is wonderful stable with < 0.01 mm tolerance, which is amazing! Also checked if I have missing steps and lowered max z speed to 1 mm/s. It's fine. Still looking for the error and still thinking about my question above: When G29 is not setting z=0 than this could cause the changing z=0 height. Need to investigate here.
BTW: When having dive height at 50 mm and then G30 down and get the probe triggered already after 1 mm it is not driving back 1 mm but driving back whole 50 mm. So it ends at 50 mm over the trigger point while started at 1 mm over the trigger point. Not sure if this is not a bug. When first setting the dive height to 180 mm (my build volume) I got the problem that it rises even over the endpoint switch. Since G29 seems to use that dive height also it is not a good idea to do so anyway (unless I have too much time).
I have a similar problem with one of my Ormerods and hadn't considered nozzle axis to bed normal alignment or more the the point variation.
Thanks! I will focus on my custom with a v-slot x-arm from now on and 'fix' the sloppy x-carriage another time.
Thx for the clarification. Like I said, I already got it working in S3D.
These are the settings I'm currently using:
M207 S4.5 R-0.05 F4800 T1800 Z0.20
But now it also works with Slic3r. Just used the newest beta version of Slic3r PE instead of the stable release.