JP1 Remotes

Is there a method (SourceForge check in or similar) to merge changes to RDFs from multiple maintainers? Or what is the best way for me to get changes put into the official copies of RDFs? Do I just Email them Nils or what.

For the moment the only change I have is adding a variantname to 001F for NAK0NAK0 to indicate that the 9960 uses 8 bytes of fixed data for protocol 001F (I think all other models use 4 bytes). That would change the first line of the Protocols section from
0000, 0002, 0006, 0014, 0015, 001C, 001F, 0022, 0027, 0029, 002D, 0034, 003F,
to
0000, 0002, 0006, 0014, 0015, 001C, 001F:8, 0022, 0027, 0029, 002D, 0034, 003F,

I was surprised to see that there are no other variant names in the 9960 RDF. I thought there were a few protocols in which we'd called the older one the "no variant name" one and given the new one a variant name. I haven't had time to check and if I find time, that might mean I have a few more changes to request.

Correction: The PVR0 RDF files need a similar change, because the 6131 also needs 8 buytes of fixed data for pid 001F

John,

My understanding is that NILS is the ONLY rdf maintainer. He's very good about making changes as required if someone points them out to him. Thus, I'd suggest emailing him direct with changes you find neccessary. If you forsee a good number of changes, it may be more efficient on your's and his part to do them in "batches" so he isn't making multiple changes in the same rdfs several times a day.

I have noticed that he hasn't visited this forum quite as often as he used to, no doubt the holidays and his 9960 extender project consuming a good deal of his time. I wouldn't have a clue as to just how often he visits the sourceforge site, but my guess is it isn't near as often as either here or his email account.

Jim

johnsfine wrote:Correction: The PVR0 RDF files need a similar change, because the 6131 also needs 8 buytes of fixed data for pid 001F

The Atlas DVR (SA_7SA_7 rdf) also has the new 8-fixed-byte version of the 001F protocol, so I imagine it will need updating as well.

I will be back on regularly on Tuesday. Have been on vacation and yes, the 9960 extender has also been keeping me busy but I am just about done with it.

John, I agree that we need to come up with a process for gathering RDF's for updates. For the time being they can either be e-mailed to me or posted at jp1 and linked from a post here. Alternatively you can just tell me the changes here and I will make them.

I still can't use the checkin or out facility at SourceForge since I am still stuck with the proprietary Shell for work and it won't let me run multiple iterations of SSH.

John, I picked up the 4 RDF's in the prerelease zip file

I also have changes to the 8910/9910 Extender 1 RDF. See https://www.hifi-remote.com/forums/viewt ... =6856#p6856

It's not ready for prime-time yet, but in the meantime you might want to scrounge around for a good picture of the Atlas 4-device...

https://www.hifi-remote.com/forums/viewt ... =6835#p6835

Mike and Greg

Got both your updates.

Mike, I will start hunting for a picture since I only got two new mouses and a BCD clock for Christmas and no digital camera

Greg, wish I would have remembered the XShift= before I added them to the 9960 extender RDF. Oh well

Nils_Ekberg wrote:and a BCD clock for Christmas

What is a binary coded decimal clock?

usblipitor wrote:

Nils_Ekberg wrote:and a BCD clock for Christmas

What is a binary coded decimal clock?

It's a funny looking little clock with a bunch of LED's that show the time in bibary. That's fine if you have time to convert binary to time of day. It's really just a fun geek toy.