Plasmac Gcode documentation

Phill, I wonder if the docs could be reorganised so that all plasmac specific gcode commands could be all placed together in the one continuous section in the docs?

When I go through the docs, they are mostly together but then there is a section about the shape library and back to more gcode stuff. So somebody reading the docs to write post processor will be forced to go all over the place.

It actually makes me wonder if there should not be a seperate shorter gcode reference for plasmac.

rodw wrote:

It actually makes me wonder if there should not be a seperate shorter gcode reference for plasmac.

I would think that could be added to the appendix?

Yeah, it is probably not a bad idea. The doc sort of just grew and grew and grew...

Yeh, I had a bit of a go at it tonight. I can email this so you can edit it.

Thanks Rod. Plain text would be fine as it needs to be converted to asciidoc.

rodw wrote:

Phill, I wonder if the docs could be reorganised so that all plasmac specific gcode commands could be all placed together in the one continuous section in the docs?

When I go through the docs, they are mostly together but then there is a section about the shape library and back to more gcode stuff. So somebody reading the docs to write post processor will be forced to go all over the place.

It actually makes me wonder if there should not be a seperate shorter gcode reference for plasmac.

Just pushed the additions Rod, thanks for putting it together.

forum.linuxcnc.org/plasmac/37233-plasmac-updates#169606

Phill you talked about an appendix but I think you just put it all together in the THC section. Is that what you did or do I have to wait for buildbot?

Yeah, you need to wait for Buildbot to update the packages then upload the packages and docs.

I was actually cursing you and your post processor today when I went to cut some parts.
So I recompiled master branch to get the changed M5 to work and for some reason lost my hypersensing. Then I halcompiled my component and all was good. In the past you would get a load error for the missing custom component now you don't. It must leave the old binary in situ now but it is broken until it is halcompiled again.

Did you do a make clean?