posted by rawray7 (rawray7)
on 18.08.2007 05:22
my kit has been working consistently for weeks, and now all of a sudden
my monome serial refuses to recognize it.  i reinstalled the ftdi
driver, and no luck.  when i plug my monome in, it lights up a couple of
lights (noise) - like it used to when it was functioning.  i've tried it
in multiple usb ports on my computer, and tried multiple restarts.
sometimes i can get a couple of lights to turn (noise) on by
unplugging/plugging the ribbon pins. the hardware does not seem damaged
in any way.  help?
posted by tehn (tehn)
on 18.08.2007 13:42
i take it this is a kit?

do the lights fade out? is it the normal startup pattern?

fade out means the device has been detected correctly.

what do you mean by (noise)?

do you have access to another computer to test on?

is this os x or xp?
posted by rawray7 (rawray7)
on 18.08.2007 23:18
so my kit works again - although this bug is still kind of a mystery to 
me.  it fixed when i switched USB cables, which is weird because the USB 
cable that didn't work for the 40h kit works just fine with other 
equipment - maybe it has an issue carrying the right charge to power the 
40h.

i'm running osx, maybe what i'm calling noise is the normal startup 
pattern.  the lights i see do fade out properly, even when it wasn't 
detecting the device.  what does the normal startup pattern look like?

thanks for responding so quickly tehn, i was getting nervous as i'm 
performing with my kit tonight.  soon i will post pictures of my <$10 
enclosure for all those 40h bargain shoppers.
posted by kid-sputnik (kid-sputnik)
on 19.08.2007 11:33
ths startup pattern is a binary count 1-8
X - - - - - - -
- X - - - - - -
X X - - - - - -
- - X - - - - -
X - X - - - - -
- X X - - - - -
X X X - - - - -
- - - X - - - -
posted by longjohns (longjohns)
on 19.08.2007 16:44
heh,

I knew there must be some logic to it

;)