#464

Sure, I’ll upload to git today. (Don’t know if Fusion can do sldprt).

The PCBs are already screwed to the bottom part though. They’re the two rows of stands in the bottom part (8 screws total). The holes in the top are meant for connecting the two parts together.

1 Like
#466

Yes, worked like a charm! It is protruding sidewise maybe 0,5mm, but that’s not really an issue. I guess it’s the same for the micro?

Thanks for your pointers!

Yes I saw that. That registry key does not exist (cleaned everything up when I set up my machine), so nothing to remove there. Starting serialoscd as a non-service also does not really do anything, but I’m not sure what the expected console output for a connected device should be (if any).

Hmm. I got this from the official pages and the github repo

Tried the version you linked (1.4.2-pre), but it gives the same result (it just installs into the 64bit app folder “Program Files” instead of the x86 folder), and when running serialoscd -v it still gives the 1.4.1a output. But still, I’ll run with this one now in my quest for detecting the neo-monome.

Just to make sure: When I connect the device to USB, one corner briefly blinks. Is that the expected behaviour?

Ah man, this is driving me crazy, having this beautiful thing sit on my desk uselessly…:confused:

#467

Boards are getting 5V. How do I check the i2c connection?

#468

You could start by using a multimeter to check for continuity between the I2c pins of the teensy and the I2c pins of each Neotrellis board. If you have a logic analyzer you could also check the signal on that bus…

1 Like
#469

Continuity is fine. I have a Rigol scope, but not sure if that has a logic analyzer.

#470

IIRC, one of the 4 channel rigol scopes has/can be hacked as a logic analyzer. If power is good, and the connections are good, it sounds like there may be a communication problem. A logic analyzer could help with that. Maybe your I2c addresses are wrong in the firmware. I’d double check that – although if it was working and then suddenly stopped working, that would point to something else being the problem.

#471

Yeah no, it’s the older 2 channel so no luck there. Yeah it worked fine, now no longer. I’ll order another teensy to see if I can get it to work again.

#472

I have this super cheap logic analyzer, which I believe I bought off amazon (it was quite a few years ago). Anyway, it works fine, and has come to the rescue on rare occasions…

2 Likes
#473

Alright so then I hook that up to the i2c connectors to see if messages are being sent out and received? This is slightly beyond my knowledge, see I’m an analog boy, this digital stuff is over my head.

#474

Yes, you can capture a snapshot of the communication (or lack thereof), and display it on your computer screen. The software can do smart stuff to help you interpret the communication (e.g. it can recognize certain sequences of pulses as start/read/write/address, and so on). You can see if the teensy is talking and the Neotrellis is responding/or not…

1 Like
#475

How are you testing?

Have you tried going back to the multitrellis test sketch/hex?

Building serialosc (also liblo, libmonome) on Windows 10 to add alternative detection methods
#476

Thanks for your advice so far. Hmmm. Tried it on a different Win10 machine, same result. One LED lights up for a tiny moment, then nothing…

Checked the USB device view, that seems to be detected the right way (please confirm if possible), it stays connected:
monome USB Serial Device Communication Yes Yes No No COM5 m4676055 04/06/2020 18:50:43 03/06/2020 07:44:32 16c0 0483 2.75 02 02 01 MANCAVE-REBORN usbser @usbser.inf,%UsbSerial.DriverDesc%;Microsoft USB Serial Driver usbser.sys SYST Microsoft USB Serial Device (COM5) 100 mA 1.10 USB Serial Device 10.0.18362.1 UsbSerial_Install usbser.inf USB\VID_16C0&PID_0483\m4676055 Removable, UniqueID, SurpriseRemovalOK

So not sure how to continue with this. Any creative ideas? Anything obvious I might have missed?

#477

node-serialoscd != monome’s serialosc?

It’s a completely independent rewrite in JS running on Node, so they couldn’t possibly be more different.

The issue I had before with lockups with all LEDs lit was a power problem, not a node-serialoscd problem.

1 Like
#478

First thing I tried, nothing.

#479

Maybe check all your address jumpers?

Another test would be to run one of the i2c test sketches to scan the i2c bus and see if all the addresses are showing up. If one address is missing or wrong it can throw off the whole thing.

in Arduino - Look at Examples > i2c_t3 > basic_scanner, or advanced_scanner (in the Examples for Teensy 3.1/3.2 section). You’ll need to ground a pin to trigger the script while connected to your computer with the serial monitor open.

#480

Are you able to test on a Fates? I found the one LED lighting on my DIY Grid when initially powered, but once I fire up a Norns app like Awake it immediately springs to life.

#481

I’m hoping you crack the code. I tried and failed. I upgraded to max4live thinking I could use it with Max… haven’t seen anything promising.

#482

That is the original intention - I plan on building a Fates, but it seems the PCB is stuck in customs…fingers crossed

#483

Hmm that is unfortunate. Is there another place to get help on the serialosc issue?

#484

I’ve got a request in with DanDerks and I’m waiting to hear back if there’s any support-y stuff he can share.

It’s possible there’s some timing of messages thing happening with the windows version that’s throwing things off.

I don’t have any windows machines so I can’t test for it.

BTW - the one LED in the corner thing is a “startup” indicator. That should happen once the init of the firmware happens and it’s communicating.

Anyone know how to sniff the serial communications on win?