#1220

thank you so much, ill try that.

#1221

How much power does the RPi have in totalt to distribute through the USB-ports with the shield attached?

#1222

not a clue!

You’d likely need to google that up or search the Raspberry Pi forum. Power supply is also maybe a factor.

USB specs mandate a certain value of power from the USB ports, but I can’t remember if that’s 250mA or 500mA or what.

1 Like
#1223

Hi!
Im trying to update my fates but i get this error?

Cannot write to ‘fates200121.tar.1’ (No space left on device).

Any ideas?

Cheers

#1224

Kinda self explanatory?

check df -h then maybe check your dust directory: du -hs ~/dust

EDIT (or if this is a new install - expand the filesystem as mentioned below with raspi-config)

Also @thopa get the newer update here

1 Like
#1225

first thing to do > ssh we@ip adres
sudo raspi-config

advanced options
expand

2 Likes
#1226

Thanks @okyeron

I went to the update folder and had a few files there, have deleted them now

I am installing from the link you provided, cheers

I also did the expand sd card option, thanks @Gregory_Delabelle

All good now, cheers

#1227

So, i have bumped into a problem.
If i use a diy grid with fates, and also have a midi controller connected (diy teensy based) eventually fates crashes.
Controls on fates become non responsive and some times the leds on the diy grid change.

Im testing with zellen and shfts at the moment.
Grid is connected to port 3 and midi controller to 4.

Does the problem with multiple devices connected on start up are happening?

I have reconnected things, trying to replicate crashes.

So i have the teensy midi controller on port 1
Diy grid on 3.

Less concepts crashes at soon as i move the midi controller.

Shfts doesnt crash until i move one of the controls on the fates.

Wonder if this is script related?

Power consumption on Pi usb ports? I have the orginal psus…

Trying different combinations atm.

Cheers

#1228

Built Fates.

upside: boots up, audio io works, some scripts work, grid connection works, joy!

issues with un-updated version of norns (skip ahead for update issues):

-can’t connect via wifi (entered network password including lowercase), status stays on activating indefinitely, network shows network name for a minute and then the name disappears, IP address blank
-hotspot just shows status unavailable (or is unresponsive, can’t tell)
-wired connection with ethernet cable seems to work since I can access maiden, and ultimately I’m fine with just a wired connection. No IP addresss is shown and status remains on activating however which is odd. Problem is, in maiden I can’t seem to update or install any new scripts. I get errors like:

“install failed: Get https://github.com/monome/softcut-studies/info/refs?service=git-upload-pack: dial tcp: lookup github.com on 127.0.0.1:53: server misbehaving”

except it says that for all updates or scripts (with a different URL). Also, after getting one or two of these errors, the check mark for installing an update/script or removing a script no longer returns an error, it doesn’t do anything.

issues with update process:

This is probably my ineptitude with computers/command line interfaces. I was able to ssh into fates and enter the password, then pasted:

cd ~/update
wget https://github.com/okyeron/fates/releases/download/v2.2.8/fates200129.tgz

but got this error:

Last login: Mon Jan 6 00:07:30 2020 from 169.254.240.176

127.0.0.1 ~ $ cd ~/update

127.0.0.1 ~/update $ wget https://github.com/okyeron/fates/releases/download/v2.2.8/fates200129.tgz

–2020-01-06 00:11:11-- https://github.com/okyeron/fates/releases/download/v2.2.8/fates200129.tgz

Resolving github.com (github.com)… failed: Temporary failure in name resolution.

wget: unable to resolve host address ‘github.com’

127.0.0.1 ~/update $ packet_write_wait: Connection to 169.254.12.129 port 22: Broken pipe

so I tried to use Cyberduck to SFTP the update to the fates update folder but was unable to connect to the server as fates doesn’t show an IP address for my wired connection and norns.local did not work as an IP address.

#1229

Not sure. I’ll probably have to do some testing to see if I can replicate.

To check for power issues - via SSH check dmesg and look for undervoltage warnings (or other errors).

Check to see if your Teensy midi controller is set to Serial+MIDI - if so, try changing that to just MIDI instead and see if the same thing happens?

FWIW - port numbers in norns should not matter, but it might be good to check that the other unused ports are set to none

#1230

This is likely because the wired connection to your computer is not able to access the internet which might be on wifi? On a Mac you’d need to enable internet sharing to share the wifi. Not sure how that works on windows/linux.

Why it’s not connecting to wifi - not sure? Be sure you scroll far enough to right or left to get both upper and lower case letters.

You can troubleshoot network connections over SSH with the nmtui command line tool.

Your update errors seem related - probably due to not having a shared internet connection.

You would use the same IP address as SSH to SFTP (over the wired connection). What are you using for SSH?

#1231

Enabling internet sharing over the wired connection fixed everything. Update completed and can now update/add new scripts. Thanks so much!

2 Likes
#1232

Thanks for the info @okyeron
I am trying with a external usb hub.
3,0 usb hub does not work with fates (as far as i have tested)
2.0 usb hub works, but still crashes.

Im trying plugging the diy grid to a usb hub and that to port 1.
Teensy controller directly into port 2 of fates.

Template: Awake
No crashes

Template: Isoseq16
No crashes

Template: Iessconcepts
Crashes and doesnt allow midi map on port 2

Template: Ioom
No crashes

Template: Iessconcepts
Crashes and doesnt allow midi map on port 2

testing…

#1233

Have you plugged your midi controller into a computer and observed the midi traffic? Is it possible you are flooding the device with midi events?

#1234

FYI I have seen some dns failure with fates connected to Mac OSX (el capatan?) with internet sharing enabled. Rebooting fates resolves the issue.

#1235

¯_(ツ)_/¯

Are your hubs powered or not? Why not just plug everything into the Pi?

FWIW - An unpowered USB hub here works OK with a midi controller + neo-grid and lessconcepts. (although my neo-grid 256 is powered separately from usb).

Again - check your teensy midi controller to be sure its not set to Serial+MIDI - this is the most obvious that I can think of off the top of my head (although even then I don’t think this would cause an error, but who knows?)

Also - open Maiden and look for errors. If its streaming loads of errors that can cause things to appear locked up.

1 Like
#1236

Yes both hub are powered.

I did try plugging directly into the pi, thats why it thought it could be a power issue, and tried a powered hub.

I looked into the .ino file of the teensy controller and it was calling a SerialBegin so i deleted that.
I made sure it was only transmitting midi (there are few options midi *4 and midi * 16) but choose the first one.

I also made sure the diy monome was only transmitting serial.

So now i dont how as many crashes but sometimes i need to replug the midi controller and the script lets me midi assign to the control i want on fates.

Checked matron and it was not giving me any errors, apart from when i was starting fates with the grid connected and / or the midi controller on bootup, then supercollider will throw an error.

Ill keep on looking into it.

Many thanks!

Edited:

Less concepts works fine of with a novation launchcontrol :frowning:
Zellen works fine with a midi twister.

Im starting to thing the bug is either when a grid is connected (since i dont have this problem with scripts that dont use a grid) or the code on my teensy controller. :frowning:

#1237

What code are you using on the teensy?

#1238

Hi @JaggedNZ im using this code here:

I managed to find a work around though. Since im syncing all the gear to my ableton setup, and using the sevilla soft midi host to usb, im re-routing the midi control messages from the teensy controller to the fates using only one usb port.

Its working good so far!

Gracias!

#1239

Hi,

not sure whether this belongs here, but I am rather clueless about this matter:

As I am using Sonic Pi (SP) for live coding I am looking for an option to sync it with fates. SP is running on my laptop and can speak Midi (e. g. it can send a Midi clock signal).

As far as I see the first challenge would be to sync two midi hosts. Am I right?

My research so far here at lines shows, that MIDI USB-USB could be a solution. Can anyone confirm that?

Is it possible at all to sync fates (norns) to an external Midi clock signal?