Fates - a DIY norns DAC board for Raspberry Pi

jamisnemo · 2020-01-19T21:16:06.998Z

I asked in a comment to your PR adding the STLs to the fates3d_case repo, but I’ll ask here as well:

Can you please upload your Fusion 360 files that have the usbc port and the 4th encoder hole?

Thank you!

pfig · 2020-01-20T23:44:30.417Z

It’s alive! I was terribly nervous as this was my first serious electronics diy project, and on my first go I soldered both headers on the wrong side of the board, but it all seems to work. Woohoo!

pfig · 2020-01-21T09:21:03.730Z

Has anyone ran into these:

error: load fail when loading ash/playfair, moln, step
error: missing ZSines when loading we/test/fonts

Cheers!

JaggedNZ · 2020-01-21T09:53:32.679Z

playfair requires Ack to be installed.
Moln requires ‘r’
Step requires Ack, but gets stuck on loading screen? Expects a grid?

And not sure why the font test requires an Sc engine… Norns big?

zebra · 2020-01-21T10:21:51.937Z

JaggedNZ:

not sure why the font test requires an Sc engine

pushed a fix for this. (answer: b/c it used to be that all scripts required one, but indeed ZSins is an extremely arbitrary choice)

Gregory_Delabelle · 2020-01-21T07:39:28.072Z

For some reason fates does not accept this diy arc and shield sees it as a Grid.

Running Orca on a WW works without a problem…

What could I test?

The diy arc project is here

GitHub

Another thing is I would like to know if there is any information when the image for a rpi4 will be available for the shield. On fates it is available and working fine.

tehn · 2020-01-21T13:40:02.640Z

from the github:

Please note: if you encounter a problem, please do not post on the monome forums ! Tehn will surely help you, but I don’t want my clone to cause them trouble and work. I’m very happy that they make their protocols open and I would like them to continue to do so in the spirit of openness.

but i’m going to contradict this— i can’t help— i actually have no idea how the DIY arc works and i don’t have time to go figure it out— i am focused on the core ecosystem which benefits everyone.

Gregory_Delabelle:

any information when the image for a rpi4 will be available for the shield

elsewhere, yes, please read the thread. it’s not a huge priority for us because we’re never planning to design anything that leverages the extra CPU power of the pi4, as the actual norns hardware uses a CM3.

please remember that most new features on norns are a product of volunteer effort.

jamesbretz · 2020-01-21T13:45:18.645Z

The one I built worked absolutely fine with Fates and Ansible, with no modifications to either. Have you confirmed it working elsewhere, i.e. Max? Did you follow the instructions for assigning the serial number and made sure it was the proper length and format?

Gregory_Delabelle · 2020-01-21T13:48:29.562Z

Yes, step by step.
I don’t know where to search atm. Now I can’t access the FTDI chip because i think when you program the serial it’s blocked. Maybe make another USB board and check if all is OK. So stupid i sold my original arc 4 and that 3 years ago. Then I could compare…

okyeron · 2020-01-21T15:14:50.046Z

Gregory_Delabelle:

if there is any information when the image for a rpi4 will be available for the shield. On fates it is available and working fine.

The fates disk image is built from the stock raspbian Buster release (which supports pi4), while the norns images are built from monomes own custom linux branch. That Monome branch is meant for maximum compatibility with the norns hardware first and then the new shield.

Pi4 requires a different set of compile instructions than pi3 due to the different processors used.

If I had more time available I’d try to recompile the various linux sources for pi4 + shield, but life is a little too busy for that right now.

Gregory_Delabelle · 2020-01-21T16:15:07.905Z

I respect everybody who is working on these fine products like norns / Fates / Shield and fully understand.

Many thanks for the joy of playing with these

okyeron · 2020-01-21T20:32:52.731Z

UPDATE WARNING

Update 200121 has been released

Once again, do not run the on-device SYSTEM>UPDATE - it’s not compatible with Fates at the moment.

I will post an updater with modified script later today (January 21, 2020).

EDIT:
UPDATER HERE:
https://github.com/okyeron/fates/releases

disquiet · 2020-01-22T02:11:28.939Z

You are awesome, sir.

michael_matos · 2020-01-22T02:19:12.838Z

I updated my fates using the latest firmware posted about. I used cyber duck to drop it into the update folder. Then I removed the wifi dongle and went to system/update where it found the file. Updated and it got to completed, then blank screen. After a few minutes of blank screen I powered off, then back on. Still blank. The led in the front is lit though. What did I do wrong? How can I fix it? Thanks!

okyeron · 2020-01-22T02:21:58.004Z

Can you be more specific? Which firmware? The one from monomes GitHub or the one from my link above (the fates GitHub page)?

If the former, you’re hosed and will need to reinstall from disk image

FWIW - I’ve not tried the method you described to update.

michael_matos · 2020-01-22T02:24:38.428Z

The one just posted in this thread. Retracing my steps, I may have been confused by the update instructions. Was it drop it in the update folder, then follow the instructions after the ssh version?
Version 200221

okyeron · 2020-01-22T02:27:44.419Z

The update should be done via SSH. Instructions on the update release page above. If the directions are confusing please let me know how I can make it better.

Not sure what to suggest. I can try to help troubleshoot in DM in about 30 mins.

michael_matos · 2020-01-22T02:30:20.607Z

Gotcha. I misread the instructions as sftp or ssh. Not sftp then ssh. Will try to reinstall the disk image. Thanks. Sorry for my poor comprehension.
Update. All fixed. Reinstalled and updated as per instructions. Thanks again.

Synesthesia · 2020-01-22T11:55:45.979Z

Hello ! how can i get a pcb for this project ?

coreyr · 2020-01-22T12:25:08.126Z

Check the first post, info there.