argh, sorry.

I am as far as this:

however, what I don’t have is accurate heights for standoffs yet. (I have not looked at this since I got back from vacation). If I knew the distance between the two boards, and the standoff height for the screen, that’d help tons.

My encoder models come from the manufacturers; the jack models are quick ones by me, and I believe the positioning/model is as accurate as I can get it.

The Pi is somebody else’s model. I might replace it with a more accurate one in due course.

1 Like

@infovore distance between PCBs is 15.88mm on my prototype but it has a bit of play of course.
The screen on my prototype is soldered on, which I don’t think/expect would be the way we’ll suggest to go. The distance between the screen’s PCB and the shield is 5.9 to 6.1mm (it’s a bit off :wink: ).
When using male/female headers the distance will be slightly greater.

Curious… I’ve got an 11mm spacer between pi and the Fates pcb with a standard 2x20 header.

Also, I end up with 6mm gap between display and main pcb using a low profile header and a slightly weird header attachment.

1 Like

Is it possible to post the 3d file?

Same here, 11mm. But on Fates and Nordhat the PCB has a different shape and is cut in such a way the USB connectors can go beyond and don’t affect the overall height too much (am I right ? :slightly_smiling_face:).

photo

image

I think the height of the RPI including the connectors is 19mm

Aha - yeah that explains it.

Confirming now that I’m at the computer. Yeah - the bom calls for the Adafruit “Tall 2x20 Female Header” (adafruit part #1992) - which they say is 16.5mm tall

1 Like

I still have the .step file of the Newhaven display in case you’d need it :wink:

1 Like

ooh that’d be handy. Can you send it to me?

1 Like

Sure, i’ll dm with the file

1 Like

Could you send it to me as well?
Thx

I was wondering if the Pi3b (not “+”) could work with this? Would the different CPU speed affect the processing power too much? I’m asking this because I might get one for free from somebody who doesn’t use it anymore and i’m looking into what to do with it.

I’m doing the development/testing on a regular RPi 3b, in general there are no issues but I’ve not performance tested it yet.
Do you have a specific script in mind that you’d want to run that’s heavy on resources that I could test?

1 Like

Not really. Just knowing it would work is enough for now! Thank you.

Did you find that Jack period settings needed to be changed for the regular 3b?

I’ll be doing some more/proper testing of the soundcard today so can probably tell you more later but I wouldn’t expect that to be necessary.

Did you run into some issues?

OK, try this:

norns-diy-wip.stl.zip (2.3 MB)

which is an STL of this:

Screen is an official part, encoders and buttons are official parts, Raspberry Pi from Grabcad, Norns DIY board from @tehn’s EAGLE files. Spacing as suggested by others here - the height of the screen from the board may be incorrect, however.

10 Likes

one fates tester with a pi3b reported Jack/supercollider xruns/errors

Aug 07 20:32:43 norns jackd[318]: JackEngine::XRun: client = SuperCollider was not finished, state = Triggered
Aug 07 20:32:43 norns jackd[318]: JackAudioDriver::ProcessGraphAsyncMaster: Process error

After changing the JACK buffer size from 128 to 256 the errors went away.

2 Likes

Thanks! I’ll keep an eye on it.
Odd though, wondering what’s causing this/what the difference is vs norns.

1 Like

I did the same thing on my 3b+ / USB audio interface setup to fix some ugly noises I was getting when I enabled input monitoring. I didn’t notice error messages like this, but that doesn’t mean they weren’t there. (edit to clarify that I chalked that up to USB performance, or lack thereof)


Another crappy picture!
[edit] There’s still a protective sticker on my display, that’s why it looks so odd

This time with a grid (and proper knobs!) for size comparison, it’s pretty small :slight_smile:

Just ran a 30 minutes “stress” test where awake was running at 480bpm no xruns whatsoever. The load is very low actually.
Also tested out all stock scripts and it all seems to be working fine.

Does anyone have any specific scripts that were causing xruns that I could test? @okyeron What was the script you experienced the xruns with?

19 Likes