The best part is, you were honest with your friend and the customer.. you both fixed the issue and you are giving your friend credit to this day.. that is how you become a stand up person in any industry!!
Great story Donnie! 2 months of generating macros for the same job sounds painful. I applaud you for the persistence and excellence in accomplishing it!👏👏
Having worked for myself, as a contractor, I can totally relate to your story. Absolutely! It sure can help to have another brain to bounce ideas off but I never got there and always did it alone. Isn't it amazing what we can learn from "failures"? Unfortunately, much of the real world is perpetually hidden behind heavy curtains to protect confidential company processes. For me, when I'd work on manlifts (outdoor elevators) or other industrial equipment, I'd always have to trace all of the wiring and make my own prints because the equipment manufacturers - in the interests of protecting their designs - would just supply useless block diagrams that had zero useful information. Secrecy, totally understandable but it means we're going to spend a mammoth amount of time in the field while the important information gradually trickles into our brains. If each company respected each other company and viewed each other as brothers on the same projects, imagine what an impact that would have on the world - teamwork!
Awesome, love the speed you recalled the story, and how you hit the important explanations, and how they relate to being a contractor. I learned a lot too.
How could the customer dictate a cost and run time without knowing the level of complexity it takes to complete such a part? or did they have a reference from another company that completed the part for them prior?
The beginning looked like a 12 Guage shotgun broach. I used to make barrel broaches on an old LaPointe cylindrical grinding machine from 1918. Still had a functional overhead belt drive. Good stuff.
Good ole macros and parameters. I am genuinely inspired by this testimonial. I work better under pressure, but one has to be careful not to bite off more than one can chew. So, thanks for sharing this experience. I feel like I'm headed in the same direction in my career and this insight will be useful when I find myself in similar situations in the future. Go, Titans!!
This is why you comment your code with explanations btw. They’re not for other people. They’re for you when you inevitably have to troubleshoot after you’ve already forgotten what the code does.
Nice man. I like the part about knowing how far to stick yourself out there. While obviously this measure is not the same for all people it is nonetheless a wise thing to keep in mind. That line between boldness and foolishness can be a mighty fine one.
Is that how it's done still? Everyone uses manual numeric register names like in cpu assembly, not variable names which a compiler changes into the register names. There's no default simulation to know how long things take until you put it in the machine? With trig calculated by hand It's very impressive but it seems so low level if it's either like a full automatically generated CAD-> CNC program or doing absolutely everything by hand. Makes me think programming language comp sci programs would like to see how much they can make things easier
I think the guys just wouldn't be able to trust the compiler not to destroy their expensive equipment. But some knowledge of higher-level concepts would definitely be useful, especially in this case.
My new favorite thing to do is write custom user cycles with multidimensional arrays and user interfaces on the Siemens 840D. The power of their high level language blows Fanuc macro b out of the water.
I used to code basic with a friend circa 1985. A not so simple program took a month to get working. In college we learned the first version of Lotus 123, an accounting spreadsheet program took something like 80k man years. A good programming friend of mine told me every problem starts with 5 words ( ALL I WANT TO DO_) and cost $60k. Home construction has "change work orders" that give terms and conditions. I have folks that come in the shop looking for expensive work that seem like simple problems they claim (it will take 2 mins- actually 2 days and 2 mins). Experience has taught me I am too old to play those games.
CAM you would need to program each part if the sizes change. This macro let's the operator make different size parts with the same program just from changing a few numbers at the controls without any CAM. Longer time to setup, but in the long run that macro has paid for it self. Probably still being used today.
He's building a macro program. One line of code that his customer can adjust the variables depending on what they are running. I don't think Fusion will cut it.
Almost 400 variables? I have done a couple macros myself and never did I even get remotely close to that number. I fail to understand why, seeing as the geometry is repeating itself meaning a sub-routine or while loop could've been used. Could you please elaborate a bit on that?
Okay its been two years so bear with me #600=62(amount of teeth on broach) #601-#699= 1,2 or 3. #601 was the first tooth #602 was the second and so on. It checked what you put in the custom macro offset to determine the geometry to create. It was just a simple counter #[600+#500] #500 being your current tooth after each loop #500=#500+1. remember it had to jump between what number it could start at and what number it could end at WHILE also jumping into rough and finish sub programs WHILE not crashing into the main and the sub. Now that I think about it I am not even sure how I did that lol #700-#730 were the geometry of tooth profile 1 and 2. REMEMBER this is all information on the blue print. #700 was the distance from tip to tip of one tooth #701 was the height of a tooth #702 was the radius of the scallop and so on #731-#760 were the trig to calculate the endpoints for #700-#730. Using TAN COS SIN ATAN ASIN ACOS example:#730=[[TAN[#705/2]]*[[#708-#701]/2]]. There were dozens of lines like this. It was pretty whack #800-#840 were the geometry for tooth profile 3. #841-#880 were the trig to calculate the endpoints for #800-#840(this one sucked... a lot) #900-#990 were tool geometry and toolpath calculations. Every tool radius, width and length had to be input for correct toolpaths. Redundant tools as well. YOU DO NOT USE CUTTER COMP ON PROGRAMS LIKE THIS!!! I did rough turning of the stock. You don't know what the customer will do. they may rough a lot off one day so multiple roughing passes will need to be automatically added if they take a huge cut. That's the backwards VNMG you see in the video #500-#599 were all of the pick and pull macros plus a bunch of other stuff like counters, collision detection, how I kept track of where Z0 was with G10 P0 Z#520. I probably missed a lot. I think my brain blocked this out after I was done. I do know that it is still used to this day.
@@donniehinske Oh, so each part has three different types of teeth, which were not standard and all have custom geometries and must be machined by tools which could have different geometries? Does that sounds right? Btw thank you for this lengthly answer, that was nice of you!
@@donniehinske I'm wanting to get into programming like this. Very early on in learning. Is this purpose of a program like this, so that the program can be altered and adapted to cut different broaches just based on basic information input into it? Essentially acting as an almost conversational style program?
Thank you for sharing your failure! I am currently working for a shop in Kansas as an operator that programs and does set-ups. obviously I am making peanuts. I am looking into becoming an independent contractor. I am using the titan school to fill in the gaps in my knowledge though I do have 10 years of experience. I found you can only learn so much working for one shop. I hope to get my own shop some day, I need to make more than peanuts and raise some capital! I love you videos, I love what you do, and I love the courage to share what you know with everyone. Companies like to hold onto information.
I have a masters degree in English linguistics but still only understood every 5th word. I don’t even know what CNC means but I watched the whole thing. Great vid!
It's the brain-dead concept that you're too afraid to say no when you go solo. Not until later do you get a voice of confidence on what you can do. It takes time. Then you learn to walk away, charge more or say no problem
The best part is, you were honest with your friend and the customer.. you both fixed the issue and you are giving your friend credit to this day.. that is how you become a stand up person in any industry!!
Great story Donnie! 2 months of generating macros for the same job sounds painful. I applaud you for the persistence and excellence in accomplishing it!👏👏
Thanks dude!
Your Friend "Jason" trained me on my new doosan last year. Great guy, small world.....
Jason is a BRILLIANT machinist and one of my favorite human beings ever! I am sure he trained you well
YASSSSS MACROS! 😂 Honestly, writing that macro sounds super painful
Hi Barry
Iv been trying to learn macros for work and it is painfully slow to learn when you don’t work with it everyday😂
Having worked for myself, as a contractor, I can totally relate to your story. Absolutely!
It sure can help to have another brain to bounce ideas off but I never got there and always did it alone.
Isn't it amazing what we can learn from "failures"?
Unfortunately, much of the real world is perpetually hidden behind heavy curtains to protect confidential company processes.
For me, when I'd work on manlifts (outdoor elevators) or other industrial equipment, I'd always have to trace all of the wiring and make my own prints because the equipment manufacturers - in the interests of protecting their designs - would just supply useless block diagrams that had zero useful information.
Secrecy, totally understandable but it means we're going to spend a mammoth amount of time in the field while the important information gradually trickles into our brains.
If each company respected each other company and viewed each other as brothers on the same projects, imagine what an impact that would have on the world - teamwork!
That was totally insane. You definitely played it down when you first told me about it. That's what legends do I guess.😆
Awesome, love the speed you recalled the story, and how you hit the important explanations, and how they relate to being a contractor. I learned a lot too.
Wow Donnie - that's an incredible story. I admired your courage when you went on your own. Takes guts. I am enjoying your journey . . . . .
Thanks Ma!!!
How could the customer dictate a cost and run time without knowing the level of complexity it takes to complete such a part? or did they have a reference from another company that completed the part for them prior?
They might have already fixed in a quote for their customer and gotten their timings from that, which would be a rookie error but it happens I suppose
Just an educated guess! Sometimes you just have to go for it.
agree, not saying the story is a lie but certain things seem off
That was crazy. you literally wrote a computer program with g code macros. Have to respect that.
You never work harder than when you work for yourself.
Prawda 😁
Dude...what are you talking about........are you working for BOOOM?!? What's this private contractor stuff??
The beginning looked like a 12 Guage shotgun broach. I used to make barrel broaches on an old LaPointe cylindrical grinding machine from 1918. Still had a functional overhead belt drive. Good stuff.
Good ole macros and parameters. I am genuinely inspired by this testimonial. I work better under pressure, but one has to be careful not to bite off more than one can chew. So, thanks for sharing this experience. I feel like I'm headed in the same direction in my career and this insight will be useful when I find myself in similar situations in the future. Go, Titans!!
Very cool story - I feel like I am playing with blocks like a toddler with my programming abilities compared to complex parts like that.
That broach cloud have been made in less than a week on manual machines. Plus heat treatment and finish grinding..,..
Great googly moogly! Meanwhile, I can’t program a tool break detection without copying and pasting from the web. 😢
This is why you comment your code with explanations btw. They’re not for other people. They’re for you when you inevitably have to troubleshoot after you’ve already forgotten what the code does.
Nice man. I like the part about knowing how far to stick yourself out there. While obviously this measure is not the same for all people it is nonetheless a wise thing to keep in mind. That line between boldness and foolishness can be a mighty fine one.
This was an amazing story!
Informative video Donnie! But who gave Donnie Redbull this morning! 😅
Idk but where they at i need one 😂
That was Donnie at half speed.
Donnie, have you ever considered making friends with some high end geeks in the software world? Your macro work is closely related to this specialty.
It is projects like this that help you learn so much to become way better at whatever you’re doing. Good job sticking to it until the ahha moment!
Is that how it's done still? Everyone uses manual numeric register names like in cpu assembly, not variable names which a compiler changes into the register names. There's no default simulation to know how long things take until you put it in the machine? With trig calculated by hand
It's very impressive but it seems so low level if it's either like a full automatically generated CAD-> CNC program or doing absolutely everything by hand. Makes me think programming language comp sci programs would like to see how much they can make things easier
I think the guys just wouldn't be able to trust the compiler not to destroy their expensive equipment. But some knowledge of higher-level concepts would definitely be useful, especially in this case.
Your customer had unrealistic expectations and you said “ok let me try”
Absolutely! Worst case scenario I have a good story for my future job on CZcams 😂
@@donniehinske well done 👏
My new favorite thing to do is write custom user cycles with multidimensional arrays and user interfaces on the Siemens 840D. The power of their high level language blows Fanuc macro b out of the water.
I used to code basic with a friend circa 1985. A not so simple program took a month to get working. In college we learned the first version of Lotus 123, an accounting spreadsheet program took something like 80k man years. A good programming friend of mine told me every problem starts with 5 words ( ALL I WANT TO DO_) and cost $60k. Home construction has "change work orders" that give terms and conditions. I have folks that come in the shop looking for expensive work that seem like simple problems they claim (it will take 2 mins- actually 2 days and 2 mins). Experience has taught me I am too old to play those games.
This guy reinventing computer science from scratch. Coroutines this time I think.
Yeah having another a machinist to bounce off is a bonus. I have my dad as i did my trade under him
I'm new to this but can't you jsut program stuff like that in fusion in like 2 hours?
The customer did not have CAM software but yes I could of used CAM but this situation did not allow for it
CAM you would need to program each part if the sizes change. This macro let's the operator make different size parts with the same program just from changing a few numbers at the controls without any CAM.
Longer time to setup, but in the long run that macro has paid for it self. Probably still being used today.
@@Hi_Doctor_Nick also that! YES! Haha
He's building a macro program. One line of code that his customer can adjust the variables depending on what they are running. I don't think Fusion will cut it.
I respect people that work hard, sounds like you're one of them. Good luck in your future! Learning makes life fun ;)
Almost 400 variables? I have done a couple macros myself and never did I even get remotely close to that number. I fail to understand why, seeing as the geometry is repeating itself meaning a sub-routine or while loop could've been used. Could you please elaborate a bit on that?
Okay its been two years so bear with me
#600=62(amount of teeth on broach)
#601-#699= 1,2 or 3. #601 was the first tooth #602 was the second and so on. It checked what you put in the custom macro offset to determine the geometry to create. It was just a simple counter #[600+#500] #500 being your current tooth after each loop #500=#500+1. remember it had to jump between what number it could start at and what number it could end at WHILE also jumping into rough and finish sub programs WHILE not crashing into the main and the sub. Now that I think about it I am not even sure how I did that lol
#700-#730 were the geometry of tooth profile 1 and 2. REMEMBER this is all information on the blue print.
#700 was the distance from tip to tip of one tooth
#701 was the height of a tooth
#702 was the radius of the scallop
and so on
#731-#760 were the trig to calculate the endpoints for #700-#730. Using TAN COS SIN ATAN ASIN ACOS
example:#730=[[TAN[#705/2]]*[[#708-#701]/2]]. There were dozens of lines like this. It was pretty whack
#800-#840 were the geometry for tooth profile 3.
#841-#880 were the trig to calculate the endpoints for #800-#840(this one sucked... a lot)
#900-#990 were tool geometry and toolpath calculations.
Every tool radius, width and length had to be input for correct toolpaths. Redundant tools as well. YOU DO NOT USE CUTTER COMP ON PROGRAMS LIKE THIS!!!
I did rough turning of the stock. You don't know what the customer will do. they may rough a lot off one day so multiple roughing passes will need to be automatically added if they take a huge cut. That's the backwards VNMG you see in the video
#500-#599 were all of the pick and pull macros plus a bunch of other stuff like counters, collision detection, how I kept track of where Z0 was with G10 P0 Z#520.
I probably missed a lot. I think my brain blocked this out after I was done. I do know that it is still used to this day.
@@donniehinske Oh, so each part has three different types of teeth, which were not standard and all have custom geometries and must be machined by tools which could have different geometries? Does that sounds right?
Btw thank you for this lengthly answer, that was nice of you!
@@shadowdsfire Yes pretty much
@@donniehinske I'm wanting to get into programming like this. Very early on in learning. Is this purpose of a program like this, so that the program can be altered and adapted to cut different broaches just based on basic information input into it? Essentially acting as an almost conversational style program?
@@SirFlibbertyJibbit yes that is Correct
Thank you for sharing your failure! I am currently working for a shop in Kansas as an operator that programs and does set-ups. obviously I am making peanuts. I am looking into becoming an independent contractor. I am using the titan school to fill in the gaps in my knowledge though I do have 10 years of experience. I found you can only learn so much working for one shop. I hope to get my own shop some day, I need to make more than peanuts and raise some capital! I love you videos, I love what you do, and I love the courage to share what you know with everyone. Companies like to hold onto information.
I wish you can open your own shop in the near future, I'm rooting for you. 👍
Damn, you are spectacular!
10/10 is that program available for " review " ? :D would love to see it. amazing work
That's what she said
What is the point making it by macro? I missed something? Why don't you just programm it with CAM?
The customer did not have CAM software. I could do that easily in CAM software but the customer couldn’t. That was the challenge
I have a masters degree in English linguistics but still only understood every 5th word. I don’t even know what CNC means but I watched the whole thing. Great vid!
It’s hella fun
I've written quite a few macros that I thought before this video were complicated, wow
It's the brain-dead concept that you're too afraid to say no when you go solo. Not until later do you get a voice of confidence on what you can do. It takes time. Then you learn to walk away, charge more or say no problem
Ahh the contractor life . Hits home.
that looks crazy
Se insisti e resisti, raggiungi e conquisti! Very strong man!
I thought WE GIVE COST AND RUN TIME not the customer 😶
Not in every situation.
did you get paid for all the hours you worked on the macro program? how did you track your time for your customer?
He wasn’t working an hourly position as a sub contractor. It’s a contracted payout.
great story... but you have to work on that "boom"... because it sounded a bit like the sound a cat does, when you step on its tail 🙀
Should have called me. CT would be about 20min😉
Shut up punk!!! haha 😆
This is why sample practice parts are important.
Very Much RESPECT
60 days ago: let’s begin
60 days later: yes finely
Your the man donnie keep up with the great story's buddy 🤟👍🤙
Cool Story Hansel
So how much was the program for several months of work?
Brilliant Work - thanks for sharing
Hello, im leraning as a CNC Programmist, can you give me some advice?
Can't wait for the next video on that amazing .......... TT 2100 SYYB 😀
Great video!!!
There's only one reason for a brooch that big the New Ukraine sniper rifle
Dude you're still my Steve Irwin
In some lines of work one is paid for the exact reason the video is titled. 😉
Parabéns !
great story!
2 decades in machine shops? Isnt the dude like 25?
lol he's a young 34. Donnie grew up working in his dad's shop from a young age. Very smart guy with lots of experience!
Engineers are overworked and under paid - no wonder theres a shortage here in the UK
Should have used ChatGPT
You can't even type a video title so I'm not surprised.
T16 ????
Love it
This just sounds like you discovered subprocedures. You know that thing that everyone who codes makes use of.
Bit more complicated then that.
I miss Titan whenever I see these manipulative video titles.
how is the title manipulative?
Been quickly done on a Mazak!
Don't know what the hell this guy talking about
the audio is out of tolerance
How to get job in this company
🥹
Not