#1077

Be sure you’re sing side to side enough to get both upper and lower case letters if your password uses both. Some people have gotten caught only entering upper case letters.

If you have Ethernet on a computer (or your router), that’s very quick and easy to get network connected.

Once connected you can try using nmtui to manage network connections from a terminal

The extra (4th) encoder will not work with norns software at all (without some deeper code changes). It’s for use with ORAC or other DIY software solutions.

#1078

Thanks for the feedback. Meanwhile wifi behaved and connected. I did not do anything different so I don’t know what happened.

Anyhow: one or the other way I can connect. I will also check out nmtui…

And yes, it is the 4th encoder I meant. Looking forward to check out ORAC … but for now I have enought to do with the norns side.

1 Like
#1079

I’ve got the case open in Fusion 360 and was intending on adding screws to close the case up…

But I think I’m going to need to redo the USB-C and extra encoder hole in Fusion before I can screws. The original author of that work only uploaded the stl files and hasn’t responded to my message asking for his .f3d file: https://github.com/coreyker/fates3d_case/pull/2#issuecomment-575926368

I’ll poke at that a bit today…

1 Like
#1080

Nice one! I prefer no screws on the lid so might find a semi-permanent solution to fix them together, if I feel confident enough that I won’t need to rebuild anything on the board :grimacing:

1 Like
#1081

If the press fit works for you, great! I just used tape around the outside until I can print an updated version. :slight_smile:

When I printed the existing case design on a Prusa i3 MK3S in PLA (a bit of a gold standard to some) I found that the top was flexed too much to make a press fit work well. In a recording environment the noise of a case flexing around isn’t great. Also, if you’re taking it on the road, I’d be worried about a press fit.

Honestly, adding screw might increase the overall size because the case is already pretty packed. It might be possible to adjust the encoder holes a bit so washers and nuts can hold the case together, but I haven’t explored that much.

I’m almost done re-adding the USB-C hole back to the .f3d file…

Edit: Done re-adding the USB-C and 3rd encoder holes to the Fusion 360 file. Untested, but the PR is here: https://github.com/coreyker/fates3d_case/pull/4

1 Like
#1082

I got everything built and running, but I’m not getting audio out of the scripts. Running the troubleshooting steps plays audio out just fine, but running say Awake or Earthsea, the screen responds but no sound is produced.

I should say that I did reboot once and get sound, but then after another reboot, it stopped working again and subsequent reboots are not solving the issue. In the system Levels screen the VU doesn’t show anything, either.

Any guesses?

edit: the nc01-drone script is playing sound, so maybe it’s something to do with synthesis vs playing samples?

#1083

With Awake, in the parameters menu check to see if it is set to output audio or midi only. Also check that the engine audio is turned up in the levels menu. The meters have only been showing input and output levels live in the recent updates, so don’t worry if the softcut/engine/tape vu aren’t drawing if you’re getting output.

#1084

Awake is set to audio output and the engine level is all the way up. Someone else pointed to the power source being a potential cause which I’ve also read in this thread - right now I’m using an Apple charger with the micro USB port which outputs 5.2V/2.4A so maybe it’s not quite sufficient. I have an official power adapter coming in a day or two so I’ll be able to rule that out, hopefully.

edit: restarting sc through maiden seemed to get it working (;restart in the sc REPL).

#1085

Ah, if it was first install of a new engine, norns needs a restart to recognize new sc engines.

#1086

Is a norns restart different than a power cycle (unplug, re-plug) after choosing SLEEP from the system menu? I went through several of those without success.

#1087

SYSTEM>RESET will restart the norns software stack. (Not actually sure if it does everything - I should check)

;restart from maiden will restart matron or supercollider depends on which tab you use

Sleep shuts down the entire pi.

#1088

Wow, what a day!

After playing with a few ideas, mounting the Pi to the back and the Fates PCB to the front (with nuts and washers on the encoders and screws around the top edge of the board inside the case) came out on top. In theory, this will allow the case to be split along the Pi header.

internal-bracket-test
internal-bracket-test1073×747 235 KB

While just using the friction of the header might be enough, I hacked together an internal bracket that can be used to secure the two halves together with 5 additional screws through the back. I don’t really like having a third piece, but there are really only two straight shots through the inside of the case that pass through holes in the Fates PCB.

internal-bracket-test-front-with-pcb-and-bracket
internal-bracket-test-front-with-pcb-and-bracket1243×808 408 KB

This means the assembly order will be:

  • Fates screws to the bracket with 3 screws
  • Fates screws to the top half of the case with 5 screws (one passing through the bracket), and using 3-4 nuts+washers on the encoders
  • Pi screws to the bottom half of the case in 4 spots
  • Top half and bottom half mesh together with the Pi header, and 5 screws through the bottom of the case and into the bracket.

A bit of a mess, honestly. I’m guessing the internal bracket will just be a nicety and could be left out, but Fusion 360 is fun so it was fun to see how far I could take it.

Once I validate the design works, I’ll upload the STL files and the modified Fusion 360 f3d file.

Let me know if you have other changes you’d like to see and I’ll see if I can get to them!

And, again, thank you so much to everyone that contributed to the original case design as well as posting the files. I’ve had a blast working on this so far!

7 Likes
#1089

How did you get the PCB into Fusion? Did you use the png file from okyeron ? I tried this but didn‘t get it to the right size.

I‘m working on a case too. Will post it as soon as it‘s finished.

#1090

Hehe, it’s just the PNG of the board from the git repo. :slight_smile:

  • Create a construction plane where you’d like the image to be displayed
  • Insert menu -> Canvas
  • Pick a file
  • Use the UI to flip and orient the image correctly. Don’t bother about scaling the image, we’ll do that after you hit OK and drop the image into the project
  • Find and expand the Canvases section of the project browser
  • Right click on the Canvas -> Calibrate
  • Click two points in the image and enter the real-world distance between those two points (I used 10 of the 0.1" headers and set them as 25.4mm (1 inch))

Now the image should be correctly scaled to your project, but you probably want to move it around to line up with stuff…

  • Right click the Canvas in the History bar and select Edit Feature
  • Move the Canvas around, but don’t scale it.
  • Done! :smiley:

Just remember that Canvas’s have zero thickness, and PCBs do…

2 Likes
#1091

wow. thanks for your reply!!! Gonna try this!

#1092

I’m trying to connect from terminal and I get this …

@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The ECDSA host key for norns.local has changed,
and the key for the corresponding IP address fe80::90ed:7045:e320:fc55%en0
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
SHA256:1JxXsCwJCm/uHIsU1IMFbMyGSdWj8nmtVE47CQRXhwU.
Please contact your system administrator.
Add correct host key in /Users/andreafiocca/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /Users/andreafiocca/.ssh/known_hosts:1
ECDSA host key for norns.local has changed and you have requested strict checking.
Host key verification failed.
MacBook-Pro-di-Andrea:~ andreafiocca$

Any idea ?

#1093

This is kinda normal and will happen if you swap SD cards between pis or use different SD cards with the same pi.

Fix posted below

1 Like
#1094

Did you reflash or similar? I’m guessing your Norns has regenerated its host key… or maybe you previously connected to a Norns from this computer, and now you’re connecting to a new one?

In case its not clear, /Users/andreafiocca/.ssh/known_hosts is a file that contains the keys of all the hosts you’ve previously connected to. The .ssh directory is inside your home folder, but normally hidden (because its name starts with a .). In macOS Sierra and later you can type cmd+shift+. to see hidden files and folders. Open the file in TextEdit, find the line that says something about norns.local and delete (or just trash the file completely if you don’t do a lot of ssh’ing).

If you’ve got two Norns, this’ll come up again.

2 Likes
#1095

Normal sounds pretty good …

#1096

(in addition to what rvense posted…)

This is the important part

All you need to do is (from a terminal)

sudo nano /Users/andreafiocca/.ssh/known_hosts

Then find the line with norns.local (or the IP address of that device) and remove it. In nano, you can arrow down to the line and then use ctrl-K to cut the line, then ctrl-O to save and ctrl-X to exit.

If you have multiple devices and want to access them with zeroconf (norns.local syntax) you could change the hostname of the fates machine using raspi-config - I have one box setup as fates.local for example (but then you need to remember that for access via maiden, etc.).

FYI - I think the norns shield has raspi-config disabled by default so the above might not be doable on a shield device.

2 Likes