CamBam
News:
 
*
Welcome, Guest. Please login or register.
Did you miss your activation email?
January 21, 2020, 11:44:56 am


Login with username, password and session length


  Show Posts
Pages: [1] 2 3 ... 6
1  Support / CamBam help (General usage) / Re: Associating dwg, dxg, stl, or whatever file name with cb file automatically on: December 18, 2019, 20:17:47 pm
It is a plugin and works well for importing small dxf files, and you are correct in not allowing it to change the file name. I just got used to using it for opening new drawings and forgot that using "open" imports the dxf file name automatically.
With that said, your plugin works as advertised and should not be changed, it was more of a brain freeze on my part.
2  Support / CamBam help (General usage) / Re: Associating dwg, dxg, stl, or whatever file name with cb file automatically on: December 18, 2019, 18:21:22 pm
You are correct. File-open must be used instead of import dxf to get the desired result. Thanks for the reply
3  Support / CamBam help (General usage) / Associating dwg, dxg, stl, or whatever file name with cb file automatically on: December 18, 2019, 16:54:47 pm
Hello everyone,
   As the subject line says, is there a way to set up CB so when you choose "save as" in the menu the actual file name of the original dxf file automatically shows up instead of "untitled". It just a minor annoyance of having to type in the file name each time you initially save the file, especially when the part number is long.
                                                                                                                          Thanks, Jim
4  Resources / Scripts and Plugins / Re: Import DXF, STL, STP plugin on: February 01, 2019, 14:48:32 pm
I have been running this plug-in through its paces with DXF files as well and it works great. Excellent job!

I find that integrating it into the file menu like other software makes way more sense.
5  Made by CamBam / Members Machines / Re: I have a friend who's interested in HAAS mills, but I've never used one on: January 06, 2019, 20:53:18 pm
We had 6 HAAS mills where I used to work. I ran a VF-3, VF-4, VF-6, and then the newest VF-5 with a probe system, which was by far the best one being newer. The other's I ran were from 5-12 years old and were still holding tolerance. I think the VF-4 and VF-3 had a spindle problem that was covered under warranty on one of them. The other was out of warranty by about 7 years. But these were production machines that cut 13 chrome, 4140, 4340, stainless steel, the occasional inconel and monel, and aluminum, so take that into account.


Service was great...if you are in their service area. They carry most of the common parts that break on their truck.


The HAAS control was basically a Fanuc with a few extra bells and whistles.


Overall I liked them.


We also had a small tool room mill. It was ok, but you could not take big cuts.
















6  Resources / Post Processors (*.cbpp) / Re: Fanuc post on: November 14, 2018, 20:57:54 pm
Just some tweaking of the post.

In the old post, the tag(comment), final depth of cut, cut increment, and stock surface would only be displayed after the initial tool change.  If you had 2 mop's next to each other with the same tool, then the following mop's with the same tool would not display the information (depth of cut, increment, stock surface, tag).

Now all that information is displayed for each mop regardless if the mop's are using the same tool number or not.

Some may find this to be too much information, cluttering the code, but here it is if you like this way better.

Everything else in the post stays the same as the previous one I uploaded.

Edit: added clearance move, then first x,y move to each mop. Sometimes when inserting NC code between 2 mop's with the same tool number, the tool would feed to the first x,y position at home position instead of a rapid move to first x,y then to z position. This was a rare bug and I only noticed it when adding outside NC code, in my case it was code telling the machine to go home and stop so I could check tooling, etc. I also renamed the post.
7  Support / CamBam help (General usage) / Re: Hoe to draw a circle tangent with other object? on: November 04, 2018, 11:44:44 am
If what you want is like the first .jpg you uploaded, then just use the move command with the snappy plug-in.

Another option is to use a second CAD program to do your main drawing, and use CB's built in cad for just making edits and tweaks to your original drawing if needed.

I love the built in CAD in CB, and I have gotten pretty good with it, but it can be a little clunky at times and slower when drawing complex shapes.

DraftSight is what I use for all my initial drawings. Its free, or you can upgrade to the Pro version like I did.
8  Resources / Post Processors (*.cbpp) / Re: Fanuc post on: September 26, 2018, 00:40:48 am
This post is just a minor update to the last one I uploaded.

Now, the part name is posted with each MOP. This is helpful when you have multiple operations/set ups that are segregated by  creating a new part for each operation and labeling as you see fit.

9  FeedBack / Bug Reports / Re: I Feel Stupid on: September 25, 2018, 01:10:54 am
Works on Windows 10 CB ver.1.0 over here. I just substituted your style with a 1/8 ball end mill.
10  Support / CamBam help (General usage) / Re: Pinning the start point to an imported NC file on: September 24, 2018, 00:12:02 am
Yes, I agree with you on CB being easy to learn.

The reason I purchased CB and several other low cost software packages is because I was tired and bored of hand coding everything.

My boss did not seem to mind, I was not after his job.

I do not own a company, CB was purchased to make my job easier.  I just think of CB as another tool in my box.

Using CB or any other Cad/Cam package and being proficient with it makes your job easier and fun.

Now if cutter comp was implemented in the plug-in.........

Have a good rest of the weekend

                                                 Jim

11  Support / CamBam help (General usage) / Re: Pinning the start point to an imported NC file on: September 23, 2018, 19:57:50 pm
Gary, you just gave me an idea with the subroutine being used, and here is what I did....


I called up a drill mop as you suggested, selected custom script and left that field blank.

Then I entered the tread mill style I wanted to use which has all parameters set up already, but really does not matter since I am importing the code anyway, I just like that info being displayed at the beginning of the mop.

Then I imported the code and selected the thread mill style again so it shows up in the mop as I wanted.

Posted code, and it works. You just have to set your nc file up in incremental only and the only thing you have to edit is the Z depth, which will be absolute.

Now I can create many generic thread mill nc files in incremental with the other program (which implements cutter comp) and use them on any part any location with the only manual edit being the Z depth. I hard coded Z0 in the nc code (subroutine) to eliminate any chance of a crash.

Sometimes it only takes a little nudge from someone to get the thought process going. Many thanks again,

Here is an example job file and the nc (subroutine) code.

Just remember to make sure the path for the nc import is the same as where you downloaded it.

Note: I had to add a space in the blank custom script field for it to not give me an error for some reason. Once saved you do not have to do it again.
12  Support / CamBam help (General usage) / Re: Pinning the start point to an imported NC file on: September 23, 2018, 00:10:16 am
That's what I figured Dave. I was just trying to streamline the process and thought there was some trick to doing it that was overlooked. I will just import the nc file like I was doing before and manually add the x,y coordinates. I still prefer to use the plug-in, but when we machine inconel, heat treated 316, and monel, those thread mills will wear rather quickly, hence the need for cutter comp at the machine. Thanks again!
13  Support / CamBam help (General usage) / Pinning the start point to an imported NC file on: September 22, 2018, 16:05:36 pm
Hello to every one.

I thread mill on a regular basis and I use CB's thread mill plug-in for that purpose and it works great except for the lack of built in cutter compensation.

Recently I have been generating all my common thread milling code with another program (https://sct-usa.com/thread-mill-code-generator/) and importing them into CB for use as an operation. This program uses cutter compensation, which I think is a necessity when thread milling a large number of holes in stubborn material.

So, basically I generated the code  in incremental (G91) so it can be universally used on any part, then label an save it in a thread mill folder for repeated use.  The only thing that will change is the Z depth, which is in absolute (G90).

This works for me except I cannot figure out how to tag a start point to the imported NC code. CB always starts it at X0Y0 when I clearly set the start point at the center of the hole I want the thread mill.

Now I have to manually edit the final post with the proper X and Y coordinates.

I realize that sometimes you have to do a little hand coding, but I would think the edit start point function should work with the imported NC code.

My question is why does CB not acknowledge the start point that is set in the NC mop?

14  Resources / Scripts and Plugins / Re: Slotter - a new MOP type on: September 02, 2018, 13:17:30 pm
Geoff,
 
  That was a fast response and much appreciated. Everything is working just fine now. Thanks for your hard work. All of you that put the time and effort into these plug-ins are what make CB standout from other cam software.

                       Thanks again, Jim

                                           
15  Resources / Scripts and Plugins / Re: Slotter - a new MOP type on: September 01, 2018, 22:05:23 pm
I figured it was not intentional, and just a bug.

We will let him rest up now

Thanks for the reply-Jim
Pages: [1] 2 3 ... 6
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.1 seconds with 19 queries.

Copyright © 2018 HexRay Ltd. | Sitemap