jiangsu cable tv remote

chuliu · Post by **chuliu** » Sun Jun 14, 2015 9:09 am

I uploaded the file for jiangsu cable tv remote.
Please help create an rmdu file.
Irscope failed to recognized the protocol.
Thanks.

http://www.hifi-remote.com/forums/dload ... e_id=13420

The buttons are 0-9 respectively.

Post by **The Robman** » Sun Jun 14, 2015 2:37 pm

Nobody will want to work from a text file like that, so please upload an .IR or .RMIR file.

3FG · Post by **3FG** » Sun Jun 14, 2015 9:59 pm

Since you seem to have captured these with a IRWidget, you should be able to upload an *.ict file. For me, at least, that's better than a RMDU file.

chuliu · Post by **chuliu** » Mon Jun 15, 2015 1:20 am

3FG wrote:Since you seem to have captured these with a IRWidget, you should be able to upload an *.ict file. For me, at least, that's better than a RMDU file.

Thanks. I will upload ict soon.

chuliu · Post by **chuliu** » Mon Jun 15, 2015 9:00 am

Here is the ict file
http://www.hifi-remote.com/forums/dload ... e_id=13421

the command in order are :

1. power
2.＋
3. -
4. vod
5. nvod
6. info
7. menu
8. exit
9. up
10. down
11. left
12. right
13. ok
14. cancel
15. display
16 .prev page
17. next page
18 .interact
19. audio
20. 0
21. 1
22. 2
23. 3
24. 4
25. 5
26. 6
27. 7
28 .8
29 .9
30. help
31. fav
32. red
33. green
34. yellow
35. blue
36. tv

3FG · Post by **3FG** » Mon Jun 15, 2015 10:46 pm

Here's an RMDU file. You'll need to revise the button assignments.

This protocol is similar to the one described in this thread. The framing is also seen in UEI executor 01FB:2 which is available in RCRP05B, OARI06G, and OARUSB04G, although the Jiangsu protocol seems to have 16 bits of variable data, while 01FB:2 has 8 bits.
Jiangsu IRP = {38.0k,182}<3,-3|3,-6>(20,-10,Dev1:8,Dev2:8,Dev3:8,20,-10,F:8,G:8,3,^108m,(20,-20,3,^108m)*)

chuliu · Post by **chuliu** » Tue Jun 16, 2015 6:56 am

I cannot open the file, the error message is no jiangsu protocol.

chuliu · Post by **chuliu** » Tue Jun 16, 2015 11:01 am

Can anyone help me with it?
The rmdu file I cannot open, error was no jiangsu protocol.

I tried to build a manual protocol from scratch.

command structure cmd-dev
dev bytes:3
bits/dev: 8

command bytes:2
bits/cmd:8

1:(546,-1092)
0:(546,-546)

lead-in style: same every frame
mid-frame burst:yes
after bits:24
lead-in on 3640
lead-in off 1820

lead-out style:oneon,lo
lead-out off:108000
off as total:yes

I have some confusion:
1 I don't know how to incorporate mid-frame burst, specifically after bits 24( I assume lead in doesn't count as bits) 3640, -1820.
2 I don't know how to make dev and cmd bits LSB.
In manual protocol of remotemaster, I cannot make the change

3FG · Post by **3FG** » Tue Jun 16, 2015 11:36 am

Sorry,
I forgot to post the entry to add to protocols.ini so that RMIR can open the RMDU file:

Code: Select all

[Jiangsu]
PID=01 EF 
DevParms=Dev1:8=87, Dev2:8=89, Dev3:8=88 
DeviceTranslator=Translator(lsb,0,8) Translator(lsb,1,8,8) Translator(lsb,2,8,16) 
FixedData=00 00 00 
CmdParms=OBC:8=0, OBC2:8 
CmdTranslator=Translator(lsb,0,8) Translator(lsb,1,8,8)
DefaultCmd=00 00
Code.S3C80=43 8B 32 8B 16 CF 44 08 08 01 11 02 12 01 11 00 FA D2 DC 07 1C 03 70 FF FF FF 19 77 77 F6 01 46 F6 01 0A 7B 01 AF E6 20 06 E6 21 E0 E6 28 C0 57 76 46 29 01 8D 01 46

chuliu · Post by **chuliu** » Tue Jun 16, 2015 12:09 pm

Thanks I got it to work.
But can you explain to me if I were to do it with a manual protocol, How would I proceed?

You can do that by answering my questions posted above.

Thanks.

3FG · Post by **3FG** » Tue Jun 16, 2015 12:57 pm

Quoting from the thread I linked above:"Setting bit W7.3 enables a mid-frame burst (same as the lead in) after the initial PD13 bits."

I don't really know how to use manual protocols, but I think you can make Dev parameters LSB on the Device Data tab of the Manual Settings dialog. I suppose that you'll need to reverse the bits for command data by hand.

chuliu · Post by **chuliu** » Tue Jun 16, 2015 5:42 pm

3FG wrote:Quoting from the thread I linked above:"Setting bit W7.3 enables a mid-frame burst (same as the lead in) after the initial PD13 bits."

I don't really know how to use manual protocols, but I think you can make Dev parameters LSB on the Device Data tab of the Manual Settings dialog. I suppose that you'll need to reverse the bits for command data by hand.

Can you elaborate on setting bit w7.3 enableds a mid-frame burst(same as lead-in) after PD13 bits? How to I set bit w7.3?

Also, for some reason, even I have set device byte to 3 and command byte to 2 and I see device 1,2,3 and command 1,2 in the device data tab. I cannot click LSB checkbox. It is untickable.

chuliu · Post by **chuliu** » Tue Jun 16, 2015 5:55 pm

Also, can you please tell me how you get the entry in protocols.ini?
I opened protocols.ini and at the beginning, there was some explanation to the script language it uses. I haven't spent much time reading it but reading the entry for jiangsu, I can guess what it is doing.

Is there any tool, like km or pb to generate the code?
Or we need to type it by hand?

Also, I don't know how to get ir engine code:
code.s3c80=xxxxxxx

Thanks.

3FG · Post by **3FG** » Tue Jun 16, 2015 10:21 pm

To see the Samsung assembler code that sets bit 3 of register W7, load the upgrade into RMIR, and click on Jiangsu in the Device Upgrade Editor. That will display the code. Generally, to make custom executors one needs to understand the Samsung assembler. I like to use RMIR directly, but others use Protocol builder.

I'm not aware of a manual for making the entries in protocols.ini. I think you just have to start trying to write entries based on the examples form existing entries and from the descriptions at the beginning of the file.

chuliu · Post by **chuliu** » Tue Jun 16, 2015 11:08 pm

3FG wrote:To see the Samsung assembler code that sets bit 3 of register W7, load the upgrade into RMIR, and click on Jiangsu in the Device Upgrade Editor. That will display the code. Generally, to make custom executors one needs to understand the Samsung assembler. I like to use RMIR directly, but others use Protocol builder.

I'm not aware of a manual for making the entries in protocols.ini. I think you just have to start trying to write entries based on the examples form existing entries and from the descriptions at the beginning of the file.

Thanks.
I read on vicky's infrared signal for beginners and she mentioned that the only midframe burst that can be built into protocol builder without additional assembler is the one that has on pulse like the oneon pulse and silence equal to lead in silence, so in the case, the midframe burst is 3640,-1820, but not 546,-1820. I cannot use a simple manual protocol to do the job. Am I right?

So regarding the protocols/ini entry, even though I understand the code in jiangsu protocols.ini entry prior to "Code.S3C80=43 8B 32 8B 16 CF 44 08 08 01 11 02 12 01 11 00 FA D2 DC 07 1C 03 70 FF FF FF 19 77 77 F6 01 46 F6 01 0A 7B 01 AF E6 20 06 E6 21 E0 E6 28 C0 57 76 46 29 01 8D 01 46"

but to handle mid-frame burst, one need to know assembler to come up with the code above, is it what you are saying?

From what I guess, the jiangsu protocol entry is defining that the protocol has 3 device bytes with 8 bits each and has LSB. It has 2 command bytes and has LSB.

I am assuming the code.s3c80=xxx code has to do with the mid-frame burst.

If so, it is quite disappointing but understandable.

Thanks.