CNC Shark Forum

Ed, Attached is the .crv file in question. I did remove parts that were not cut with the .tap file I uploaded yesterday, so it's now a simple file with two drilled holes. The .tap file generated should be identical with the original, which means it should also take off like a bat out of hell, smashi...

Odd that my problem couldn't be reproduced. I am attaching the file that is repeatably causing the gantry to runaway using V2.1 Build 15 (latest 15) with Preferences set to "Image Cutting Area". Maybe my file is corrupted, although I did re-create the file after the first runaway with the same resul...

Ed, Please run your test one more time only this time in Preferences set "Image Cutting Area" instead of "Material Edge". That's when the runaway occurs. Note, keep your other hand on the Emergency Stop button when clicking Run, this is not for the faint of heart! Craig, I also have the bug you desc...

Joseph, Look at the attached picture from the release of today (you still call it Build 14 even though you made changes) . It confirms what I said in the previous post. You still don't have mm and inches sorted out. The picture shows the saved Virtual collection points and they are all in mm not inc...

Joseph, The first time I used V2.1 Build 14 this morning, with the first file I loaded the router took off like a bat out of hell and crashed into a clamp breaking my 0.062 bit before I could hit the Emergency button. Will this latest patch fix that? Is that what you meant by "Virtual borders are no...

I put a thick washer under one end of the wood just to make it more interesting. The difference from end to end was about 0.070 inch. Unfortunately, I don't have a depth gauge so I had to use my caliper type micrometer which isn't as accurate, but the depth readings I got for a GCode specified depth...

I think I've found out what's happening and why Virtual is not giving the correct offsets. It's not that the software is offsetting the virtual correction in the wrong direction as I previously thought. I looked closer at the actual virtual offset required at Line 133 and it's closer to 0.003 when I...

Hi Ed, Sorry, I meant V2.1 Build 10. Take a look at the new attached photo. It's the same as the previous photo, except this one shows the Virtual GCode alongside the input GCode. If you look at Line 133, you can see that the input GCode z is -0.125 and the Virtual GCode z is -0.129. Based on the co...

I didn't change the Virtual Offset from the default of 0.
Regards,
Kevin

Joe, I've tried out V2.1 Rel 10 and everything looks good, but I do have a question. Please look at the attached photo. It's a screen shot of the run I used to test out the new revision. I'm running the GCode with Virtual on. Note the Virtual screen on the right. See the coordinates for the center, ...