Hi,
I would also prefer the RaspberryPi. Same reasons already mentioned by others.
And great to see work is still ongoing :)
Regards,
Espen
Hi,
I would also prefer the RaspberryPi. Same reasons already mentioned by others.
And great to see work is still ongoing :)
Regards,
Espen
Well, I was afraid of getting that feedback :-)
From an engineer point-of-view the BBB is so much better.
The used processor will be available at least until 2022 and the schematic + all layout files are freely available.
Somebody can easily build a clone or modify the design at their own needs. I've already done this and it works great...
So when it comes to repairability the BBB is much better than the RPI. But I highly doubt that you really want to replace BGA and QFN components on your own ;-)
There is also a very strong support on the SW side of the BBB. The mainline linux kernel supports BBB without patches. RPI has a custom kernel.
btw: I would LOVE if we'll have an option of a small hide away device that is able to transmit light and control commands over the ML received by IR from Beo 4,5,6, ONE etc.! This would be great for rooms where no compatible/capable B&O product is installed (e.g. Beolink passive, active etc.).
Yes, there will be a RJ45 connector for connecting the silver IR eye.
Do we want to use the buttons and LEDs also? Would require I2C and additional voltage-shifting...
Any idea whether it would be possible to go to audio-mode for airplay and for video-mode when playing videos via Openelc/Kodi. For me, the biggest advamtage is that this magic device would allow to turn the BV without remote.
Since this are all SW based things (as soon as the ML interface is working correctly) it should be possible with some hacking within Kodi.
Let's wait until the PCB is finished. I and maybe other too will surely write up their experiences and tipps and tricks here regarding this.
I'm thinking of providing a super slimmed down linux distro featuring shairport-sync and a little browser interface for selecting which link devices should be automatically activated when streaming airplay.
If we really go the RPI path I will totally ignore the mechanical HAT specification, for sure.
I'm sure that you also think that having all connectors on the backside (where already LAN and USB are) is a much preferable solution than having some on the side and some on the back...
This way I would be able to develop and 3D print a little case in the style of the Essence hide-away-box. :-)
Well, I was afraid of getting that feedback :-)
btw: I would LOVE if we'll have an option of a small hide away device that is able to transmit light and control commands over the ML received by IR from Beo 4,5,6, ONE etc.! This would be great for rooms where no compatible/capable B&O product is installed (e.g. Beolink passive, active etc.).Yes, there will be a RJ45 connector for connecting the silver IR eye.
Do we want to use the buttons and LEDs also? Would require I2C and additional voltage-shifting...
Hi,
i would also prefer the Raspberry Pi for the same reasons. The RPi 2 is also very efficient and uses also just 2,4 W if active. BT and Wifi could be added via nano USB plugs leaving still two free USB connectors so the addon board could be cheaper and it leaves some room for other components like A/D and /or D/A chips.
Location: Near Munich
My B&O Icons:
A summary of the final connectivity:
A summary of the final connectivity:
- 4x USB (RPI)
- 1x LAN (RPI)
- 1x HDMI out (RPI)
- 1x Aux-In (RCA conn.)
- 1x IR-eye In (RJ45)
- 1x PL Out (RJ45)
- NOT semi-balanced (blue wire tied to ground)
- NO DATA
- 1x ML (RJ45)
- ML Slave only. You might use the powerbox from BLC to gain Master support.
- ML audio output only.
- Data send and data receive
- barrel jack for power input (5V)
Okay, okay, I give up... No beagles. Only raspberries :-)
Regarding the connections: I don't care if usb is on the front and ML on the back of the box as I would install it somewhere out of sight.
But I do. Even where I can't see it I hate cable clutter that much... :-)
Oh, that's another idea: Would it be possibe to use an IR transmitter to send out infrared commands, too?
Okay, maybe an 3.5mm jack in PUC style where you can plug in a original PUC cable? I don't want to use RJ45 here because they are big and expensive...
What do you want to control?
But please only give up on that beagle thing! ;-)
yes, the cables need to be well installed, but I don't care if the cable is coming out of the front or back.
3,5mm jack is ok. No need for further complications. :-)
There's no simple infrared extension available that is capable of receiving/transmitting B&O ir signals! Light/Control to ML would be great! So I can use this receiver in a room without a Link speaker or B&O TV or B&O sound system to send Light commands from a Beo 4... to the MLGW/BLGW.
If it can send out/transmit IR signals, too, it would allow to control 3rd party devices like the jbmedia Lightmanager etc., too.
Endless possibilities... :-)
If it's just a software thing and it could control other infrared devices, too, it would be a welcome addition but for that we have the fine Lintronic box.
There's no simple infrared extension available that is capable of receiving/transmitting B&O ir signals! Light/Control to ML would be great! So I can use this receiver in a room without a Link speaker or B&O TV or B&O sound system to send Light commands from a Beo 4... to the MLGW/BLGW.
Yes, this is no problem when you connect that IR eye. If you have a ML cable in that room you can connect that device to, then everything is fine. If there isn't ML access in that room there is the possibility to transmit the control commands two a second one via WiFi which than is connected to the ML bus..
.If it can send out/transmit IR signals, too, it would allow to control 3rd party devices like the jbmedia Lightmanager etc., too.
Endless possibilities... :-)
Okay, I know what you mean. Last time I played with LIRC (the Linux IR software) the RPI had problems sending the 455kHz B&O carrier. Technically it should be possible but I didn't look too deep into it. Other IR signals with a lower carrier are no problem.
Yes, I will include one 3.5mm jack in PUC style.
BTW. My personal usage for this device is to replace the BM5 and connect a BS5 to it. I already programmed a little driver that understands the USB commands of BS5. Next step is to start with the UI. Will be done using QT embedded. But this has low priority at the moment.
You must be logged in as a BeoWorld member to post replies to forum threads.
Register to access the forums, reference material, and exclusive member benefits — including our monthly prize draw.
Become a Member