You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+51-2Lines changed: 51 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -623,7 +623,57 @@ After you have loaded the tool, if no M argument (default) or an M1 argument is
623
623
624
624
Example MDI Command: G65 "UNLOAD" T10
625
625
626
-
626
+
## Maker Macro Usage
627
+
628
+
These macros, in their base form with human readable file names, must be put in the top level of whatever program you want to run.
629
+
Typically this means leaving them in the root folder of the machine and running all programs from there.
630
+
Though you could keep copies of these macros in sub-folders to run from them if you want.
631
+
632
+
Some users may want to use the `maker_macro_m##` feature of the control.
633
+
This lets you put files with that naming convention into the `maker_macros` folder on the control,
634
+
and then call those macros via an Mcode from any folder.
635
+
636
+
If you do this, then instead of calling --- for example -- `G65 "PROBEBORE"` you instead call `M810`.
637
+
So its up to you to remember the mapping somehow.
638
+
639
+
We've provided a python script that converts all the named files into the maker macro format for you.
640
+
That file, `build_maker_macros.py` can be run to convert all macros into the maker_macro format.
641
+
The script places all the new files inside the `maker_macro` folder.
642
+
Note that the script first DELETES EVERYTHING inside that folder, so do not make any manual edits to those files.
643
+
They will be lost.
644
+
Any edits need to be made in the top level macro files, and then propagated to the `maker_macro_m##` files via the
645
+
build script.
646
+
647
+
The mapping of file name to maker_macro is:
648
+
649
+
'CALIBRATEPROBEBLOCK':801,
650
+
'CALIBRATEPROBERING':802,
651
+
'CALIBRATEPROBEZ':803,
652
+
'CALIBRATETOOLSET':804,
653
+
'CHECKPOSITIONALTOLERANCE':805,
654
+
'COMPZEROPOINT':806,
655
+
'COPYWCS':807,
656
+
'FINDCOR':808,
657
+
'LOADTOOL':809,
658
+
'PROBEBORE':810,
659
+
'PROBECIRCULARBOSS':811,
660
+
'PROBECONFIG':812,
661
+
'PROBEINSIDECORNER':813,
662
+
'PROBERECTANGULARBOSS':814,
663
+
'PROBEY':815,
664
+
'PROBEYWEB':816,
665
+
'PROBEXSLOT':817,
666
+
'PROBEPOCKET':818,
667
+
'UNLOADTOOL':819,
668
+
'PROBEXYANGLE':820,
669
+
'PROBEOUTSIDECORNER':821,
670
+
'PROBEXWEB':822,
671
+
'PROBEYSLOT':823,
672
+
'PROBEX':824,
673
+
'TOOLSET':825,
674
+
'PROTECTEDMOVE':826,
675
+
'SAFESPIN':827,
676
+
'PROBEZ':828
627
677
628
678
## TODO
629
679
@@ -633,7 +683,6 @@ Example MDI Command: G65 "UNLOAD" T10
633
683
- Add a macro to check min/max values against soft-limits (would also like to add this to my post processor)
634
684
- Add probe runout compensation into the calibration: Rotate the spindle 180 degrees with M19P180. Then re-do calibration and compare results to compute runout. Need to figure out the math for how to compensate for it during probing.
635
685
- Add probe Angle routines (i.e. probe a wall and compute its angle, so you can rotate the X/Y axes)
636
-
- Add 4th Axis probing routines
637
686
- Add wear comp macros or wear comp to existing macros
0 commit comments