#880

Based on what you’ve reported @rrvvzz and what others have found using the FTDI breakouts as well as some norns/fates/shield users is that they have some immediate power on issues. In the case of the FTDI breakout boards the best results were when the teensy was powered separately and already on when connecting to a Teletype. In regards to the norns/fates/shield users were having to reset after connecting the DIY grid or power on with it connected. Personally I have fallen into both camps in my experimenting.

I’m curious if bodging in a MIC803 would help in this situation like it has other euro teensy projects. It seems counterintuitive in that you’re delaying the boot a bit but perhaps it would boot far more gracefully and perform better out the gate? I don’t know, kind of above my head but I’d definitely be willing to experiment. Literally just ordered a MIC803 a day ago for a t3.6 going into a TXO+ but I only ordered the one unfortunately.

#881

I got an FTDI friend working well with a modified version of my palette selector on Fates, Norns shield, and teletype. I keep hoping the couple of kind people who are working on revising the teletype code will make my hack unnecessary. But to save people the hassle I went through, I’ll post details on my GitHub this weekend.

3 Likes
#882

I’ve got a newer version of the code that eliminates a previous “long connection time errors” with libmonome - so that might solve the problem you’re seeing… I’ll check my github for whenever I did that last push (UPDATE - looks like the teensy code is updated on github - so try with the most recent code). I’ll re-do a hex with the new version soon.

What software are you connecting to on linux?

2 Likes
#883

I’m connecting to PD, tried connecting to Renoise as well. Works fine when I run serialoscd after connecting my grid. I’ll update my teensy though!

Does this also eliminate the device detection problems I mentioned with serialoscd on linux?

Update: The newest firmware looks to have solved the long connection time issue!

1 Like
#884

noob q…did some searching and couldn’t find an answer.

The teensy/grid device isn’t showing up in the maxpat test, but the terminal and system monitor are recognizing the monome usb connection. I flashed the teensy with serialosc unloaded.

Am i missing something obvious?

#885

you’ll need to load serialosc to get it to be recognized by Max

Assuming you’re on MacOS
launchctl load /Library/LaunchAgents/org.monome.serialosc.plist

#886

Yes I reload it before launching Max (forgot to mention)

#887

Are you working from the pre-made hex? If so - did you make sure your board addresses are the same on your hardware as in the example in the build guide? (also reminds me I need to make new hexes)

If you compiled yourself, then triple check your addresses in your version of the main sketch.

#888

Yes I uploaded the hex from the git with teensy loader and then uploaded the .ino file.

I used the address guide from the image in your git as well.

But would the hex need to be correct for the teensy to be recognized in max? Is it necessary?

#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