G98 and G99 are now done.
G98
G1 Z-15.400
G0 Z-12.000
G1 Z-15.800
G0 Z-12.000
G1 Z-16.200
G0 Z-12.000
G1 Z-16.600
G0 Z-12.000
G99
G1 Z-15.400
G0 Z-12.000
G0 Z-12.400
G1 Z-15.800
G0 Z-12.000
G0 Z-12.800
G1 Z-16.200
G0 Z-12.000
G0 Z-13.200
G1 Z-16.600
G0 Z-12.000
G0 Z-13.600
G73 is coming along but I am tired.
When this is finished who around here has access to Solidworks Cam and can test the PP on their CNC?
As closely as I’m following your progress I really wish I did. I feel like I’m invested at this point.
This is always the problem because I have no idea but I am normally the one that comes up with a solution but finding people to test the solution is almost always impossible.
I guess I will throw it up on Thingiverse and hope to get some responses from someone who uses it. I have G73 to finish then one more drilling cycle and that is all that I see in this CAM.
Congrats on getting it working! I know I was pushing you to try another route, but it was only because I was wanting to try to help you succeed the only way I knew how.
It looks like you stuck with it and found a solution.
No sweat. I just didn’t want to relearn everything all over and I have to say the CAM in Solidworks really makes it a one button solution. Now I am sure it will not be for really complicated stuff but for a 3 axis mill I think it will be the best.
Once I am done with the post processor I get to learn about the tooling and honestly I am lost.
G73 is now done so one left to go.
;Simulate High Speed Peck Drilling G73
G1 Z-30.000
G0 Z-27.000
G1 Z-30.400
G0 Z-27.400
G1 Z-30.800
G0 Z-27.800
G1 Z-31.200
G0 Z-28.200
G1 Z-31.600
G0 Z-28.600
G1 Z-32.000
G0 Z-29.000
G1 Z-32.400
G0 Z-29.400
G1 Z-32.800
G0 Z-29.800
You know I almost threw my hands up yesterday because suddenly everything that was working ceased to work. I still do not get why this wants to take a value and do a metric to imperial on it when it should just shut up and print the value as is. n ceased to be what is needed and it became N and one of the values I must use suddenly would crash to desktop the compiler if I tried to pass it as an argument but if I just used it straight in the subroutine there was no issues.
I feel as if I am trying to bust a Bronco with this and it isn’t me it is it. Never seen fully working cease to work before to the point I had to rewrite.
I had that happen with a python script one time. If you aren’t doing it already, I’d suggest putting your code into a git repo and pushing changes every time you have it working. That way you can revert when you break it.
You know I have been a user of github for over a decade but I swear I have no idea how to do a project on it. I really do need a way to version but with this I went to bed and everything was working then I woke up and nothing was. All fixed now but it took an entire day for all of it.
I found out that G83 Variable Pecking is only for a HAAS machine and for all other machines it just mimics the other. Funny thing is I can’t find anywhere in this thing on setting I,J,K so if I had a HAAS I have to be able to set that and it needs to be set on a per drill bit basis.
FWIW, you can commit changes in git without github. Git is separate, and github is just a popular place to share git repos. You can commit changes, branch, merge, rebase, all without access to a server. It is a really good way to add version control to text editing.
I would also tell you something I was told when I started programming. It isn’t magic, and it isn’t an animal. There are reasons for everything, even if you can’t always see them. So something must have changed overnight.
No idea but this language is held together with bubble gum and I know this because the same bugs that are hitting me has hit that VAR. The biggest bug is that one moment a value will print out right then the next it decided to do a multiply, or divide, by 25.4. If it hits VARS then it hits me I can safely say it isn’t me that is the issue though I am not making money putting out faulty stuff like they do.