@dc42 yes already printing parts RIP delta but now i cant wait to saw it in half^^

would it not be easier to do it in the slicer?

@Hergonoway said in Smart Effector including toolboard-capabilities?: I'm currently dealing with the same issue regarding the filament path right after the BMG gears in my version (the path before the BMG gears is not as critical, I'll keep it as it is). I think that maybe using a PTFE tube correctly cut to follow the curve of the gear is not a bad idea too. I'll try this approach and gonna design a cutting jig to perfect cut the required PTFE part. The problem with using a piece of PTFE extending up into the gear area is that on retraction, the PTFE might move up (toward the gears) slightly - and then get pulled up into the gearing. Designing the filament guide piece to have the bump area to guide filament was easier than I thought it would be in Fusion360. Start with the sketch facing the filament guide head-on, on a place centered on the filament path. Then draw a circle matching the smallest existing "hole" for the BMG gear. Then mirror that circle using the filament path as the mirror line. That leaves you the perfect area to extrude in both directions. Then fillet the new extrusions and re-do the filament hole path. In the snippet below (of my actual sketch in 360), "A" is a 3 point circle based on 3 points projected from the inner-most gap for the BMG gear. "B" is a vertical line which is the filament path. "C" is a mirror of "A", using "B" as the mirror line. "D" is the area extruded to make the bump for the filament path. (Cleaning up the extrusions from D to meld properly with the rest of the body is annoying, but probably only because I don't know what I'm doing with Fusion360.) After that "bump" is made, I just used a 0.7mm fillet on the ridge, and then re-cut the filament path holes.

here is another idea. print these https://www.thingiverse.com/thing:2519593 they will also provide good noise dampening. now you have space underneath the delta where you can mount the duet without interfering with the motors.

@bassco Great! Glad it's working well for you. Ian

@taconite said in bed mesh compensation unclarity: Question: Why is it not possible to load a previously saved height map, without establishing the Z=0 datum? Because of the homing of the axis the position of Z=0 should be the same (Ignoring possible jitter in the homing switches). on a delta this should still work. if you just ignore the message you should be able to print just fine.

Hi ! I know you've solved the problem you initially asked about. I'm wondering it you could give my some info on how tricky putting a Duet board on a WASP delta was? I have a WASP 60100 (build 2017) and would love to upgrade it with a Duetboard and maybe a E3D Volcano hotend. But, I'm not really sure what I'm getting myself into Would you mind me asking a couple of newbie questions about your process?

As @carlosspr says. For stall detection to work, the feed rate in your G1 S1 commands must be at least (60 * m915-h-value / full-steps-per-mm) . If your printer has 80 steps/mm @ x16 microstepping, that's 5 full steps/mm. You are using H200 in M915, so the minimum G1 S1 feed rate would be (200 * 60)/5 = 2400.

@dc42 I checked the belts and they all seem tight. My joints are these plastic ball cup arms and seem to have no binding to them when moved. I think it might be my carriages or the motors. I emailed seemecnc to see if they had any suggestions. I’m at my wits end with this. I have tried to run the mesh with the hotend off and on. Tried adjusting the delta radius and arm length but I keep seeing these ridges caused by backlash somewhere. I just can’t quite figure out where

Sure, if using the wrong rod length gives you a flat bed height map and good linearity, go with it. It's probably helping to compensate for a geometrical error elsewhere in your printer.

Hi @Gary, I forgot to upload my solution to this thread, because luckily I've been able to solve it. It turned out to be simpler then I first assumed. Basically, the error occurred due to another error in the measurements in calibration. This was then stored in the override.g file. I was suspecting that there might have been an error there, but each time I tried deleting it, it was already stored in the machines RAM. Here is a step by step guide, explaining how I fixed it: Temporarily delete/comment out the M500 command in the bed.g file. (It causes the machine to store the new values after calibration) Delete the config-override.g file and do an emergency stop of the machine. Restart it, (hopefully there shouldn;t be a config-override.g file) and add the M500 command back in, then perform a delta calibration. This should have: removed your previously stored values in config-override.g for good --> allowing for new values to replace them, so the printer will home properly. Also, you don't need the G92 command, it was only a temporary fix

@phaedrux Lack of layer shifts aside, I would say that the print quality is as good if not slightly better than it was before. I have only run a couple of small calibration prints so far but I do intend on printing a Sir Layers-A-Lot with a filament sample tonight or tomorrow.

@adrian52 good to know!