JP1 Remotes

Are there any extenders for JP1.x remotes yet?

In particular, I now have an Atlas 5-Device (Day) (URC-11055) JP 1.3 (rdf sig 30003000) Learning remote (thanks speaker.guy 8) ), which I really like, but of course I want LKPs, and ToadTogs and fast macros and, and, and ...

What would it take to make an extender? How does one go about creating one from scratch - or has some preliminary work been done by anybody yet regarding extenders for these remote?

Ideas? Pointers?

I'm happy to do any testing (once I get my cable) if somebody has the time, capability, and inclination to build this extender.

kupakai wrote:

Capn Trips wrote:The more I look at these Atlas remotes things, I'm really liking their form factor and button layout, so I'm of course interested in seeing the support for them continue to develop and be right.

I agree with you; I think it's a great remote, especially the JP1.3 version. It has fairly large memory (5k), layout is great, and the JP1.3 version can use the executors (or the custom protocols) from the JP1 remote since the processors are compatible. Lot of the protocols have been rewritten for JP1.2's processor, but there are still lot more for the S3C80 processor.

Does this mean that the same Special Protocols that are used in the 8910 extender could be used in the Atlas JP 1.3s?

Hi Capn,

Are there any extenders for JP1.x remotes yet?

I like those Atlas Remotes too! They really do have a nice feel to them.
I've been working on a jp1.x extender for the past month, but I'm targeting JP1.2 URC8820 because the big guys (John Fine and Binky123) had already done a lot of work figuring those out how that one works. I've got HT and nested macros working with DSM. I'm currently working on ToadTog. I expect to have my extender done and ready for testing by August. My plan is to port it to the Atlas PVR Days that I got from Speakerguy, but my Atlases are the JP1.2 version.

kupakai wrote:

Capn Trips wrote:
The more I look at these Atlas remotes things, I'm really liking their form factor and button layout, so I'm of course interested in seeing the support for them continue to develop and be right.

I agree with you; I think it's a great remote, especially the JP1.3 version. It has fairly large memory (5k), layout is great, and the JP1.3 version can use the executors (or the custom protocols) from the JP1 remote since the processors are compatible. Lot of the protocols have been rewritten for JP1.2's processor, but there are still lot more for the S3C80 processor.

Does this mean that the same Special Protocols that are used in the 8910 extender could be used in the Atlas JP 1.3s?

No, the special protocols need to be patched to work with JP1.3. When an expert does study the new JP1.3 remotes, they can patch the code for the special protocols, instead of having to translate the whole thing into another language like I'm doing for the JP1.2. The JP1.2 processor has a different language and some instructions don't translate easily.

When I get my jp1.3 remotes (atlas PVR) and interface, I'd be interested in trying to learn how to work on an extender. Let me know what I have to do.
Best,
jeff

but....


lots of other stuff going on here, specifically I'm taking a new job and moving across the country in the next couple of weeks. It's close to being in a beta form at this point, I just need a few hours to work on it in between the house cleaning, painting, packing and all of the rest of the stuff I have to do in the next two weeks.

As for what you have to do, the first is you need to have a reasonably good understanding of assembly language (any machine will do) and then read and understand the instruction set for the S3C80 processor from Samsung.

Then you need an expert to help you find the right entry points in the ROM to do what you want to do, and to help you figure out what registers are used for what in the non-extended remote. Debugging is a pain in the neck since all you really have is the LED to blink status when you get to different spots, there is no such thing as a debugger here. (and if I ever get ambitious some day I'll finish the emulator that I was working on, but it has a long way to go!)

-bill

For those without an assembly language background there are still opportunities to help with testing and documentation.

Testing is an important aspect of extender development. For the JP1.2 extenders, I had a lot of help from capn_trips, underquark, evans and rindertp. Testing is a huge part of the development of a stable extender. Its a valuable contribution.

Documentation is a big help too. I know SOME PEOPLE DO read the documentation and its nice if it makes sense to the average extender user.

I've programmed in assembly back in the day on an IBM 360/370, these days it's fortran (yes fortran), C and C++.

I can debug on massively parallel computers using print statements , since debuggers typically don't run well on 1000's of processors. That's close to an LED blinking, isn't it.

I'll start by looking at the S3C80 instruction set.

Best,
jeff

I've looked over the language spec. I've also got my jp1.3 atlas working, thanks Tommy. An extender is clearly needed as I can't live without LKP. Macros on device buttons is just not enough for me.

I'm ready to start given available time.

jeff