#546

Mine is working exactly as it should after a two line fix. Are you set up to compile the code if I show you how to fix it? (Requires hacking the TinyUSB library in a slightly tricky way that I’m not sure I can explain.) If so then DM me and I’ll show you the fix; if not then better wait for @okyeron to check everything out and produce an amended firmware.

#547

Thanks for your reply @hollasynth !
Unfortunately i just uploaded the latest neotrellis monome code to my 8*8 and nothing is working.
The start up led doesn’t either.
Im having trouble uploading the sketch to the grid. I know the grid is working good because i am using some of the neotrellis examples and they work ok…
Im up for compiling for sure! I have the teensy version :slight_smile:
Cheers!

Edit:
I compiled fine after a computer reset, no errors on arduino log, but when i plu my grid now to the computer it doesnt do anything…neither the start up flash light.

Do i need to make some modifications to the code like when it says

#define NUM_ROWS 8 // DIM_Y number of rows of keys down
#define NUM_COLS 16 // DIM_X number of columns of keys across

Edited 2: If i change columns to 8 i do get an error compiling:

neotrellis_monome_teensy:62: error: too many initializers for ‘Adafruit_NeoTrellis [2]’
too many initializers for ‘Adafruit_NeoTrellis [2]’

Edited 3: oh dear, i just saw the 88 settings in the ino file… i commented it out the 168 and made the 8*8 active, compiles well but no response from the grid :frowning:

Thanks

#548

Probably wrong addresses.

If you can find our previous messages When we were debugging that would probably help.

1 Like
#549

My adresses (tested) with the multitrellis are:

{ Adafruit_NeoTrellis(0x2E), Adafruit_NeoTrellis(0x2F) },

{ Adafruit_NeoTrellis(0x37), Adafruit_NeoTrellis(0x3F) }

Looking at the grid from the front:

Top left:0x2E Top Right:0x2F

Bottom left:0x37 Bottom Right:0x3F

Thanks!

Big shout to @okyeron and @hollasynth for helping me sorting it!

1 Like
#550

Tried out this new (to me) acrylic material for the neotrellis grid today:

(it’s a faux brushed aluminum surface)

It only comes in a 1/16inch thickness, so needed to do the layer stack a little different, but works out pretty close to what I had with the EVA layer.

5 Likes
#551

That’s one sexy look right there! Nice.

1 Like
#552

just bought the boards! as of now, what is the best option for cases? is anyone offering kits?

#553

I’ll have some acrylic case kits in a week or two. (waiting on my flexible pcb order to ship)

4 Likes
#554

Just built both grid and norns using ponoko and okyeron’s designs. I was able to get a theoretical 11mm internal layer using three 3mm and a clear 2mm, but there is still some wiggle room between the layers that might be caused by imprecise layer thickness:

IMG_20200729_190141
IMG_20200729_1901414608×3456 4.61 MB

IMG_20200729_190203
IMG_20200729_1902033456×4608 3.59 MB

IMG_20200729_190906
IMG_20200729_1909064608×3456 4.5 MB

5 Likes
#555

I finally finished my build of the diy grid, I’ve had so much fun with this, thanks a lot @okyeron, it’s a masterpiece design!

4t
4t1600×1200 186 KB

I now want to use the grid as a controller/sequencer for Pd and Orac and make some patches but I’ve had some issues with talking to it directly via serialosc on my Fates. Some people made it happen on this forum thread with an Organelle but they seemed to have used some original monome grids.
In my case (because of the teensy I think) it doesn’t want to automatically start an osc server for the device when I plug it in. It works when I start it manually using the command serialosc-device /dev/ttyACM0 which is already not bad but I would like to go to the bottom of this so that we can share patches afterwards without too many problems.

In the source code of serialosc-detector I found a detection condition that seems to rule out arduino based devices because their udev parents subsystem attribute seems to be “usb” and not “usb-serial” (see the the list of all the attributes of my device below).

(Arduino based grid udev attributes) 
$ udevadm info -a -n /dev/ttyACM0

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0/tty/ttyACM0':
    KERNEL=="ttyACM0"
    SUBSYSTEM=="tty"
    DRIVER==""

  looking at parent device '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1:1.0':
    KERNELS=="1-1.1:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="cdc_acm"
    ATTRS{authorized}=="1"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bInterfaceSubClass}=="02"
    ATTRS{bmCapabilities}=="6"
    ATTRS{bInterfaceClass}=="02"
    ATTRS{bNumEndpoints}=="01"
    ATTRS{bInterfaceProtocol}=="01"
    ATTRS{supports_autosuspend}=="1"

I don’t understand half of this and would be very thankfull for some help. I am trying to find out if the parent’s subsystem device attributes can be modified or if there is a better way to make serialosc detect the diy grids automatically. I know that there has been some discussions over this but regarding norns device detection, does someone know how these things relate ?

I have also been looking into the norns device monitor hack of @okyeron that makes the diy grids detectable by norns. It seems to handle the same kind of issues but it directly uses libudev. I don’t understand why norns doesn’t seem to use serialosc to communicate with grids and others :stuck_out_tongue: Too many questions

Ps: @Gerald_Stevens thanks for the nice colored version of the arduino firmware! I tried it out and the palette selection works but I’m getting no lights and interaction with norns afterwards… Do you have any tip on how I could try and find the bug? Maybe with the arduino serial monitor?

Pps: maybe some have seen it on the picture, I have soldered the teensy directly to the board and kept it out of the box for now. When trying to solder the flexi-pcb to the board I applied too much heat (I think) and one of the pads of the flexi-pcb fell off. I tried to glue it back but the current isn’t going through, does someone have any advice? Maybe I should scratch a bit of the hidden conductor cable and solder to this?

3 Likes
#556

Excuse me for asking. I’ve poked into this thread a few times to see folks building these NeoTrellis grids!
It’s a neat project as all the parts are from a source other than Monome!

What I’m curious about is:
How are folks building them with Adafruit having discontinued some of the NeoTrellis products?
Is there a guide for someone fresh wanting to put a complete 128 varibright neotrellis grid together?

I’ll continue to read the thread for tips n’ tricks. These are some things on the top of my mind.

Thanks!

#557

Norns uses libmonome and not serialosc.

DM me about the flexi - maybe with a picture - and I can offer suggestions

#558

Not sure what neotrellis products are discontinued, but they have the boards you need in stock. That and a teensy and the buttons is all you need.

1 Like
#559

Well I believe the molded button matrix is discontinued at this point.

#560

Oh. I see that kit comes with the silicone grid, too!

#561

Keypads:

#562

I’m new here. I tried to send a DM and it said I can’t send you a private message.

#563

Strange. Those test prints got taken a long time ago, though.

#564

Hello!

I just got my diy grid built, trying to get it to play nicely under linux. Not sure if I’m running into the same issues w/ norns (it’s almost 2am here, haven’t dug into any of the code yet :slight_smile:)

I get the nice little led lit up on the upper left corner, still see a teensy listed with lsusb

Bus 001 Device 023: ID 16c0:0483 Van Ooijen Technische Informatica Teensyduino Serial

serialosc-detector /dev/ttyACM0 just hangs, but I do have the serialosc daemon running on my system. Tailing syslog isn’t showing any monome detected though.

EDIT: serialosc-device /dev/ttyACM0 works, I’m going to sleep now :sweat_smile:

#565

So I just built a norns shield this weekend, finally have something that works with grids after applying @okyeron’s patch… Does anyone know how the update procedure works on the norns by the way? Is it pulling the latest relase via git and compiling on the device? Maybe we could add a git hook to apply the patch automatically for each update…? :thinking:

Has anyone gotten this trellis to work on a linux desktop by the way? I’m not super familiar with C++ or the serialosc codebase, I might start poking around (good excuse to learn!)

So far I’ve gotten the neotrellis to be “detected” by running serialosc-device /dev/TTYACM0, but any program I run can’t seem to connect to the serialosc server. Does the waf script have an option to compile serialosc in debug mode so I can poke around?