The instructions are not adequate. They are lacking in certain areas.
In some areas, they are total crap, and I want the makers of ShapeOko to do better.
I agree with several of the previous posters; you need a combination of instructions.
a) for every step, you need a set of photographs of that completed step, with satisfying text describing what you did, and where you are in the process.
b) for every major piece completed, (mounting plates, z-axis, gantry, and so on...) a photo array of all perspectives, with accurate text accompaniment.
c) as build progresses, a video that shows completed parts, in relation to each other, with any movement (wheels, pulleys, ) described and displayed in motion.
````````````````````````````````````````````````````````````````````````
Postby cvoinescu » Wed Jul 16, 2014 2:58 am
One man's excessive detail is another man's "I wish they said more about this".

It's hard (and relatively unrewarding) to write good documentation.
I think Will is doing an outstanding job (although he does err on the side of excessive detail sometimes).
```````````````````````````````````````````````````````````````````````````````````````````````````
It is not hard to write good documentation; It is a duty to reward your customers for buying the product.
Can you imagine potential customers reading a really well put together manual? nothing like a sales device....
It is not unrewarding; it rewards the company by displaying what quality of docs can mean to the competition. Shows a good example.
I looked for 4+ months a dozens of websites and a lot models. I decided on ShapeOko 2. A fine manual will sell more.
I have read several thousand posts on the assembly and quality of ShapeOko.
I have attempted to follow the current 'instructions' for assembling the device.
The videos which are linked to from the ShapeOko site are not true company videos. I cannot build a machine from what is available.
The closest to quality of any kind are the set from Winston Moy. ( I commend them, I learned a lot; but they are not enough)
I was drafted in 1971, so I joined the Air Force 1971 - 1974.
I have been building computers since 1985. I have worked on workstations, servers (of many flavors), dialers, various network devices, PLC's, to name a few.
I have worked for Department of Defense ( as a civilian) at BAE Systems and Lockheed Martin contractor sites.
So this is not my first rodeo.