Shapeoko Repair Madness 2016

Survey the Field of Carnage

Death of the Shapeoko is just the beginning.

An important aspect of diagnosis is examination of the patient and the environment. In this case, a table was set aside in the hackerspace for the shapeoko. This table was meant for the "working" shapeoko and had little, if any room, for diagnostics and repair. When the shapeoko stop working, the table became the diagnostic and repair area. The following pictures show the state of the table after several attempts to diagnose and repair.

The tables was now unusable from a diagnostic and repair point of view. The next step is to clean up the area and select a suitable place to work. Rather than simply clearing off the table, I decided to remove items from the table until only the components of the shapeoko remained.

Tool Extraction

The tools below were all removed from the table. An important finding is that multiples of the same tool were found. This may indicate that multiples were needed at the same time but the tools in question and work to be performed do not support this. Instead, the multiple tools indicate multiple attempts to repair that were abandon, a single repair attempt were tools were recklessly left about or multiple repair actions in parallel. Regardless the reason, the abandoning of the tools on the table are signs of an incomplete and disorganized repair attempt. Hackerspaces can be chaotic, but a little organization when repairing equipment is of immeasurable value.

Here is how the table looks with tools removed. Evident in the photos is debris from the prior repair attempts or possible usage of the shapeoko before it stopped working.

Next step is to remove the debris.

Debris Removed

Below is a photo of the debris removed followed by a photo of the debris that can be used in the future by anyone. The majority of debris is wire clippings. This indicates that rewiring played heavily in the prior repair attempt. The different gauges and types of wire is common for hackerspace work. Tie-wrap pieces, wire insulation and simple trash make up most of the remaining debris. Cleaning the working space and especially the repair space can not be over emphasized. First thing to do when operating or repairing is clean up. When operating or repairing, periodic cleanups are important to ensure a smooth work flow.

What Remains is the Shapeoko

Inventorying The Assemblies

Below are photos of the shapeoko electronics as wired together and separated. From these assemblies a simple inventory of components will be made.

Assemblies are:

• Powerbrick for Steppers
• Stepper Controller Board (GSHIELD)
• Arduino UNO
• Power Supply for Spindle
• Relay Module
• Spindle Motor Controller
• Wiring Patch Board

And the Mechanical Beast

Cleaning Up at the Stopping Point

Time ran out at this point on the diagnosis and repair adventure. Keeping with the advice to cleanup, the shapeoko table and parts was secured until next time.

Preliminary List of Findings

Hardware

These are items directly observed on the shapeoko:

• Cables need to be labeled
• Cable routing and securing needs to be redone
• Limit switches need to be securely mounted and wired
• When wire ties are used, they need to be trimmed
• Missing insertion nut for securing device bed

These are some suggestions from users and experience:

• Cables need to be consistent gage and type
• Connectors need to be keyed (so they only fit together one way) and standardized
• Mount assemblies in enclosures to limit exposure
• Motor connections must "lock" together to prevent intermittent disconnect and connects from damaging controller circuits
• Install an "Emergency Stop" which is consistent with this type of device
• Cooling requirements tested and accommodated

The lists above are very telling. The lists above cover things that are applicable to the device even if it was in working condition. Whether in a hackerspace or not, these findings have practical survivability and safety value. Just because something works, does not mean it is safe to use or will survive a single use. If we intend to share the equipment, we need to offer protection to the user and ensure the machine works for the next user.

Finding Out Why It Doesn't Work

Items needing to be tested:

• Stepper Control board (GSHIELD)
• Stepper motors
• Power supplies
• Arduino UNO
• Spindle Controller

Things to be researched and documented:

• Connection diagram for the assemblies
• Determine heat sink and cooling fan needs for control boards
• Determine how control board interfaces with spindle (ON/OFF and Speed)
• Research connectors and cabling appropriate for this device type
• Research alternatives for table materials & mounting

Details and Findings

Missing Insertion Nut

The insertion nut is the rectangular piece. M5 thread, 10mm x 15mm x 1.5mm

This is a common type of hardware for the aluminum extrusion framing used. A replacement will be located and purchased.

= Stepper Controller board (GSHIELD)

The board was tested and the following was observed

• The D1 LED onboard blinked
• As the LED blinked, the power supply also blinked indicating a shorting condition
• A review of message boards indicate that the situation, when presented on a new board, requires return of board for replacement
• This condition on a previously working board indicates damaged board also needs replacing.

This board was replaced at least ounce before on the shapeoko. The prior incident and the latest incident were reported to occur after a shorting event. This means the problem is in the board being shorted and not the board itself. The previously mentioned need for enclosures would reduce the likelihood of additional shorts.

Information

Stepper motor specs

Note: Stepper motors are Smart Automation SM42HT47-1684B. Specs are on this page.

Rated voltage = 2.8 V

Rated current = 1.68 A

Rated resistance = 1.65 Ohms

Rated inductance = 2.8 mH

possible e-stop solution

Note: Here's a block diagram for adding an emergency stop that looks like it may be a reasonable solution:

Software

Note: This section will be expanded when hardware issues are fixed.

• Determine whether min/max limits are stored
• Determine optimum software versions and document all settings