Ruark Vita Audio R2i & R2 remote control IR codes for universal remote

[rh100605]

Does anyone have the IR remote codes for the Ruark-Vita audio R2i so that I can program a universal remote with a laptop and the YS-IRTM infrared to serial (eBay) ? The same board can be used to "read" remote codes.

I have already published the Remote codes for the Ruark R4i on eevblog.
Now I would like to help the community by publishing other Ruark remote control codes  so those who have lost their remotes can program a universal remote such as the "one for all Contour" universal remote URC1210 / URC1240 or the Geemarc TV10

The NEC 38khz codes for the R2i all start with 0x86 6B  and follow a pattern very similar to the R4i. So Preset 1 is 0x86 6B 01 and power is 0x86 6B 1E
Pej has agreed to post on EEVblog how to use the Source Forge program RMIR to load these to any JP1 universal remote control. More details later

If the long push on Presets and Info does not work remember that older IR receivers are sensitive to Electronic ballast high frequency Fluorescent lighting, creating pulses in the null fields sent on a long button push..

[rh100605]

Update 11th June 2023 - The actual Ruark R2i Remote codes

I received from Pej  a list of the learned Hex command codes that RMIR reported after uploading the remote via the JP1 serial port using the program RMIR.
After downloading Java , I downloaded the RMIR ( Remote master) program from Source Forge.

I had previously made the Contour remote learn some of the R4i codes using the instructions that came with the remote.
So I started RMIR coupled to the JP1 connector and FTDI USB to serial converter and downloaded the Contour 4 urc1240 remote data.

Connections:- Look for the dot on pin1  More detail http://www.hifi-remote.com/wiki/index.php/JP1_Cables
1 - (empty):VDD   2 - Yellow:RTS   3 - Black:GND  4 - Green:TXD    5 - (empty)  6 - White:RXD
Blue:CTS (not connected)  Red:5V (not connected)

The Contour remote R4i learned codes had Device 143 sub device 239 which in Hex is 0x8F and 0xEF .
The listing Pej sent started with device 134 and sub device 107 So I tried 134/107 or 0x86 and 0x6B as the fixed device code in the YS IRTM transmitter from eBay.

The PEJ listing Hex command codes (18 of them) did not work, however I started at 0x86,6B,00 then 01,02 etc to see if they had any effect on the radio.
E.G using the program Realterm (which is needed to send hex) + the eBay YS IRTM board send A1,F1,86,6B,0A for DAB as the source.

Nineteen codes worked on the Ruark / Vita R2i that corresponded to the 18 buttons on the remote and Mute
A very similar layout to the R4i !!!
Hex Function  RMIR Hex cmd
01   Preset 1       7F
02   Preset 2       BF
03   Preset 3       3F
04   Preset 4       DF
05   Preset 5       5F
06   Info             9F
07   Left/down    1F
08   OK              EF
09   Right/up      6F
0A   DAB            AF

0C   Aux1/2        CF
0D   IPOD           4F
0E  Volume dwn  8F

12  Clk/Alarm     B7

1A  Audio           A7
1B  FM               27

1E  Pwr on/off    87
1F  Volume up    07

FF  Mute            00

So what is RMIR reporting as Hex commands. The secret is in the NEC Protocol
We were much closer then either of us thought, you needed the Hex version of OBC as the last code !

The Hex command code is in NEC1 format. The binary has first to be reversed then inverted, I found this by looking up OBC to Hex command conversion on Google.

For example
Clock    B7 (1011 0111) reverse (1110 1101) invert 0001 0010 or 0x12 . Total code 86 6B 12
Preset1 7F (0111 1111) reverse (1111 1110) invert 0000 0001 or 0x01.  Total code 86 6B 01
Preset2 BF (1011 1111) reverse (1111 1101) invert 0000 0010 or 0x02.  Total code 86 6B 02

Now to see if RMIR (Remote Master IR) program can take these codes and put them into the one for all remote using the JP1 serial link which is explained in a post by pej

Note that RMIR uses decimal when entering the One Button Codes (OBC) and the device / sub device numbers.
Clock would be Device 154, Sub device 107, OBC 18. i.e 0x86 6B 12 in decimal

[pej]

Intro:
There seem to be quite a number of R2 / R2i's missing IR remote controls. Neither have I seen remotes for sale. The Ruark remotes look as if they are glued together and so do not know what is inside.  I provide a replacement solution that uses readily available Contour One for All. Contour learnt all the functions and allowed me to build setup code 2000 for R2 / R2i using no other equipment other than a UART for interfacing to a computer.

The Contour is a stunning remote control that includes a remote learning function (provided you have the original).  But I found the performance of the learnt functions good, but a little inconsistent.  If you don't have the original remote you are really stuck because Ruark/Vita is not listed on code list provided with this remote. I recall only Logitec might offer Ruark IR it is discontinued.

Older R2:
There is a slight oddity with this solution. So it may not be technically perfect. (Solved - see next post) The original Ruark remote fully works BOTH R2 and R2i models, but the Contour (One for All) will ONLY works fully the R2i. Press and hold does not work on the older R2.  That means, for example, you cannot use the Contour remote to store a station in pre-set memory or scroll up and down volume or stations by holding button on remote. You need to use the R2 Rotordial for push and hold.  But it is still very useful to have for R2 and gives full access to 3D Sound and Audio settings which are not on the R2 Rotordial.  The Ruark R2 and R2i remotes look almost identical apart from the the first two (top LH) buttons which are labelled 3D and EQ while R2i is labelled Clock and Audio respectively.  IR Hex codes are the same respectively.

There has been some confusion over Hex codes and OBC with rh100605, partly because I have never done anything like this, but am learning! This solution never used OBC codes but Fig 3 shows them.  Now I know how they are worked out.

Software:
As mentioned above, you need RemoteMaster from SourceForge and it requires Java Development Kit dependency.  Within RemoteMaster there are three programs - RMIR, RMDU and RMPB.  RMIR and RMDU are used here.

Hardware:
You will need a Contour / Contour 4 / possibly Contour 8 (8 not tested).
As mentioned above,  underneath the Contour battery cover you will find a 6-pin connector which is a JP1 interface.  Pin 1 should be identified with a careful look at the PCB silk screen.

You need a USB UART with flow control running at 38400 bps connected to the JP1 interface.  The JP1 is fussy with the UART used - CP2102 did not work, I gather FT232RL works.  Bus Pirate has FT232RL within - I had to use this.

Bus Pirate (you don't need to do all this if you are not using Bus Pirate), (Windows Device manager is all you will need with conventional USB UART).
So I used Bus Pirate which I detail here - Bus Pirate is a bit fiddly to set up and you will probably use something simpler. I use Tera Term SW as a terminal for setting up Bus Pirate (Tera Term SW not needed for a conventional USB UART setup).

Bus Pirate (BP) Setup:
   Contour remote JP1 interface connections to BP

                  BP
                  GND
                  |
               -------------------
         |   5   3   1                |
         |   Contour Remote     |
         |   Pin Nos                |
         |   6   4   2                 |
               -------------------
             |   |   |
             BP   BP   BP
       MISO   MOSI   CLOCK


Plug in Bus Pirate to computer USB
Win device manager - initial port speed setting is 115200 bps
-------------------------------------------------------------------
Tera Term software settings I used -
serial USB com port (COM1)
setup/serial port - speed 115200 & 'enter new setting'
-------------------------------------------------------------------
In Tera Term terminal - press enter - HiZ
then enter the following for setting the mode and final bit rate:
m  -   3 UART
   7 38400
   1 8 Data bits and parity (default)
   1 stop bit (default)
   1 Idle 1 (default)
   2 Normal (H=3.3v,L=GND)(H can be up to 5.5v)

b  -   7 38400
-------------------------------------------------------------------
In Tera Term window menu - setup/serial port - speed 38400 & 'enter new setting'
Win device manager port settings set speed to 38400
-------------------------------------------------------------------
In Tera Term terminal - space to continue - UART>

In terminal enter (3) - this is UART with flow control
   UART Bridge
   Reset to exit
   Are you sure? - enter 'y'
-------------------------------------------------------------------
Bus Pirate is ready to go configured as a 38400 bps UART with flow control.
Close Tera Term (otherwise it will conflict with RMIR) and open RMIR

Using RMIR/RMDU software:
Firstly download the contents of the Contour Remote.  I just found pressing the download button works if all is connected/setup correctly.  This download brings up the menus you need.

Next click on Devices (Fig 1) and then new - that will take you to RMDU Device Upgrade Editor (Fig 2).

On the Setup page (Fig 2) I entered NEC1 protocol Device 134, Sub Device 107. The fixed data and protocol ID should take care of themselves and show the values below. I used default setup code 2000 and I selected AMP (for Contour 4, or TV for Contour).

Under the functions menu (Fig 3) I recall adding the Ruark remote key name to the corresponding hex code shown below and in Fig 3.

Under the Buttons menu (Fig 4) I recall dragging the Ruark remote key names (as just entered above) to the function column.  This is where you make a choice as to which button on the Contour remote does which function of the Ruark remote.  And it seems quite flexible.

Move on to the layout menu (Fig 5) and you will see a picture of the Contour remote and the keys used.  You will also see a few extra Contour keys highlighted, but not assigned (eg 6 to 9 and mute). These highlighted keys appear to be a feature of how this software works, they all have 00h assigned and they all mute the R2i - added bonus that is not on original remote!

The key map (Fig 6) just shows an map of the Ruark keys against the Contour keys.

Recap:
For Ruark Vita Audio
1. Setup
Device       134
Sub Dev      107
Prot       NEC1
Fixed Data      20 9E 29
NEC1 Protocol   PID 005A

2. Enter HEX & name under function
   B7   A7   87
   Ck   Au   On/Off



   7F   BF   3F
   1   2   3



   DF   5F   9F
   4   5   Info



   1F   EF   6F
   Bk/Dn   OK   Fwd/up


   AF   27   07
   DAB   FM   Vol up


   CF   4F   8F
   Aux   iPod   Vol dn

3. Under buttons drag and drop to assign as you wish.

I uploaded the above to the Contour remote.  Unplugged the JP1/UART connection.  Press the AMP button (because I have Contour 4)  press setup and enter code 2000 just like you would for any other alternative IR product. All worked perfectly on R2i as far as I could make out.

Conclusion:
If you have just the single device Contour URC1210, you need to select TV (not AMP) on the set up page of the Upgrade RMDU software (Fig 2).

Indeed there has been confusion between Hex and OBC (Fig 3 shows both).  Confusion as to what device and sub-device values are, what is the fixed data?   I am new to all this and learning. How rh100605 figured it out is amazing. Perhaps I should have posted this earlier.

The above Hex values came, from the learnt function of the Contour Then Contour was connected to the RMIR software to reveal those values. No OBC values were used.

The software did not recognise Contour (URC1210), but selecting Contour 4 (URC1240) worked fine.  Single device Contour URC1210 does have phantom buttons which allow you to have more than one device!  I find this interesting but not investigated it. These Contour remotes are quite clever particularly when connected to a PC.

As stated earlier I found the learned values a little inconsistent in performance, so entering them manually as an upgrade resolved this.  I found only learnt codes got older R2 fully working including press and hold, but did not know how they differed to the manually entered codes or what was missing.

Hoping there is enough here to get remotes working with R2 and R2i with many thanks to rh100605 for encouragement.

[pej]

In the post above I said the Contour 4 remote solution may not be technically perfect - it does fully work Ruark R2i and only partially works older R2.

I discovered the Contour's IR signal was a little fast in timing by just 1.03%.

There is a fix for the remote push and hold for the older Ruark R2.  This will still also work the R2i by bringing the IR waveform timing much closer to the original Ruark remote which fully works both Ruarks R2 and R2i.

These additional steps are what I did:

Within RMIR click on devices (Fig1).

Double click on NEC1 to bring up Protocol editor (Fig2).

Change the following uSec times by adding 1.03% to them:
1 Burst ON - 564
OFF - 568
0 Burst ON - 564
OFF - 1706
Lead-in ON - 9086
OFF - 4542
Lead-Out OFF - 108988

This is important to do in this order (as there is a bug in the software), go the PF Details tab (Fig3) and then click update and OK.

Download to the remote and all should work.

This timing issue and bug was raised here:
http://www.hifi-remote.com/forums/viewtopic.php?t=103333

This is my full working solution here:
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=26773
but you will need to sign in.

This is the JP1 owner's full solution which happens to work without changing anything:
http://www.hifi-remote.com/forums/dload.php?action=file&file_id=26769
But again you will need to sign in

Many thanks to rh100605 for the support to solve this.