Plasmac Gcode documentation
31 May 2020 08:22 #169488
by rodw
Plasmac Gcode documentation was created by rodw
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.
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.
Please Log in or Create an account to join the conversation.
- thefabricator03
- Offline
- Platinum Member
-
Less
More
- Posts: 1130
- Thank you received: 533
31 May 2020 08:24 #169490
by thefabricator03
I would think that could be added to the appendix?
Replied by thefabricator03 on topic Plasmac Gcode documentation
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?
Please Log in or Create an account to join the conversation.
31 May 2020 08:26 #169491
by phillc54
Replied by phillc54 on topic Plasmac Gcode documentation
Yeah, it is probably not a bad idea. The doc sort of just grew and grew and grew...
Please Log in or Create an account to join the conversation.
31 May 2020 10:03 #169500
by rodw
Replied by rodw on topic Plasmac Gcode documentation
Yeh, I had a bit of a go at it tonight. I can email this so you can edit it.
Attachments:
Please Log in or Create an account to join the conversation.
31 May 2020 10:08 #169501
by phillc54
Replied by phillc54 on topic Plasmac Gcode documentation
Thanks Rod. Plain text would be fine as it needs to be converted to asciidoc.
The following user(s) said Thank You: rodw
Please Log in or Create an account to join the conversation.
01 Jun 2020 04:59 #169608
by phillc54
forum.linuxcnc.org/plasmac/37233-plasmac-updates#169606
Replied by phillc54 on topic Plasmac Gcode documentation
Just pushed the additions Rod, thanks for putting it together.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.
forum.linuxcnc.org/plasmac/37233-plasmac-updates#169606
The following user(s) said Thank You: rodw
Please Log in or Create an account to join the conversation.
01 Jun 2020 05:37 #169609
by rodw
Replied by rodw on topic Plasmac Gcode documentation
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?
Please Log in or Create an account to join the conversation.
01 Jun 2020 05:46 #169610
by phillc54
Replied by phillc54 on topic Plasmac Gcode documentation
Yeah, you need to wait for Buildbot to update the packages then upload the packages and docs.
Please Log in or Create an account to join the conversation.
01 Jun 2020 06:16 #169612
by rodw
Replied by rodw on topic Plasmac Gcode documentation
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.
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.
Please Log in or Create an account to join the conversation.
01 Jun 2020 06:18 #169613
by phillc54
Replied by phillc54 on topic Plasmac Gcode documentation
Did you do a make clean?
Please Log in or Create an account to join the conversation.
Moderators: snowgoer540
Time to create page: 0.093 seconds