So, a per-gcode switch ‘halt/alert/ignore’? A ‘halt’ group, ‘alert’ group, etc. Which would the default action be for codes not in a group?
Roll it the other way around. What are the CAD/CAMs using and what G-code is exported with which post-proscessor ? We know what we can cut and do. 3 groups maybe? We know it and cut it, We know it and HALT, We know it but sadly not implemented yet but of no Danger so move on?
4 Likes
Blunt question. Grbl is some sort of in roadmap, but is it a guide for the Maslow until we have our own Post-Processor?
well, the thinking is that when we have time, we should ‘steal’ the grbl code
for the g-code parsing and acceleration planning, and use it to drive the maslow
rather than continuing to create our own parser, and have to write acceleration
handling code from scratch.
If so, we have a clear picture of commands that could end badly. Can we have the software decide when to ignore it and when to ask?
It just takes someone spending the time to go through and make stubs for the
ones that can safely be ignored.
3 Likes
What if the gcode section of the Grbl code could be made as a module, And shared back to them, so that Maslow and Grbl can cooperate to improve that module. And both benefit of the future evolution.
Yeah sounds idealistic and maybe it’e a headache… Still it should be looked at for a moment.
If two and eventually more other projects could benefit share and cooperate then all could grow together.
But i’m not sure if that keeps the code small enough for grbl to fit on an Arduino nano
Maybe it is already modular enough…
1 Like
realistically, they are so far ahead of us in gcode handling, that I expect we
would not have to do much, but if we implement any improvements, the patches
should be able to apply to the upstream grbl as well
But that’s a bridge to burn when we get to it
1 Like
Blurfl,
The list was taken from standard milling G-Godes just to get me started. No doubt in this application tapping and threading does not make sense but it lets people know what is implemented and what is not as others may want to adapt the software at a later stage.
I guess the reason I was raising this was from the original comment about not knowing the supported syntax for G3.
Also we are reliant on third party tools for G-Code generation where no doubt things like G17 do get generated.
Anyway happy to support what the community feels is appropriate. I will continue to finish off the Supported codes table and feel free if I make any mistakes to let me know and I can change it.
Kind Regards Stuart
2 Likes
This seems like a really good resource to have an keep maintained as we add new features.
Does a wiki page feel appropriate? If you (@stuartri) don’t want to make a wiki page would someone be willing to transcribe the fantastic resource that @stuartri is putting together to a wiki page when it is finished?
1 Like
Bar,
A wiki page for supported G-Codes, M-Codes etc and associated syntax is a great idea as the Pdf version is not that user friendly.
This will also help if there are issues in the future with code generated from multiple packages as we don’t have a specific post processor for Maslow CNC that is available to wash the G-Codes generated from other packages.
I should be able to complete the pdf version by tomorrow then if anyone can assist we can work out where to put it in a wiki format.
One thing that was a little tricky in finding the supported CNC codes was the fact that CNC_functions.h file is actually an implementation file and not a header file in the traditional sense but all good.
Kind Regards Stuart
3 Likes
Bar,
I was thinking about the wiki format you mentioned and loved the idea. I then got to thinking it would be great if we could show a functional block diagram of the system which would then allow you to click on links to explore specific areas. To this end I have created the following functional diagram [Excuse me if I have got anything incorrect]. Any feedback would be greatly appreciated.
This would be very useful for exploring the project and at the same time get familiar with how it is all put together. It is very time consuming trying to work your way through the ins and outs of the hardware and software [if you are that way inclined].
MaslowCNC-FunctionalDiagram.pdf (320.3 KB)
As per requests please find the .png and.jpeg versions
Hope people find this useful.
Kind Regards Stuart
6 Likes
YES! I love it!
Can I put that on the front page of the wiki? Or maybe it belongs on the main page of github…or in the assembly instructions.
That is a super useful resource, where does everyone think the best place to prominently display it is?
Bar! Glad you like it. I am using it as a form of documentation as I work through the ins and outs of the system as this is one area where things need to be tied together visually.
I am thinking on the forums page would be a good place to start as that is where you start to explore areas of interest but will leave it to you and the communities better judgement. I am happy either way to continue to develop the idea and share findings.
Also in the diagram I can put an upper layer in for the sled itself which the X and Y Chains connect to and which the router is mounted on that way we have links to all the threads including the most recent investigations on the ring designs which lead to the triangular kinematic which is the next area I will be looking at.
I am also thinking about how to represent things like the kinematics as a linked item on the block diagram as well as commissioning / tuning so all ares are covered.
We could also have a basic description of what you would expect to find in that section as you hover over the item.
I am a firm believer this magnificent project has huge potential so I am happy to keep documenting and sharing progress.
Any improvements or comments are welcome.
Kind Regards Stuart
2 Likes
Given the functional block diagram should not be in the G03 Support and Limitations thread can anyone suggest where I should move it to while I go through a couple more iterations.
Stuart
2 Likes
Please also make this depiction available as .png or .jpg so we can use it in the forum as a tool to explain stuff. Or point to with specific questions if needed.
Very nice graphical presentation @stuartri.
Thanks for that Vertex. I have added the .jpeg and .png versions.
Can you suggest a better place to post this so that I can add some updates in future.
Kind Regards Stuart
I created a page for this in the wiki - please add it and maintain it there.
How to for the wiki is here -
http://www.maslowcnc.com/howtoeditthewiki/
May the force be with you
Thank you
1 Like
Bee,
Just to confirm you would like the JPEG under this link ?
Stuart
both an image and a pdf please?
Thank you
Bee,
I accessed the page, started editing then when I tried to save got a 404 error now I cannot seem to access the page for some reason.
Stuart
Do you have a github account setup and signed in? The first time I tried to edit my account was flagged and I got an e-mail, I had to reply and wait for it to get worked out.
I was getting those earlier today, too. That and a message about ‘too many accesses, try again after a few minutes’. I guess offline editing would be the solution for that.