mattb wrote:

Hi all, I just came across this and read this thread and the technical one. I'm very interested in a PCB to connect to a RPi. In fact, I would take two. The idea I'm having is to connect a Raspberry to the BLC and read Masterlink data. I could then control my Yamaha AV-receiver for Internet Radio and Spotify, the audio is already connected to the BLC line in.

@BeoMotion: you mentioned you have some initial python code to interpret masterlink telegrams. Did you put that on github or somewhere else yet?

kind regards, Matt

Hi Matt,

Welcome to beoworld and thanks for your interest in this project.

Decoding of the ML protocol is still at a very early stage - once I have an interface to work with and can start injecting telegrams into the ML network it should become easier to make progress on this. So far I have just worked with some sample data that BeoMotion logged whilst performing various actions with the connected equipment.

Nothing is on github yet, but I'll upload a tgz to the technical thread now in case you or anyone else wants to take a look.

Kind Regards,

Martin.

Hi,

thanks a lot for uploading the perl decoder, riverstyx!

Unfortunately the current ML PCB is not fully functional.
The transmitter part isn't working. I have not that much time at the moment for debugging but I will come back to this.
Also the pinout of the RJ45 connector isn't correct although I have checked everything at least twice.

I'll post the schematics of the non working PCB later this day. Maybe someone can see the problem without wasting a whole day for debugging.

BR,
BeoMotion. 

BeoMotion wrote:

thanks a lot for uploading the perl decoder, riverstyx!

No problem - there's still loads of stuff to figure out, even with the current relatively small data set, and like you I am struggling to find much time to work on this at the moment. I will make some time to carry on with this in due course but by making the code public it gives others the option of contribute if they are able and so inclined. The current 'tree of switch/case statements' is messy but covers all of the TELEGRAM_TYPE, PAYLOAD_TYPE, PAYLOAD_VERSION combinations seen so far (and will flag up any new ones encountered as new telegrams are added to the data set) and thus gives a place to add comments for each as their meaning are determined.

BeoMotion wrote:

Unfortunately the current ML PCB is not fully functional.
The transmitter part isn't working. I have not that much time at the moment for debugging but I will come back to this.
Also the pinout of the RJ45 connector isn't correct although I have checked everything at least twice.

I'll post the schematics of the non working PCB later this day. Maybe someone can see the problem without wasting a whole day for debugging

Sorry to hear this. It proves you were right to take the decision to limit the first prototype to data only but I know this will be of little comfort right now. I'm happy to work my way through the schematic to see if I can identify anything as sometimes a different set of eyes can save hours - this is often the case with finding bugs in code too as it's easy to repeatedly read what you intended to write rather than what you've actually written!

Kind Regards,

Martin.

riverstyx wrote:

I'm happy to work my way through the schematic to see if I can identify anything as sometimes a different set of eyes can save hours - this is often the case with finding bugs in code too as it's easy to repeatedly read what you intended to write rather than what you've actually written!

Hi Martin,

yes this would be really great!
I've uploaded the current schematic as a pdf in the technical thread. 

Thanks a lot.

BR,
BeoMotion. 

Unfortunately, I have no capabilities and talent in coding or engineering, so won't be able to help. Having said this, please let me know if you need help with testing. Also, it may be worth to put the financial burden on more shoulders and I am happy to contribute. Others of the beiworld community may follow. OR you even go with kickstarter?

Hi,

I would also take 2, potentially 3. One question, though: do you think it would be possible to communicate with Beolink Wireless as well or is anyone else working on that?

The main reason why I am asking is, because I am also considering a project were I would try to realise something like the LC2 using an Arduino. If Beolink wireless communication is possible, the light controllers wouldn't need their own IR receivers.

Regarding the electronics I am afraid that I can't offer any useful help. But if you need help with designing a casing and making 3D CAD drawings of that, I am happy to contribute and make them accessible for customisation and 3D printing (I'm not a professional, but it wouldn't be the first time I'm doing it).

Okay, great. Thanks for the feedback.

Yes, I also thought about crowdfunding but I think it is a bit to special.

First thing now is to get the DATA PCB up and running.
Unfortunately I haven't had the time until now for debugging.
Hopefully there will be some hours left for that next weekend.

I'll keep you posted on the progress.

Yes, 3D printed cases would be the way to go on such a small series.
So I'm sure you could help and contribute some nice STL files to the project as soon as the size of the PCB's are final :-)

BR,
BeoMotion. 

Great, just let me know when you have some more input on that 

Great, just let me know when you have some more input on that 

Hi all,

finally I was able to find some time to hook up a scope and do some investigations.
The ML transmitting part is perfectly working, which are indeed very good news. :-)
The level shifter was the problem.   

There are also some other minor design changes to do and then I will send out a second prototyping PCB for manufacturing.

Will keep you posted.

BR,
BeoMotion.