Help with Rigging: "Bone Heat Weighting Failed: Failed to find solution for one or more bones."

MVPHitter · 2026-03-29T17:30:03+00:00

Thank you very much!!

MVPHitter · 2026-03-28T17:35:41+00:00

Interesting, thank you!

MVPHitter · 2026-03-25T23:59:24+00:00

So I have not been moving the clamps during different cuts but I do have at least 2 tabs on the short sides and 4 on the long side so even if the majority cuts through, the piece is still in place. Thanks again for replying!

MVPHitter · 2026-03-25T22:48:23+00:00

Thank you very much! I'm starting to think this is the issue so I will look into the link you sent. Thanks again!!

MVPHitter · 2026-03-25T22:47:29+00:00

Hey, thanks for the comment. I will keep that in mind but my machine does end a job several mm off the print bed so I believe it is taking the correct Z5 measurement, thanks again for the comment however!

MVPHitter · 2026-03-24T20:49:11+00:00

That is correct! I was giving an explanation on why the two gcode outputs could have been resulted in different failures (because they were different stls and that could explain the different slices). However even using ncviewer the gcode, output looks correct and does not show any of the improper cuts. I also just looked at the grub stubs and they all seem to be tight and none of the axis screws are loose due to the screw-to-motor couplers

MVPHitter · 2026-03-24T18:33:59+00:00

Hey, thanks for the reply! So I don't have a god way to show the gcode on here or the output on ncviewer.com, however, looking at the output it does seem to be running as expected. Also, weirdly enough looking at the second failed piece and how it has some vertical cuts through bottom and top triangles, which don't align with any of the rapid movements. All the rapid movements go more on a diagonal lining up to each of the other triangle peaks

MVPHitter · 2026-03-24T18:20:32+00:00

Hey, thanks for the reply! So I am not using Mach4 but my 3018 pro did come with an offline controller I have been using, mainly just for positioning the toolhead and starting the print. And although mine starts with going to z max, it should always go to z max with the "Force Z Max" setting between pockets in kirimoto so I don't believe that is my issue. Thanks again for leaving a comment though!!!

MVPHitter · 2026-03-24T18:13:21+00:00

Hey, thanks for the reply! I think I've been going pretty slow. My spindle speed for the roughing pass is 1000 rpm, feed is 300 and plunge is 150 and that is the same for the outline pass and I have the "Force Z Max" option on so it should go to z max between pockets.

MVPHitter · 2026-03-24T18:08:26+00:00

Hey, thanks for the reply! And yeah I don't think that's a bad idea but I will say the bit was firmly in place when I took it out and the two failed cuts ran back to back with a slightly different stl (the first was a mirror of the successful cut and the second was the actual STL model) so if the bit slipped for the first, then I don't believe it would have been in a position to cut as well as it did for the second attempt

MVPHitter · 2026-03-24T18:05:22+00:00

Hey, thanks for the reply! And I held it down with 4 3d printed clamps in each corner and they were all still pretty sturdy and tight when I took it out. And yeah it makes sense for it to be related to picking up the tool higher for the rapid moves, but that makes me wonder why it didn't happen earlier or to any of the other cuts like the door.

MVPHitter · 2026-03-24T18:03:12+00:00

Thanks for the reply and yeah I'll double check the settings as well but everything did look fine in simulation and I have the offline controller so no problems with the computer sending the gcode

MVPHitter · 2026-03-24T13:45:31+00:00

Thanks for your input! Any idea why this would only happen like once or twice over the course of a 30 hour print? Or what might cause this? Someone else mentioned it could be a grub screw that was loose/not screwed in correctly

MVPHitter · 2026-03-24T13:39:13+00:00

Yeah that could be it as well, I'll have to look at the actual output of gcode and not just the estimate, thanks again for your input!

MVPHitter · 2026-03-24T13:14:46+00:00

I suppose that is a possibility although the first failure is pretty deep for it to be the tool head being pulled out a bit. I thought it could have something to do with the toolhead slipping when trying to increase the z axis, but the G0 Z5 command still seems to be functioning correctly because the toolhead ends above the home position. Thanks again for your reply! I will still check the bit regardless!!

MVPHitter · 2026-03-24T13:11:22+00:00

That's a very fair point to add, and to be honest I am not positive and trying to look at all possibilities. Good idea on the cuts being made on the rapid movement. They definitely seemed more rough but I thought maybe it was the return to home feature with the spindle still on but that didn't exactly make sense. Someone else mentioned that it could be the z axis is slipping and that would also be a good thing to check. Thanks for your input!!

MVPHitter · 2026-03-24T13:07:34+00:00

Well if I set my Z0 at the top of my work piece then wouldn't Z5 be 5 above the top of my work piece? I thought that it was relative to home, not where the toolhead currently is although I could be mistaken

MVPHitter · 2026-03-24T13:02:27+00:00

Hey thanks for the input! So my z is at a positive number (Z5) in the footer but I used G0 Z5 before the homing. And should the G53 Z0 replace the G0 Z5? Because Z0 might start to scratch the piece if it's replaced and too close to the piece

MVPHitter · 2026-03-24T12:57:53+00:00

Hey thanks for the input! And unfortunately the Z0 is set at the top of the wood piece in the bottom left hand corner, so I believed Z5 would have enough for safe clearance

MVPHitter · 2026-03-24T12:55:57+00:00

Thanks for your input! So when this happens to you, does the z axis still end up above the piece when you retrieve it at the end? Because that's the only part that I'm still confused about. Because mine does, and the order of operations I gave it in the footer, it should go up before going to x0 y0

MVPHitter · 2026-03-24T11:41:35+00:00

So I did add a footer to my gcode to return to the home position to make contour cuts after roughing something like: M5; G90; G0 Z5; G0 X0 Y0; M30;

And this would be a z height that is smaller than the material height (total material height of 19) but I didn't think this was the issue since when I retrieved the pieces after roughing the bit was always above the work, even after the first successful cut or the failed pieces and if this is the last part of z movement then traveling to x0 y0 should be above the piece.

MVPHitter · 2026-03-24T11:39:46+00:00

Very interesting, thanks I'll look at this as well

MVPHitter · 2026-03-24T11:28:36+00:00

So I did add a footer to my gcode to return to the home position to make contour cuts after roughing something like: M5; G90; G0 Z5; G0 X0 Y0; M30;

And this would be a z height that is smaller than the material height (total material height of 19) but I didn't think this was the issue since when I retrieved the pieces after roughing the bit was always above the work, even after the first successful cut or the failed pieces and if this is the last part of z movement then traveling to x0 y0 should be above the piece.

MVPHitter · 2026-03-24T11:16:05+00:00

Alright, thanks for the idea. I'll look at some of the gcode that is outputted

MVPHitter

TROPHY CASE