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
Dear all,
I was wondering if anyone had successfully captured the obsolete IR commands from the MCL 5500/6500 or the Beolink 7000 that relate to status, clock and timer settings? As you know these are not included in the Beo4 repertoire. The reason I ask is that I have a lintronic code converter and want to use my PC to set the clock and timer (fairly straightforward over the serial bus if you know the IR codes for the commands you want to send). Incidentally, if there are any lintronic users out there that are interested in how to do this I'd be more than happy to share tips and a bit of C code!
I used to have an MCL 6500 but stupidly sold it before analysing the IR codes! If anyone has managed to capture the binary/hex/ASCII data for these commands then I'd be really grateful if you could share them with me!
Best wishes
Luke
Not that simple I'm afraid; they are not simple commands, but long two-way conversations. For example, here's what happens when the MCP is used to set the clock to 12:34, then weekday stepped twice (you can only advance it, not set it directly) and then the result stored while the radio is playing:
Reading input from /dev/ttyUSB000001 0008:3E5B/2200002 0000:1E74:4012:F350/4700003 0008:3E5B/2200004 019E:22F0/2700005 0008:3E01/2200006 0001:9E06/1900007 0008:3E02/2200008 0001:9E06/1900009 0008:3E03/2200010 0001:9E06/1900011 0008:3E04/2200012 0001:9E06/1900013 0008:3E5A/2200014 0000:1E74:4012:F340/4700015 0008:3E5A/2200016 0000:1E72:2012:F340/4700017 0008:3E5A/2200018 0000:1E71:1012:F340/4700019 0008:3E0B/2200020 0001:9E07/1900021 0001:9E01/1900022 019E:2011/2700023 019E:2114/2700024 0000:0001:9E40:0002/3500025 0000:001E:E5FF:FE03/3900026 0000:0158/17
(the /xx part is the frame length in bits; command 00001 is the initial "clock" keypress from the MCP)
Same thing from a Beolink 7000, the date not modified but just checked:
00001 0008:3A7D/2200002 0000:01A6:6001:FF06/4300003 0008:3A58/2200004 0008:3A5B/2200005 001A:9400:0124:0020/5500006 001A:9401:1070:4130/5500007 0008:3A2F/2200008 001A:9400:0124:0020/5500009 0008:3A01/2200010 001A:9400:0000:1020/5500011 0008:3A02/2200012 001A:9400:0001:2020/5500013 0008:3A03/2200014 001A:9400:0012:3020/5500015 0008:3A04/2200016 001A:9400:0123:4020/5500017 0008:3A31/2200018 001A:9401:1070:4130/5500019 0008:3A00/2200020 001A:9401:1F00:4130/5500021 0008:3A07/2200022 001A:9401:1070:4130/5500023 0008:3A00/2200024 001A:9401:107F:0130/5500025 0008:3A04/2200026 001A:9401:1070:4130/5500027 0008:3A01/2200028 001A:9401:1070:4F10/5500029 0008:3A03/2200030 001A:9401:1070:4130/5500031 0008:3A0B/2200032 001A:9400:0123:4020/5500033 001A:9401:1070:4130/5500034 0008:3A58/2200035 0008:3A7D/2200036 0000:01A6:6001:FF06/4300037 0008:3A58/22
I wouldn't want to even try setting timers...
--mika
Ah, I was hoping that wouldn't be the case! Looks like I'm going to have to delve deeper into two way comms than I wanted to! Many thanks for posing back - the initial two way exchanges you've posted are really helpful.
with best wishes
These aren't completely hopeless to reverse engineer as the payload in the command frames is usually BCD coded and aligned to four-bit boundaries (to the trailing end of the command) - see for example the clock 12:34 and date 07-04 (7th of April) on the BL7000 status updates (commands 32 & 33).
The addressing and other stuff is far from obvious though, so you will really need to get one of the two-way remotes so you can try stuff yourself. I still believe it will be far easier to program something else to command the Beomaster at timed intervals, not the other way round.