Sign in   |  Join   |  Help
Untitled Page

ARCHIVED FORUM -- March 2012 to February 2022
READ ONLY FORUM

This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022

 

Obsolete IR codes - setting the clock an a beomaster 7000

rated by 0 users
This post has 3 Replies | 1 Follower

L Spad
Top 500 Contributor
Brighton
Posts 271
OFFLINE
Bronze Member
L Spad Posted: Sun, Apr 7 2013 10:08 AM

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

tournedos
Top 10 Contributor
Finland
Posts 7,357
OFFLINE
Bronze Member
Moderator
tournedos replied on Sun, Apr 7 2013 11:59 AM

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/ttyUSB0
00001   0008:3E5B/22
00002   0000:1E74:4012:F350/47
00003   0008:3E5B/22
00004   019E:22F0/27
00005   0008:3E01/22
00006   0001:9E06/19
00007   0008:3E02/22
00008   0001:9E06/19
00009   0008:3E03/22
00010   0001:9E06/19
00011   0008:3E04/22
00012   0001:9E06/19
00013   0008:3E5A/22
00014   0000:1E74:4012:F340/47
00015   0008:3E5A/22
00016   0000:1E72:2012:F340/47
00017   0008:3E5A/22
00018   0000:1E71:1012:F340/47
00019   0008:3E0B/22
00020   0001:9E07/19
00021   0001:9E01/19
00022   019E:2011/27
00023   019E:2114/27
00024   0000:0001:9E40:0002/35
00025   0000:001E:E5FF:FE03/39
00026   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/22
00002   0000:01A6:6001:FF06/43
00003   0008:3A58/22
00004   0008:3A5B/22
00005   001A:9400:0124:0020/55
00006   001A:9401:1070:4130/55
00007   0008:3A2F/22
00008   001A:9400:0124:0020/55
00009   0008:3A01/22
00010   001A:9400:0000:1020/55
00011   0008:3A02/22
00012   001A:9400:0001:2020/55
00013   0008:3A03/22
00014   001A:9400:0012:3020/55
00015   0008:3A04/22
00016   001A:9400:0123:4020/55
00017   0008:3A31/22
00018   001A:9401:1070:4130/55
00019   0008:3A00/22
00020   001A:9401:1F00:4130/55
00021   0008:3A07/22
00022   001A:9401:1070:4130/55
00023   0008:3A00/22
00024   001A:9401:107F:0130/55
00025   0008:3A04/22
00026   001A:9401:1070:4130/55
00027   0008:3A01/22
00028   001A:9401:1070:4F10/55
00029   0008:3A03/22
00030   001A:9401:1070:4130/55
00031   0008:3A0B/22
00032   001A:9400:0123:4020/55
00033   001A:9401:1070:4130/55
00034   0008:3A58/22
00035   0008:3A7D/22
00036   0000:01A6:6001:FF06/43
00037   0008:3A58/22

I wouldn't want to even try setting timers...

--mika

L Spad
Top 500 Contributor
Brighton
Posts 271
OFFLINE
Bronze Member
L Spad replied on Sun, Apr 7 2013 12:38 PM

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

Luke

tournedos
Top 10 Contributor
Finland
Posts 7,357
OFFLINE
Bronze Member
Moderator
tournedos replied on Sun, Apr 7 2013 12:53 PM

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.

--mika

Page 1 of 1 (4 items) | RSS