|
JP1 Remotes
|
View previous topic :: View next topic |
Author |
Message |
vickyg2003 Site Admin
Joined: 20 Mar 2004 Posts: 7073 Location: Florida |
Posted: Thu Oct 28, 2010 3:25 pm Post subject: |
|
|
The Robman wrote: | vickyg2003 wrote: | I just took the two CH+ keys timing data, dumped them into Excel and then did the ABS, of all the times the two rows, and added them up and subtracted the difference between what the Mitsubishi and the OEM were, and adjusted the lead-out time by the units of time. |
I just tried a different approach. I calculate each ZERO to have a time of 1070 and each ONE to be 2140 (ie, double). So each 16-bit signal has a base time of 1070*16 (ie, if the signal were all zeroes) and the true total time is that total (17,120) plus the number of ONEs times 1070. I then added that number, plus 260, plus the leadout time to come up with 47,050 which I think is probably the true "OFF as total" value. |
The channel off frame length was 47000 from the OEM using the ABS calculation, the Mitsubishi signal was 54070. But the protocol specified 53700, so the timing is a bit off. There was a difference of 7070. I subtracted 7100 to from the 53700 to come up with 46600. It seemed reasonable. That's why I usually use IRScope to fine tune a protocol. I just haven't had the time to be thorough. _________________ Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
|
|
Back to top |
|
|
Plomaris
Joined: 20 Oct 2010 Posts: 38
|
Posted: Thu Oct 28, 2010 5:58 pm Post subject: |
|
|
Success! I put in the first protocol upgrade from Vicky's message and now everything works perfectly! All the buttons work as expected, and the mouse movement buttons work fast and smooth like the OEM remote.
Thanks for all your help! _________________ Tom |
|
Back to top |
|
|
vickyg2003 Site Admin
Joined: 20 Mar 2004 Posts: 7073 Location: Florida |
Posted: Thu Oct 28, 2010 7:11 pm Post subject: |
|
|
Congratulations!
The KM file has been loaded here.
no-name USB Remote for Windows (circa 2010)
Tom you can open this KM file in RM and finish the button assignment. I changed the protocol ID in the official version to be 01FF, to be consistant with the way we name custom protocols, the one I posted in the thread was called 0014. You can adjust your IR file if you want to, but its not really necessary. _________________ Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
|
|
Back to top |
|
|
Plomaris
Joined: 20 Oct 2010 Posts: 38
|
Posted: Fri Oct 29, 2010 6:16 am Post subject: |
|
|
Vicky:
Thanks again for all your help! _________________ Tom |
|
Back to top |
|
|
sriram
Joined: 04 Apr 2006 Posts: 44
|
Posted: Fri Sep 20, 2013 10:16 pm Post subject: |
|
|
Finally got around to installing another one of these I bought a while back and so glad to see an upgrade already available. Thanks Vicky! I've bought three of these so far (at different points in time) and each one has been a little different (different remote codes or different keys they send to the computer).
These are great receivers for HTPCs, but by default are not very configurable, but combined with Eventghost become quite flexible in what each button can do. It does take a bit of configuring and installing a custom driver, but the effort is worth it. I'm using mine to control XBMC and they work pretty well! |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|