posted by kevin (kevin)
on 04.09.2007 00:58
i'm not really sure what's going on here..

i was running mlr doing some stuff and then i try to turn the level of
group 3 down with the shift buttons and i look at the screen and nothing
happens, then i look down at my 40h and get this:

http://www.vimeo.com/296519

i took the 40h apart on saturday to use the keypads to test that my
logic kit was functional, so maybe a connector came loose or something.

any ideas?
posted by tonedeft (tonedeft)
on 04.09.2007 01:10
it's not the FTDI USB board, it'd reboot with the startup pattern

it's not the microcontroller because I think you'd get the bootup 
pattern

it could be the LED driver, the maxim 7221 chip, look for loose/cracked 
solder joints or just go back and touch them up with more solder or just 
re-heat the solder joints.

are button presses ignored?

it  might also be the 74hc165 or 74hc164, I don't recall which is which.

I don't think this is a catastrophic fault, it can be fixed.
posted by tehn (tehn)
on 04.09.2007 01:25
that looks like test mode going on/off, which indicates some sort of 
static on the spi line potentially.

your atmel chip might be zapped, reprogramming it would fix the problem.

if you don't have any ideas after debugging for awhile, e-mail me and 
we'll set up shipping for a quick repair.
posted by kevin (kevin)
on 04.09.2007 04:39
it worked fine when i plugged it back in.

opened up a little mlr session and it's not spazzing like it was before, 
but the lights are frozen. button presses are still working fine.

now i'm going to open it up and see if anything is loose.


--


everything looks ok. 64step works with no immediate glitches.


i have been using the version of mlr that i hacked to support 16 step 
resolution across 2 rows, so maybe it's something in that.. checking the 
regular mlr now.



----

regular mlr seems to be working fine
posted by kevin (kevin)
on 06.09.2007 08:50
ok, so it looks like it isn't the software. i was running mlr tonight 
and all of the lights turned on.

presses still registered, but i had to restart monome serial.

i'm not really sure what's going on. maybe something with the cable?
posted by tehn (tehn)
on 07.09.2007 01:52
if the keypads still work, it's something with the maxim chip. keep me 
posted and if you find something consistent i'd be happy to repair it.

when it went into test mode, did monomeserial lose connection?
posted by kevin (kevin)
on 07.09.2007 02:06
> when it went into test mode, did monomeserial lose connection?

i don't think so. button presses were still working and i didn't get a 
"USB Unplug Notice" or whatever. I'm going to be using it this weekend 
at a noise festival in seattle, so my fingers are crossed. i'll check it 
with the good ol' multimeter when i get back.

is it possible that i zapped the chip by powering the device on with the 
connector shifted up? (i.e. bottom row of pins disconnected, bottom row 
of connector connected to the top row of pins, top row of connector 
loose)

cause i did accidentally do that when i put it back together. =X
posted by tehn (tehn)
on 07.09.2007 21:27
everything is possible in terms of damage, though these things are 
pretty resistant.

hope your show goes well. just remember monomeserial supports 
hotswapping, and saves your settings... so your re-boot should be quick.
posted by kid-sputnik (kid-sputnik)
on 08.09.2007 03:41
on windows, make sure you are using the newest monome serial for 
hotswapping, its not on the wiki, but in a thread in "applications" 
(wiki was not uploading at the time).  make sure you test out on your 
system, of course, it should be fine but id hate it if i somehow screwed 
up you show!