DIY: norns shield

Yeah
Now we’re talkin
Maybe stick a zener diode in there

5 Likes

Vacant RasPi jack ⤳ NTS-1 audio in ⤳ norns input, while norns is running Changes at MIDI CC 87-94

Works

7 Likes

Oh! Inspireing. Tapping into the computer brain noises. One of the Kastl noise sources is a playback of the device source code. This one is more accidental, the noise is a residue of processing.

1 Like

The binary in the case of Kastle rather than source (sorry for being pedantic, I’m writing about Mark Marino, Wendy Chun, Adrian Mackenzie &c this weekend :sweat_smile:) but yes. I think this idea of using memory as sound was discussed also in Composing with Process serie on RWM by MACBA but i cannot figure out right now which episode. The Von Neumann architecture also is about memory as data. I can access a random memory (pun intended) of being baffled by someone using a mouse driver as a sample with Amiga tracker in the 1990s. All fantastic avenues!

What would this mean for norns shield? I made a symlink in dust/audio to / to be able to select arbitrary files as samples (on Unix everything is a stream), also stuff in /proc and /dev but that was a half-assed idea. Could one establish a hybrid feedback which wasn’t audio-only, but would run though the ADC→kernel(→maybe upper layers of the software stack)→DAC machinery?

Computer brain noises, I love this concept! :exploding_head: Thank you for flipping my brain around – strange noises seem to emanate from my brain right now!

I have no idea what comes out of the RasPi jack with a half-plugged cable, and whether processing affects it. Isn’t it the right channel being grounded? Maybe flickering the norns shield to produce onboard noises; from what I’ve understood from the monome folks and other users the shield is subject to it?

I will apply granular synthesis to it later today to investigate these ideas!

2 Likes

I have a secondhand Norns Shield from a local builder and the screen protector is pretty flimsy. I tried to attach it more firmly to the case with super glue but of course it turned out to be a bit messy… My DIY skills are not the best :grinning: Its not too bad, you can still see everything and everything works fine, but I was wondering if its possible to order only the ”official” shield casing from Monome? It looks much better and I’m already ordering stuff from Monome once the Grids are out again. I couldnt find that option from their website. Or are there other good casings that are very easy to put together I could buy, preferably in EU? And are all the cases compatible with the regular Shield hardware?

we tend to keep the shield circuit + cases stocked 1:1, so we don’t typically have extras :\

this thread has a lot of great 3-d printable options: Norns shield case designs. @JHC designed the one that ships with shields when you buy from monome: Norns shield case designs - #244 by JHC

2 Likes

Thanks for the answer! I’ll start looking for these other options people have made.

Help me please! I have no idea what happen, but now i can’t instal something from maiden

install failed: Get "https://github.com/xmacex/connect-opz/info/refs?service=git-upload-pack": x509: certificate has expired or is not yet valid: current time 2020-12-27T15:24:50+07:00 is before 2021-03-25T00:00:00Z

hmm. i think this suggests that your shield’s sense of date is 2020-12-27. has it been powered off for a long time or not connected to WIFI before now?

as @ngwese has mentioned elsewhere, norns should resync to the correct date/time when it’s connected to a known WIFI network while booting, so i’m curious if a reboot after being connected doesn’t resolve the issue?

I use Norns every day(wifi work permanently)
Reboot and reset with known WIFI network doesn’t work for me.

oh, weird. it’d be good to collect a bit of information:

  • please ssh into shield using these steps: wifi + files | monome/docs
  • once logged in, please execute date and share the output here?

edit: solution here DIY: norns shield - #1747 by csboling

Seems like changing Time zone doesn’t work too: Date still Sun Dec 27 17:18:19 +08 2020

ah! @Nghttgr , try rebooting after the change and then re-run date – does that work?

if not, you can manually set the date/time, but i’m hesitant to suggest this as it might just continue getting out of sync. @tehn / @zebra , any better suggestions?

These are just timezones options I think, and would not affect the date. Is NTP (network time synchronization) turned off? What is the output of

timedatectl status

If it does not say

Network time on: yes
NTP synchronized: yes

you can run

sudo timedatectl set-ntp true

and then reboot.

This is a problem on stock norns as well, the raspi does not have a hardware real time clock or little battery for keeping it running as is found in desktop computers. You are stuck using NTP to get accurate time information. The issue this can cause is that Supercollider for some reason can get in some bad state when the system time suddenly jumps, like if you power off for a while and then power on and connect to the network – in this case SC will sometimes just start chewing CPU and can lock up the whole system.

However, if your system time is not accurate, you can run into problems like this – github.com probably rolls over their HTTPS certificates every year, so if your system time is months out of date then your pi will think the certificate is forged or someone is otherwise trying to interfere with your connection, and will refuse to connect.

1 Like

oh! rad, sorry, changing timezone returns this afterward, which i took as a false positive of sync:

Current default time zone: 'America/New_York'
Local time is now:      Sat Apr  3 10:14:14 EDT 2021.
Universal Time is now:  Sat Apr  3 14:14:14 UTC 2021.

but if it’s just taking the assumed system time and reworking it with a timezone difference, then it makes sense that it returned the same for @Nghttgr !

i’ll log timedatectl as the right solution for this moving forward, thank you Sam!

Well, supposing it fixes the problem… and if it does it leads one to wonder how NTP got turned off in the first place? Or was it ever enabled on the shield? This is probably also an option in raspi-config, maybe accidentally disabled when expanding the filesystem?

1 Like

If memory serves I don’t believe a NTP daemon like ntpd or chrony has ever been installed or enabled on the norns images. I could be totally wrong but I believe the clock syncing is done as a one shot operation on boot or network connection by systemd-timesyncd.

2 Likes

hmm…i have checked date status, run ntp - true command, reboot, but nothing happen

Local time: Sun 2020-12-27 17:30:12 +08
Universal time: Sun 2020-12-27 09:30:12 UTC
RTC time: n/a
Time zone: Asia/Singapore (+08, +0800)
Network time on: yes
NTP synchronized: no
RTC in local TZ: no

May be something wrong with my network? I work on ship and we have our own network with satellite internet connection. But previously i use this network for installing and updating scripts. Weird.

Ah okay, so maybe the configured NTP timekeeping server(s) are not reachable? Maybe you can try using something like sudo date -s '3 April 2021' to set the date manually and then check if date / timedatectl status are right.

2 Likes

Well…now date is correct! Many Thanks!

1 Like