Half way through a print, the print suddenly stopped.
I shut it all down and then reconnected but now when pluging in the usb plug i get this error
(Device descriptor requiest failed)
This has given me a horrible sinking feeling… I don’t have time for hardware failures, specially not before completing even my first print on a new machine.
The machine was build correctly… I have half a print to prove it was working correctly.
Any ideas?
tested on multiple computers…
same result… after spending almost 600 euros, and waiting a month for it to arrive… and this after just 90 minutes of use makes me feel sick.
after further investigation, it seems that most of the board is fully functional, however the fdti chip which provides the usb to uart serial interface has failed.
This leads me to conclude the only possible cause was a factory fault in that chip.
Which would mean that i could at worst order this chip or an external fdti developer module to get it all up and running… but in all reality I deserve a working board…
Who do i contact for a replacement?
arstechnica.com/information-tech … e-hackers/
looks like it’s the window drivers that brick the fdti chips
[quote=“ngrawlings”]http://arstechnica.com/information-technology/2014/10/windows-update-drivers-bricking-usb-serial-chips-beloved-of-hardware-hackers/
looks like it’s the window drivers that brick the fdti chips[/quote]
yes, i heard about that too.
There is also a vido on it on the EEVblog :
FIXED!!!
Ok so what had happened was not the pid reset problem but turns out the fdti chip I had on the board was part of a bad batch…
which made it impossible to correct via the software… I have the dmesg output which i will send a little later…
So what I did was remove the rxd and txd smd resisters and soldered a ftdi developer module using the flat cable provided to the pads of the removed resistors…
and just like that, every thing worked again!!!
Saves the time of getting it replaced