So yes, that should be OK.

A couple notes/thoughts…

If you order fancier material like matte black, all of the pieces will be cut from that (and may be more expensive). I don’t know if it would be cheaper to make separate orders of the top/bottom from one material and then the others from glossy.

With 3mm material your stack will be 9mm in the middle - Thus use 8mm standoffs and you should be OK.

2 Likes

Argh. I’ve managed to lift a data pad on the bottom of the teensy with some clumsy soldering.

Is there any reason I can’t take the D+ and D- out of the onboard usb slot by cutting open a micro usb cable and have the power run under the board?

Sounds like a reasonable bodge to me.Try it and see?

Worst case, replace the teensy.

1 Like

Question
I have the opportunity to buy an old 128 for 290 euros near me in Italy. Is the walnut one so no varibright. Should i go for that or build the neotrellis one? I already built a fates so I’m not scared about going diy, the thing that scares me is the possible problems with this clone

1 Like

Varibright makes a huge difference for most norns scripts. Some are just not very effective with mono-bright.

Not sure what possible problems you might be expecting. Neotrellis grid works like a champ with Fates.

1 Like

Would you mind to share a product name or a link for the black spray paint ?

I need to paint an old Launchpad and if the paint you used works well for ABS, then I suppose it would be all right for a (sanded) Launchpad original.

fwiw, it depends on the year it was manufactured. 2007-2010 walnuts require an external power supply (vs. bus-powered off USB, though they could be upgraded) and are the “series” generation, which is monobright. otherwise, all later walnut generations (2011-2013) are bus-powered and either 4-step or 16-step varibright. more info here: https://monome.org/docs/grid/editions/

Hello!

I just built my diy neotrellis grid, and I’m trying to use it with my Fates. I used a teensy 4.0, and believe its all wired correctly. After plugging in the diy grid to fates, within a couple seconds the top left LED blinks white (which I believe means it’s loaded), and then my fates does detect the grid under devices (neo-monome m4676055).

No scripts seem to work with the grid, and I tried using @okyeron’s grid-test, and that doesn’t light anything up either.

I built it 16x8 buttons, using just the teensy 4.0 for power.

Hi.

Im having problems with the interrupt pin in a multitrellis grid.

Does anyone has an Arduino code using interrupt I can check out?

Hello!

I just built my diy neotrellis grid, and I’m trying to use it with my Fates. I used a teensy 4.0, and believe its all wired correctly. After plugging in the diy grid to fates, within a couple seconds the top left LED blinks white (which I believe means it’s loaded), and then my fates does detect the grid under devices (neo-monome m4676055).

No scripts seem to work with the grid, and I tried using @okyeron’s grid-test, and that doesn’t light anything up either.

I built it 16x8 buttons, using just the teensy 4.0 for power.

Edit:
I later realized I needed to do a git pull, to be able to run the fates script, but didn’t have internet at the time. I did a git pull, and tried running the diy device fix, and I get a bunch of errors:

Setting top to : /home/we/norns
Setting out to : /home/we/norns/build
Checking for ‘gcc’ (C compiler) : /usr/bin/gcc
Checking for ‘g++’ (C++ compiler) : /usr/bin/g++
Checking for program ‘pkg-config’ : /usr/bin/pkg-config
Checking for ‘alsa’ : yes
Checking for ‘libudev’ : yes
Checking for ‘libevdev’ : yes
Checking for ‘liblo’ : yes
Checking for ‘cairo’ : yes
Checking for ‘cairo-ft’ : yes
Checking for ‘lua53’ : yes
Checking for ‘nanomsg’ : yes
Checking for ‘avahi-compat-libdns_sd’ : yes
Checking for ‘sndfile’ : yes
Checking for libmonome : yes
Checking for supercollider : yes
Checking for program ‘dpkg-architecture’ : /usr/bin/dpkg-architecture
Checking boost includes : 1.62.0
‘configure’ finished successfully (1.410s)
Waf: Entering directory /home/we/norns/build' Waf: Leaving directory /home/we/norns/build’
source not found: ‘src/SoftCutClient.cpp’ in bld(lib=[‘jack’, ‘pthread’, ‘m’, ‘sndfile’, ‘atomic’], use=[‘ALSA’, ‘LIBLO’, ‘BOOST’], target=‘crone’, idx=1, posted=True, tg_idx_count=5, meths=[‘process_rule’, ‘process_source’, ‘apply_link’, ‘create_task_macapp’, ‘create_task_macplist’, ‘install_boost’, ‘process_use’, ‘propagate_uselib_vars’, ‘apply_incpaths’, ‘set_full_paths_hpux’, ‘set_macosx_deployment_target’], includes=[‘src’, ‘./’], cxxflags=[’-std=c++14’, ‘-O2’, ‘-Wall’], source=[‘src/main.cpp’, ‘src/BufDiskWorker.cpp’, ‘src/Commands.cpp’, ‘src/MixerClient.cpp’, ‘src/OscInterface.cpp’, ‘src/SoftCutClient.cpp’, ‘src/Taper.cpp’, ‘src/Window.cpp’, ‘src/softcut/FadeCurves.cpp’, ‘src/softcut/SoftCutHead.cpp’, ‘src/softcut/SoftCutVoice.cpp’, ‘src/softcut/SubHead.cpp’, ‘src/softcut/Svf.cpp’, ‘src/softcut/TestBuffers.cpp’], path=/home/we/norns/crone, _name=‘crone’, typ=‘program’, features=[‘c’, ‘cxx’, ‘cxxprogram’, ‘cxx’, ‘cxxprogram’]) in /home/we/norns/crone

gotta pull submodules.


git pull
git submodule  update --recursive --init 


./waf clean
./waf configure --enable-ableton-link
./waf build
sudo reboot

For testing the grid - can you get Maiden open and look for any errors or other REPL output?

(dumb question) Are you sure you have a known good Data cable for the teensy?

I’m probably asking a very dumb question:
Can I use a “normal” usb b breakout? I really hate the micro usb b one, I’m always ending breaking them…
Obviously i have to change a Lil bit of the enclosure, do you think it can fit?

Yeah. It should be fine.

I have one here and it sticks out a bit farther (the mini pcb is wider than the micro one)

Can you upload a picture? Or tell the part you used?

On the GitHub page there’s a load of images as well as links to everything used including the breakout board.

Sorry i wasn’t very specific. I meant the usb mini b breakout from adafruit.

I don’t think the “big” usb b would work

Fwiw - sine the breakout (mini or micro) only costs $1.50 it’s not such a big deal if it breaks and needs replacing

Or Maybe use usb-c instead?

1 Like

regarding this, i followed my typical process which is “use whatever interface board you have around because hot glue will make anything fit”

DIY fates connector
2 Likes

I ran those commands all without error.

So this is what I see in maiden when loading grid-test:

# script load: /home/we/dust/code/grid-test/grid-test.lua
# cleanup
# script clear
libmonome: error in write: Resource temporarily unavailable
libmonome: error in write: Resource temporarily unavailable
libmonome: error in write: Resource temporarily unavailable
libmonome: error in write: Resource temporarily unavailable
ERROR (i2c/hp) failed to write
pset >> write: /home/we/dust/data/system.pset
# script run
>> reading PMAP /home/we/dust/data/grid-test/grid-test.pmap
m.read: /home/we/dust/data/grid-test/grid-test.pmap not read.
Engine.register_commands; count: 0
___ engine commands ___
___ polls ___
amp_in_l
amp_in_r
amp_out_l
amp_out_r
cpu_avg
cpu_peak
pitch_in_l
pitch_in_r
# script init
grid neo-monome m4676055 16x8

Whenever I try and change what should be shown on the grid on grid-test, I get 2-4 of these:
libmonome: error in write: Resource temporarily unavailable

I’ve tried 3 different cables, and I’ve tested them with a camera I have and I can see images from the camera, so I assume the cable is good. I’ve also tried uploading the teensy with the different cables, they all seem to work.

I usually get a bunch of those libmonome: error in write: Resource temporarily unavailable errors when connecting the neo-grid, so that’s somewhat normal I think - although maybe this may mean there’s some communication issue.

Can you test with a regular computer with Max (free version is OK) and the Monome Home patch?

Maybe a picture of your teensy to neotrellis wiring would be helpful?

So I haven’t really used Max before, just downloaded the 30 day demo. Upon opening Monome Home patch, no grids show up. Do I have to do anything for it to show up? Or is that my issue, that it’s not showing up?
Read below (Edit 2), kinda figured out how to use Monome Home.maxpat, but it seems to be failing.

In your multitrellis_test in your git, that doesn’t show anything on the neotrellis.
If I load one of the examples (Adafruit seesaw Library–>NeoTrellis–>multitrellis–>basic), a rainbow chase occurs on 2 of the Neotrellis (top right ones) (the ones that are addressed by default on that sketch, I tried playing around with it to see the full 4x2 neotrellis, but I can’t quite figure that part out).

I’ve included pictures of my wiring:

Thanks once again @okyeron for helping me learn this stuff!

Edit:
So for fun, I’ve modified your code from the white top left bootup, to 4 LEDs (white, red, green, blue), and for a longer duration. That works when it boots up, but I still can’t use it as a grid.
Using the test-grid.maxpat (from https://github.com/monome/serialosc.maxpat), I can control the first 4x4 grid, turning buttons on and off. But as soon as I press a button on another neoetrellis, it doesn’t work and the 4x4 that was working stops responding.
Included a video showcasing that:
https://www.dropbox.com/s/gokyvlbqq1tjriw/IMG_0621.MOV?dl=0

Edit2:
Testing with Monome Home.maxpat, it registers keypresses. from the first neotrellis (top left), but doesn’t detect key presses from any other neotrellis. If I press “all 0” under the led part, nothing happens, but as soon as I press “all 1”, nothing lights up and the only working neotrellis stops registering keypresses.
To get it to register key presses again, I have to unplug the grid and plug it back in.

Edit3:
Ok, so I’m narrowing it down to something wrong with the addresses. I flipped the order on the code, and now the top right 2 neotrellis’ are responding to keypresses, but the rest aren’t.
If you’re looking at the board from the back, I soldered these jumpers exactly like this image. I’m going to toy around and see if I can figure it out. I put solder where there is bright green. Did I do this right? I’m 99% sure it’s right, but I can’t figure it out.