Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: turmite on November 04, 2007, 03:36:20 PM
-
Calling Terry Parker.
Hey Terry here is the thread for digitizing. I will post the image of the guitar in a little while, but wanted to get this up and started.
Mike
-
I am waiting. In the meanwhile I have figured out that if we scan in in a specifc order say CCW that all you would have to do is add a preamble to the top of the points file and issue a G1 and the points file will cut itself in the order it was probed. Aint that a kicker built in mini 2d cam.
You will have to set up mach to do a 3 axis points file with axis letters included, simple enough
If you add in the proper approach you can even use tool comp.
So that means if we can probe the outer in the same specific order it will also cut itself after being setup.
But all it can do is line segments so we probe in fine detail or just clean it up in CAD/CAM and do it right.
Hum All I have to do is write several direction order specific probing routines, add a startup preamble to configure the mill and it can cut the points file. SWEET
This sounds like a GREAT new feature that is needed in LCAM. 2D POINTS TO G CODE conversion.(;-)
(;-) TP
-
Here is another interesting tidbit If when you probe in order then you can take the points file and ADD a G1 to the top and load it up as a GCDOE file and see the line shape of the object. You should be able to then open LCAM and load up the MACH Gcode file and have a LCAM project to work with.
BUT I can't get Lcam to open the file(or any MACH gcode file for that matter) So I cannot test that part yet.
So If we can back load the Gcode file into Lcam then we can use all the features of LCAM. IFIFIFIF it would open the file.
Backdoor CAM so to speak.
(:-) TP
-
Hi Terry,
Sorry about being so long getting back with you. I am an ordained minister, though not pastoring a church and a local congregation called early this morning and needed a fill in. Their pastor is bad sick.
Anyway here is a file that is similar to what I want to do, but not the actual guitar. I will have to get in photographed or......I have a cad file of it already, just a cad that is not correct. I would possibly get us close enough to do the probe job though. This jpg will give you a good idea though of what I need.
Mike
ps the second shot with the real guitar is actually closer but both will give you an idea. I have to digitize from the back side and all I want is the outside profile.
-
Not a problem Mike, If you have the lords work to do then take care of that first We have all the time in the world to work on this project, Unless of course I hear the horns blowing and his voice calling from the clouds, then you are on your own I am going HOME(;-)
I THink this is going to be a piece of cake with the new G31polar arrays we have now. They are completly configurable as to the area they can probe. All or any portion of a circle inside or out in any direction and any diameter at any resolution (;-)
What we will have in the end is a 2d point SHAPE file not a point cloud.
Also we are working on a way to backload the points into LCAM for Cut file processing that way you will not have to be specific on the probing order just collect the points any way you choose. Then you can process the Shape file with all of LCAM functions to produce a proper gcode file for Mach to run.
Can you tell I am excited about this developement with the arrays????
(;-) TP
-
Terry I can tell you are real excited! Now I just wish I knew why! ;D Would you prefer to have the cad that is close to right to set your boundries with? Now remember, I only need this for cad at the moment as I have lots of modeling to do such as putting the neck pocket in, pickup cavities and wiring routes. I will of course have to put the neck attachment screw holes but that isn't a biggy.
Mike
-
Terry I got to thinking. If you can use the polar array point gathering thing, is there any way to incllude something like that in the 3d probe plug where tihe array is used to determine the physical boundries of a contained point cloud? You know where I'm going with this one don't you?
Mike
-
MIke that file would help out.
-
Terry I keep thinking of all these things after I have hit the post button! Any chance you can be in Knoxville Tn the last full weeked in Feburary for a tentative Southeast US Mach convention? Poppabear (Scott) is heading it up. If it goes off, I have already comitted to give away a $1995 seat of Madcam which is a cam plugin for Rhino and hopefully by then I will also have a new cad/cam beta to let people try out? This would be a good time for you to teach about the probe plugin as well as demonstrate it.
Mike
-
Terry what file extension and I would rather not post this one on the web since it is for a customer. Email me at
turmite
too
at
g
mail
dot
com
You should know how to put it all together to make it work. I will then send the file directly to you.
Mike
-
You guitar lads really are going the hard way about it.
A soundcard, and SF2 file with your guitar sounds, and you could make your computer play the guitar while you cut it out !!!
Jim
-
HiMike, enclosed are the files you will need, The gcode files go in the gcode directory and the Macro file goes in the macro directory.
Also there is a short MANUAL describing the process.
Play with the arrays to get used to them.
I believe we can get the scan in 1 pass of the array and get 99% of all the points needed
. If not I can program you a special one just for the guitar
-
here are the rest I hope(;-)
The G31PACMv1.00.txt is a text version of the Macro file for those that want to see it.
-
Well that did not go well?????
Well I am Brain Dead today, it DID take the files. SSSHEEESH
(;-) TP
-
HEY BENNY could we get an area off the general path to work with the G31 discussions it may grow large before it is over.
(;-) TP
-
OK this should be the MANUAL(;-) and the picture.
-
MIke you are a clever one(;-) The idea to have the program do a boundary survey of the object has occured to me.(yougest son is a surveyer) If we can do that then the array can become self aware of it parameters.
I have seen some very safisticated probing routines(oldest son 2 masters degree in Machine technology related fields). Some boggled my mind (would not take much there) as to the ability to probe with 4-6 axis ON its own. Just start it an walk away and COme back tomorrow.(;-)
(;-) TP
(;-) TP
-
MIke have you calibrated your probe to make sure you have the correct probe tip offset setting???
(;-) TP
-
Hi Jim,
That feature will probably come down the road a little bit. I'm mostly concerned in getting as accurate profile of this body as possible.
Terry,
Something is up with the email alerter. I got your private emails but nothing to tell me there had been any post to this thread. I have been knee....no...chest deep in a battle with my cam program today and I know it is probably a parameter I am not setting correctly, but that doesn't lessen the stress level any. You should have another private email from me now. I will try to get to the shop this afternoon and test this thing to see what I get. For safty I am going to use a block of foam for the test. Other than the one on the machine, I don't have any probe tips left! :'(
Mike
-
Terry I thought I would add the last email you sent to me to include it in the thread and maybe it will help others follow along and you kindly lead me to 2d knowledge! ;)
"Hi Mike, there is an interior and exterior Gcode file. THe m1299 macro will work for both.
The best center start point is on the center line of the neck and about 1.5" in from the left hand edge of the body. I believe that will give you a 99%+ fill rate on points.
I have a polar line array printed on a sheet of transparent Mylar (24" dia)that I can overlay the drawing and work out the best approach and center start point.
You might want to make one for yourself to lay out over the parts to figure out for yourself if there is a better point. Just place it on top and look at the approaches on the lines and look for areas that the probe cannot reach traveling in a straight line. (;-)
Do a couple of small objects first to get a feel for the process(;-) I would hate to know I helped to scratch a LES PAUL.
I did a 1" 6 sided Hex socket here inside and out, it was amazing. I then washed it thru Lcam to create a cut file with tool offsetts. Then cut another socket out just like the original even the square drive hole at the bottom of the socket.
(;-) TP"
Now I have a question from the manual.
"4. SafeZ: The safe Z height at which the probe can
travel.
5. Probe Height: The Z height of the probe cycle."
In setting these z heights are we staying in referenced dro readings or do we have to zero the dro's of do offsets and such? The reason I ask of course would be the long dialogue we had on the yahoo group about crashing my probe the last time.
If I follow the following sequence will I be ok?
1. reference machine and have dro's at 0. Mdi to my cpl and set my z axis to the "safe z height'?
2. run the exterior probe gcode, which will pull up a menu for me to set that is shown in the manual?
3. complete setup and run the code.
You ask me about calibrating my probe tip. Is this done in Mach or in the array probe set up?
Mike
-
Oh yeah I forgot, what kind of angle is needed to get a decent point file? Is the photo you posted earlier like you think I should set the body up with, and if so, are the polar array lines about what you think is needed?
Now come the really not understanding part. If the photo represents your optimum cpl for this guitar body, why wouldn't a symetrical polar array based on the therotical center of the body be a better solution? The reason I ask, is if you choose the center/1.5" from left side cpl it looks to me like you are going to have some point not be picked up due to the leg length no being long enough on the right half of the guitar?
Questions......questions?
Mike
-
MIke you can reference you machine or not it does not matter in the end. As long as you do not rezero or re reference after you have started working.
I would reference the machine and then JOG over to where I wanted the CPL then take a tape measure and measure to the furtherest point of the object away from the tip of the probe. That will be the leg length I would add about a 1/2" more to be safe. The safe Z height is the height that you see on the Zdro that is safe for the probe to travel in without hitting anything. The probe height is the height that you want the probe to probe in so it can touch the object.
Now you can start the program file . there will be several boxes pop up to allowing you to enter the config info. it will be done one box at a time. when you input the values and press enter then the next box will pop up,etc
Just for a general test I would set the resolution (leg separation angle) to 10deg that will give you a real course resolution but will go faster as there are less cycles to complete. To do a final resolution for real work take the diameter of the circle and solve for circumference. Next take the distance appart that you want each leg to be( probe tip diam works well for fine resolution.) and divide it into the circumference this gives you the number of legs you want to use. next divide 360 by the number of legs and that will give you the angle setting.
I guess I can make that part easier if the CONFIG asks you a few more question.(;-)
For the first test run I would set the probe to probe above the object to run in air and trip the probe with my figure. to make sure you do not break the tip(;-) It will cycle as follows. It will raise up to the safeZ height then travel over to the outer legnth of the first leg. It Will then lower down to the probe height and begin the cycling it will move towards the CPL postion until it either hits , or reaches the CPL. It will then move diagonally to the next start position and repeat the cycle. It will cycle all the way around the object . When it it complete it will closed down the saved points file.
If for some reason the probe sticks and MACH gives you an error ans stops. Wait until the cycle start button shows a black ring around it instead of yellow then press cycle start to resume. (Art is working on that part)
To calibrate the probe I will have to send you another code file that will find the center of a circle and report the diameter. You probe a known diameter hole. then you can set the tip dia comp on the SETTINGS page in mach.
then go back and redo the COC and check the diameter to see if it is correct. If not change the COMP value to make the diameter come out correct. That way when the probe trips during a cycle, mach will record the position of the edge of the tip not the centerline of the spindle.
(;-) TP
-
AH but they are good questions(;-)
If you can imagine the array located at a point on the body. ( I have one printed out on a transparency that I can lay on top of the object or drawing) Then you can follow the lines down to the center point to see if the probe is going to be able to touch all the surfaces. You will see IF there are any voids where the probe will not touch. The overlay does not have to be finely graduated you can simply rotate it on the centerpoint to see all the possible approach legs.
Heck even a piece of string with one end held on the CPL and rotated will let you see the voids. The overlay just lets you see ALL the angles at one time so you can move the CPL around to pick the best spot.
(;-) TP
-
Here is a tidbit for those that always wanted to CNC port cylinder heads but did not know how to probe the ports for a reference.
If you start out with a probe tip the same shape as the cutter tool you will use (WE use a 3/8" ball tipped tool on a long taper shank) then you can take the polar array and probe a slice section of the port one step at a time.
For example position the head in a fixture you would use to hold it during machining. Pick a center point location that allows you to get as far down the port as possible. Next start the array running and allow it to step down a certain amount each cycle. When you have reached the bottom you will have series of slices that can be used to create a cutting program to replicate what you have probed.
Next rotate the head in the fixture to setup the other end of the port and repeat the process.
As long as you use the same shape tip as the cutter then the probe shape will translate directly to the cut shape accurately. You can then cut it like you probed it.
Just A Thought (;-) TP
-
Mike if yoou find that you cannot get all the points then the array gives you the ability to move to that area and tune the array to the shape of the area you need to pick up.
For example say you could not get all the point in one of the curves in the neck area. After you have done the initia array look at the tool path window and you will see all of the probe points displayed for you to see. If you see some areas missing then move over to that area and setup another run this time with the interior array. you can setup just an arc to probe a certain area. you can start at any point and stop at any point. Being able to tune the array makes it very handy. Remember the ZERO deg stating point is at the 3oclock position on the array based on the x axis.
If you have a transparency overlay make sure you print the zero point on the array that way you can lay it on the part and see where you need to start and stop the array and setup the CPL.
Make sure you name the second file something different. I use the old add a number to the end of the file name trick. IE: guitar1,guitar2,etc.
When you have collected all the points you need just cut and paste the files together or append them all on to the master filename. Then when you import them into your cad they will all be there. You can then clean up any wild dots and smooth the curves.
-
Hi Terry,
I just got back from helping my son in law process some fresh venison. I'm tired and will now wait till morning to test the array code.
I kinda suspected you were into motors of some sort when I saw your post about cam grinder over on the yahoo group and now that I have seen the head porting post I know for sure you are. If I could show you the other project I am working on I bet it would get you going. Full size car body made from slices of foam 1.5" thick then glued together to make a plug. This thing is going to be nice.
Mike
-
Tip diameter note: The smaller the tip diameter the less distortion of the point position due to acute angulation from the approach angle verses the surface angle. That is to say if the surface angle has a steep angle to it the trip point may deviate slightly due to the surface touching the side of the tip instead of headon. Machs Tip comp is calculated from a headon approach angle.
(;-) TP
-
If you want to see what the shape file will look like as a line drawing
Then take a copy of the point shape file and add a G1 as the first line. Then load it up in mach as a GCODE file. You should see the shape file as a line drawing in the tool path display.
(;-) TP
-
Hi, Terry
Would you post an example "shape file" for us to look at and how to load/import into a Cad program.
Just getting started with probing hear.
Thanks, Chip
-
Hi Chip,
To make sure you are aware, this array system Terry has developed is currently for 2d point finding. With that said, nearly any 3d model that has an odd outside shape or cavity that needs to be reversed engineered can be probed for the data. Here I am speaking like someone who knows what I'm talking about, but I will actually get to run my first test tomorrow morning. Terry developed this to help me get a profile of a guitar that I just could not get in cad. I tried several times and it was taking way too much time. If you want I can post some sort of model tomorrow morning for a sample.
Mike
Hi, Mike
Thanks for the Reply
I had posted this Nov 2006
Hi,Art, Brian and All
Is there a way Mach3 can follow a X,Y path, set to pick-up Z value (set to probe at X Y move distance say .250) and incorporate it into a new file with X Y Z moves.
Need to trim off some excess edges, on some (one off) curved shapes 2 x 4 feet, plasma, Water-jet ?.
Any Thoughts Ideas ??
Thanks, Chip
-
Chip hopefully your quest is where this testing is headed. While it is nice to be able to do this in a macro, it would be so much nicer if all were included in the probe plugin. I hope you noticed my question to Terry about the possibility to use this as a means to set a profile that could then be digitized within the parameters picked up by the array macro. That almost sounds like what you are looking for as well.
Mike
-
Hi, Mike
Just trying to get back up to speed, Converted a WaterJet cutter to Mach3 awhile back 4x8' Z 24".Wanted to cut the edges of a curved part's on it.
Have a small mill with 4 th axis and probe to work with at home, Just interested in your project.
Hi, Terry
You expressed a desire to move this topic to a different area, You name it "G31 Probing" ??, Will move it.
Thanks, Chip
-
Good Morning Guys, What I am working on is a suite of of arrays. We have the polar arrays working next will be to develop
a set of linear arrays that are as tuneable as the polar version. This will give us the ability to probe in a head on approach to get the best accuracy. Things like x-,x+,y-,y+, z-
For example I could start at one spot use a x+ array to go down the first side, switch to a polar to go around a rounded end, switch back to a X- array to go down the other side. Switch back to the ext polar array for the other rounded corner and then move to an inside cavity and fire up an interior array to gather more data from a pocket,etc,etc.
This way you would not have to use a method that is NOT optimized for the shape you are probing.
It may even be possible to select a batch of arrays to form the best shape to probe an object and then have them run as ONE programed cycle.
NOW when we have the suite all ready with all the different arrays available then it will be time to build a FIRST CLASS MACH page to be able to run them all from. It could give you a host of controls and displays to aid in 2D probing .
Hopefully we can get one of the page building Gurus to help us out on the PAGE, so be thinking of functions you would like to have Incorporated.
Also we may need to develop a couple of simple utilities to make life simple. One such as converting the points string to a Gcode file. It would just need to add a preamble of code to the top of the file. Or one to append one file to another(dos command somewhere). Maybe one to add line numbers to the file????, you get the idea. Perhaps someone could build a small utility program with all the functions rolled into one for us 2Ders. I might could do it but it would be UGLY(;-)
NOTESNOTES: Keep notes or just update the topic with them.
I will have a simple shape file in a little while. I am doing an example of a connecting rod. It will be a low resolution scan but you will be able to see detail. and play with the points if you want.
With all you guys help we can have a really nice application for MACH users. Just a little payback to ART for all his hard work.
(;-) TP
-
OK thinks are looking up I found a SWEET gcode to DXF convertor(free) to use to create a dxf from the gcode file.
SO now all you have to do is take the points file, add a g1 to the top of the list and that will convert it to a simple gcode file.
next convert the gcode file to a DXF. THen you can load up the dxf in your favorite CAD program and clean it up if needed.
Then you can load it into LCAM and process back to a first class GCODE program.
Enclosed are the following files(IHOPE)
ANrodpoints.txt The raw points file or shape file
Anrodshape.txt Raw Gcode file
AnrodDXF.dxf Raw Shape DXF file
ANRODJPG.jpg Image of the raw dxf file
THe converter file is in the next post(;-)
-
AND here is the converter file.
-
Hey Terry,
I am on my way to the shop to test this out and will be back later to post some results.
Mike
-
SOME of the jitters in the picture are from me adjusting things on the fly. Seems I did not have the height right to catch all the surface edge so I just tweeked it a bit you an see by the rest of the surface it came out quiet well. And it was not in high resolution.
THe polar arrays can do fie with smaller simple objects BUT
I think that building a suite of arrays is going to be the ultimate approach. We just need someone that can build a great wizard to assemble the arrays into a single program. Seeing how the actual code runs as a sub program it should be easy to assemble the program . (YEA RIGHT)
OH RON OLD BUDDY WHERE ARE YOU ?????? This falls into your expertise with conversation programming. CARE to join in the FUN.????
(;-) TP
-
We need to locate some of the following programs or pieces of code.
Points to ACAD
File appending code
file renaming code to rename file from a .txt to a .tap
-
MIke hop over and check out what Stirling has running in the 2.5d probing topic. COOL
It may be more of what YOU had in mind for probing the guitars.
(;-) TP
-
MIKE, on the general config page 3 columns over to the right and 5 inputs down you will find a check box called
" Ignore M calls while loading" You need to check this box so MACH will ignore the M call when it loads up and checks the file.
If it is not checked then MACH will run through the macro before you get to see it on load up.
THEN when you run the Gcode it will call it up .
(;-) TP
-
Thanks Terry,
I am knee deep in pink foam shavings at the moment and may be through tomorrow. If I get tired after while I may hook the probe back up and give it another try.
MIke
-
Now that ought to make a good picture, knee deep in PINK foam???
Take your time no hurry here . I have been processing some points files. I noticed that we need to convert all the little point segmented lines into a continueous line segments to make a better cut file. Also we need to figure out how to turn all the small line segments for curves into arcs.
Just some thoughts (;-) TP
(;-) TP
-
Hi guys learned a new trick tonight. I have been working on a way to pick up a single point and have it written to the open points file.
The g31 is the only way to write to the points file. So I set up the non used A axis as a phantom axis. Mach thinks it is on but it is really shut off so it does not move.
I opened the points file with the M40 macro and named the file. Then I used a test macro that calls for "G31 a1000 F1".
Mach starts the movement but the drive is shut off so Mach does not know it is not really moving.
Anyway I then can take my hand pendant and step over to a touch point until the probe trips( LED turns on) at that point the g31 code will write the position to the points file.
Next I start the macro again and move to the next point until it trips and the g31 write to the points file again.
After all probing is completed use the g41 to close the points file.
SO NOW we can collect points by hand. (;-) That allows us to collect the few missing points not on the tool path screen by hand and not have to repeat a small array just for a couple of important points.
We can set up the macro to run from a button push or a hotkey I believe.
You can also set up the Probe input to be emulated by a hotkey such as F12.(;-) you would move into the position you wanted to record , start the macro and push the F12 key to record the point to the file. You won not even need a probe if you do not need the accuracy just a small sharp point to reference where the center of the spindle is.
HUM probeless probing that is a new one(;-)
We are gettin close to a total solution for 2d probing.
(;-) TP
-
Mike here are the update array files. It should cure the random stop error(does here) The problem seemed to be that Mach did not have enough time to handle all the functions in between cycles and get everything done. All it took was adding a 1ms delay after the cycle to allow Mach time to do its thing.
NOW you will need to go to the config page and look in the far right column and check the box "G04 Dwell in MS" or else you will get a 1sec delay after every probe cycle. After you leave the config page make sure you pull down the config tab again and do a "SAVE SETTINGS" to make sure it is saved.
Just delete the old files and copy these to the Gcode directory. I have also noticed that Mach has a limit on the number of loops a gcode sub can make. So for now that limits us to .36deg of leg separation. At a 24"diam circle that equates to about .075" leg separation. My probe tip is .078". Should do for now. If not I have a solution(;-)
(;-) TP
-
Hi Mike
Thanks for the link. Just to confirm that I am looking for a suitable digitising probe with a 1/4" or 6mm shank (or an easy and accurate mod) for use on my desktop CNC router. ( I have a licenced copy of Mach3 which I find excellent).
Regards
John
-
Hi John,
this probe doesn't have a 6mm shankand the threads for adapters is quite small. Most of the extensions are about 3mm in diam and the threads are not close to being the same diam of the shank. Now you might be able to find a 6mm or 1/4" ruby tip that will work, assuming a tip will do the job for you. I can look to see if I can find one.
Mike
-
Terry I have today to digitize the guitar before I get back in the foam again. I went through the M1299 file and compared it to the rest of the macros in the macro folder.......it doesn't look anything like them. Everything is on a single line. I didn't do it....I promise! Can you post the macro in here as is should look in the folder?
Mike
ps where is that kart part? ;D
-
MIke if you look at it from notepad that is the way it is suppose to look. If you look at it from the VB editor it will look normal.
Did you make the change in the CONFIG to allow MACH to ignore the Mcode on loading a gcode file??? If not you will not see the array configuration program run.
I have done some very interesting profles so far with the arrays(;-) SOme were able to be cut immediatly with MACH without the aid of another program to clean it up(:-) PROBE TO CUT in one easy step.
(;-) TP
-
Mike to gather more detail in the neck area you can run the primary array based on the center of the body like you asked about earlier, and then set up two small half circle arrays in the curved areas of the neck. THen append the two small array points file to the primary file.
You will also notice that ART has setup the toolpath display so it SHOWS you the points as we gather them. SWEET THat way you will be able to see if any sections are missing and can go back and get them.
I have worked out a way to collect single points and have them written to an append file. So you can go back if you need to a collect a few more points to complete the shape.
BUT seeing how easy it is to set up an array it is faster to use the array.
(;-) Get at it, you are falling behind (;-)
(;-) TP
-
MIke if you look at it from notepad that is the way it is suppose to look. If you look at it from the VB editor it will look normal.
Did you make the change in the CONFIG to allow MACH to ignore the Mcode on loading a gcode file??? If not you will not see the array configuration program run.
I have done some very interesting profles so far with the arrays(;-) SOme were able to be cut immediatly with MACH without the aid of another program to clean it up(:-) PROBE TO CUT in one easy step.
(;-) TP
Terry I still can get it to read the m1299. It skips right over it and stops on the M40 line asking for a name. Name it, hit cycle start and when it hits line n73 G0 X #106 Y #107, it sends the machine to home????? I dd check the ignore in the config too.
Mike
-
(;-) Get at it, you are falling behind (;-)
(;-) TP
You taskmaster! I have been trying.....I just can't get it to work.
Did you get my email about the Mach convention in Knoxville Tn in Feb? You gotta be there to teach a class on the "ART" of probing! pun very much intended! ;D
Mike
-
OK what part does not work?
Move into the center point position.
Load up the outside array file as you would a gcode file. Then press cycle start to begin. IT will then present you with a window and ask you a question about the array. It will do one window at a time. WHen that part is done you will press cycle start to start the gcode side. It will then run the array based on the centerpoint location and the configuration you gave it.
??? (;-) TP
-
OK what part does not work?
Move into the center point position.
Load up the array file as you would a gcode file. Then press cycle start to begin. IT will then present you with a window and ask you a question about the array. It will do one window at a time. WHen that part is done you will press cycle start to start the gcode side. It will then run the array based on the centerpoint location and the configuration you gave it.
??? (;-) TP
Terry that is the problem. It moves right by the n1 M1299 to the M40 and ask me to name the file. It never has opened the m1299. I have even gone back and arranged the file to match what the other macros look like, though I did not do it manually. I simply opened as a txt file, saved it as m1299.mls. Would it help if I email you the set of original files you sent me as well as the macro I have loaded in the machine?
Mike
-
MIKE have you checked the "ignore MCODE on file load" on the config page? Go back and look. If it is unchecked then check it again and when you leave config do a save settings from the same pulldown menu. SOme times MACH will not save unless you manually save the settings.
Try download a new copy of the M1299.m1s from here and load it into the c:\mach\macro\machmill directory
IF that does not work then I will send you a fresh copy of all the files off of my machine. I know they work I use them every day now(;-).
(;-) TP
-
Terry I will go to the shop after it gets too dark to shoot! Waiting on a big whitetail to show up for supper! ;D
Mike
-
OK are we having Venision for lunch or do we have to chew on some of that left over PINK foam?? (;-) TP
-
Foam! ;D but only because my brothers two dogs interfered (sp). I had watched to does feed in the field and one kept looking back into the trees so I knew he was there. When he stepped out he was looking right at me and I couldn't tell if he was legal. When he finally relaxed, I raised my scope to eye level to take a look and just at that perfect time, the dogs saw him. I will tell you though, it was so much fun just to watch him react to the dogs, that made the hunt successful. That kind of success just doesn't taste as good though.
I didn't make it to the shop last night, but will go now and report back in a few.
Mike
-
Terry I just got back from the shop and here's the rundown.
The ignore is checked, and saved, and I even closed Mach and restarted to check again. Same problem. I then went to my macro folder to check the name on the folder and the extension. It reads as follows:
M1299.mls
I tried the program again and once again it skipped the macro and went straight to the M40 line asking for a name for the triplet file.
I have to download from the net and put it on my shop computer by disc. Could this be causing a problem. I always change the read only file when I do that because my home pc creates my cd's as read only. Other than that, I simply downloaded the stuff you sent me, plus the updated gcode files you posted here.
Mike
-
OK the file should be M1299. m 1 s Not . m l s ??? TYPO?? THat could do it.
I'll send you a fresh copy of the M1299 file. EMAIL as there is already a copy of the same name here on the site and it will not let me download another.(;-)
You may want to try downloading another fresh copy and trying that??
(;-) TP
-
Ok Terry I got the file, downloaded to cd, installed it in the macro folder just as you sent it to me and I am still getting the same thing. It skips the m1299 and goes directly to the m40????
What am I overlooking?
o0001 (G31 Exterior Polar Array V1.01)
n1 M1299
n2 M40
Is there anything in these three lines that isn't supposed to be there? There are three empty line spaces above the code when opened in notepad. Would that mess it up? Remember this is the same instance of Mach3 that would not allow me to type a m40 in the mdi line???
Mike
-
Terry I am going to do a copy and paste to the Yahoo group as well and see if anyone there has any ideas.
Mike
-
OK key word here " when opened in notepad" it should read as one long continuos line of code. You should not be able to see the three empty lines above the m1299 line (;-)
If you save it in notepad after you opened it you may have corrupted the file.
Look at the file on your cd using MY COMPUTOR does it show the file as "M1299" A m1s file? Or does it say" M1299 "a txt file?
(;-) TP
Take a fresh copy and just load it to the proper directory. Do not open it (;-) Try that
-
Hi Terry,
The first version you emailed me directly read "M1299.m1s.txt when I opened it. When opened in notepad it was in a single line across the screen. I didn't think that was right, but loaded it in the Mach3 folder in the macro folder and tried the program, which of course failed. I then saw you had posted two new versions of the gcode, interior and exterior, to this thread. I downloaded them and tried again. This time it did not have the txt extra extension and did not have the single line problem, but it still wouldn't work.
This morning I did a save target as my cd drive and downloaded directly to the e drive, but still had to burn the cd. I took that cd to the shop, move it to the desktop, opened properties to change the read only function, applied the change and then moved it to the Mach3 macros folder. I tried the program and still had the same problem, but this time I had not opened it in anything until I had tried it. After it failed, I then opened it and that is when I noticed the three empty lines above the code.
Mike
-
OK I just have to ask ,why do you reset the read only bit of the CD???? (;-)
How about emailing me all the files you are trying and I will check them out on this end.(;-) We ARE going to solve the mystery.
The original M1299.M1s.txt is a file that was a notepad version that could be opened and looked at by notepad as a reference
The actual MACRO is M1299.m1s
THere should be two array files that end in .txt and one MACRO file that ends in .m1s
(;-) TP
-
OK MIKEY, You were wanting to do a survey of an object and then create a grid based on the perimeter.
Take the perimeter points and import then into the cad side. Now set up a POINT HATCHing profile that is the correct spacing and direction (90deg to X axis) for your grid. Now hatch the shape drawing. NOw you have a grid based on the shape file.
You job is to figure out how to get the grid exported out as a point file so we can apply it to the G31 process(;-)
Almost there(;-) TP
-
HEY MIKEY YOU STILL THERE????? NEW things with probing, Mach now has probe tip offset for acurate shape profiling.
Did you ever get the guitar done???
(;-) TP
-
Hey Terry, I checked out your probing arrays today. They are very cool. I'm one of those people who is planning to do cylinder head port work. I have several questions. First, my g31 code output file doesn't list the axes like your example did. I just get three columns of number. Is there a setting I have missed? Second, how would I incrimentally move down a port in Z? Is this something that must be done manually?
-
Is this macro up and running? I would like to try and use it. Any updates?
-
The last version was V1.01 it always worked fine so no need to do anymore updates. There is also a manual here somewhere with pictures and drawings. The arrays are completely programable as to provide for the best coverage. Multiple scans can be run and the points appended to the main point file.
There should be a M1299 macro that is used to program the arrays. The array runs in Gcode so there is NO vb weirdness to interfere. I have run countless probing operations totalling many hundreds of thousands of cycles without fail.
NOW that was with older versions of MACH, the newer versions ????? (;-)
(;-) TP
-
I stand corrected the last version was V2.01 Int and Ext.
There are 2 Macros M1299 and M1289 one for each of the arrays In/Out.
That was years ago and 1000s of programs down the road(;-)
IT still should work fine today, give it a whirl.
(;-) TP