Hi,
PIbakery Setup is done, PI is connected to the beocreate and rechable in the own WLAN, but the guides setup hangs with "Searching"
http://www.bang-olufsen.com/recreate/setup/
Are there any checks on the Pi via SSH possible to verify the installation, check the health oth the beocreate or do the setup manually?
The board is connected to a cx100
Thanks, P
Hi!
Sorry to hear you are having troubles with the setup. There are multiple points where things might've gone wrong. Let's start with these basic checks. If you need help with anything or things don't go as expected, let me know.
Can you SSH to the Raspberry Pi at the address beocreate-4ch-blank.local? If not, try raspberrypi.local, or the IP address if you can find it out. Log in with the default password raspberry – change it if you want.
Step 1: Check that the necessary files are in place
When you get in, type ls to list the contents of /home/pi/. At least the following files (except the ones I've dimmed out) should exist (note that the version of Node may differ). If they do, it would indicate that the setup has indeed downloaded all of the required files. Skip to step 2, if the files are there.
If instead you only see beocreate-installer, check its contents by opening it in a text editor. Type nano beocreate-installer. The file should begin with the following:
#!/bin/bash
echo "BeoCreate Installer, 2017 Bang & Olufsen"
If instead of this you see a bunch of HTML code and references to Dropbox, we need to download the file and run it manually.
Exit the text editor with Ctrl-X keyboard shortcut.
Please then run the following commands to download and run the automated installer manually:
Sit back and let the installer do its thing, which will take a while (we've seen anything from 10-30 minutes, depending on internet speeds). At the very last, you should see:
Base installed. The installation is ready for guided setup. Rebooting now.
The Pi should automatically reboot and if the issue has been resolved, setup should begin in the setup tool and you don't have to go to step 2 here.
If the installation finished but the setup tool still does not do anything, SSH back into the Pi (it should now be called beocreate-4ch-blank.local) and check step 2.
Step 2: Check if the BeoCreate server is running on the Raspberry Pi
A server runs on the Raspberry Pi to communicate with the setup tool. To check if it's running, type sudo forever list in the terminal. An output like following means that the server is running:
If you get something else, please let me know here and we can figure out what are the next steps to solve it.
All the best,
Tuomas from Bang & Olufsen
Whoopsie, I accidentally uploaded the same image twice (and for some reason, I can't get my edits to save). Here's the correct output for step 2:
Best,
Tuomas from Bang & Olufsen
Hi,
I am able to access the pi via SSH and the Beocreate server seems run run
but still the guided Setup does not start and hangs with searching the device.
Any further hints? Thanks, Pat
Thanks.
Which operating and operating system are you running?
Best,
Tuomas
Am using windows 10 and tried several Browsers to start the setup
/Pat
Thanks.
Currently to use the setup under Windows, you need to install Bonjour Print Services from Apple, which allows the PC to connect to devices on the network by name. Download here: https://support.apple.com/kb/DL999?locale=en_GB
I recommend using Google Chrome for setup.
In an upcoming release of the setup tool we will support connecting using an IP address, so that it's no longer mandatory to install that software.
Best,
Tuomas
setup started after installing Bonjour Print Service, but then int hangs in stage inst. sound profile...
/Pat
I tested it also with different Browsers (including Chrome) but the process hangs after BT Install in the stage
"inst. sound profile..."
Are there further hints available?
Thanks, Pat
Hi Pat,
I apologise for the delay. I created a fresh installation of the 4-Channel Amplifier here to troubleshoot your case and I found two possible issues you might've experienced.
Issue 1: Some packages failed to install
This happened to me, which prevented building the background daemon that talks to the sound processor.
Check if you need to fix this before moving on to issue 2. Run:
If you get output like the following, with paths following the command name, all is good here and you can skip to issue 2.
cmake: /usr/bin/cmake /usr/share/man/man1/cmake.1.gz
Otherwise, follow these instructions. First, let's clean the package manager, update the package lists again and install the missing packages:
Then, let's build the background daemon that talks to the sound processor (notice the space and period after cmake):
Issue 2: A bug in the server software for CX100
Even if you didn't see issue 1, issue 2 will definitely be there waiting for you.
The second issue is a bug that causes the server to get stuck into a loop: after the sound profile has been installed, the setup will just begin again. This is due to the CX100 being a 3-way loudspeaker and requiring different crossover settings, which weren't correctly saved, and the server would crash. When that happens, the server is automatically restarted, hence the loop.
I have uploaded a fix for this. We install it by stopping the server, removing the old server files and downloading new ones in their place (be careful with the rm command!):
Finally, reboot the Pi (sudo reboot) and you should be good to go – the guided setup should begin again, and this time it should go all the way through.
Please let me know if you hit any more roadblocks.
Best,
Tuomas from Bang & Olufsen
Hi Tuomas,
I used your fix from issue 2 and the guided setup started working, thanks for this.
But know I have a problem in using the cx100.
It is accessibel technically by bluetooth and raspotify, but there is no sound output.
Is there a option to check the health and the output of the board and speakers directly from the pi by commandline?
Thanks, Pat
Hi Pat,
good to hear that we're getting forward!
Do you hear a startup tone when the loudspeaker boots up? It should be two short tones like in other B&O connected/Bluetooth speakers. Additionally, there may be clicks/pops as the components activate (these will be fixed). If not, here are some steps to troubleshoot – the streaming services should be working OK. If yes, the issue is with the streaming services and I'll write more instructions to troubleshoot those.
There are things you can check from the command line:
Check if the 4-Channel Amplifier is seen by the system. Run aplay -l (lowercase L). An entry with HiFiBerry DAC should appear on the list. If you see it there, run alsamixer to see which sound device appears as a default. It should open up with the same HiFiBerry DAC as the current sound device. It should say that the selected device has no mixer controls.
If all is well until this point, try playing a locally stored sound file through the loudspeakers. Run aplay /home/pi/Music/startup.wav (this is the startup tone) and see if sound comes out.
After these, I would check if there is a sound program running on the 4-Channel Amplifier. You need to physically access the board for this.
With power on, look for a small green LED on the board (not on the Raspberry Pi). It should be labelled D2. This light is on when a program is running on the DSP. A red light should also be seen in the optical output connector. If you don't see the light, the program is not running.
Locate a two-pin connector/jumper labelled "selfboot". Is it currently closed with a jumper? It should be closed for the DSP to automatically load the stored program. If it's not, bridge the jumper and reboot the system.
If all of it checks out until this point – none of the listed commands return errors, the green light is on – try this:
First disconnect the selfboot jumper from the board.
With the speaker plugged in, access the setup tool from the web. The main menu should open.
Go to Sound Profile menu and select the CX100 profile to install it again.
When the programming is complete, you can replace the selfboot jumper. After this, reboot just in case. As said, a startup tone should be heard.
Does this do anything? If you get the startup tone, I would suggest trying a quiet song from Spotify or via Bluetooth – the volume control with these has been known to be spotty, something we hope to address soon.
Best,
Tuomas from Bang & Olufsen
Hi Tuomas,
Thanks for sending the next steps.
First, there is no startup sound when I boot the system, just a click in the speaker when the power is turned on.
aplay command and alsamixer show the correct hifiberry dac, but aplay does not output a sound.
All LEDs on the board are off and there is no red light in the optical output. The selfboot jumper is closed.
Are there more steps to check?
Thanks, Pat
Hi Pat,
thanks for checking things out. Indeed it sounds like there isn't a program running on the DSP. Did you already try reinstalling the Beovox CX100 sound profile through the setup tool?
Best,
Tuomas from Bang & Olufsen
Hi Tuomas,
yes, the reinstall of the sound profile has been done. But there is still no sound and also no LED on the board.
Regards, Pat
Hi Pat,
let's try narrowing down the problem some more, and try reinstalling the sound profile via command line (just in case the UI is doing something wrong). For this, we need to first compile another piece of software:
Now we can to manually type commands to the DSP. Run:
./SigmaClientTool 127.0.0.1 write_eeprom /home/pi/dsp/beovox-cx100.xml
This should show the following output:
Initializing connection to 127.0.0.1
Writing /home/pi/dsp/beovox-cx100.xml to EEPROM
SUCCESS
If it fails, try the same command again, just in case. If successful, try the following:
/home/pi/bin/sigmareset
This should reset the DSP and make it load the program from memory – if there is one, in which case the lights should come on and you should be able to play sound. If you hit a roadblock again, let me know.
Best,
Tuomas from Bang & Olufsen
Hi Tuomas,
there is still no sound and there are still no lights after reinstalling the soundprofile manually.
Anything else I can check?
Thanks, Pat
Hi Pat,
this could be a hardware issue. I spoke with Daniel from HiFiBerry, they will follow up with you on this issue.
All the best,
Tuomas from Bang & Olufsen
Hi Pat,
what power supply are you using?
Best regards,
Daniel
Hi Daniel,
I am using a 20V 3.25A power supply.
Best Regards,
Pat
Hi Daniel,
is this power supply sufficient?
Best Regards, Pat
Hi,
the power supply is ok. Let's test with a simple image. Please download and install this image and boot from it:
http://downloads.hifiberry.com/images/beocreate-test.img.zip
Best regards,
Daniel
Hi,
I booted with your image, but nothing changed.
As I can see on the screen
but there is still no LED lighting on the beocreate board and there is also no sound.
Any other tips to solve this?
Best Regards,
Pat
i was trying to install the software with the newest raspian version from novemver 2017 and with the script from the 2. post...
but i was unable to start the setup....
then i tested the file from http://downloads.hifiberry.com/images/beocreate-test.img.zip
and also the http://downloads.hifiberry.com/images/beocreate.img.zip (build on 2018-02-06) so it is farely new..
bot versions are running but im always unable to start the setup after estabvlishing the connection to the beosetup ssid.
tested on 3 windows 3 mashines and 2 different android smartphones.
is there anything i can try?
on my firewall i also created an rule with service= any for the connection from and the conenction to the raspberry.. which is not required for the setup over the beosetup ssid.... :(
Hi Christian,
at present to use the setup tool on Windows, you will need to install Bonjour Print Services from Apple, which allows the PC to discover devices without an IP address. Download here: https://support.apple.com/kb/DL999?locale=en_GB
I recommend using Google Chrome.
With Android you're currently out of luck.
I apologise for the suboptimal situation – we're working to find a better solution to this. In the meantime I will try to help in any way I can.
All the best,
Tuomas from Bang & Olufsen
Thanks for the tip. With the bonjour plugin i was able to connect and start the setup of the Board.tomorrw i will attach some test speakers and play a bit with signa.
Hi,
I have been experiencing the same problems as pgluke and still no sound. To recap:
Installation script run and terminated smoothly. All files in place. Beocreate server is running. Setup page works without problems.
I can connect via bluetooth, Shairplay, etc without problems
Green led on board is on.
No sound, even if feeding through the optical input or playing the startup.wav with aplay. No startup tone is heard through the speakers either.
I have tried re-installing the sound profile (generic stereo speakers in my case) to no avail.
Speakers are connected on the 30W outputs
The system was working properly until I downloaded and installed the last beocreate image; it then stopped working, so maybe the amplifying stage is not the issue here. I have tried re-downloading and re-installing several times without success, so whatever went wrong, it is very persistent.
Please help me, I have already run out of workarounds and ideas.
Cheers
Hi Ignacio,
sorry you are having issues.
Do you have your amplifier and Raspberry Pi properly separated with spacers? In a v1.0 board, there is a reset jumper under the HDMI port. The metal in the HDMI port can bridge the jumper if spacers are not used, preventing the amplifier from starting up.
If you are not using spacers, you could put some tape on the reset jumper pins so that the HDMI port can't make contact with them. I actually had this issue with a system I was setting up and didn't have proper spacers, and was very puzzled why the amplifier wouldn't start up.
This issue has been corrected in a later hardware revision.
EDIT: The aforementioned placement for the reset jumper is for the beta boards, and was corrected for production models. My apologies for misinformation.
Best,
Tuomas from Bang & Olufsen
Thanks!
Yes, spacers installed.I believe that's not the problem. In fact it was working fine in the past. No changes in hardware since then.
Can you confirm what is the configuration for jumpers JP 3 & 4 defining the sampling rate? I have been able to get some output by removing them.
Is it also possible the DSP was not using the Mute jumper in previous versions of the full range profile?
My board is one of the Beta lot. I did experience the shorting thing with the HDMI but fixed it with spacers.