Mk debugging

Justmat · 2020-08-16T13:51:10.216Z

Just change the last number in the g:led calls to 15 or 0. It looks like you also changed some additional numbers in the calls.

for instance:
g:led(one.pos, 1, 3)
becomes…
g:led(one.pos, 1, 15)

The first and second arguments are for x/y coordinates, and should remain the same. (i edited my post above to express this more clearly.)

Scrubber · 2020-08-16T14:19:40.262Z

done this as suggested:
function gridredraw()
local grid_h = g.rows
g:all(0)
if edit_ch == 1 or grid_h == 16 then
for x = 1, 16 do
if one.data[x] > 0 then g:led(x, 9-one.data[x], 15) end
end
if one.pos > 0 and one.data[one.pos] > 0 then
g:led(one.pos, 9-one.data[one.pos], 0)
else
g:led(one.pos, 1, 15)
end
end
if edit_ch == 2 or grid_h == 16 then
local y_offset = 0
if grid_h == 16 then y_offset = 8 end
for x = 1, 16 do
if two.data[x] > 0 then g:led(x, 9-two.data[x] + y_offset, 15) end
end
if two.pos > 0 and two.data[two.pos] > 0 then
g:led(two.pos, 9-two.data[two.pos] + y_offset, 0)
else
g:led(two.pos, 1 + y_offset, 15)
end
end
g:refresh()
end

still nothing , no LEDs lighting up at all???
cant win
ive put the g:led messages in bold for ease on the post

Scrubber · 2020-08-16T14:43:38.447Z

something wrong here?
none of these 64 patches work at all?? tried the MLR and Otis ect
the button presses work but never any LED???

Justmat · 2020-08-16T14:48:07.080Z

Are you certain that your grid leds are functional?

Oootini · 2020-08-16T14:58:36.114Z

Maybe an issue with the mk board and Norns? Can you try one of the norns test scripts to ensure you can light the board? Ie make sure Norns itself can light the board, not just test patches on a laptop.

Scrubber · 2020-08-16T15:00:14.507Z

just done this! no LED’s on the tutorial scripts at all
my LED’s defo work in general
i can get 1 LED to light up on the MLR patch somehow?? weird, i can also get all the LED’s to light up on the Grid test patch pressing K3 (start) but then they wont go off ever, the button presses respond tho everytime as can see the square light up on the Norns screen???
Also the leds do the startup flash when plugged in
not sure what to do now

Scrubber · 2020-08-19T19:31:11.743Z

Hey
I’ve been using Norns with my Grid (64 mk version) and all button presses work and register with the apps but no matter what I try I cannot get the LEDs to respond even using the script tutorials and editing the scripts to work with 64 grid?? Out ideas now
The grid does have a ISP/AVR programming header (and I do have an Olimex programmer) should i update the firmware released a while back to fix it
http://archive.monome.org/community/discussion/18015/mk-firmware-update/p1.html
Or is this an issue with MK boards and Norns???

Oootini · 2020-08-19T22:47:17.742Z

Update to that firmware. This sounds about right:

mk update for varibright message translation. … mk does not support actual varibright. levels are translated to on/off at the mid-threshold level.

Scrubber · 2020-08-20T08:53:54.176Z

Can anyone remember how to flash using AVR dude? I have the cross pack installed but the wiki is old and doesn’t show up anymore from the archive monome site
Just so I dont have to solder headers onto the board as they aren’t on cos I’m sure you can do it via USB using the ttyserial type thing
Or failing that what’s the pinout for the mk board header?
Thanks
Sorry to be a pain

Scrubber · 2020-08-20T14:46:26.929Z

can’t get onto this anymore: http://docs.monome.org/doku.php?id=tech:mk:flash

tehn · 2020-08-20T16:12:31.928Z

moved this to a new thread as it went way off topic.

here’s the info you want:

GitHub

monome/mk

monome kit. Contribute to monome/mk development by creating an account on GitHub.

github.com

monome/mk/blob/master/firmware/default/Makefile

CC=avr-gcc
CFLAGS=-g -Os -Wall -mcall-prologues -mmcu=atmega325
ALL_CFLAGS = -mmcu=atmega325 -I. $(CFLAGS)
LDFLAGS = -Wl,-Map=$(TARGET).map,--cref	
OBJ2HEX=avr-objcopy 


#### enter your serial number below
#### for windows users, enter com port, for example SERIAL = COM4

SERIAL = /dev/tty.usbserial-m0000109




####### Files:

SOURCES       = mk.c \
				button.c

This file has been truncated. show original

try archive.org to get that dokuwiki page from 2013 or so

Scrubber · 2020-08-20T18:52:28.590Z

Thanks for this! Much appreciated!

Scrubber · 2020-08-22T11:25:54.411Z

This did indeed fix my issue! Works perfect with norns even without editing patches now
I also had a clash of the older ftdi driver running alongside serialosc which has now been deleted

Shimoda · 2020-09-05T17:18:01.832Z

Currently trying to flash the firmware that had varibright fixes (from 6 years ago) onto my mk128. Can’t get atmel studio and my avr-isp mkii programmer to see the device. Stopped serialosc service. Used this same programmer, back around 2011 or 2012 to flash the device before. Would there be new win 10 services keeping me from having the mk board seen? Seem to remember that there used to be directions for using atmel studio, including fuse bits, but it’s been forever. Trying to use an mk128 and mk64 with my norns…(shield)

I do have a 2008 mac with something pre-catalina I can use if needed but no experience there.

Scrubber · 2020-09-05T18:47:21.963Z

Should be all good on win10 and atmel studio as that’s what I used
What version of Atmel studio you using?
You got correct pins on the board to the programmer? You powering via usb or via programmer?

Shimoda · 2020-09-05T19:07:17.631Z

atmel 7 I believe. Powering mk board via usb. Getting MOSI error saying the data line isn’t open or some such thing.

Shimoda · 2020-09-05T19:08:46.427Z

update2: success programming! Feedback with norns! Now to program the mk64

Scrubber · 2020-09-05T20:31:55.791Z

What was it? Out of interest or anyone else with similar problem
Too good when get feedback from Norns!

Shimoda · 2020-09-05T21:07:15.038Z

Well, not sure. I did pull the driver boards. I think serialosc was running one instance. Shutting it down and restarting everything seemed to work. Fingers crossed for my 64+8 (led fader encoders for sending midi ccs)

Ian_Lennox · 2024-10-07T05:44:17.110Z

Update: keypad sensitivity fixed

After some back and forth and a quick email to help@monome, I decided to glue little circles of aluminum foil to the pills. The results are (for now) fantastic! My research tells me it’s possible the foil won’t stay conductive for longer than a few months, but let’s see what happens and I’ll report back.

IMG_18151855×2021 399 KB

IMG_18282160×2196 440 KB

This is just dollar store aluminum foil, it was dirt cheap, and actually feels thinner than the name brand stuff at the grocery store which I think is a good thing for this.
I used a standard 6mm hole punch from Walmart ($3CAD) and a 10mm punch to cut around the holes to make the donut shape.
I used dollar store pva glue that came in a spray bottle, but I ended up spraying some onto a paper plate and dipping the foil pieces in before affixing to the pills. It seems to be holding up very well, and hopefully I made life easier in the future if I come back to this.

Original post :
As I illustrate in the video below, I’ve got the whole thing together but I noticed I had to push quite hard to get any response out of the buttons. I disassembled, cleaned with alcohol, sanded pads, washed them, put back together…if I just keep pressing the button over and over again it’s almost as if it starts to “wake up” and now I’ve got about 2 dozen buttons feeling close to “normal” using this technique…

2010 Monome Kit Action

Just wondering… am I missing something? Should I splurge on new pads? It’s also possible that my enclosure just wasn’t built with enough precision, which is why I bring up the alignment of pads vs pcb. Did I screw up?