Forum Replies Created
-
AuthorPosts
-
JulianRendellMember
@cmcgrath5035 & @alden – thanks for the replies.
Apologies for not replying sooner; other projects got in the way. Plan to get back to this over the weekend.
I’m using CamBam to generate my G-Code, and OpenSCAM as my viewer.
Both of these previewed the files ok.
@cmcgrath5035 – interesting that other CAD/CAM packages are mis-interpreting the files as well. Wonder if CAMBAM is doing something that is either ambiguous or complex to correctly implement in the G-Code spec.(I don’t use CP very much… at time of purchase I wanted to set up my small CNC like my 3D printers, driven by a Raspberry Pi class machine, vetted TGFX and then ordered the machine. To have TGFX dropped by the time the hardware arrived, and CP is a PIA to use on lower powered machines- and not particularly ‘safe’; there can be terrible lag in the UI and it’s difficult to get it to reliably pause quickly.)
Let me know if there’s anything I can do to help track down this bug!
Cheers,
Julian
JulianRendellMemberI’m seeing the same problems- really good description HCamp!
Here’s a photo of the results (stopped as soon as I heard it cutting through the clamping wood):
https://www.dropbox.com/s/uniruk76xcqhowx/Messed%20up%20arcs.jpeg?dl=0
And the G-Code generated by CamBam that caused this:
https://www.dropbox.com/s/sc31kq7v5tzy3vv/slingshot-middle.Part1%20%5B3DSurface1%5D.nc?dl=0
To be clear- the circles carved are not supposed to be there!
I’m on the latest firmware, and checked $CT; it’s set to the recommended default.
I’m switching to use line segments and not arcs; fingers crossed that will work with ChilliPepper on a Raspberry Pi…
Really hoping TinyG gets these bugs ironed out soon- I love the potential, but it’s driving me nuts!
- This reply was modified 9 years, 7 months ago by JulianRendell.
- This reply was modified 9 years, 7 months ago by JulianRendell.
-
AuthorPosts