simple linux cam

More
30 Apr 2022 03:03 #241693 by Reinhard
Replied by Reinhard on topic simple linux cam
Hi,

thank you for your attention and your interest.

No, that is not an issue for me.

There are several reasons why I don't want to commit to freeCad:
    - freeCad's data model is insecure and unstable. If you change something in history, the whole model gets corrupted and there is no way to recover.
    Therefore (in my opinion) freecad is unsuitable for long term technical projects. I have been following freecad for many years and that basic model problem has not changed at all
    - freecad has many very good developers and freecad has a very good collaboration mechanism (incl. code review). That would be a reason, but - each developer cares only about his agenda. There is no collaboration where a common path is followed. One or two developers (fortunately) have the whole project in mind. The rest just do their thing
    - freecad is very python heavy and I don't like python!
    - freecads developers are all much better in math and better than me - I am just a simple hobby coder

That's why I decided to use a neutral format that can be written by all CAD systems. This makes me independent from CAD systems and my application can be used not only by freecad users.

As far as the missing binding to the CAD model is concerned, I even see this as an advantage (see above). My goal is to make the steps so simple that you can delete and recreate an operation at any time (currently: select drawing element, create operation, set machining parameters and select "create toolpaths". Toolpath creation can be executed at any machning parameter change). I plan to be able to show differences between model and product (sometime in the distant future - I'm at the very beginning of the project)

In addition, my focus is on the areas that are rather neglected by Hobby-cams. I do not intend to create a full-fledged CAM. Some things, like 3D surfaces, Deskproto already does better (which I think has very fair conditions for hobby use), other things are covered by CamBam or Estlcam.

I didn't find a cam to generate paths for my technical parts at that time, so had to program by hand. Such parts are my focus and I try to generate GCode as it is used in profesional environments.

Don't know if there is any interest in a product with my focus. We'll have to see.

Anyway, this is my way.

... by the way:
Suggestions, criticism and/or contribution are always welcome
The following user(s) said Thank You: tommylight, MTronics

Please Log in or Create an account to join the conversation.

More
02 May 2022 13:36 #241850 by Reinhard
Replied by Reinhard on topic simple linux cam
Hi,

With my project, I'm still at an early stage where I'm constantly questioning myself and my design decisions.
Following the mantra: "first make it work, then optimize" I'm still in the early stages of getting things to work. So far away from possible optimizations. Still, I'm not willing to use code that I'm already convinced is wrong or bad.
I only know the problems with freecad as a user. But I am aware that it is due to opencascade. I also had to realize that opencascade is not reliable at all. That's why I use opencascade only in the sense of "fire and forget", i.e. create ooct objects when I need them and immediately forget them again. I don't rely on occ datastructures at all!

I only rely on my own data and data structures.
I liked the structures of cavalier contours very much, but I had to realize that I am not skilled enough to adapt the library to my needs. So unfortunately I have to live without that library.

My data structures are redundant and consume much more memory than, for example, cavalier contours. Its because I understand my data structures only.
Maybe something can be optimized later?
Maybe I still learn and make friends with cavalier contour?
No idea what the future will bring.
For me, everything is new territory with which I am currently struggling.

Therefore - if you can tell me advantages that the data model of freecad can offer me, then please write that. I am open to any suggestion to seriously consider.
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
03 May 2022 16:02 #241928 by Reinhard
Replied by Reinhard on topic simple linux cam
Hi,

a small update.

For 5-axis operations like this you'll need a clamping plug.
 

With the update, you can define the clamping plug on top and create milling paths for it:
 

To try the generated paths only little change is required. The generated gcode starts like this:
( Job /media/Scratch/CP013.ngc );
( generated by kuteCAM V0.01 );
;
G40 G80;
T4;
M98 P100;
;
( ClampingPlug #0 );
( T4 12mm HPC Endmill - D:12 L:50 );
N10 G0 G90 G54 X-70.600 Y33.640 S4775 M3 T4;
G43 H4 Z61.000 M8;

The line "M98 P100" is a subroutine call for tool change. Replace that line with "M6" and have fun :)
Attachments:
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
08 May 2022 15:43 #242306 by Reinhard
Replied by Reinhard on topic simple linux cam
Hi,

just worked out open pockets on round and rectangular workpieces.
 
 
Attachments:
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

Moderators: Skullworks
Time to create page: 0.241 seconds
Powered by Kunena Forum