JP1 Remotes

The following pronto hex decodes as protocol Gap-578-1708-32?
It's from a Bosch DVR.
Any clues as to which protocol to use to generate this with Make Hex?
This is the "Cursor Right" command. The code repeats about 4 times causing the cursor to jump too far.


0000 006D 0022 0002 0157 00AB 0016 0016 0016 0040 0016 0040 0016 0016 0016 0016 0016 0016 0016 0016 0016 0040 0016 0016 0016 0016 0016 0040 0016 0016 0016 0016 0016 0040 0016 0040 0016 0040 0016 0016 0016 0040 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0016 0040 0016 0016 0016 0040 0016 0040 0016 0040 0016 0016 0016 067F 0157 0056 0016 0E2F

Any help would be appreciated.
Cheers
Peter

I suspect that you're not using an up-to-date copy of DecodeIR because it decodes as NEC1-f16, device 134.228, OBC 2, EFC 067 for me.

simonsezdothis wrote:The following pronto hex decodes as protocol Gap-578-1708-32? It's from a Bosch DVR. Any clues as to which protocol to use to generate this with Make Hex?

I get almost the same results as Rob. Though I should probably point out that since this is NEC-f16, it has two OBCs; #2 and 116. I'm thinking that's why my EFC(3)# 190 and EFC(5)# 00190 are different.

In case you don't know how I came upon this information. I used IR Scope (https://www.hifi-remote.com/forums/dload ... le_id=8499). Went into File > Import... (Ctrl+I) and entered the Pronto Code in the box below then pressed the Ok button.

I used Remote Master (https://www.hifi-remote.com/forums/dload ... le_id=1339) for the EFC codes. Just opened up a valid Atlas Remote and selected the "NEC1-F16 Official" Protocol in the Setup tab and input the device, sub-device, obc1 and obc2 codes in the functions tab.

Thanks.
I've downloaded the latest DecodeIR files etc and will have a play around again today.
Really appreciate your help.
Thanks all.

simonsezdothis wrote:Thanks. I've downloaded the latest DecodeIR files etc and will have a play around again today. Really appreciate your help. Thanks all.

You're welcome. Glad to help. Though, when you're done would you mind uploading your files to our file section? It would be nice to finally have Bosch Security DVR IR codes. Even if you didn't have a JP1 remote, a full set of the compatible Pronto codes would be awesome!

Have downloaded DecodeIR 2.43.
Importing the files into IRScope as you've done, decodes them as either NEC-f16 or NEC-y1.

Neither of these protocols were included in the DecodeIR 2.43 Zip file.
Is there a zip file of the latest .irp files somewhere? I must be going senile cos I cant find them anywhere!

also looking for RECS80

simonsezdothis wrote:Have downloaded DecodeIR 2.43.
Importing the files into IRScope as you've done, decodes them as either NEC-f16 or NEC-y1.

Neither of these protocols were included in the DecodeIR 2.43 Zip file.
Is there a zip file of the latest .irp files somewhere? I must be going senile cos I cant find them anywhere!

I believe the tools on our site interacts differently with DecodeIR library than what you are using, since we don't use individual .IRP files. Our signal references are usually located in the "protocol.ini" file. The Remote Master tool which I referenced earlier, uses its own copy of the "protocol.ini" file for the signal encodes.

simonsezdothis wrote:Have downloaded DecodeIR 2.43.
Importing the files into IRScope as you've done, decodes them as either NEC-f16 or NEC-y1.

Neither of these protocols were included in the DecodeIR 2.43 Zip file.
Is there a zip file of the latest .irp files somewhere? I must be going senile cos I cant find them anywhere!

MakeHex uses IRP files, and they are all included with it. As eferz said, IRScope doesn't use IRP files as far as I know.

Ah .. OK, I get it now.
I had IRScope set to "export from decode" also.
Thanks -

Re: the Bosch 600 Series Security DVR ... I haven't learnt the entire remote yet, but will do so in the next day or two and post as requested.
Cheers

We don't have a convenient way to generate Pronto Hex from NEC-f16. But it can be done.
One way is to convert the device.subdevice, OBC, and OBC2 values to hexadecimal and enter them into the Yamaha ProntoIR Hex Converter . Yamaha uses NEC1, so this works for any brand component that is also using NEC1. For example, 134.228 OBC=2 OBC2=116 is 86.E4 02 74 in hexadecimal. So enter 86E4 0274 into the converter. Be sure to include the space in the middle.

Another way is to use the following IRP file. Here everything is entered in decimal format, but one has to use MakeHex.exe and not mdavej's GUI for it. The irp file has to be edited anytime OBC2 is changed.
Device=134.228
Function=2
#Function= 0..61 for example to give a range of OBCs
Define E=116
Frequency=38000
Time Base=564
One=1,-3
Zero=1,-1
Prefix=16,-8
Suffix=1,-78
R-Prefix=16,-4
R-Suffix=1,-174
Default S=~D
Form=*,D:8,S:8,F:8,E:8,_;*,_

IrMaster also won't always work, even with the suitable IRP added to IrpProtocols.ini, because it only handles function numbers up to 32767 rather than 65535.
irp={38.4k,564}<1,-1|1,-3>(16,-8,D:8,S:8,F:16,1,-78,(16,-4,1,-173)*) [D:0..255,S:0..255=255-D,F:0..65535]

Are you sure that there isn't some pattern among the 16 bits of function data? We've seen -y1, -y2, -y3 variants (Yamaha) and one I'll probably call -rnc (reverse nibble complement), which is used in the SlingCatcher. All of these can be represented by a single byte OBC once the pattern is recognized. Apple TV is another IR protocol that doesn't follow standard NEC1 consistency rules, and which would be decoded as -f16, if we hadn't recognized its pattern.

Have placed an IRScope ict file in the Misc Files section for the Bosch DVR.
The Bosch DVR seems to have 9 selectable control ID's (for controlling multiple units) so this learn is for ID#2 - which is where the extra OBC comes in.

I'll try your method of producing these files too. Thanks.

simonsezdothis wrote:Have placed an IRScope ict file in the Misc Files section for the Bosch DVR.

The Bosch DVR seems to have 9 selectable control ID's (for controlling multiple units) so this learn is for ID#2 - which is where the extra OBC comes in.

Excellent. Thank you for the upload. Though I was wondering how you came upon these signals? Were they learns on an IR Widget or did you get them as either a Pronto or UEI Learned codes? It is curious because the majority of the protocol used was NEC1-f16 except for three; #26, 29 and 30. Also, you didn't have a name for #26 and it came up as <unknown> so I wonder if it been a part of the command above or below it.

------
If there are any NEC signal experts out there, I'd like to create a Slingbox upgrade for this. Especially, since there are quite a few people wanting to have a security DVR available like this. This will enable to them to watch it remotely using their Slingplayer clients for computer, smartphones, tablets, and smart TVs. The only problem is that Play and Stop comes out to the same OBC #2 but uses different protocols NEC-y1 & NEC-y3. So, I was wondering if there was a way to translate them into a NEC1-f16 compatible functions?

eferz,
All of these signals have OBC1 = 2, so use the NEC-f16 NEC-f16 3Fixed protocol. Enter 134, 228 and 2 into the 3 device fields. On the function tab, enter in OBC2.

I'll get to the unknown, y1 and y3 signals tonight. BTW, y1 and y3 are just special cases of f16, and regular NEC is an even more special case of f16.