![]() ![]() Any changes in how the machine behaves between operations is probably going to be here. Export() decides whether or not to insert tool change code, spits out unit strings for the machine, headers, comments, etc. All the magic is in export and parse.Įxport() handles the big picture and assembles one big-ass gcode string which is the final output. ![]() Linenumber just does what it says, handles the line numbers. Nothing too interesting unless you want to add new arguments.Īfter that there are just three procedures. Looking at the GRBL post, the code down to line 140 is setup, defining some globals, and parsing the arguments. The posts are mostly self-contained scripts and not too complicated. Probably the best thing is to look at the existing post processor code. In fact, the wiki page about customizing post processors is a bit thin. ![]() My question is what should i read in order to customize the post processor.įantastic! I'm afraid there's not much written yet. Ello, so I decided to give it a 2nd try on working with the PATH for generate g-code for a grlb based plasma machine I built. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |