#1645

Recently built a fates and I’ve been having an issue with power. I’m using an rpi 4b with a Cana kit power supply rated at 5.1v with 3.5 amps. Everything works fine when I plug directly into the rpi and will run for about 30 minutes to an hour until the fates shuts off completely, goes dark suddenly. I have a grid attached and it will shut off no matter which script it’s running. Also, when I try to connect to the input for the power on the back near the ins and outs nothing turns on. Is my power supply an issue? Or something else? Would love help with this if anyone has some time!

#1646

Does the pi itself shut off? (Like the pi leds go out?)

Or is it just the display going off?

Are you able to SSH/SFTP to the device after it’s gone dark?

Did you solder the usb-c jack or was this an assembled board/kit?

Itd be good to check and see if anything is getting stupid hot to the touch when it’s powered up (like the voltage regulator up by the power inlet)

Have you checked for shorts on 5v?

#1647

The pi itself shuts off. Leds and screen go dark. I haven’t checked SSH when its down because it reboots within 5-10 seconds if still plugged in. I didn’t solder the USB-C jack, this was one of the pre-soldered kits. It do feel warmth when running, so I will take the case off and see if anything is too hot to touch. I haven’t checked for shorts on 5v, but will.

#1648

Ok - so if the LEDs go dark that’s the Pi freaking out and shutting off for some reason.

(EDIT - checking dmesg or other logs - /var/log/syslog - or journalctl might be a good idea to see if there’s an error triggering the shutdown)

FWIW - The hot question is more like “damn that’s hot” rather than “warm”.

Pi header pins might be suspect. Give those a good inspection and maybe reflow?

something def fishy if the fates USB-C power jack is not working at all. Do you have some other USB-C cable or PSU to test with by any chance?

#1649

When I purchased a Pi4 I also did buy some heat sinks like these. Currently I am not using my Fates much but I’ve never had any problems so far. Maybe worthwhile to try.

#1650

Thank you for the tips. I ordered another Pi power supply to try out, and just realized I didn’t install the heat sinks. I also reflowed, so I’m going to see if that helps.

1 Like
#1651

Update 200424

If you are on a version prior to 200218, DO NOT USE SYSTEM > UPDATE.
You must update manually via SSH. Instructions are on the release page: https://github.com/fates-project/norns/releases/tag/2.4.0

If you are on 200218 or later
use SYSTEM > UPDATE while connected to the internet.
(please report back if you have problems with this)

General Norns update notes and info about this release are on the norns release post here Norns: update 200424

Aside from those updates, this release should improve HOTSPOT functionality on Fates.

15 Likes
TimeParty
#1652

The System > Update worked for me (I was updating from the immediate previous version). Thanks for all you do!

3 Likes
#1653

SYSTEM > UPDATE somehow not responsive for me, but manual update worked without issue.

Thanks.

1 Like
#1654

SYSTEM > UPDATE worked for me updating from 200328.

4 Likes
#1655

Buttery smooth SYSTEM > UPDATE (from 200328) :slight_smile: Thank you!

2 Likes
#1656

Another seamless system > update here too. Thanks!

#1657

SYSTEM > UPDATE (from 200328) worked on my end. :pray:

#1658

Another seamless SYSTEM > UPDATE (also from 200328)!

#1659

Done. system>update from 200328 works fine. thanks

#1660

I can help with this…even add some CV input. But i need help with the software part. I`m clueless with something so complex.

#1662

my fates isn’t recognizing any midi device. just started today. i have a usb20midi (usb to din midi cable), Nanokontrol2, and bluetooth keyboard connected. Aconnect isn’t showing any devices. Im on 200424. the most recent thing i did was today i updated cheat codes, pedalboard and compass. i usually have my launchpad pro plugged in to use as a grid, which normally caused the devices to not be recognized on startup, but after a reboot they would always show up. I haven’t had that connected for about a week though.

#1663

reboot with devices unconnected. Reconnect devices. Try aconnect -l again

Go to SYSTEM>DEVICES>MIDI and try to set them all to none. Try reconnecting MIDI devices.

Probably best to try just one device at first. then add others. Could be one is being extra stupid? Could also be the midigrid script causing problems if you’re using that.

1 Like
#1664

just did for the maybe 5th time. this is what maiden says when running your midi debug script

Summary 
metro_stop(): pthread_cancel() failed; error: specified thread does not exist

# script load: /home/we/dust/code/midi-demo/midi-devices.lua

# cleanup

# script clear

ERROR (i2c/hp) failed to write

pset >> write: /home/we/dust/data/system.pset

# script run

>> reading PMAP /home/we/dust/data/midi-demo/midi-devices/midi-devices.pmap

m.read: /home/we/dust/data/midi-demo/midi-devices/midi-devices.pmap not read.

Engine.register_commands; count: 0

___ engine commands ___

___ polls ___

amp_in_l

amp_in_r

amp_out_l

amp_out_r

cpu_avg

cpu_peak

pitch_in_l

pitch_in_r

# script init

-midi.list-

-midi.devices-

-

-

-midi vports-

1 table: 0xd3eab0

2 table: 0xd74f40

3 table: 0xd74f18

4 table: 0xd74dc8

1: none

2: none

3: none

4: none

-

-midi device details-
#1665

oh shit i did update midigrid too. thats probably it, thanks

soon i will build that neotrellis grid and i won’t have to deal with this anymore

EDIT* i thought deleting the new midigrid script would help but it didnt. still having the same problem. even when i remove all instances of midigrid