Unrecognized USB device when trying to connect Replicator 1 to pc

[Kennet McCoy]

Up until about a week ago, the usb port on my Rep 1 was working fine, but now, it just gives an error that a usb device has malfunctioned.

I have ran multiple malware, spyware, antivirus apps - no change.

Tried it on 2 windows 8 boxes, and 2 xp boxes.

I'm relatively certain that the port on the printer's board is faulty, but I would like to rule out everything.

Any suggestions?

Thanks

Kennet

[Eighty]

Have you tried a different cable?

[Kennet McCoy]

I have swapped out a couple of cables, but I guess it's possible I might have a couple of bum cables, I'll try a few more and see if anything else helps. Thanks

[Dan Newman]

On 8 Sep 2013 , at 2:11 PM, Kennet McCoy wrote:

> I have swapped out a couple of cables, but I guess it's possible I might
> have a couple of bum cables, I'll try a few more and see if anything else
> helps. Thanks

How have you determined that the bot isn't presenting itself as a USB device?
Because MakerWare cannot connect to it or because when you use a windows
device manager it doesn't show you the device on the USB device tree? The former
doesn't mean the printer's USB is broken; the latter would strongly suggest
it.

Dan

[Kennet McCoy]

It only is showing as Unknown Device. Windows recognizes a new USB device, tells me the device is ready, but then immediately displays an error that the USB device has malfunctioned

[Dan Newman]

On 8 Sep 2013 , at 2:23 PM, Kennet McCoy wrote:

> It only is showing as Unknown Device. Windows recognizes a new USB device,
> tells me the device is ready, but then immediately displays an error that
> the USB device has malfunctioned

A number of things can cause that,

1. The USB device is trying to draw too much power over USB. Not Good. I don't
know what sort of error Windows gives when that happens. Mac's give you an
explicit error indicating that that was the case.

2. USB enumeration is failing. Could be a bad connection, a bad cable,
or the USB chip on the MightyBoard failing.

If you've ruled out the bad connection (try different ports. try through
a USB hub if you have one. Cut the USB port out if you are using one.)
And if you've ruled out a bad cable, then you probably need to contact MBI
support.

Dan

[Eighty]

I've had the same problem with other USB devices when the connectors are dirty or not making good contacts. Since he problem exists on multiple computers, it could be a flaky pin on the bot. Have you taken a peek at the USB port to rule out a dirty port?

[Kennet McCoy]

Great suggestions, I'll try this.

Thanks

[Kennet McCoy]

I had not even thought about the physical connection on the bot in that regard, you guys have given me some great options to explore. 

The printer itself is working great with the exception of the port. Thank God for the SD card slot

Thanks 

[Kennet McCoy]

This appears to be pointing toward the printer's M-Board. Tried multiple cables on multiple ports. Same results each time. 

Windows recognizes a device has been added via USB, Indicates that it loads the drivers, but then states it's an Unknown Device, then the error with a Malfunctioning device.

I have a ticket in with Makerbot.

Thanks for your suggestions.

On Sunday, September 8, 2013 4:27:48 PM UTC-4, Kennet McCoy wrote:

[Kennet McCoy]

Port appears to be fine, no damage on the port, no dirt.

No go.

On Sunday, September 8, 2013 4:27:48 PM UTC-4, Kennet McCoy wrote:

[Sean Trowbridge]

I am seeing the same problem, starting just this week.  

The device manager reports"Device Descriptor Request Failed", with some event details:

Device USB\VID_0000&PID_0002\7&2ea512f2&0&2 was configured.

Driver Name: usb.inf

Class Guid: {36FC9E60-C465-11CF-8056-444553540000}

Driver Date: 06/21/2006

Driver Version: 6.3.9600.16384

Driver Provider: Microsoft

Driver Section: BADDEVICE.Dev.NT

Driver Rank: 0xFF0000

Matching Device Id: USB\DEVICE_DESCRIPTOR_FAILURE

Outranked Drivers: usb.inf:USB\DEVICE_DESCRIPTOR_FAILURE:00FF2000

Device Updated: false

Did you ever resolve this?  I also opened a ticket with Makerbot but they have been unresponsive.

Sean

[Kennet63]

--
You received this message because you are subscribed to a topic in the Google Groups "MakerBot Operators" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/makerbot/I1K8nbYTUuQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to makerbot+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hey Sean

Yeah, I ended up having to replace the mighty board, sucks only because past warranty - not cheap , I think about 360 dollars to replace.

I tested the unit on multiple pc's / variety of OS's - even on a machine that had never been connected to the replicator. That was the final bit I needed for confirmation.

One thing I did not think about until after I got it replaced though...
If one of the Botsteps controls the usb function, it could be a lot cheaper to replace.

Ken