Templates, guides, calibration

Hi is there a dedicated thread where all the details for when I receive my machine, putting together, calibrate, trouble shoot…?
If not I would like to suggest it. Make it proud and sticky. lol

There is the set of instructions on the wiki that should include all of that.

1 Like
1 Like

Hey @bar, at the top of the screen here on the forums are green buttons for the Maslow website and the Community Garden. Could we add one for the wiki?

5 Likes

Absolutely! Which page should it send folks to?

1 Like

If there is any possibility of a single Wiki installation (perhaps within Discourse? or as a module to the core maslowcnc.com domain?) vs. the current Status Quo, it would really be easier.

As it stands, (https://github.com/MaslowCNC/Mechanics/wiki) is the ‘home page’ of the 5 wiki’s each (loosely) focused on the github sub-projects.

“This is cumbersome and you should feel burdened by it”, to borrow a phrase from Futurama…

3 Likes

I agree!

The current wiki seems like it’s a little difficult to use because it’s so spread out and hidden.

Would using the discourse wiki features be a good idea?

Or something more like this in the garden?

Wiki posts looks like the easiest one to implement, but you’d know better than I. No activity in ~2 yrs on the 2nd option…

If Discourse allows like 6-8 levels of Forum/Topic hierarchy, that should do it.

Thinking through things, here are some points before heading in a new direction/duplication:

The current wiki does work, is easy to edit and can suit all needs well but It’s major problems are:

  • Discourse doesn’t read the Wiki page name into the forum, it reads Github’s title for the project section, which isn’t providing an accurate summary of any linked page or subsection of a page. Forum links to the wiki don’t make it easy to get to and fro between discussion and (possible) solution (or contribution).

  • Github Wiki is keyed to the code project titles, this doesn’t provide adequate direct compartmentalization for CNC and Maslow related topics (ex: is G-Code Output intrepretation ‘Firmware’ or ‘GroundControl’, what about Frames? Mechanics?)

  • The Github Wiki has fallen well behind the Forums in current development and best available information (especially bits and materials imho) It will typically always be somewhere behind the forums, but currently needs some attention to bring it up to a more current ‘collective awareness’ of problems and solutions.

  • Contributors need to be Github users. This is probably a good filter preventing casual wiki additions, and (I’m not volunteering, mind you) assigning some moderators to comb through the forums and add Wiki content regularly would work well to keep things up to speed.

if we could solve the Discourse-page summary situation we’d probably not need to do more than what already needs doing: updating the wiki to the current state of affairs (inc kit changes, board revisions, etc.)

2 Likes

on the one hand, a unified wiki would be good, on the other hand, using a wiki
tied closely with the code/repo content is also useful.

I think that what we may really want is a wiki somewhere (possibly in github,
possibly not), that is used for the completed machine and everything related to
it, and that will let us leave the existing wikis to be tied closely with the
specific components (so that if/when we change components, say the new motor
controller board design), we don’t end up dragging a lot of old stuff in with
the new stuff.

1 Like

If Discourse allows like 6-8 levels of Forum/Topic hierarchy, that should do it.

I don’t like forums replacing the wiki, things age out too fast in forums and
it’s too hard to hunt for old data.

Thinking through things, here are some points before heading in a new direction/duplication:

The current wiki does work, is easy to edit and can suit all needs well but It’s major problems are:

  • Discourse doesn’t read the Wiki page name into the forum, it reads Github’s
    title for the project section, which isn’t providing an accurate summary of
    any linked page or subsection of a page. Forum links to the wiki don’t make it
    easy to get to and fro between discussion and (possible) solution (or
    contribution).

fair, but is this a problem with discource or the wiki?

  • Github Wiki is keyed to the code project titles, this doesn’t provide
    adequate direct compartmentalization for CNC and Maslow related topics (ex: is
    G-Code Output intrepretation ‘Firmware’ or ‘GroundControl’, what about Frames?
    Mechanics?)

This is the biggest problem IMHO with the wikis tied to the different
repositories

  • The Github Wiki has fallen well behind the Forums in current development and
    best available information (especially bits and materials imho) It will
    typically always be somewhere behind the forums, but currently needs some
    attention to bring it up to a more current ‘collective awareness’ of problems
    and solutions.

this is not a technology thing, but a community culture thing. We need to tie
the wiki in to the community flow so that it’s easy to update and have
discussions about it.

  • Contributors need to be Github users. This is probably a good filter
    preventing casual wiki additions, and (I’m not volunteering, mind you)
    assigning some moderators to comb through the forums and add Wiki content
    regularly would work well to keep things up to speed.

again, not a technology problem, whatever system we use will require people to
have accounts for it, and there is always a problem with getting things from
forums, mailing lists into the wiki

<soapbox.

I think the ideal situation would be something sort of resembling the community
garden. A wiki page that can be edited, host images, etc and then one or more
linked forum threads referencing the pages (potentially a many <-> many mapping)
so that someone going to a page can see the discussions on the topic, and
someone stumbling onto a topic has a trivial way to get to the relevant pages
(and from there to other, similar discussion)

I don’t know if there is anything out there that does this well.

David Lang

I see the firmware, ground control, and sled are on the garden. Why not just add the frame and a trouble shooting guide there?

1 Like

That is a great idea! I’ll work on getting the frame posted, does someone else want to take on posting the trouble shooting guide?

What picture would we put for the trouble shooting guide?

there is a section in the wiki that shows pictures of bad cuts and what the
problem is.

the recent thread working on testing in the bottom corner produced several more
really good pictures.

Any progress on this?

The frames are posted in the garden now, but I have not had a chance to do a trouble shooting guide yet

1 Like