search

probonopd / irdb

One of the largest crowd-sourced, manufacturer-independent databases of infrared remote control codes on the web, and aspiring to become the most comprehensive and most accurate one
Other
798 stars 148 forks source link

Adding Cambridge Audio Topaz AM10/SR10 #80

Closed willstott101 closed 2 years ago

willstott101 commented 2 years ago

I've tried my best here but have honestly really struggled with trying to understand how to convert from CA's docs to this CSV format. So I would very much appreciate a sanity check:

Sources: https://techsupport.cambridgeaudio.com/hc/en-us/articles/201026141-Topaz-SR10-IR-Codes https://techsupport.cambridgeaudio.com/hc/en-us/articles/201010471-Topaz-AM10-IR-Codes

Would some documentation and/or simple python/JS tooling be in scope for this repo?

i.e. how to go from "SEC Format" hex codes in a list... to this DB and back...

Also the index seems to be very out of date - but I added my line anyway

probonopd commented 2 years ago

Thank you @willstott101

bengtmartensson commented 2 years ago

I've tried my best here but have honestly really struggled with trying to understand how to convert from CA's docs to this CSV format.

You are right; it is not straight forward. First, there are several "NEC" protocols to our disposal. Likely you should select NEC1, unless the repeats are not working, in which case you can try NEC2. NEC2x uses a different timing in the lead-in. The NEC1 protocol has 3 byte-size parameters, not four as in the document. The NEC1 protocol uses a payload of 32 bits; the fourth byte is the complement of the third (which is the function number). Inspecting the document shows that byte 3 and byte 4 all add up to FF, so everything seems to be ok. So you should probably take the device as the first byte, the subdevice to the second (just as you have done), then the third on as function. Ignore the fourth.

The file as given will not work.