#889

Ok - this is confusing. These are two different tasks and they don’t go together (at the same time). You either load the hex file with Teensy Loader OR you compile the .ino file with Arduino and upload it.

Only do one of those things

I wasn’t sure, but tested just now - flashing the firmware to a bare Teensy - and the device will not show up in the Monome Home patch.

I believe the setup process needs to complete talking to the neotrellis boards before it finishes the monome setup. So yes - it is necessary for the neotrellis boards to be correctly addressed.

you can test your situation in Arduino/Teensyduino by plugging in your device and opening the Serial Monitor, then hit the button on the Teensy to get it to restart and you will see the following if your addresses are wrong

trellis.begin() failed!
check your addresses.
reset to try again.

FWIW - I’m updating github with a new 16x8 hex for teensy right now.

EDIT - Run the multitrellis_test firmware to check your board setup.
neotrellis-monome/multitrellis_test at master · okyeron/neotrellis-monome · GitHub

#890

Great, this is helpful. Didn’t realize they overlapped. Thanks for your thoroughness.

The test is running and works when plugging into the micro breakout. I uploaded the neotrellis_monome_teensy.ino file by plugging directly into the teensy (not the breakout)

Max now recognizes the neo_monome when plugging into the teensy directly but not the usb breakout. Is the issue now just my poor soldering of the microusb?

EDIT: When i plug into the microusb, the top left LED flashes

#891

I’d say double check your data connections (D+ and D-). The soldering could be poor or you could be like and have just soldered + to - and vice versa. Your power and ground lines are good since it is booting up and flashing that LED.

1 Like
#892

Thanks, It’s definitely the microusb. I’ve decimated the pcb, in my manhandling. Gonna try to add some 5pins and clean up the connections

Edit: added a photo of the horrendous correction but it works now! Thank you

PXL_20210121_171732647.MP
PXL_20210121_171732647.MP3024×4032 2.37 MB

1 Like
#893

Hi there, any news about official support of ACM devices? Thanks

#894

20 characters of not yet

#895

it’s about 2-3 months out.

but if this is regarding adding “monome compatibility” to OX instruments new thing, the respectful thing to do would be writing us an email.

#896

has anyone been able to get their neo-monome working on Windows 10? Latest serialosc installed but monome isn’t showing. works fine on OS X and norns shield, so I don’t think it’s the teensy?

#897

Getting this error in maiden when connecting to norns shield:

ttyACM found, but not a crow
dev_list_add: error allocating device data

However, when plugging into the computer, Max is fully recognizing the device.

Guessing that’s because the script didn’t run correctly in maiden. How do we know when the script runs successfully in matron?

#898

The DIY device hack described here needs to be run from the command line on the Pi itself. Not via Maiden.

So - you’d need to SSH to the shield and then execute those commands. (Note - this will need to be re-applied after any norns update).

#899

you’d want to search back through this thread.

@Gerald_Stevens may have suggestions

#900

THANK YOU :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag: :checkered_flag:

#901

Thanks. based on the thread, my assumption is no: the current official serialosc for Windows doesn’t work with the neo. I was just hoping someone might chime in to say they had it working somehow.

@nexnex is working on a python implementation of serialosc, but it’s not working for me

#902

Hi. I made a Neo-Monome 256 with a little help from @okyeron (thank you!!!) on addressing the extra grids; it started life as a 128 but some of my boards from Mouser arrived batch missing a 0603 1uF capacitor. They replaced them free without need to return so after repairs I decided to get enough extra buttons to make a 256.

image
image3024×4032 3.61 MB
image
image3024×4032 1.93 MB
image
image3024×4032 2.75 MB

It works just fine playing Polygome and all the old 256 aware Apps with a separate power supply. I’ll make a case next for it. Despite being a 256, its still quite small. I’m building a Norns eventually to play with it.

11 Likes
#903

Looks great! Sometimes i think to just open my 128 and upgrade to 256.
Are there many scripts that use the 256? Is it worth it?

#904

Scripts for norns… a few, (enough to give it a try). Hard-coded grids appear amenable to extension/modification. For max & m4l there remains a legacy treasure trove to make it worthwhile. Even simple sequencers like Polygome in Max8 make still-relevant texture generators.

When not in use for music I think I might make it a pixel art display.

1 Like
#905

thanks for your reply. i guess i’ll stay with the 128, as i understood that a 256 need an external power supply…
how are you going to do your case?

#906

Aluminium and walnut like the originals but thinner. Yes it requires an external power supply. I don’t see that as a limiting factor

#907

To me it is, mostly because norns+grid is my togo instrument! So are always powered by a phone brick charger.
Might as well do a 256 for use in studio maybe?

#908

Considering internal battery charger controller for that. 5V @ 4A with charge/power passthrough (or just use a 4A power brick), With planning it could power a Norns shield.& Pi — and more. LiPo makes good use of internal enclosure space. Will consider it.

1 Like