Toolhead not found, can't flash

54 views
Skip to first unread message

DogWood

unread,
Apr 24, 2012, 11:55:02 PM4/24/12
to MakerBot Operators
My TOM has been working well, up until tonight when I turned it on to
print something, got the dreaded toolhead 0 not found.

Did some reading, decided to try and flash it again, no go fails right
off the bat.

I disconnected it from the motherboard and the power supply to flash
it.

Windows "sees" it and loads drivers to it's not completely dead

the debug led is constantly flashing very faintly

Ideas? suggestions? throw it out a window and scream profanities?

Thanks

DogWood

unread,
Apr 25, 2012, 12:09:49 AM4/25/12
to MakerBot Operators
Well I rebooted my PC and was able to re-flash the extruder
controller but still getting Toolhead 0 not found error

Mark Cohen

unread,
Apr 25, 2012, 12:10:09 AM4/25/12
to make...@googlegroups.com, MakerBot Operators
If it is not getting power from the power supply you would see the same error

Sent from my iPhone

> --
> You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
> To post to this group, send email to make...@googlegroups.com.
> To unsubscribe from this group, send email to makerbot+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/makerbot?hl=en.
>

Dan Newman

unread,
Apr 25, 2012, 12:14:54 AM4/25/12
to make...@googlegroups.com

On 24 Apr 2012 , at 9:10 PM, Mark Cohen wrote:

> If it is not getting power from the power supply you would see the same error

As per Mark: check that there's power on the Molex connector to the EC board.
Also, check the RS-485 cable between the Motherboard and EC board. If it's loose,
the Motherboard won't get a response when it queries for EC's and RepG will then
give that error. Since you disconnected it, you're half-way to checking the
cables: now just reconnect the power and RS-485.

Dan

Mark Cohen

unread,
Apr 25, 2012, 12:20:51 AM4/25/12
to make...@googlegroups.com, make...@googlegroups.com
One more thing. If you have it on a power y splitter then don't use that as they burn sometimes. Use that on a stepper.

Sent from my iPhone

DogWood

unread,
Apr 25, 2012, 7:44:55 PM4/25/12
to MakerBot Operators
It is on a splitter and with this supply there is no way around that.

I checked the power with a multimeter and I'm getting 11.9V and 5V on
the connector.

Tried to check the rs-485 cable but my meters probes are too fat.

Everything seems nicely connected but I keep getting the not found
error.

I can re-flash it so its obviously not dead, perhaps the rs485 cable
(unlikely) or the connector has gone bad.

I think I'll pull the board and check the solder joints.

open to any other ideas

Thanks for the help


> One more thing. If you have it on a power y splitter then don't use that as they burn sometimes. Use that on a stepper.
>
> Sent from my iPhone
>
> On Apr 25, 2012, at 12:14 AM, Dan Newman <dan.new...@mtbaldy.us> wrote:
>
>
>
>
>
>
>
>
>
> > On 24 Apr 2012 , at 9:10 PM, Mark Cohen wrote:
>
> >> If it is not getting power from the power supply you would see the same error
>
> > As per Mark: check that there's power on the Molex connector to the EC board.
> > Also, check the RS-485 cable between the Motherboard and EC board.  If it's loose,
> > the Motherboard won't get a response when it queries for EC's and RepG will then
> > give that error.  Since you disconnected it, you're half-way to checking the
> > cables: now just reconnect the power and RS-485.
>
> > Dan
>
> >> Sent from my iPhone
>
> >> On Apr 24, 2012, at 11:55 PM, DogWood <dogonw...@gmail.com> wrote:
>
> >>> My TOM has been working well, up until tonight when I turned it on to
> >>> print something, got the dreaded toolhead 0 not found.
>
> >>> Did some reading, decided to try and flash it again, no go fails right
> >>> off the bat.
>
> >>> I disconnected it from the motherboard and the power supply to flash
> >>> it.
>
> >>> Windows "sees" it and loads drivers to it's not completely dead
>
> >>> the debug led is constantly flashing very faintly
>
> >>> Ideas? suggestions?  throw it out a window and scream profanities?
>
> >>> Thanks
>
> >>> --
> >>> You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
> >>> To post to this group, send email to make...@googlegroups.com.
> >>> To unsubscribe from this group, send email to makerbot+u...@googlegroups.com.
> >>> For more options, visit this group athttp://groups.google.com/group/makerbot?hl=en.
>
> >> --
> >> You received this message because you are subscribed to the Google Groups "MakerBot Operators" group.
> >> To post to this group, send email to make...@googlegroups.com.
> >> To unsubscribe from this group, send email to makerbot+u...@googlegroups.com.
> >> For more options, visit this group athttp://groups.google.com/group/makerbot?hl=en.

DogWood

unread,
Apr 25, 2012, 8:14:52 PM4/25/12
to MakerBot Operators
Solder joints all look good, hit the connector joints anyway.

If I don't plug anything into it other than power and the rs485 the
error light stays on, If I plug in the thermocouple it blinks
continually, but very faintly.

Mark Cohen

unread,
Apr 25, 2012, 8:34:02 PM4/25/12
to make...@googlegroups.com, MakerBot Operators
So maybe it's the motherboard. I had one like that.
It could also be that the reset trace on the motherboard isn't cut. That did strange things like that. Usually a big pause when recognizing the motherboard.

Sent from my iPhone

Mark Cohen

unread,
Apr 25, 2012, 8:34:50 PM4/25/12
to Mark Cohen, make...@googlegroups.com
Reset trace on the arduino actually.

Sent from my iPhone

Mark Cohen

unread,
Apr 25, 2012, 8:40:23 PM4/25/12
to Mark Cohen, make...@googlegroups.com
Also could be issues with the comm chip on the motherboard or the jack. We used to get solder balls on the comm chip wires with gen3 boards.

Dan Newman

unread,
Apr 25, 2012, 9:51:30 PM4/25/12
to make...@googlegroups.com
> Tried to check the rs-485 cable but my meters probes are too fat.

You can use any ethernet cable to test with

> I think I'll pull the board and check the solder joints.

That's been a problem for many folks with the motherboard. It's possible
that there's a bad joint on the mb which is impacting comms with the ec.

Dan

Jetty

unread,
Apr 25, 2012, 11:10:39 PM4/25/12
to MakerBot Operators
Try the ethernet cable as Dan suggested. There are 2 RS485
transceivers, one on the EC and one on the motherboard and plastic
being pushed through the nozzle can build up ugly static voltages and
they are static sensitive.

However they're surface mount, but if you're happy with that, they are
cheap, can be tested first with an oscilloscope made out of a spare
arduino. Then ground your HBP and extruder assembly (I ran a wire to
the case of the PSU) to make sure it doesn't happen again.

It happened to me via the thermocouple, but there are likely a few
vectors for this one.

http://groups.google.com/group/makerbot/browse_thread/thread/8cdc7154a74ebf7f/faa76f7f9f4fa590?q=

It creates exactly the error you're seeing, however there are multiple
potential causes for that error too.

DogWood

unread,
Apr 26, 2012, 8:10:55 PM4/26/12
to MakerBot Operators
Thanks Guys,

Tried both ports on the MB. no-go, tried a new ethernet cable, both
ports, no-go

I will ground the extruder block and HBP.

whats the part # on the transceivers? I do have access to an
oscilloscope so I can take a look at the outputs.

-Doug

On Apr 25, 8:10 pm, Jetty <clelland...@gmail.com> wrote:
> Try the ethernet cable as Dan suggested.  There are 2 RS485
> transceivers, one on the EC and one on the motherboard and plastic
> being pushed through the nozzle can build up ugly static voltages and
> they are static sensitive.
>
> However they're surface mount, but if you're happy with that, they are
> cheap, can be tested first with an oscilloscope made out of a spare
> arduino.  Then ground your HBP and extruder assembly (I ran a wire to
> the case of the PSU) to make sure it doesn't happen again.
>
> It happened to me via the thermocouple, but there are likely a few
> vectors for this one.
>
> http://groups.google.com/group/makerbot/browse_thread/thread/8cdc7154...

DogWood

unread,
Apr 26, 2012, 8:12:49 PM4/26/12
to MakerBot Operators
Forgot to mention, I pulled the Arduino and the reset has been cut

Dan Newman

unread,
Apr 26, 2012, 8:33:33 PM4/26/12
to make...@googlegroups.com
See

http://www.thingiverse.com/thing:4969

The transceiver itself is a sn75176a. On the motherboard,
the part is routed to the following ATmega [Arduino] pins

[D19] PD2 (RXD1/INT2) R
[D30] PC7 (A15) !RE
[D32] PC5 (A13) DE
[D18] PD3 (TXD1/INT3) D

Those are from some old notes of mine.

Dan

DogWood

unread,
Apr 27, 2012, 8:01:33 PM4/27/12
to MakerBot Operators
Thank you. most helpful.

went ahead and ordered some transceivers since they are so cheap.

Hopefully I will be back in business by next weekend.

Thanks again for the help

-Doug
Reply all
Reply to author
Forward
0 new messages