JP1 Remotes

If you want to try searching for other OBC codes that may control the CM-7004, download the RemoteMaster software ( http://www.hifi-remote.com/forums/viewtopic.php?t=101110 ) and then use Advanced->Import Binary Upgrade to import the V1518_PL.bin file for the CM DVR+. The Setup protocol shows NEC1 ...

Another thought is to modify the Xiaomi MiBox to accept a different IR protocol. I usually see NEC1 in the android remote.conf files posted in this forum. NEC1 is probably easier for the MX-500 to learn.

I made a new version v0.22c at same place http://www.hifi-remote.com/forums/dload.php?action=file&file_id=25218. This version replaces the calls to SETRTS/CLRRTS with SETDTR/CLRDTR in jp2_14connect(). The timing of the signal matches the original waveform seen on the RTS pin.

The first versions ...

You can look at this project by user Barf, http://www.harctoolbox.org/arduino_nano.html, if you are handy with a soldering iron.

#amlogic NEC remote
factory_code = 0xFE010001

I believe this means NEC1 device 1.

The key_begin section maps the IR keycode(OBC) into a Linux keyboard function.

0x15 139

This means OBC=31 will map into function 139 which is Menu.

So convert the file into some format that IrScrutinizer will ...

Thanks for the pointers. There is a I2C driver on the Pi. It isn't difficult to bit bang things on the Pi. There is a wiringPi library with C, Python interfaces.

I think others have run RM/RMIR on the Pi itself but I haven't looked into it much.

Can you post pointers to what files you used? I have a Raspberry Pi and URC-6131 EEPROM remotes and may be interested in making it work with the RPi.

I believe you are making the Arduino act like a EEPROM Protocol Adapter(UART on one side and SDA/SCL on the other side).

Thanks.

Here is a protocols.ini entry that will look for HEX=62 and replace it with 55 and set repeat count to 30.

[Kaseikyo (30 repeats on OBC185)]
PID=01 F8
VariantName=slingbox
DevParms=OEM1=84,OEM2=87,Device:4=5,Sub Device=88,Leadout(mS):20|33 only 40 bits!|70|44=3
DeviceTranslator=Translator(4,8,0 ...

So we can probably add code in so when you use a certain OBC/Hex byte, it'll switch to using 30 repeats instead of the standard 2 repeats. This would be your long OK virtual button. You would still be able to use the short OK button as well.

Sorry about that. I copied the wrong entry in protocols.ini to start with.

[Kaseikyo (30 repeats)]
PID=01 F8
VariantName=slingbox
DevParms=OEM1=84,OEM2=87,Device:4=5,Sub Device=88,Leadout(mS):20|33 only 40 bits!|70|44=3
DeviceTranslator=Translator(4,8,0) \
Translator(lsb,comp,0,8,8) \
Translator ...

I created the following protocols.ini entry(only shown if Options->Show slingbox protocols enabled) that sends out 18 repeats with a total time of 2026ms. If you want to change the number of repeats, just change the 12h=18 decimal in the sequence E6 0D 12. If you want 16 repeats, E6 0D 10 ...

It is not difficult to create a bin with only the "select" function assigned to a button. You can do it in RemoteMaster.

I think you want a slightly modified protocol that loads a higher repeat count so that when you click on the select virtual button, it sends out the select OBC for around 2s.

I looked at the RMDU files for mode 1 and mode 2.

mode 1 RMDU file refers to JB chip. I selected PL chip to match mode2 RMDU file.

mode 1 uses Kaseikyo 162-42 with device code 8.23 and G values.
mode 2 uses Kaseikyo 162-42 with device code 8.55 and G values.

Both use the built-in 00F8 protocol id ...

The previous posts on this receiver pointed to this thread http://www.hifi-remote.com/forums/viewtopic.php?p=104061#104061. This last thread mentioned the upgrade as having 3 repeats. Normally, the Slingbox upgrades are treated like macros and 2 repeats are used.

Are you using the upgrade with 3 ...

The voltages on the pins swing from 5V(High signal) to 0V(Low signal). Even if RESET pin starts out at 0V, the rising voltage from 0V to 5V will cause the remote control to reset.