NativeCAM is Features renamed

FernV wrote: The reason why I did not give more info on how to do it is because it saves some values twice and I did not have a chance to verify if it affects the setting you would have to do, which I promise you will find very simple

I checked and I found that the data in double is only in my Dropbox directory. My office PC is Win10 and I often develop/debug the ncam.py on that platform and since it does not recognize linux path very well, it saves the path to cfg files in the way it interprets it and when working with the same ini file from my mill pc (linux of course) it saves the path from it's point of view. The result is 2 references for one file. On my home PC it is not the case and paths are saved only once, so I do not have anything to change and I will explain how to order the quick access tool bar.

THIS HAS TO BE DONE WHEN LINUXCNC IS CLOSED OR THE FILE WILL BE OVERWRITTEN

NOTE THAT THE TOOLBAR WILL BE MOST USEFULL WHEN WE HAVE THE RIGHT ICON ON IT. MANY ARE NEEDED AND I AM NOT GIFTED AT DRAWING. YOU CAN IDENTIFY EASILY WHICH ONE I ADDED

From ncam_demo/ncam/catalogs/mill/ open quick_access.lst
(if the file does not exist, it will be created the first time you select a subroutine, open linuxcnc with the ini you want and simply select an item then exit)

The INFO section says it all :
"columns are : source, total usage, last time used and order of preference
Delete this file to reset or edit rank in descending order"

You should recognize by the files name what you want : circle.cfg, end-mill-change.cfg, etc...
Find the line of the one you want leftmost like end-mill-change.cfg (IMHO it should be the one). The last number of the line is the order. Set the highest number for it like 10000. Find the second you want and assign the second order like 9000 and so on.

Save the file and start lcnc. The order should be what you set and will not change on anything you set the order

Fern

kramdradoow wrote: When I first attempted to load a file from the examples subdir, I saw the tool paths fine but no outline of the workpiece. I also tried to create a new project with a new workpiece. No luck there.

Then I found if I added a tool BEFORE I added the workpiece I could successfully add the workpiece and modify values.

This should not be, Be assured that I read/listen to all feedback and will correct asap.

kramdradoow wrote: So I was able to add the workpiece, tool and some basic geometry but only if I loaded them in the order described above. However, I still had no workpiece visible on the AXIS toolpath screen. After watching Floris video I selected the "toggle skip line" icon and magic happened. I now can see the outline of the workpiece.

This is the behavior we want

kramdradoow wrote: Once I established this very first project and saved as default template I no longer have to think about this. (But I wonder if I have to follow that order if I choose a new project without having defined a default template.)

Your default template will load everytime you click "New Project"

kramdradoow wrote: For new folks trying NativeCAM, maybe my observations will help others out. I also don't know if this is your intended process because I ran gmocapy sim and did not see that if mattered what order I created workpiece/tool in nor did I need to select any "skip line". icon. Indeed, I don't even know if there is one on gmocapy.

The button is visible only when you are in auto mode not mdi. It is on the lower bar at about 1/3 from the right

Fern

Thanks Fern. I successfully loaded up axis sim with embedded lathe. I have had no time to examine it but am grateful that you shared this. I'm no programmer so I can be of no help except to try your programs out. I do recognize you will not be supporting lathe yet so I won't bother you with requests and questions.

Mark

newbynobi wrote: I just tried NativCAM on a real machine with very strange behavior!

I tried to machine the part from the previous screen shot.

My 4.2 mm drill has a tool length offset of -6.25 mm. I touched off with tool 1 (tool length offset = 0), than I loaded tool T7 M6 G43 with offset -6,25 and started the code (just drilling), the tool begins drilling about the tool compensation over the workpiece and thats why it would not go through the workpiece.

I never worked with tool length compensation yet, be carefull and keep me inform of your observations

newbynobi wrote: Very strange, as If i unload the tool with T0 M6 G49 before starting the code, it is fine.

Next, after finishing the part, I just mounted a new part of material and pressed start again, but then your code moved the zero point of the part! The code finished with the tool in position X90 Y0 and after the restart the position X90 was X0! Also the tool compensation made strong behaviors.

So I added as last code T0 M6 G49 G0 X0 Y0 and could make my three parts.

Have you ever noticed that?

If you cancelled the job, it is possible that it stayed in G57 instead of restoring G54 coords offsets. Refreshing the file corrects that.

newbynobi wrote: I made a new clone on my productive machine, running fresh master with rip-environment (I need my baby gmoccapy 2.1.5 for testing on that machine).
I followed the instructions of readme.dev. (By the way you missed to mention, that you need to copy the ui file to the config dir)

Right the information is not in README-DEV but commented in the [DISPLAY] section of all ini files

Please continue giving me feedback

Best regards
Fern

Thank you Fern!, now I have a step by step workflow



Floris

eFalegname wrote: Fern, thank you very much for being so helpful, you've done a superlative tremendous nice job.
This morning I found a very strange behavior, I think it's better to illustrate it with a video, I do not know if I should do the steps in a certain order to get that these things do not happen

Hi
I spent time studying the file you posted and it lead me to functions I never really edited before because this code written by Nick never caused a problem. I think newer versions of python are more sophisticated and surprising events happened when the treestore was empty. I think I solved something and I encourage everyone to switch to the updated ncam.py

Please report

Best regards
Fern

P.S. Your video is very well thank you