Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - grzgrz

Pages: [1] 2 3
Feature Requests / Re: List
« on: April 23, 2021, 20:57:43 pm »
I too am waiting for a sign of life from Andy, as I've been unable to improve on the current Polish CamBam translation without some changes to the menu item naming convention. Let's hope he finds time to address these issues.


As I've explained earlier, the mount (or should I say bracket?) would only serve the purpose of attaching a dial indicator to the spindle, for checking if the router bed and jigs are level or not. Maybe my wording is as bad as my typos  ;).

I might buy some more sheet Acetal -- though milling it makes an absolute mess -- just to try and find the sweet spot machining parameters, but I also have a beech wood plank and some aluminium (though I don't know the exact type). However, I'm not sure I'm ready for milling the latter material without at least some mister setup.

I stand corrected! That was a typo on my part :P

Thanks for your replies!


EDIT: @ Don, you're right! I typed <'> instead of <">. Thanks for pointing that out. According to at least two online conversion tools, 0.008' really does translate to 0.2(032)mm, so I don't quite understand.

If I set the cutwidth property to 6,5 mm, does it make two passes of 3,25 mm at each DOC level?

I do have a 6 mm 2-flute general purpose HSS end mill. Do you think it could do the job, or should I get a dedicated HSS tool for plastics?

I will also see to securing the machine. Being no engineer, I have no idea why the router would move by itself during the cutting  ???


Actually, the material thickness of this part was 16mm, so the DOC of 6mm would take 3 passes.

Do you mean a chip load of 0.04 mm or inches?

Also, the mount was intended for attaching a dial indicator to the spindle  :D . But I like your comparison!



Hi guys,

I attempted to cut a spindle mount out of some scrap piece of 16mm sheet POM and the result was really poor.

Here's the setup:

The machine itself is a lightweight (ca 50kg) extruded aluminium profile router with a water-cooled 800W 1000-24000 RPM spindle and can supposedly feed up to 2500mm/min.

The stock had been drilled, placed on a wooden spoilboard and attached to the T-slot table by two screws.

I used a 6mm 1-flute, polished rake solid carbide end mill designed for machining aluminium/plastics. Not an Onsrud, but I fed their cutting data for soft plastics for a 1/4 inch diameter end mill (ChipLoad = .008-.012', or ,02-,03mm) to the CamBam's Feeds and Speeds Calculator, setting the RPM to 10000, F to 2000 (mm/min) and DOC to 6mm (=1D).

That's when black magic happened! The machine is not designed for running coolant, but I suppose chip evacuation wasn't an issue, as the black flakes flew everywhere. Also, the router itself began to dance on the table and the first half of the mount did not stay in place despite using some holding tabs. Needless to say, the end result was really poor and the surfaces really rough.

I remember machining POM before and encountering the opposite of this problem. The surface finish was better... until the plastic started to grow hair, so I imagine that the feeds were too slow back then.

Anyway, any words of advice on how to obtain a good finish on this router? Can it be achieved e.g. by reducing the feed and speed and/or DOC, better securing the workpiece, attaching the machine directly to the table (as it is, it stands on four rubber feet), all the three solutions combined, or something else?



...I've just tested your updated plugin and it's worked fine so far on Windows 10 64-bit.

Merci, David!

Hi, not sure if this is the right thread to report a bug (I don't know if it's the plugin or the CamBam), but I'd like to report a repeatable crash of both the NumMove plugin and the CamBam. Closing the plugin window (either by clicking the "close" or the "X" button) causes CamBam to crash and return to Windows desktop.

Plugin version:
CamBam version: [1.0] Rel 16
Windows 10 64-bit [edit: specified the Windows version]

Scripts and Plugins / Re: 'Simulate with CAMotics' plugin
« on: February 13, 2017, 09:39:07 am »
...I've found out that Camotics works fine when I define the tool library and tool number in the Part section. I don't even need to select any postprocessor.


Scripts and Plugins / Re: 'Simulate with CAMotics' plugin
« on: February 05, 2017, 09:18:08 am »

Thanks for your explanation. But shouldn't Camotics render my machined workpiece properly regardless of where (i.e. in which section) the tool was defined and whether or not it is a library item? Depending on a project, sometimes the simulation works and sometimes it doesn't and I don't know why.

Take #1: I've just tried again, chose a 'Mach3+CutViewer' postprocessor, defined stock, selected tool #1 from library (in Part), and Camotics still only displays the uncut workpiece (its dimensions and offset, as well as the tool type and diameter, are fine).

Take #2: Started from scratch with the same imported model. Same postprocessor. Same stock. Same cutter type and diameter, this time entered manually in MOP. Got a warning in CamBam '3DSurface1 has tool diameter overridden. Sim results may be wrong', yet this time everything seems fine in Camotics.

Any thoughts?


Scripts and Plugins / Re: 'Simulate with CAMotics' plugin
« on: February 05, 2017, 07:42:23 am »
Just when I thought I finally knew how to get Camotics to work, I gave it one more try and it only displayed the workpiece without the machined area... I even made sure to use a tool from a tool library.

Is there any procedure I should follow in CamBam to ensure proper simulation of my MOPs in Camotics?

That there are three places for defining tool parameters in CamBam (Machining, Part and MOP) sure is confusing...


Scripts and Plugins / Re: 'Simulate with CAMotics' plugin
« on: February 04, 2017, 12:25:14 pm »
Hi jk,

Camotics doesn't actually animate the removal of the material, does it? What I see is in fact a cutter moving over a workpiece that is already machined. Am I doing something wrong or is it just the way it works?  ???


Latest News / Re: CamBam plus V1.0 (new development release)
« on: February 04, 2017, 12:07:27 pm »

Merci beaucoup! Thanks to this plug-in I finally found out that, for Camotics to simulate properly, it's best to use the tool definitions from tool libraries instead of those entered manually in MOPs.

Anyway, maybe it's the Windows 10 and its updates. I've experienced some graphics card glitches recently, so maybe the system also affects CamBam's behaviour?


Latest News / Re: CamBam plus V1.0 (new development release)
« on: February 03, 2017, 22:42:35 pm »

Changing the postprocessor to 'Mach3-CutViewer' didn't help. Camotics still wouldn't display anything, which leaves me somewhat puzzled.


Latest News / Re: CamBam plus V1.0 (new development release)
« on: February 03, 2017, 14:46:21 pm »
Hi all,

I've experienced several crashes of the new release recently. The Windows' error code is this: "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available".

This usually happens after choosing a different postprocessor and/or generating G-code (incidentally, I also haven't been able to get Camotics to even load the .nc file generated for Mach3 by CamBam, but I don't know if these two issues are related).

Is there any way I can debug this?



Latest News / Re: CamBam plus V1.0 (new development release)
« on: January 17, 2017, 09:03:30 am »
Hello Eddy,

Thanks for the links! CamBam is now working fine. I did a fresh install (just in case), right clicked the CamBam plus 1.0 folder in Program Files (x86) and unchecked the Read-only attribute (I don't know why this folder was read-only in the first place...). Then I copied the license key and plugin files into their proper folders, and then unblocked (right click + Properties) these files. (Unfortunately, you can't batch process files this way, so the more the .dll plugin files, the longer it takes.) It turns out that the original error message had nothing to do with the .NET framework, as both functions are active by default on my Windows 10 machine.



Pages: [1] 2 3