I really liked the way you talked through how the post processor works. Maybe you could do some more videos like this in the future. I had a problem at a previous job where the post would output the tool height offset on the same line as the first Z move, which made it difficult to step through and validate the program. Normally I would step through in single block mode and check the distance to go to make sure I wasn't going to crash the machine. But having the tool offset on the same line as the next move, you couldn't see this. If I knew how to modify the post processor I would have done this, and made my life a bit easier.
Thanks Dominic, I can make more of these if people would like. The post videos are some of the most viewed so other people share in that request. If you or anyone else has some ideas or requests on a topic to cover let me know. I make these as I think of things that people might run into.
Great tip! I'll have to start using G53, thanks. I'm not running a Fadal, just mach3 on a low budget mini mill, but hopefully I can get it to work. Out of simplicity I've just had G28 off in fusion's P.P. It would always cause it to hit a limit switch...so I simply end a program with a Z retract and manually (hot keys) jog it where I want it. Having the G53 automatically go to a specified coordinate will be helpful, thanks again.
Another very helpful video...Thank You. The part about adding user defined properties is awesome! We have a Haas VF-E and a Fadal 4020 and I use the generic Haas post on both of them and always have to manually change those lines to G90 G0 X0 Y7. for the Fadal and G90 G0 X0 Y4.5 for the Haas, the X value varies depending on which vise I use. Being able to add user defined properties and using G53 will be awesome. Thx again
Thank you! I have an old supermax mill I converted to linuxCNC . I use Fusion360 and have added hand tool changing to the code, this will be very helpful for rounding out my post!
this video is fantastic! i am new to Fusion360 and the G28 was driving my table to the far right position. now its right where i want it! Looks like this coded it will default to the last homeX and HomeY values used too? if so that is a major bonus. Thanks again . I subb'ed and a big thumbs up!
Really useful insight and something I will now try to implement myself. Some of this is starting to make sense to me finally! Could you paste the various lines of code so we can copy and paste them rather than starting and stopping the video and writing them down? I'm finding these videos on post processors really handy. I'll have to see if I can get my head around tool tables next....
Hello Murray, I tried to do that in the past and google flags me for inappropriate content or refuses to allow the post or comment. Some of the videos I was able to get the code into the description. I love it when a robot tells me I can't do something that is legit. Anyway, just send me an email and I will be more then happy to send you the code snips. Tim
Thanks - I wondered! I also just found that the "generic Fanuc with subprograms" post seems to be write protected but the "generic Fanuc" isn't. If I "save as" something else, I'm OK. Perhaps it's something I did....
Could just be the way fusion installed the files. I never mod the supplied posts directly or your changes can get over written by an update. Just make a copy some where else and mod the copy.
Wow you certainly have done the leg work for us. Man, this info is incredibly valuable and no one I know of has ever provided it in such an easy to follow format. Really many many thanks. Its cool to hear the reasoning behind some of code. This kind of info is the missing link for so many guys. I would love to learn anything regarding post refinement like this your willing help with in vids to come. Thanks again. just Steve P.S. Do you have Patreon? I would love to contribute to the channel somehow.
Thanks Steve, if there is a post issue you would like to see covered let me know. I currently do not have a Patreon, maybe I will make a Talken Swarf video on the subject and see if there is interest. I was holding off because I didn't know what the reception would be at this early point in the life of the channel.
If someone does this and runs into problems such as HomeX unknown, be sure to include the properties like below. if (properties.SetHomePosition) { machineConfiguration.setHomePositionX(properties.HomeX); machineConfiguration.setHomePositionY(properties.HomeY); }
Yes, there seems to be a bug in the old versions of fusion that they patched and the old post worked with the old code but was not correct. The new version of fusion needs those variables.
now i need to add a switch to remove G54 and replace M2 with M99. reason is my control can merge NC with conversational. So for instance i can use program conversational to probe the part setup automatically, then run the NC code, then i could go back and probe a feature size etc or run another conversational block. Assuming this is the same procedure as you showed for the G53 example? i get nervous when modifying posts.
Yes, it should be. I like to write a working example file by hand first. Then I work to make the post output match my working example. If you need help getting it done drop me an email.
i'll give it a shot on a copy of my working post. one thing i have noticed for the G53 modified post is for posting a new program the X zero (15.0) is remembered from the last post but the Y zero defaults to "2". is it from this line? HomeX: 1, //set x home position HomeY: 2, //set y home position
With Fusion it seems to remember if you change something from the defaults. But yes, those lines are where you can change the default to something else.
I learned a lot with your 2 videos here, but for some reason it does not work for me the way you described. I particularly get a "ReferenceError" that HomeX and HomeY are not defined. Trying to figured it out, I found that HomeX and HomeY are properties, and the sentence machineConfiguration.setHomePositionX" needs a variable, right? So I replaced "HomeX" with "properties.HomeX" and it works!... but it's not like you describe, why? Here is the sentence that works for me: machineConfiguration.setHomePositionX(properties.HomeX) thanks!!
Not sure on that one, I tested all these changes when I made the video. But I think the call of properties.homex would be correct. Fusion might have changed there code since I made the video.
Hi, I been learning a lot, but there are a tons of information, so I must to take my time. Thanks to your videos above all!! But right now I have another question, in post there are some text for tell warnings or indicate something like changes on WCS, "Invalid coolant mode" or "Spindle speed out of range". When this text appears? It is for commenting inside g-code, or when it´s fail like a dump file, or what? I think I saw some g-codes with comment at the end of certains blocks after //. It was maybe writen by man after post?
Thanks Darren, I have not heard that before. There is a significant amount of clearance between the edge of the table and my doors. Does that 4th axis hang over that much? I have the iron for a 4th but I don't know what it came off. Won't have an issue with that one, it is small. Just need to get a motor and resolver for it. Tim
Not sure how you set your tools. I touch all mine off the table with a 1-2-3 block the 2" side, then after touching the last tool i move it up is "z" then 4-2 the machine send it to home goto mdi type G43 z say 8" H (what ever that last tool is) then the readout "z" will be at 8" hand z to the top of the work piece and put that as the "z" value for what ever offset you are using. Now you can use any tool(s) on another job or offset just set that new "z" to the new offset. Basically how a probe works.
This has been helpful! Working through editing a robodrill post to work with my Hyundau Wia drill tap center!
I really liked the way you talked through how the post processor works. Maybe you could do some more videos like this in the future. I had a problem at a previous job where the post would output the tool height offset on the same line as the first Z move, which made it difficult to step through and validate the program. Normally I would step through in single block mode and check the distance to go to make sure I wasn't going to crash the machine. But having the tool offset on the same line as the next move, you couldn't see this. If I knew how to modify the post processor I would have done this, and made my life a bit easier.
Thanks Dominic, I can make more of these if people would like. The post videos are some of the most viewed so other people share in that request. If you or anyone else has some ideas or requests on a topic to cover let me know. I make these as I think of things that people might run into.
Great tip! I'll have to start using G53, thanks. I'm not running a Fadal, just mach3 on a low budget mini mill, but hopefully I can get it to work. Out of simplicity I've just had G28 off in fusion's P.P. It would always cause it to hit a limit switch...so I simply end a program with a Z retract and manually (hot keys) jog it where I want it. Having the G53 automatically go to a specified coordinate will be helpful, thanks again.
Remember when using G53 that you need to have some type of machine home. Either by limit switches or a know startup position.
Thanks, yeah I've got home and limit switches...I'll give it a try this weekend.
Another very helpful video...Thank You. The part about adding user defined properties is awesome!
We have a Haas VF-E and a Fadal 4020 and I use the generic Haas post on both of them and always have to manually change those lines to G90 G0 X0 Y7. for the Fadal and G90 G0 X0 Y4.5 for the Haas, the X value varies depending on which vise I use. Being able to add user defined properties and using G53 will be awesome.
Thx again
I knew someone would find the properties thing useful! :)
Thank you! I have an old supermax mill I converted to linuxCNC . I use Fusion360 and have added hand tool changing to the code, this will be very helpful for rounding out my post!
Your welcome, sounds like a cool project.
this video is fantastic! i am new to Fusion360 and the G28 was driving my table to the far right position. now its right where i want it! Looks like this coded it will default to the last homeX and HomeY values used too? if so that is a major bonus. Thanks again . I subb'ed and a big thumbs up!
Thank you, Yes Fusion will remember custom settings most of the time. Just double check them on a new project of if you change posts for some reason.
Really useful insight and something I will now try to implement myself. Some of this is starting to make sense to me finally! Could you paste the various lines of code so we can copy and paste them rather than starting and stopping the video and writing them down?
I'm finding these videos on post processors really handy. I'll have to see if I can get my head around tool tables next....
Hello Murray, I tried to do that in the past and google flags me for inappropriate content or refuses to allow the post or comment. Some of the videos I was able to get the code into the description. I love it when a robot tells me I can't do something that is legit. Anyway, just send me an email and I will be more then happy to send you the code snips.
Tim
Thanks - I wondered! I also just found that the "generic Fanuc with subprograms" post seems to be write protected but the "generic Fanuc" isn't. If I "save as" something else, I'm OK. Perhaps it's something I did....
Could just be the way fusion installed the files. I never mod the supplied posts directly or your changes can get over written by an update. Just make a copy some where else and mod the copy.
Awesome, thank you!
Wow you certainly have done the leg work for us. Man, this info is incredibly valuable and no one I know of has ever provided it in such an easy to follow format. Really many many thanks. Its cool to hear the reasoning behind some of code. This kind of info is the missing link for so many guys. I would love to learn anything regarding post refinement like this your willing help with in vids to come. Thanks again.
just Steve
P.S. Do you have Patreon? I would love to contribute to the channel somehow.
Thanks Steve, if there is a post issue you would like to see covered let me know. I currently do not have a Patreon, maybe I will make a Talken Swarf video on the subject and see if there is interest. I was holding off because I didn't know what the reception would be at this early point in the life of the channel.
If someone does this and runs into problems such as HomeX unknown, be sure to include the properties like below.
if (properties.SetHomePosition)
{
machineConfiguration.setHomePositionX(properties.HomeX);
machineConfiguration.setHomePositionY(properties.HomeY);
}
Yes, there seems to be a bug in the old versions of fusion that they patched and the old post worked with the old code but was not correct. The new version of fusion needs those variables.
now i need to add a switch to remove G54 and replace M2 with M99. reason is my control can merge NC with conversational. So for instance i can use program conversational to probe the part setup automatically, then run the NC code, then i could go back and probe a feature size etc or run another conversational block. Assuming this is the same procedure as you showed for the G53 example? i get nervous when modifying posts.
Yes, it should be. I like to write a working example file by hand first. Then I work to make the post output match my working example. If you need help getting it done drop me an email.
i'll give it a shot on a copy of my working post. one thing i have noticed for the G53 modified post is for posting a new program the X zero (15.0) is remembered from the last post but the Y zero defaults to "2". is it from this line? HomeX: 1, //set x home position
HomeY: 2, //set y home position
With Fusion it seems to remember if you change something from the defaults. But yes, those lines are where you can change the default to something else.
I learned a lot with your 2 videos here, but for some reason it does not work for me the way you described. I particularly get a "ReferenceError" that HomeX and HomeY are not defined.
Trying to figured it out, I found that HomeX and HomeY are properties, and the sentence machineConfiguration.setHomePositionX" needs a variable, right? So I replaced "HomeX" with "properties.HomeX" and it works!... but it's not like you describe, why?
Here is the sentence that works for me:
machineConfiguration.setHomePositionX(properties.HomeX)
thanks!!
Not sure on that one, I tested all these changes when I made the video. But I think the call of properties.homex would be correct. Fusion might have changed there code since I made the video.
Hi, I been learning a lot, but there are a tons of information, so I must to take my time. Thanks to your videos above all!!
But right now I have another question, in post there are some text for tell warnings or indicate something like changes on WCS, "Invalid coolant mode" or "Spindle speed out of range". When this text appears? It is for commenting inside g-code, or when it´s fail like a dump file, or what?
I think I saw some g-codes with comment at the end of certains blocks after //. It was maybe writen by man after post?
Typically those warnings get placed in a .fail file that will dump the error codes and not produce a G code file.
Make the Y6.5 on the Fadal if you get a VH65 4th axis otherwise your right the door off.
Thanks Darren, I have not heard that before. There is a significant amount of clearance between the edge of the table and my doors. Does that 4th axis hang over that much? I have the iron for a 4th but I don't know what it came off. Won't have an issue with that one, it is small. Just need to get a motor and resolver for it. Tim
I have a 3016 and that's what i set mine too. Assuming like me your cold start is your home?
Yes, my cold start is at the center of the table.
Not sure how you set your tools. I touch all mine off the table with a 1-2-3 block the 2" side, then after touching the last tool i move it up is "z" then 4-2 the machine send it to home goto mdi type G43 z say 8" H (what ever that last tool is) then the readout "z" will be at 8" hand z to the top of the work piece and put that as the "z" value for what ever offset you are using. Now you can use any tool(s) on another job or offset just set that new "z" to the new offset. Basically how a probe works.
I think where ever the machine zero's out is where all the offsets should come from
Doesnt workl
machineConfiguration.setHomePositionX(1.0);
machineConfiguration.setHomePositionY(2.0);
It says HomeX is not defined