Information Cleanup

21

Yes. This is important.

1 Like
22

Move stuff. I am still figuring out Github

1 Like
23

Are the physical part specs and printing files in the wiki repo? I see we have a section for firmware, a section for user docs but we need one for physical things and parts lists?

1 Like
24

wouldchuck wrote:

Are the physical part specs and printing files in the wiki repo? I see we
have a section for firmware, a section for user docs but we need one for
physical things and parts lists?

yes, we need a section in docs for things like parts list, and a place to either
put the cad files, or point at where to get the cad files (cad files can be
large, which can be a problem. Also, what do we do when we want to point at an
onshape or abundance part?)

David Lang

1 Like
25

Ok, new readme file made and committed as a rough draft. I need help with this section with dates and people and accuracy and a link to the old versions and old documents if possible.

Here is the section I need help with:
History (I don’t know a lot here)

In ??? (Barbour Smith and ?people?) designed the first Maslow as a wall mounted CNC routing robot that hung from two chains and pulled itself back and forth across a space. The robot at that point was designed around an ?arduino? microcontroller and was an open source design. Barbour set up the forums and github groups and sold ??? machines.

It is still possible to make a Maslow Version 1, 2, or 3 and many people have been happy with them as useful tools. Makermade was a company that sold version ?2? under the open source license that is not affiliated directly with Maslow’s developers.

The current version Maslow 4 was prototyped as 3D printed parts with standard hardware. It has four machine belts instead of two chains. The parts are not interchangeable with earlier versions. It uses a custom printed circuit board PCB built around an ESP microcontroller. The board also incorporates motor controllers.

It is still possible to 3D print your own parts and replacement parts. It is still possible to design and program your own generic ESP microcontroller and use off the shelf motor controllers. In ?2023? Barbour and ?? ran a successful Kickstarter campaign with which they used the proceeds to design and have injection molds made for injection molded parts and better compact custom PCBs. Injection molded parts are much stronger than most 3d printed parts. This is what you are buying when you buy a Maslow kit. The custom PCB, the custom wires, the motors and custom made hardware, nuts and bolts, and the injection molded plastics with fiberglass inclusions. 4.1 was the result of a second kickstarter campaign that upgraded the PCB, wire connectors, the nuts and bolts and other metal hardware as well as a better spool design.

Also this part:
Community members who have made significant contributions:

bar founder and primary developer Other people who made the first machine?

dlang ?Programming?

Ian_ab?Programming?

1 Like
26

Just me and the Maslow community

Arduino Mega 2560

Just me

1 Like
27

Making a document in the repo for a library of frames to pull pictures and descriptions from the forums.
@dlang I wanted to include a link to the frame calculator, what is the address for the best version? How long can belt extensions be?
Does anybody have a favorite frame design? or detail?

How much force does the maslow pull on the belts with?

1 Like
28

A while ago I tried to make a tool to see the effective area on a frame, using frame dimensions, belt length, max angles as input. If it’s of any help to somebody: https://maslowcnc.nl/frame. Disclaimer, it’s a little buggy on the mouse movements.

2 Likes
29

@geertdoornbos Cool. Thank you

1 Like
30

Maybe we should have a page for some simulators? I’ve got a couple too:

2 Likes
31

Cool. Will include them in the frame instructions and again maybe in troubleshooting.

1 Like
32

wouldchuck wrote:

@dlang I wanted to include a link to the frame calculator, what is the address for the best version? How long can belt extensions be?

https://lang.hm/maslow/maslow4_frame.html

I also have it up in github and it’s all one self-contained file, so it would be
easy to have it anywhere

no limit on belt extensions.

David Lang

2 Likes
33

Thank you.

I have accidentally made a new patch branch in my github branch. How does one delete or trash a bad patch or pull request that you yourself has made?

Also is there a spreadsheet that lives inside GitHub like markdown does for text? I would like to make a library of router speeds and cut settings that seems like a spreadsheet would be better than a MD file

34

wouldchuck wrote:

I have accidentally made a new patch branch in my github branch. How does one
delete or trash a bad patch or pull request that you yourself has made?

look at git reset

if you have not done a commit yet, git reset HEAD ir gut reset --hard HEAD

if you want to eliminate the top commit, git reset --hard HEAD^

if you need to go back to an earlier commit git reset --hard

and if you get messed up, look at git reflogs to see your history and you can
reset to any of those points.

David Lang

35

Thank you @dlang I will try.

Also is there a spreadsheet format that lives inside GitHub like markdown does for text? I want to make a library of router settings.

36

wouldchuck wrote:

Also is there a spreadsheet format that lives inside GitHub like markdown does
for text? I want to make a library of router settings.

No.

you can do a table in markdown, or a csv file that is parsed by a javascript
page to display.

David Lang

1 Like
37

@bar a few questions about the repo as an archive

  1. How much is data space an issue? Photos, CAD files STL ? How much do we want to collect directly?
  2. When I make a MD file and drag a picture into it is the picture stored in the MD file or in a repo library or do we need to ask the AI to collate them all in an accessible repo folder? We could do this once we have a solid set of documents. I have not figured out the AI yet
  3. I.see your repos for the PCB and Maslow build. Do we plan for those to be incorporated in the Maslow4 repo or do we just link to them?
  4. When collecting things together from the forums to document projects frames and designs in files in the repo is it polite to use the pictures and info in the forums to build things with attribution? I can comment on the threads that I pull things from and give credit but I am wary of grabbing. .Are the forums contributions labeled in the structure as a creative commons license?
  5. We should add a creative commons license to the repo readme.
  6. How durable and stable are the forums? Do we link to things there or copy information to the repo?
38

I think that the best way to do it is probably as a table in markdown. Basically you just need to use | to divide the columns. Checkout this markdown cheat sheet: Markdown Cheatsheet · adam-p/markdown-here Wiki · GitHub

Its not a big issue. I wouldn’t worry about it unless we want to add something really big like video files

You probably want to put them in a folder in the repo. Markdown files just have links to pictures which are hosted somewhere else, so if you drag an image into a markdown file it will link to that file wherever it was dragged from. If that source goes away for some reason the picture will stop showing up, so the safest thing to do is put the images in the repo directly like this: Maslow_4/docs/assembling-the-sled-4-1/images at Maslow-Main · MaslowCNC/Maslow_4 · GitHub

I’m thinking that we want to put everything in the same repo. Having everything in one spot feels like the simplest and cleanest option.

I think it’s generally good polocy to ask folks before posting it. I think that most people will be fine with it, but it’s always nice to give people credit. At the very least we should credit the original poster

I think that sounds good to me!

They’re quite stable, they shouldn’t go anywhere. They can be hard to search tho so linking to things in the forums is a good way to make sure that they don’t get lost

1 Like
39

Which creative commons license do you want to use? It may depend on how fluidnc is licensed. It looks like they use GNU version 3. We should probably just copy that as we are using their code.

It goes in the custom properties section of the repo I think @bar has the access to change that.

1 Like
40

Bar wrote:

Its not a big issue. I wouldn’t worry about it unless we want to add something really big like video files

git has a limit of 4g for a repo (32 bit addressing), so if we are going to
store CAD files and images in the repo, we should look at Large File Support
(LFS) which stores the large files elsewhere and points at them from the repo.

I know github supports this, we will have to look into the details.

David Lang

2 Likes