ARCHIVED FORUM -- March 2012 to February 2022READ ONLY FORUM
This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022
"You think we can slap some oak on this thing?"
leosgonewild:Would it be possible to have a gramofon connected to the Raspberry, so that it would send a signal to turn on the system when the raspberry gets an audio signal via audio input? And also turn it off when the audio signal stops? That would make the gramofon a killer integration with B&O systems :)
That would make the gramofon a killer integration with B&O systems :)
No, with the BeoPi HAT this won't be possible.If this first version works as expected we may build a "server version" that includes an ADC and therefor would be possible to convert the analog audio from Gramofon to a digital stream that is distibuted to another Raspberry with a normal BeoPi HAT attached. Then it would be possible.This will take some time and I really hope that either spotify published the CONNECT API before this is the case...
A workaround would be to connect the Gramofon to the AUX from a TV or music system and let the BeoPi execute a macro that can be triggered via a webUI.
I'd be interested in one
My B&O products: Beosound 9000, Beosound 2300, Beosound Century, Beolab 8000, Beolab 6000, Beolab 4000 x2, Beolab 3500, Beolab 2000, Beolab 10, Beolink Active x2, Beotime, Beo5 x2, Beo4, A9 keyring x2, LC2 dimmer x6 and growing....
Hi,
just found this tread not sure how I missed it the first time, but I am interested in one of the units, as looking to gain control of my ML products with Bluetooth.
regrads
Toby
badgersurf: Hi, just found this tread not sure how I missed it the first time, but I am interested in one of the units, as looking to gain control of my ML products with Bluetooth. regrads Toby
no, you didn't miss it. The final PCB layout is still pending and I need to put about two evenings into it to get it finished.You are on the list - watch this space for updates...
BR,BeoMotion.
Very exciting to see this project still alive. If I understand it right, this would allow to use the ML "sense-in". So, I could play audio over my RPi and my BV would turn into audio-mode or I could play videos and it would turn the BV into vide mode. Pretty much like the BC2 does? This would be so great!
BeoMotion: Hi, no, you didn't miss it. The final PCB layout is still pending and I need to put about two evenings into it to get it finished.You are on the list - watch this space for updates... BR,BeoMotion.
It's good to hear from you. I will try to pick up where I left off with regard to decyphering the masterlink protocol as soon as I have some time - I seem to be experiencing a sucession of minor disasters at the moment which are preventing me from devoting any time to this, but I am still on board and will return to it as soon as I can.
Kind Regards,
Martin.
Hi all,
chances are looking good that I can finish the schematic and layout this weekend.
One important question for all that are interested in that piece of hardware:
How about switching from Raspberry Pi (RPI) to Beaglebone Black (BBB) ?
The major advantage would be that BBB supports a low-power suspend mode with super short wake-up time and a build in RTC.In general the used processor (TI AM335X) is more suitable for embedded usage and there is also an onboard emmc.The BBB consumes about 2.5 watt in active mode and 0.4 watt in suspend mode. Wake-up would be possible using incoming ML-commands, the RTC or a connected IR receiver.AM335X is also used by some current NL audio products...
Some of you asked about bluetooth.It is possible to integrate a BT module directly onto our PCB. Would add the possibility to wake-up the machine from standby using BT.There are 3 options of which we have to choose one.This one could be optional and left be unpopulated if somebody don't want it.
Feedback is very welcome!
I wouldn't recommend switching from raspberry to BBB because the raspberry is more famous and that means that it will be much easier to get spare parts in the future in form of unused/used raspberries! I don't like products that are not repairable. ;-)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.).
Same here, clear preference for the RPi. Much larger userbase and better support.
Fantastic to see the progress!
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.
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.
TWG: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...
steve1977: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. :-)
BeoMotion: Well, I was afraid of getting that feedback :-) TWG: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...
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.
Ralph-Marcus
A summary of the final connectivity:
BeoMotion: 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 :-)
TWG: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... :-)
TWG: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.
TWG: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..
TWG: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.
This all sounds like you are developing a module that B&O should buy from YOU! :-DI'm happy looking forward reading more about the progress. Hope you're able to solve the 455kHz problem, too - but it's not top priority. Receiving of the commands and sending them to the MLGW/BLGW is already nice enough!BeoMotion... that "BTW" thingy with the Beosound 5 makes me VERY curious! :-)))
Getting the 455KHz carrier is quite easy when a ceramic resonator is used (Intermediate frequency for AM receivers .
Gating the 455KHz with one gate from a quad NAND Gate (4011 or similiar), the remaing three could be used as the oscillator , gives a nice B&O IR transmitter when an IR LED is connected with a small transisor 'booster'. B&O used the same principal in the Beolink 1000 IR Remote. Circuit diagram. It is on the last page of the Datalink Manual iirc.
TWG:This all sounds like you are developing a module that B&O should buy from YOU! :-DBeoMotion... that "BTW" thingy with the Beosound 5 makes me VERY curious! :-)))
Well, maybe this is my way to overcome recent product strategies from B&O. I don't want to complain all the time but also try to make the good old stuff last longer ;-)
BS5 is one of my favorite B&O designs and I really don't want to see them dying with their BM's in future...Let's hope that the CCFL LCD's and those two always-on internal IR rotation sensors will last for a very long time.But first we need to get that ML/PL/IR interface up and running...
RaMaBo: Getting the 455KHz carrier is quite easy when a ceramic resonator is used (Intermediate frequency for AM receivers . Gating the 455KHz with one gate from a quad NAND Gate (4011 or similiar), the remaing three could be used as the oscillator , gives a nice B&O IR transmitter when an IR LED is connected with a small transisor 'booster'. B&O used the same principal in the Beolink 1000 IR Remote. Circuit diagram. It is on the last page of the Datalink Manual iirc.
Okay, thanks for that hint. The problem is that several years ago LIRC + RPI + 455kHz was working well. I think that was on the 3.12 kernel tree.On 3.18 I wasn't able to reproduce that. That is also some time ago and now we are on 4.2. Maybe now it works again without additional work. We'll have to see.SW based modulation is much better since then we can support all carrier frequencies with just one "PUC" out. Everything else would add extra cost and I don't really see the necessity here since we already have ML.
could this even turn a BS5E or an Essence into a ML device?
steve1977:could this even turn a BS5E or an Essence into a ML device?
In theory: yes.
You could use the line-out and the IR-in of those systems in combination with the BeoPi we are talking about here.But you would be limited to simple IR commands from link rooms. Something like CD, RADIO, STANDBY, PLAY, STOP which could be transformed into IR commands the Encore or Essence understands.
For the Encore I have something special in mind. :-) Do you own one?
BeoMotion: In theory: yes. You could use the line-out and the IR-in of those systems in combination with the BeoPi we are talking about here.But you would be limited to simple IR commands from link rooms. Something like CD, RADIO, STANDBY, PLAY, STOP which could be transformed into IR commands the Encore or Essence understands.
Sounds perhaps strange, but I would be interested in that solution if it means I can use the BS5 or BS5E with a beomaster 5500. The BM5500 cannot work as slave, and does not understand N.Music / N.Radio, so currently I see no option to control the BS5 from link rooms, and it is therefore on my "black-whish-list".
Thanks for the work so far, interesting hack!
Beosound 5 Encore + Beosystem 5500 + S45.2; BV7-40 MKV + BL7.1 + BL14.4+ AppleTV4; various link rooms with MCL2 A or MCL2 A/V + RL60.2 / CX100 / CX50 & Cona / IWS2000; BG4000; Beosystem 1200 + BV1600.
MJBeo: Sounds perhaps strange, but I would be interested in that solution if it means I can use the BS5 or BS5E with a beomaster 5500. The BM5500 cannot work as slave, and does not understand N.Music / N.Radio, so currently I see no option to control the BS5 from link rooms, and it is therefore on my "black-whish-list". Thanks for the work so far, interesting hack!
Yes, in theory this could work.BeoPi could act as audio master with BM5500 connected via IR and Line-In.BS5 could be slave and correspond to N.M and N.R.
Well, a lot of "could". Needs further testing when the PCB is ready.
BeoMotion: steve1977:could this even turn a BS5E or an Essence into a ML device? In theory: yes. You could use the line-out and the IR-in of those systems in combination with the BeoPi we are talking about here.But you would be limited to simple IR commands from link rooms. Something like CD, RADIO, STANDBY, PLAY, STOP which could be transformed into IR commands the Encore or Essence understands. For the Encore I have something special in mind. :-) Do you own one?
I don't own one yet. I own a BV and would really like to find a way to stream to it audio and turning it on automatically when doing so. Basically how my BC2 already works (start CD, audio turns on; start DVD, video turns on). I could do this with a BS5/BM5 (audio only), but I would need to put the big BM5 box somewhere. Also, Alac and video is not supported. So, I would hope that I could use the BS5E basically as a DLNA client, which can select music or videos (smiilar to the Creation 5 app, but wit the BS5E design). And by doing so automatically turn the BV on (and off). This would be the absolute killer!!!
steve1977:I don't own one yet. I own a BV and would really like to find a way to stream to it audio and turning it on automatically when doing so. Basically how my BC2 already works (start CD, audio turns on; start DVD, video turns on). I could do this with a BS5/BM5 (audio only), but I would need to put the big BM5 box somewhere. Also, Alac and video is not supported. So, I would hope that I could use the BS5E basically as a DLNA client, which can select music or videos (smiilar to the Creation 5 app, but wit the BS5E design). And by doing so automatically turn the BV on (and off). This would be the absolute killer!!!
Okay, now I didn't really get what you mean.You want to use the BS5 or BS5e user interface to select a video out of your library which then starts to play on your BV?Although both can be DLNA clients this is only possible for audio files.
It should be possible to connect a BS5e to the BeoPi (IR/audio) and use is as a ML based system. There would be some limitations. E.g. you would have to activate the audio sources always via remote since we cannot detect whether the BS5e is running or not.
It is also possible to integrate Kodi into that constellation. Than it would be possible to switch on the TV automatically on an incoming video or audio stream and set it to standby afterwards.
But selecting videos out of your library on the BS5 screen is not possible running the B&O SW.This would require a lot of hacking, programming and a single-board-computer with two HDMI outputs since we also have to render the BS5 display. Would maybe possible with a quad i.MX6. Would require much more time then I am able to put into it.
Got it, thanks for your reply.
Just to clarify. I do not want to have the video play on the display of the BS5/BS5E. Just want to use it as a DLNA device (basically like Creation 5 on the ipad) and output it to the BV.
If not possible, I am equally excited by sticking to Kodi on the RPi and having the BV turn on automatically (audio or video depending on what I play) would be absolutely outstanding. Kodi has already shariport implemented for airplay and is also a fully functioning DLNA device for both video and audio.
If you have other ideas how the Essence or BS5E can be used, I will be all ears. I really like both, but currently have no idea how to use them as they both have no ML, so cannot use them to automatically turn on and off the BV. Anything that you come up how to use the BS5E or the Essence will bring a high chance for me to buy one of them :-)
steve1977:Just to clarify. I do not want to have the video play on the display of the BS5/BS5E. Just want to use it as a DLNA device (basically like Creation 5 on the ipad) and output it to the BV.
... which would require a custom made BS5 UI and a second HDMI out... :-)
steve1977:If not possible, I am equally excited by sticking to Kodi on the RPi and having the BV turn on automatically (audio or video depending on what I play) would be absolutely outstanding. Kodi has already shariport implemented for airplay and is also a fully functioning DLNA device for both video and audio.
Yes, this will be possible.
steve1977:If you have other ideas how the Essence or BS5E can be used, I will be all ears. I really like both, but currently have no idea how to use them as they both have no ML, so cannot use them to automatically turn on and off the BV. Anything that you come up how to use the BS5E or the Essence will bring a high chance for me to buy one of them :-)
Currently I am thinking of replacing the RCA connector of line-in with a RJ45 PL-in. This way we could easily detect if the connected PL source is active. So in your case if the Essence or the Encore switches on their "speaker" we could "pipe through" this command and the audio to the BV which switches on.
Great work BeoMotion.
There's been so much activity on this thread today, I'm just catching up now
Having scanned through quickly, just some initial thoughts...
BBB vs RPi: I can see both sides of the argument so whilst with my tech hat on I would say BBB, from a userbase / initial demand for the interface point of view I'd say RPi. You're the one setting aside your time to design the PCB so ultimately it's your decision - you certainly wont receive any criticism from me either way (actually, this extends to the rest of my comments below too). Conclusion? None - I'm sitting firmly on the fence on this one
BeoMotion: There are 3 options of which we have to choose one.This one could be optional and left be unpopulated if somebody don't want it. BT/BLE only (add 15,-) BT/BLE + aptX for streaming (add 25,-) BT/BLE + normal audio streaming + WiFi (add 20,- / tradeoff would be that we would have to switch from emmc to normal sd)
There are 3 options of which we have to choose one.This one could be optional and left be unpopulated if somebody don't want it.
I'm not sure this is necessary on the BeoPi interface - I'm of the opinion it is best to concentrate on the B&O specific connectivity stuff. There are plenty of USB bluetooth and wifi receivers available that are tiny. Admittedly, APT-X support is an issue in linux though, so if a module were to be incorporated then option 2 would be my preference.
Regarding ignoring HAT spec, that is fine (although obviously we have to drop HAT from the name too as we're not allowed to call it a HAT if it isn't). I think given the amount of components and connectors you're trying to incorporate into the design and the complexity of the track routing, I'll be happy whichever side the connectors end up on!
Just a few questions/observations relating the above list:
Aux in - yes, having this as a powerlink in (with sense) makes sense to me, it's a change of connector and an additional level shift to gpio input (bearing in mind the voltage of this signal is not clearly defined so this would need to be allowed for).
The presense of a powerlink output, but lack of support for masterlink audio input confuses me. I can see it would be desirable in some circumstances to connect speakers direct to the BeoPi (link room use for example), but cant see any circumstances where having done this I wouldn't also want the ability to output to them what was on the masterlink audio bus. An ADC is not required here as the RPi doesn't need to sample the audio, just the ability to route the analogue audio from ML in to PL out (and of course adjust the volume). Please do let me know if there is a useage scenareo you think I'm missing here though.
Regarding IR eye input - if you decide not to support the buttons, then I would suggest opting for a 3.5mm stereo jack instead of an RJ45 as per some of the older B&O products, as only +5V, GND, and IR-in would be required and the jack connector will require less PCB real estate and should help to keep costs down.
Likewise with the PUC output, a 3.5mm stereo jack is fine, no need for 455kHz oscillator etc as that will increase cost and we have (in most cases) masterlink to communicate with other B&O products. If there later becomes a need to transmit 455KHz carrier IR and it is determined that this is still unreliable with current kernels or that range is insufficient as a result of inaccurate carrier frequency then there is always the option of building an external oscillator / modulator / IR emitter and then simply configuring LIRC to send unmodulated signals from the PUC output to this more sophisticated transmitter unit.
BeoMotion: steve1977:Just to clarify. I do not want to have the video play on the display of the BS5/BS5E. Just want to use it as a DLNA device (basically like Creation 5 on the ipad) and output it to the BV. ... which would require a custom made BS5 UI and a second HDMI out... :-)
Yes, although on your proposed replacement for the BM5 this could also be achieved quite easily without a second HDMI output - display cover art (in this case the movie cover) on the BS5 in the same way as is done for audio files, but also turn on the BV via masterlink and signal another RPi (which would be connected to the BV directly by HDMI) to start playing the video. The possibilities are endless...
I'll stop there as I am getting into things which are something to think about much later, so don't need discussing now!
Thanks again for all your efforts.
Hi Martin,
great to hear from you again.
The general idea is to have a PCB that sits beside the RPI with all connectors (ML, PL, IR, power) to the backside. This PCB should have a 40 pin male header connector on the left side.Connection between the RPI and the PCB would be done using a short 40 pin ribbon cable.This way we are also a bit more flexible when it comes to replacing the RPI with a different SBC.Even on a different pin layout you could still use single jumper cables for connecting...
I think that we should keep the RJ45 connector for the IR. I will connect I2C to it since I'm sure that the buttons might be a nice addition in some setups.
Regarding the ML audio input I'm still not conclusive. If we really want to have that input feature wouldn't it be better to have a separate ADC for it?This way there would be the possibility to build something like a streaming bridge on a later point.Would connect it's data out to both, the data-in and data-out of the pi using a data selector multiplexer like the SN74LVC2G157. So we could choose between sending the ML input to the DAC directly or to the RPI.
Additionally the more analog multiplexing we are doing the more the SNR degenerates. If final price wasn't a concern I even would put in a second DAC for PL only. TI has some really neat devices that even include small DSP's that could be used for EQ. This would also bring the possibility to play locally a different source than on the ML. But this would require a SBC with multiple I2S data-out's. I know that this is possible with TI AM335x and AW A20 but not with BCM on RPI.
Okay, maybe we are getting to technical now since this thread was meant to be only for general interest and feature request...
BeoMotion:The general idea is to have a PCB that sits beside the RPI with all connectors (ML, PL, IR, power) to the backside. This PCB should have a 40 pin male header connector on the left side.Connection between the RPI and the PCB would be done using a short 40 pin ribbon cable.This way we are also a bit more flexible when it comes to replacing the RPI with a different SBC.Even on a different pin layout you could still use single jumper cables for connecting...
Perfect - this removes some of the potential issues with regard to having to work within a pre-defined PCB footprint, and as you say, will permit greater flexibility with regard to choice of SBC.
BeoMotion:I think that we should keep the RJ45 connector for the IR. I will connect I2C to it since I'm sure that the buttons might be a nice addition in some setups.
Yes, if you are intending to route the i2c for the buttons, then the rj45 makes perfect sense (especially given with a side-by-side arrangement for the RPi and the BeoPi, the space occupied by the connector is less of an issue)
BeoMotion:Regarding the ML audio input I'm still not conclusive. If we really want to have that input feature wouldn't it be better to have a separate ADC for it?
Perhaps...
It is, as you mention, a better solution technically, as it would allow additional usage scenarios such as bridging (and probably others that we have yet to even consider) by allowing the RPi to actually sample the audio digitally rather than simply routing it between audio inputs and outputs (albeit, there would be a cost implication too).
My concern though, by whichever method this might be achieved, is that since powerlink outputs have been incorporated into the design, there will be an expectation that any connected beolab will be able to play audio from other sources on the masterlink network as well as local audio from the device itself (off the top of my head I can't think of any masterlink capable B&O audio device that does not support this), so lack of this functionality in a device which is primarily about masterlink connectivity feels like a fairly major ommision (to me at least, pehaps others may disagree?)
With additional functionality comes additional cost, and I'm a little concerned that we risk pushing the price point too high. I'm not sure how far you have already gone with the PCB component layout, track routing etc, and certainly don't want to throw a spanner into the works so my next suggestion may not be practical at this stage, but I'll throw it out there anyway - what are your thoughts about taking a more modular approach with multiple PCBs?
I'm thinking here that many of the usage scenarios could be achived with a subset of proposed feature set, so could be served by (for example) splitting the design into:
This would keep costs as low as possibly for those who do not require the full feature set (or who may want multiple RPi and interfaces within their setup each with a different usage scenario), whilst still allowing for a standard case design - perhaps with blanks or knockouts for the potentially unused connector locations. It also has the potential advantage of reducing digital noise introduced into the audio paths and improving overall SNR by introducing some separation between the digital and audio parts of the design.
I am though, as I have already mentioned, aware of the potential implications of introducing major changes to the design at this stage so I userstand you response is likely to be dictated by how far you have got with the PCB layout! Ultimately, you have my support whatever design decisions you take.
Yes, I like the modular approach, too. But at the quantity we are talking here the PCB itself is the most expensive part.Manufacturing 3 different PCB's the overall cost would be dramatically increased.
It is much cheaper to have only one PCB and maybe offer two versions of it.One can be full blown and the other only with populated parts for ML data and IR. Not populating some parts could save maybe 10,- to 15,- per PCB on the "budget" version.
Don't worry about digital noise in the analog audio signal.As long as there are split ground planes and a dedicated LDO for the analog part this never was an issue in my designs.
Currently I'm placing the components for ML data. Maybe give me a day to think about the ML-in / ADC stuff. I will also dive a little deeper into the datasheets of some codecs. Could be possible that a full blown codec with analog in/out gets cheaper and does the trick for us. Maybe I finde a nice one in the TI TLV320 range. If I remember right I also have an eval kit of such a thing.
I will also recalculate the price since we now have some more components and RJ45 connectors. Let's see but I think that we still end up in the 60...70,- range.
Beovision 12-65 NG, Beosystem 4, Beolab 7.2, Beolab 6000, Beolab 5, Beolab 4000, Playmaker, Beogram 5005, Beo4, Beo5, Beovision 7-32 MK3 (2x), Beovision 4.42, Beosystem 2 HD, Beolab 7.1, Beolab 7.4, Beovision 10-32, Beovision 6-26, Beosound Moment, Beosound 2300, Beosound Ouverture, Beogram TX2, Beogram 2404, Beomaster 3002, Beovox CX 75, Beovox CX 100, ibundo, Keyring.......
Although the buttons are nice, the RJ45 connector is a bit harder to solder at home - at least in my "workshop".
MJBeo: BeoMotion:I think that we should keep the RJ45 connector for the IR. I will connect I2C to it since I'm sure that the buttons might be a nice addition in some setups. Although the buttons are nice, the RJ45 connector is a bit harder to solder at home - at least in my "workshop".
No need to solder any connectors...
The board will come with an already soldered in RJ45 connector.You can then plug in an ethernet cable and cut off the plug on the other side.There the IR eye will be connected using its internal screw terminals.This is exactly the same way you would connect an IR eye to e.g. the BLC or BSys4.
Ah i did not know that, then it is fine