Nomad: Serious gouging problem [FIXED]

CNC Machines Nomad
1

Edit: This may be the same problem as listed here
Edit x2: It is not the same problem as listed above, the zero holds, and is correct until I run it and it does… whatever it is doing.

Ok, So this is the second time this has happened in a row, different files completely. (Two different days as well, though that should change nothing) Ill run the file through meshcam v6. The first time using the carbide autopath, and the second time using the regular toolpath generator with data from gwizard.

I’ll run the meshcam into carbide create, zero to the corner, but when I run it the first thing the nomad does is goes to the correct X Y, but then gouges into the piece as far as it can press in, and then tries to move in the XY. The first time it gouged through a 1/4" piece, then most of the way through the wasteboard. I think it was stopped only because it was a 1/16" bit and it made it to where the bit size increased to 1/8." Fortunately the bit broke, so only the piece was ruined.

I should be on the newest version of both meshcam, and carbide create.

1.png1600×829 294 KB

This isn’t the first piece I’ve done, and I’ve never had this problem before the last two times. Any ideas?
[/quote]

Ok, So this is the second time this has happened in a row, different files completely. (Two different days as well, though that should change nothing) Ill run the file through meshcam v6. The first time using the carbide autopath, and the second time using the regular toolpath generator with data from gwizard.

I’ll run the meshcam into carbide create, zero to the corner, but when I run it the first thing the nomad does is goes to the correct X Y, but then gouges into the piece as far as it can press in, and then tries to move in the XY. The first time it gouged through a 1/4" piece, then most of the way through the wasteboard. I think it was stopped only because it was a 1/16" bit and it made it to where the bit size increased to 1/8." Fortunately the bit broke, so only the piece was ruined.

I should be on the newest version of both meshcam, and carbide create.

1.png1600×829 294 KB

This isn’t the first piece I’ve done, and I’ve never had this problem before the last two times. Any ideas?

2

Your roughing plunge is at “ludicrous speed”. Generally a plunge will be half or less than your feed rate for roughing. I would try 40 IPM.

Can you please post the STL? I suspect your CAD zero and CAM zero (MeshCAM) aren’t where you expect them. I can’t see what MeshCAM was “thinking” from your pictures.

mark

3

scorerdoblesidetop.stl (174.3 KB)

Noted on the speed as well.

4

That was fast! Give me a few minutes to look at it.

mark

5

Your roughing step over is too small. I would use 0.625. No need to go that fine if you going to do a finish pass.

@Rand and I like 47/43 for the angles - leave some overlap. Not effective here since you’re not using a ball end mill.

The finish speed and plunge is a bit fast - based on your roughing speed. You step over is a OK - a bit small or a square end end mill but good for a ball end.

Pencil is OK. Me I would go a bit slower - 60/30 - but that up to you.

What is the stock?

mark

6

@imp and I went over EVERYTHING. We even phoned and talked through setting the parameters and zeros. We ran simulations of the G Code and verified that things were as expected.

We managed to get the cutting going - correctly - but within a few seconds the “plunge from hell” occurred. Using the G Code we proved to ourselves that there was no plunge anywhere near where things failed.

@imp observed that the initial plunge - after we double checked everything and regenerated the G Code (there may have been a Z0 issue) - was what was expected. As the profile proceeded, the depth grows noticeably deeper… until things jammed. The stock is taped to the spoiler so it is quite flat.

Sadly, this suggests @imp is doing everything correctly and the Nomad itself is misbehaving. This “feels” like a hardware problem (e.g. cross talk, PCB issue) but I can’t say for sure. @imp is going to talk to support@C3D and see what they think.

@imp: there is one more experiment to try: reduce the depth to 0.03 and try again.

mark

7

Looks like it was something wrong hardware side. Jorge sent me a new board, and everything works just fine now.