RuneAudio Forum

Hi,

If this may help someone in debugging its startup/shutdown scripts, here is the led sequences for a fully functional Sabre V3+power button setup on a RPI 3, using the scripts described in audiophonics-i-es9023-sabre-dac-v3-tcxo-raspberry-pi-2-0-a-t3277.html#p12548 (but Frank scripts given in the present thread should work as well, if not better)

Hardware start (power button)
- the white led of the power button blinks slowly (~1 s) + the red led on the RPI board turns on steadily,
- the blue led the Sabre board turns on in a steady manner,
- the white led on the power button becomes steady.

Hardware stop (power button pressed for more than 0.2 s and less than 4 s)
- the white led of the power button starts blinking slowly (~1 s) + the red led of the Sabre board turns on steadily (in addition to the steady blue led being on since the startup),
- the blue & red leds on the sabre board turn off,
- the white led on the power button and red led on the RPI board turn off.

Software stop (Rune GUI "Power off")
- the white led of the power button starts blinking fast (~0.5 s),
- the blue led on the Sabre board of turns off,
- the white led on the power button and red led on the RPI board turn off.

Software reset (Rune GUI "Reboot")
- the white led of the power button starts blinking very fast (~0.25 s),
- the blue led on the Sabre board turns off,
- the red led on the RPI board remains on,
- the blue light on the Sabre board turns on,
- the white led of the power button becomes steady.

Note that in every sequence the green led of the RPI board is turning on and off "randomly" once the red led of the RPI board is on, denoting read/write on the SD card.

Regards,

Lionel

Bruno.dualo wrote:So to summarize, here is how to make the OLED 16x2 works on a Audiophonics RaspDAC V2 (I-sabre V2 DAC ES9023) with a Raspbesrry 2 (be aware I'm talking about RaspDAC V2 not V3) with RuneAudio.

First wired the RaspDAC and the OLED like shown in this page:
http://forum.audiophonics.fr/viewtopic.php?f=4&t=1492

Update your RuneUI:
how-to-update-the-runeui-via-git-t547.html

If you get a message:

Code: Select all

error: Your local changes to the following files would be overwritten by merge:
(...)
Please commit your changes or stash then before you can merge.


Then if you know your changes you can use

Code: Select all

git reset --hard

or otherwise

Code: Select all

git stash

Run a git pull once again:

Code: Select all

git pull
curl -s -X GET 'http://localhost/clear'

Then:
set a softlink to python2

Code: Select all

ln -s /usr/bin/python2 /usr/bin/python

install GCC

Code: Select all

pacman -S gcc

install RPIO.gpio

Code: Select all

wget https://pypi.python.org/packages/source/R/RPi.GPIO/RPi.GPIO-0.6.2.tar.gz
tar zxvf RPi.GPIO-0.6.2.tar.gz
cd RPi.GPIO-0.6.2
python setup.py install

get the python script and uncompress it
download/file.php?id=587

Code: Select all

tar zxvf 16x2_oled_runeaudio.tar.gz

copy this file

Code: Select all

cp 16x2_oled_runeaudio.py /usr/local/bin/

Register the script as a service, to launch it at startup:

Code: Select all

nano /usr/lib/systemd/system/oled.service

Copy the following in the file:

Code: Select all

   
[Unit]
    Description=Audiophonics OLED Service
    After=mpd.service

    [Service]
    ExecStart=/usr/bin/python /usr/local/bin/16x2_oled_runeaudio.py
    ExecReload=/usr/bin/kill -HUP $MAINPID
    KillMode=process
    Restart=always
    RestartSec=10
    StartLimitInterval=30
    StartLimitBurst=20

    [Install]
    WantedBy=multi-user.target

Enable the service

Code: Select all

systemctl enable oled.service

Start the service

Code: Select all

systemctl start oled.service

Many thanks Franck!
If I have forgotten something, tell me and I will add it.

before I start messing around, can this be used for V3?
Not sure if the pinout is same etc.

Thanks to @Bruno.dualo for great simple HowTo guide and thanks to @Frank for updated python script for V3 board

So all is working perfectly now. Power button and OLED screen, everything.
Actually it works better than what Audiophonics have done with Volumio.
With runeaudio and this I have all the track information from Tidal streams displayed correctly
Happy days



edit: here is the python scrip for V3 DAC

Happy to hear you got it all working! I am glad you persevered through this endless thread, LOL..

PeteB wrote:Happy to hear you got it all working! I am glad you persevered through this endless thread, LOL..

this and long? THis is nothing. Go to forums like OnePlus which I use to moderate.
Some of the threads have hundreds or thousands of pages
This is a little thread

I still need to find a way to edit some bits in this python.

I would like to change the switching time between artist-title and also I would like to see IP address on display instead of runeaudio.local

rikardo1979 wrote:I would like to change the switching time between artist-title and also I would like to see IP address on display instead of runeaudio.local

search for "hostname --fqdn" and replace it with "ip route get 1 | awk '{print $NF;exit}'". This should display the IP instead of the hostname. The script is written a little strange. Wonder that the RasPi still has the time to play music.

rikardo1979 wrote:

PeteB wrote:Happy to hear you got it all working! I am glad you persevered through this endless thread, LOL..

this and long? THis is nothing. Go to forums like OnePlus which I use to moderate.
Some of the threads have hundreds or thousands of pages
This is a little thread ...

True, but that is why I no longer spend my time in certain corners of the web, LOL. Anyway... I meant the effort you put into getting RuneAudio to work on your hardware, and the number of posts it took, and, just trying to be funny, which is hard to do while I am typing (!)

I just hope the next person will not have to start over, when this thread gets buried...

PeteB wrote:

rikardo1979 wrote:

PeteB wrote:Happy to hear you got it all working! I am glad you persevered through this endless thread, LOL..

this and long? THis is nothing. Go to forums like OnePlus which I use to moderate.
Some of the threads have hundreds or thousands of pages
This is a little thread ...

True, but that is why I no longer spend my time in certain corners of the web, LOL. Anyway... I meant the effort you put into getting RuneAudio to work on your hardware, and the number of posts it took, and, just trying to be funny, which is hard to do while I am typing (!)

I just hope the next person will not have to start over, when this thread gets buried...

then is just a matter to bring it up and link those together
Once is here, its here And as now runeaudio is best for proper sound I not going to leave
I will be around and pain in a...

But all the credits go to Frank and others from this community as I was just following instructions. If they are not here I would have nothing.
And Volumio guys are really unfriendly. I mean the developers and the community is none existent there...
Keep away from there

rikardo1979 wrote:...
And Volumio guys are really unfriendly. I mean the developers and the community is none existent there...
Keep away from there

I've been reading some of the threads, and I notice a definite chill in the air, which is sad.

I think there is an extra hurdle to overcome with RuneAudio, because most people (including me) get stuck on the differences between Arch and Debian and its forks. I don't just mean the command line, but getting something like a simple 2-line display to work becomes a project... >

I think there is an extra hurdle to overcome with RuneAudio, because most people (including me) get stuck on the differences between Arch and Debian and its forks. I don't just mean the command line, but getting something like a simple 2-line display to work becomes a project... >

same here. So far I always used raspbian/debian so coming to Arch is a bit like landing on Mars
I am pretty lost in it