M581 Description
-
@dc42 I have started working through what is required to undertake my planned switch over to RRF3 in the near future.
So I started looking over the "RepRapFirmware 3 overview"
Would it be possible to get a little clarification on what the exact function of M581 is.
As in the overview M581's description is nigh on the same as M577...
is there another explanation for them being so similar.
thanks
-
@calvinx On the basis that DC is a bit tied up, I'll jump in here and try to help if I can. AFAIK, the only difference between gen 3 and gen2 with both of those commands, is that instead of specifying an end stop, you specify a pin.
The functionality is the same and that functionality is maybe a little clearer if you look at the gcode meaning in the wiki here https://duet3d.dozuki.com/Wiki/Gcode#Section_M577_Wait_until_endstop_is_triggered
and here
https://duet3d.dozuki.com/Wiki/Gcode#Section_M581_Configure_external_trigger
Essentially, M577 waits for an end stop to trigger so nothing much will be possible until that end stop triggers. Whereas M581 is more like an interrupt so you can do other things and everything will function as normal until that interupt happens. At least, that's my understanding........
-
That makes sense, which is why I asked as the docs are sometimes explained in such a way that it is sometimes assumed that everyone has the same level of understanding as the Author.
Wording can be a funny thing, and as an engineering educator I understand differentiation only too well, one person can read a thing and bam, ok let's do it, while the next person reading it goes "eh wtf does that mean" that's when you have to rephrase it to get the other person to understand it.
Sometimes stating the obvious is required an example of that is M305 being replaced by M308, it says that you use M308 in the M305 section, but doesn't actually say that M305 is now defunct and no longer used untill you read further on in the M308 section.
When a simple "M305 has been superceded with M308, see M308 for further explanation" would avoid any confusion whatsoever.
maybe it's just me !!!
-
@calvinx I tend to agree. I think of necessity, the author of the original documentation is the person who has designed or developed the "thing" in question. Then familiarity with that "thing" on the part of the author, can lead to the use of terms or language that may seem vague or even incomprehensible to someone not familiar with the "thing" in question.
We are all guilty of it though. When helping others on these forums, I have often used terms such as DWC which will make no sense to someone new to Duet. I guess the answer is that the documentation should be proof read by someone who is not the original author, and then the necessary changes made to make the text clearer. I have a feeling that the response to that is that we are all free to suggest or make changes to the documentation via the wiki.
-
@CaLviNx We will expand on the information in that page, and port the information back to the main gcode page, ASAP. I realise its a bit sparse right now.
-
Please don't take my post as a complaint. its not, I understand you are all super busy, once I understand the new code better I will try to read it over and help with upgrading it.
I have a full printout of the old set of g codes in a folder I refer to anytime I want to make any meaningful changes. And the engineer in me likes to be prepared hence the reason I was trying to get my head around the new changes to the g code.
I think what might be handy is a few example config.g files that relate to certain printer types like before, yes i know David has said the duet 3 is over kill for a "normal" 3 printer, but you just know many are still going to do it..
-
@calvinx said in M581 Description:
I have a full printout of the old set of g codes in a folder
Beware - we update that page frequently!
@calvinx said in M581 Description:
I think what might be handy is a few example config.g files that relate to certain printer types like before
We will need examples for Duet 3 for each gcode that is specific. I hope to have some exmaples of a Delta, CoreXY/Cartesian, tool changer and maybe one or two more before TCT show. In the longer term @chrishamm has now updated the backend of configtool.reprapfirmware.org so adding Duet 3 configuration generation will be easier for him to do
