Strange that this is working. You will need to set an address for each board, so your monome trellis code looks right, though I didn’t look at the board jumpers.
I had a problem with my 128, perhaps yours is the same - nothing was happening after I updated the code and uploaded it. I had made the basic test using two soldered boards, and it worked, so I changed the monome code to just reference my top row of boards. That worked, so I updated the code to refer to a single board (4x4 LEDs) and tested each board in the bottom row. One of them failed, in spite of the address being set correctly for the jumpers. So I tried a different jumper configuration for that board and that solved it. My jumper contacts were definitely good, so I think there must have been an error in the board itself.

TLDR: check each board individually and if it fails try a different jumper configuration.

No, I’m a member of a local makerspace with a laser cutter. If you have one near you I recommend it. You get a bit closer to the process and you can prototype and iterate.

1 Like

@Lemmy (cool name btw, anything to do with Mr. Killmister?!)

I tried the sessaw library, both with the single 4x4 led arrangement and with the mutlitrellis setup. Both work fine :frowning:

Im trying to find a solution with @okyeron who as always is being super helpful!

Sadly my local space has no laser cutter. Costs to get it done locally are about the same as buying the real grid!

@thopa So you plugged the cable into each board in turn and tested each one successfully with the seesaw code? That should rule out the problem I had. I’m sure you will get it sorted out with @okyeron’s help.

P.S. Motörhead not really my thing, but I was always fond of ‘Killed by Death’ as a lyric :wink:

That’s a pity. Have you looked at options like Ponoko?

Yeah i did, and they all worked good.
I also tried with the home pax patch and some of the monome max devices, all working.

Ps: Im not massive fan, but got lots of respect for Lemmy, he was a unique individual!

cheers

1 Like

I’m sooo confused… Wikipedia says this, verbatim, about the USB 3.0 electrical characteristics (USB 2.0 is lower):

Max. current 900 mA

How does that even make sense? The minimum current draw for a NeoPixel-based 128, according to Adafruit, should be

128 NeoPixels × 20 mA ÷ 1,000 ≈ 2.5 Amps minimum

That’s 2.5 amps

From the adafruit link…

gross rule of thumb

What’s confusing? The leds eat power.

Like how does it even work properly with 500-750mA? Lots of mucking around with brightness or fudging gamma values

Also: magic :laughing:

This, but asked and answered :stuck_out_tongue:

1 Like

So I started on a thing yesterday which might come in handy for testing neo-grids.

A Grid Test script for norns.

Preview here if you wanna check it out (i.e. test it for me) New version down below

5 Likes

Probably an RTFM, but does Norns communicate with a connected Grid via MIDI messages, or using proprietary commands?

1 Like

It speaks a serial protocol, which is defined here.

2 Likes

Ah, OK. I wonder if it would be possible to make a firmware for the Teensy that would respond to both MIDI and Monome serial commands. Maybe it would need to be switched from one mode to the other…

What is your goal? I’m sure you could write an alternate implementation of the Grid class that behaves identical towards the script, but communicates with midi to the outside. I don’t know how you’d plug that into the existing source code, since I don’t know much about lua, but it should be simple enough in principle.

But why? Do you have a gridlike thing that talks midi that you want to use instead of a grid?

I have non-Monome stuff (I know, weird… :wink: ) that I’d potentially like to use with a DIY grid controller.

Usually your end device is going to determine what protocol you can use.

Unless you’re specifically needing a DIY grid to talk to Max/MSP or norns, then you don’t really need monome serial compatibility at all. Just use midi (or OSC or ?)

There’s piles of examples or projects with code available using midi.

FWIW - it’s super easy to just reflash separate firmware for different uses.

2 Likes

Nice!
Issues (fates 200129; neotrellinome/custom firmware[1]/Teensy 4):

  • keypresses don’t register
  • K1 only ever flips to the main menu

[1] Mostly to do with color/gamma; currently e.g. loom, meadowphysics, awake all work as expected, so…

That’s true. My (vague) plan was to try and roll both forms of communication into the same firmware, and have some kind of hold-a-pad-at-startup thing to swap between MIDI and Serial.

I was planning to use it with my new DIY Norns, but then I thought “why not make it talk MIDI, too”.