Plasmac Gcode documentation

phillc54 wrote: Did you do a make clean?

Nah, I have not done that for quite a while! It just says I have to clean up my revised component and get it into master!

You could set up a script to do it all automagically but I really think you need to set up a github repo and then put in a PR.

Yes you are right. I will eventually. Just keeping everything in sync scares me. I'm not retired like you

Until recently it was better to stay within the boundaries of plasmac and get you to make the changes.

But as I have pushed a few more boundaries, its hard to hack into Plasmac configs as its a very centralist paradigm. Adding some pins to plasmac.comp to allow third party enhancements would be quite useful I think.

eg. The now defunct hpid.comp Dewey wrote had several pins to enable the THC via various external functions which were or2'ed together internally. Just one external hold pin would be helpful as it would avoid some awfully complex unlinkp's to avoid changing the defaults but I gave up recently and found I had to modify a screen handler file.

Yes you are right. I will eventually. Just keeping everything in sync scares me. I'm not retired like you.

Honestly it is easy. I was doing it long before this permanent long weekend.

rodw wrote: I'm not retired like you

What is this "retired" you speak about? Is it something to spread on toasted bred ?

tommylight wrote:

rodw wrote: I'm not retired like you

What is this "retired" you speak about? Is it something to spread on toasted bred ?

No we Aussies use Vegemite!

rodw wrote:

tommylight wrote:

rodw wrote: I'm not retired like you

What is this "retired" you speak about? Is it something to spread on toasted bred ?

No we Aussies use Vegemite!

Now i am really lost !

rodw wrote: But as I have pushed a few more boundaries, its hard to hack into Plasmac configs as its a very centralist paradigm. Adding some pins to plasmac.comp to allow third party enhancements would be quite useful I think.

It seems a bit silly to add ?? amount of pins to a component on the off chance someone wants to change things, that is what HAL is for.

eg. The now defunct hpid.comp Dewey wrote had several pins to enable the THC via various external functions which were or2'ed together internally. Just one external hold pin would be helpful as it would avoid some awfully complex unlinkp's to avoid changing the defaults but I gave up recently and found I had to modify a screen handler file.

If you need to modify a screen handler then that is because of the GUI config rather than the component.

Thats the problem. the GUI is pure Plasmac too so its not a good idea to to alter the GUI handlers as it complicates upgrades.

A single external THC-hold pin would allow any external program to override the existing Plasmac enable/disable THC without the hal gymnastics that I found is required now.

But you would need to write HAL code anyhow so it just another line to unlink the existing pin.