> For the complete documentation index, see [llms.txt](https://ms-kb.msd.unimelb.edu.au/msdmaker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ms-kb.msd.unimelb.edu.au/msdmaker/msd-model-making-space/hot-wire-foam-cutter/troubleshooting.md).

# Troubleshooting

## It's not turning on!

### Make sure the power is ON

Make sure the power is on (button located on the left side of the machine). A light will turn on if the cutter is running.

Step on the pedal and take a spare piece of foam to check the wire is in operation. The wire cutter will not operate unless the pedal is being stepped on.

Never touch the wire with your hands unless you are 100% sure the machine is OFF.

### Ensure cables are connected

Check the power cables.&#x20;

A power cable should be plugged into the inner left leg of the wire cutter, and both wire cutter and pedal must be plugged into power points located underneath the work benches.

If the problem persists, notify a FabLab staff member.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ms-kb.msd.unimelb.edu.au/msdmaker/msd-model-making-space/hot-wire-foam-cutter/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
