Welcome, Guest. Please login or register.
Did you miss your activation email?
November 12, 2018, 21:45:55 pm

Login with username, password and session length

Pages: [1] 2 3 ... 10
 on: Today at 19:13:19 
Started by onekk - Last post by EddyCurrent
Compiled plugin dll attached, tested on CamBam v0.9.8 and v1.0 in Windows 10 64bit

This is the "Boxes_Tres" version.

 on: Today at 16:49:11 
Started by onekk - Last post by onekk
I'm working on some improvement on the auto resize code, some polishing are needed, but in the next days i will publish another WIP version (maybe a pre-beta stage) no improvement in other places of the interface other than autoresizing the form to suit the font dimension you choose.


Carlo D.

 on: Today at 14:51:37 
Started by onekk - Last post by EddyCurrent
It's very strange that Eddy has not said anything yet.

   A r m a n d o

Eddy was busy.

This is how to avoid trouble;

With .NET Framework 3.5 as the Target Framework (as Carlo chose) you have to Reference CamBam 0.9.8 files.

If you want to Reference CamBam v1.0 files then you must change the Target Framework to 4.5

 on: Today at 13:53:02 
Started by onekk - Last post by BR52
Hi Carlo

In the Boxes_Tres version you complicated in the Analysis of the construction of the designer.
I compiled this version is in trouble.
It's very strange that Eddy has not said anything yet.

   A r m a n d o

 on: November 10, 2018, 18:10:36 pm 
Started by tshawkins - Last post by onekk
@GaryLucas  you are right, but if you are putting the 0 at the wrong place your working coordinate are reversed as the orginal author reported, saying that CamBam uses the wrong coordinates, resoect to GRBL.

As I'm a GRBL user and a CamBam user, I have pointed out that "wrong" is not the exact term, as Cambam uses the right coordinates, (0 to X+ moving to the right) and (0 to Y+) moving far from you, as in the cartesian Axis (like in the CamBam drawing Canvas).

The problem maybe is not setting G54 and not zeroing it at the correct place at the starting of the work, and maybe a wrong origin (and x direction settings).

Im new to CamBam, and CNC in general, but im struggling with coordinate systems

I have a small GRBL based CNC system with limit and homing switches fitted, and the ability to run the $H homing cycle

if i'm sitting looking at my machine from the front, looking down on the bed, the machine by default homes to the closest left hand corner of the bed, and because of backoff it considers that to be position (-4,-4). The default coordinate system that GRBL uses has negative numbers going left to right, and negative going closest to furthest, ie if i move my x position to the right hand side of the bed it will be at (-130,-4). This is apparently the default GRBL behavior and is expected, so the furthest away right hand corner is (-130,-100) based on the size of my bed.

Now CAMBAM seems to have an inverted coordinate scheme, in that the only way i can get negative coordinates is to move my work piece into the bottom left most quadrant of the drawing screen, where it is upside down and back to front.

Am i missing something obvious here, how can i align the coordinate system in CAMBAM with the physical CNC machine so i dont keep on having to do metal jiggery pokery to correct the coordinates.

I'm obviously missing something.

From these words I suspect that @tshawkins has some settings in his machine that are "incorrect" respect to  the "right" behaviour when machining a piece.

As I remeber when I've setup my GRBL machine, I've found some "instructions" using the "3D printer" convention of Z 0 at the bottom (working plane) and they placed the "Z min" limit switch at the bottom.

As I'm a owner of a 3d printer and  similar discussion are daily discussed on "3d printing forum" asking if a modified 3d printer firmware could be used to drive a CNC (dremel type ones, ad the CNC derived from 3d printers are not very stiff), and almost daily I'm struggling with those that didn't know these differences, and obstinately tell that a 3D firmware that didn't have the distintion between "working coordinates" and "machine coordinates" (some firmwares lack even a difference between G0 and G1) are perfectly usable for "CNC machining".

If I guessed wrong, I will apologize, but speaking of "wrong" behaviour about a widely used program like CamBam is somewhat "strange" if you are accustomed with a CNC.


Carlo D.


 on: November 10, 2018, 13:23:20 pm 
Started by coolant slinger - Last post by dave benson
Well I hope people can get some use out of it, personally I've not much use for it either.

I'm glad your got more work coming in, it sure bests "Not Enough" , but that presents it's own challenges.

Streamlining your work flow has probably taken on more importance now, although on a very small scale I'm been looking at ways to to be more efficient at making the turrets, and one job making the indexer wheel (think small bicycle sprocket) where i was spiral milling the
scallops with a 3mm end mill, this was taking forever to do. If I went too fast I was getting some draft to the cut, from top to bottom.
So I re evaluated the task and tried drilling the tooth centers out and finishing on the lathe.
Not only did this get the job done much faster, I hit my tolerances better and the finish of the tooth profile was better too.


 on: November 10, 2018, 12:09:26 pm 
Started by coolant slinger - Last post by lloydsp
Dave, thanks!  I don't have one now that actually requires incremental code, but I know some day I'll bump up against a controller that does.

Good job!

This is going to be a busy year!  We just got a year-round contract for more material each week than I was normally delivering during peak 'seasonal' times -- and the seasonal work hasn't gone away, either!


 on: November 10, 2018, 07:09:27 am 
Started by coolant slinger - Last post by dave benson
Here is the .nc File

 on: November 10, 2018, 07:03:59 am 
Started by coolant slinger - Last post by dave benson
Typically absolute=G90, incremental=G91. NOTE! Incremental distance mode is not currently supported.
It is now!
I also looked around for a converter, and also looked at many of the code repositories, but Huh no luck It seemed that if you wanted one, you were going to have to buy for it or do what squibload did.

That didn't seem satisfactory, so I've made a post processor for cb to do that.
Pop the PP and the .exe in the Post folder. and the style lib in the styles folder.
play around with the cb file.
Remember you have to change the clearance height in the PP it's metric and set to 3 mm, but in imperial files that would be 3 inches, you can also remove the clearance = 3 altogether and the default is 1 so for you that would be 1 inch.
the code sets and unsets the G91 G90 pair also.
I've ran out of attachments here so I'll post the Gcode file for the cb file so that you and look at it.
edit just realized I didn't add the zip!

 on: November 09, 2018, 18:14:22 pm 
Started by tshawkins - Last post by Garyhlucas
I never home my machine to any position of the spindle to the bed because it only matters if you are using soft limits to keep from crashing against the end stops.

The commonly used origin for milling is the upper left corner only because milling vises have a movable front jaw and working against a stop on the fixed back jaw allows you repeat the part.  For round parts you would likely want to work from center. On a router machine with vacuum or clamps it makes absolutely no difference. So position your spindle over the part at the same place you chose to put it in CamBam and zero the X and Y readouts and you are good to go.

Same deal with Z axis. Many people use top of part as zero. If the stock varies in height you may want to program from the table so you can cut the material to a specified thickness by simply machining at the appropriate Z height.  Again neither CamBam nor a CNC care which way you do it.

Pages: [1] 2 3 ... 10
Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines

Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM
Page created in 0.091 seconds with 16 queries.

Copyright © 2018 HexRay Ltd. | Sitemap