Macros Are More Than IF Statements . . . They Are Lie Detectors! - Haas Tip of the Day

[@harrisonius]

This is a particularly excellent video for all the aspiring CNC programmers out there without a computer programming background. Fantastic presentation from Mark, as always!

[@Rickgrott100]

Wow! Thanks, I didn’t know the Haas control can do all these behind-the-scenes Thank you, Mark the Haas team! I have learned so much from these videos!!

[@SaviorTheBurn]

This has nothing on real programming. Seriously macro programing is simple.

[@andrew_the_machinist]

This is great. The world needs more macro programming videos. GOTO MORE MACRO VIDEOS

[@vojtechjakes9379]

I would really appreciate it if you made more macro videos! Thank you for your work!

[@jeffstark4196]

I use macros all the time. Great video Mark. Please do more on mod’s.

[@Mattias-mc1rm]

good video .. I like that you are back in this format, doing what you do best. Not trying to sell trinkets. :)

[@BobVawter]

I like using the "Power off at M30" setting at the end of the day, but want to park the table and/or unload the spindle before the machine shuts down. (Empty the spindle if poweroff on M30 is set); IF [#20002 NE 0] THEN T29 M6; Also, I use some tools and grippers powered by through-spindle air. I have the programs guard themselves by monitoring the TSC pressure sensor (identified in the IO page as analog input 7). M73 (AIR ON); #3001 = 0 (RESET MILLISECOND TIMER); G103 P1 (DISABLE LOOKAHEAD); WHILE [ #13007 LT 675. ] DO1 (WAIT FOR PSI TO RISE); G4 P0.1; (SLEEP 100MS) IF [ #3001 GT 30000. ] #3000 = 1 (OH NOES); END1; G103 (ENABLE LOOKAHEAD);

[@shagbuilt]

Mark, would love to see more about checking to see if there is a tool length in the offset table, and erroring if not. I find it crazy that this isn't a default for the control. Have never needed the gage line to hit Z0. :) Also, more on MOD please! Would be great to set up things like chip conveyor on X# of parts ran, etc. Thanks for the great videos, I use macros all the time as I am running lots of production parts.

[@markterryberry4477]

We have a Software Project (BZ1254, TP63937) that will have the control alarm out if we try to run a tool with an offset set to zero. On machines with probing, that could result in a crash. The code is written for this and the task is going through testing now. Great idea. We’ll put MOD on the list. We love macros, and have another video on them coming out after the holidays.

[@shagbuilt]

​@@markterryberry4477 Awesome! This will be a much appreciated safety/sanity check. I have never understood why it will alarm on so many other/lessor infractions, but would allow an operator whom forgot to touch off a tool to run it. Will also save from having to edit post processors to do this. Look forward to seeing them!

[@williamjohnson7764]

I have been using macros for awhile now. I have setup a whole library for my operators to use. They control tool #, diameter, rpm, feedrate, spin direction, part parameters, etc. A future video idea, that is more advanced, would be looping. Drilling holes in a rectangular array for example. I did it via a loop within a loop to do X direction then reset X count and move once in Y until completed. What could thousands on lines of code was reduced to just a few dozen.

[@crashfactory]

i love the 8 bit code idea. Not sure when i'd use that one, but dang, so clever!

[@markterryberry4477]

Follow the link in the description for “Bonus Content”. We have listed all the example programs we used in this video, including the 8Bit ID program.

[@ps9417]

Thank you Mark. You're a great teacher. How valuable this information is!

[@Austinfamily1]

Another excellent video! Thank you for all you do to educate us

[@jpa162232]

please do mor of these macro videos. huge help.

[@TJ4A9]

I use a Macro as a calculator to easily figure out an ARC TAN for a bolt circle. Sometimes I am doing repair work and need to line up to an existing bolt circle. I probe the center of the part, and then any hole, and run the Macro. It'll record the degree of rotation and put it into whatever variable I want to use. Then, I can program accordingly and use G68 and use the Macro variable and voila, it lines up perfectly. If anyone would like more info on that I can gladly share.

[@markterryberry4477]

That’s a perfect example of how powerful macros can be.

[@Einzbrn]

Could you share some g code examples? My brain functions better seeing it done

[@florianpohl3735]

Thank you for the great video. Please more on that topic

[@Bfreese12x]

Awesome Video. I personally would be interested in more macro videos! And the MOD video as well.

[@andrew_the_machinist]

Ok. The 8bit setup is redonk! That was a great climax for us computer science turned machinist guys!

[@kopsik111]

How do you use extended tool offsets? Or doesn’t Haas support using more than 30 tools per program?

[@teekteekteekteek]

Thanks mark! Very helpful!

[@markterryberry4477]

Check out the Bonus Content link in the description as well. We have posted all the programs used in this video, even the 8-Bit Macro Program.

[@neilattaway2182]

Very interesting. As yet, i have no use for this at the moment, but it takes me back to my solidworks training. How about writing a macro to convert imperial to metric ( vice verser ) for thread milling regardless of whether the machine is set to metric or imperial ?

[@markterryberry4477]

Great use case for macros. We can do anything! The Renishaw probing macros have IF statements that multiple our values by 1, if in Metric mode, or by 1/25.4 if in Inch mode. They store the multiplier in #179, so I tend to do the same (#179=1/25.4, or #179=1). In/mm is stored in Setting 9, which is variable #6009 on Classic Control, and #20009 in Next Gen control.

[@precisioningenuity2133]

Can you make a video on the new "Broken Tool Detection" camera option that is now standard on all UMC's? I would like to know how it works. Also, can it be added to machines other than UMC's? And is it something that "Just works" or is there setups and processes that need to be implemented to use it properly?

[@markterryberry4477]

Great topic. Well put it on the list. As far as availability, it is only available on UMC machines in the U.S. and Europe right now. There are new developments being worked on, for this product, and I’m excited to see that line grow.

[@O3DB]

Solid video 👏👏

[@DonkeyHotie]

Very timely. I am in the middle of trying to add a few unassigned Renishaw macros to a new VQC category (adding 4th axis X and Y, 3-point bore, 3-point boss). The one I thought would be simple was 9823 (Three point bore/boss). Similar to 9814 with three angle values, right? Except 3-point uses an A input (#1) for the angle, which is already the program selection used by 9823. I thought I could assign it to another variable but, I believe it passes #1 to the macro that determines the variable offset number. Now I'm wrapped around the axle. 9823 continues to us A as it passes it to 9727 so I can't just pick another variable for the angle and substitute it. Gahhh! I'm spending all my time reading and writing notation in the Renishaw programs, just to track what it's doing.

[@RobertOsterhoudt]

Is there a way to use macros to detect operator input? For example, with some stock that is widely variable or close to finish size and where the first operation cleans up a face. I'd like the control to pause, ask the operator for some input (Is the face fully cleaned up? Yes/No) and then proceed based on that response. Possibly making another skim pass and then adjusting a work offset by the amount of the 2nd skim pass.

[@markterryberry4477]

Yes. Check out M109 in the Haas manual for more info. This code works exactly as you described.

[@akronimm862]

Broh took b roll footage from a redstone calculator in Minecraft LOL

[@markterryberry4477]

Thanks for noticing :). I was happy that made the cut.

[@CAMER_21]

we got so many cam softwares..... we don't uses macros

[@p38pilotdk01]

In a production setting with various skill level operators, macros really make life easier. Just eliminating human error from changing over castings is huge

[@markterryberry4477]

@@p38pilotdk01you nailed it. Many of my macros, in a production environment, were just making sure that things couldn’t go wrong. Usually written after something went wrong.

[@CAMER_21]

@p38pilotdk01 yeah in production maybe it is useful ...

[@markterryberry4477]

@@CAMER_21I’m with you though, I try and avoid macros if there isn’t a legitimate need - it can turn a program into unintelligible gibberish, fast. Balance is needed.

[@CAMER_21]

@@markterryberry4477 sometime macros are so complex even programmer get confused .... so we avoid and let Cam software to there work

[@finchi55]

Fanuc Macros > Haas macros

[@Rickgrott100]

Why

[@markterryberry4477]

Automation.

[@andrew_the_machinist]

It's pronounced arithmetic 😂