Skip to main content

Site Navigation

Your Account

Choose Language

Anyone having Interface 2.0.1 Errors

I’ve never seen this before but it seems like there was a software update that started causing problems last time I tried to use boxzy to 3d print. That was a while back and I walked away from it till now.

What I have happening is in the lines of “code” at the bottom of the interface I see a line that says

“extruder 0:temp sensor defect

Error: Printer set into dry run mode until restart!”

It’s extremely frustrating. I was trying to work out a clog heating the extruder with a mini torch with the heater on and it goes into this. Then the heater turns off, and the extruder won’t work so I have to disconnect and reconnect and then it works again.

I moved away from the 3d print and onto the laser. Now I’m getting more errors.

“Error:expected line 533 got 536

Warning: Seems like we missed a ok, got a wait - continue sending

Resend 533

Error Format error”


Something is screwball, I’ve never had problems with the software before.

Are there any known issues with this and how can I go about fixing them? Ideas? I’m redownloading the interface software and will reinstall I guess??

Answered! View the answer I have this problem too

Is this a good question?

Score 0
Add a comment

1 Answer

Chosen Solution

Hi Walt,

The first issue you describe is an intentional design feature. If the print head is significantly hotter, or colder, than the target temperature after a certain period of time, the machine will disable the print head to avoid a fire hazard. The machine believes it is not getting accurate data from the sensor.

The second issue can happen for many reasons. It will likely happen a few times over any file. Basically sometimes it takes the machine longer to execute a line of code than expected, and so the commands get ahead of the real world progress and the buffer fills up. So the interface has to resend the commands. If it is bad enough to have a real world affect on your lasering work, than you have a communication delay likely caused by a bad USB cable, too long of ISB cable, or weak/loose connection.

Was this answer helpful?

Score 1


Sounds like it's working as designed for the first issue.

For the second issue boxzy just stops during the error period, if it were buffer full wouldn't it run until it could take some more commands? I've used the lazer more than anything on this and never had this problem before. The only thing that has changed is the software. Odd.


Loose connection at the laser head is what I think was causing it. I reached in while it was just sitting there and pushed the connector in and it took off running. It's been running nonstop for about 10 minutes without a hick up. I can tell that this is much better already.


Add a comment

Add your answer

Walt will be eternally grateful.
View Statistics:

Past 24 Hours: 0

Past 7 Days: 0

Past 30 Days: 1

All Time: 11