New PS2 remote & more

wwwoholic · Post by **wwwoholic** » Sat Sep 04, 2004 1:54 am

Could anybody with new PS2 remote (SCPH-10420) take some time and learn codes for all the keys, please? The codes at yahoo do not have many buttons e.g. "power" and "reset".

Also, regarding posting to yahoo group... Most of the upgrades are final versions tailored for particular remote model and author's taste. It seems much more logical for those who have OEM remotes to learn ALL the buttons and upload like that. Whoever uses the upgrade will be able to assign functions that the author might consider useless.

Post by **The Robman** » Sat Sep 04, 2004 7:09 am

That's exactly what we ask people to do, the trick is getting them to do it.

wwwoholic · Post by **wwwoholic** » Sat Sep 04, 2004 8:13 pm

Well... there is a solution, but it is more of a headache than a real one: to separate two KM formats. One for device side with protocol id and function codes, another for remote configuration with remote type, buttons and key moves. But again, splitting perfectly working code would be such a time waste.

gfb107 · Post by **gfb107** » Sat Sep 04, 2004 8:41 pm

KM and RM already do that. That's exactly why there are seperate tabs for Functions and Buttons.

The Functions tab is supposed to be a generic list of the known available functions of the device.

The Buttons tab is the mapping of those known functions onto the buttons available on the user's remote.

wwwoholic · Post by **wwwoholic** » Sat Sep 04, 2004 9:02 pm

When I said "separate two KM formats" I meant those .txt files at yahoo... and I already admitted it is not such a good idea. Technically, KM could load/save function configuration separately. But saving remote configuration separately is a bad idea.

Post by **The Robman** » Sat Sep 04, 2004 9:50 pm

But like Greg said, that's the idea with the current KM and RM files. If the user has created the upgrade properly, they should have included the OBCs (or EFCs) for every button on their original remote, plus any additional codes that they have discovered that work (such as discrete codes, etc).

Then they would have assigned the functions to buttons that make sense for their remote.

In most cases, when the next user loads this upgrade into KM or RM, and they change the selected remote to some other remote, 90% or more of the buttons will still be assigned to the most sensible button, leaving just a few for the user to customize to their taste.

wwwoholic · Post by **wwwoholic** » Sun Sep 05, 2004 2:27 am

The Robman wrote:90% or more of the buttons will still be assigned to the most sensible button

Yeah, I saw that. I'm just curious, how this assignement works? By function name?

BTW original topic was about PS2 remote...

Last time I saw them, they were about $30. It's kind too much for me just to learn two or three codes.

Post by **The Robman** » Sun Sep 05, 2004 12:09 pm

I can't speak for how RM does it, but in KM there is a hidden chart that links "similar" buttons together. For example, if the upgrade file has a function assigned to the DISPLAY button, and your remote has an INFO button instead, the function will be assigned to that button.

gfb107 · Post by **gfb107** » Sun Sep 05, 2004 4:26 pm

I can speak for how RM does it.

The available buttons on the remote are defined in the RDF file, in the [Buttons] section. The format of a button definition includes a generic, standardized name in addition to the name as printed on the remote. It is this generic standardized name that RM uses for matching buttons between remotes.

For more details see RDF3Spec.doc

Mark Pierson · Post by **Mark Pierson** » Sun Sep 05, 2004 5:38 pm

wwwoholic wrote:BTW original topic was about PS2 remote... Last time I saw them, they were about $30. It's kind too much for me just to learn two or three codes.

You can always search for those missing codes by trying all the unused EFC's between 000 and 256. The hard way would be using SET-#-#-# while the easier method would be to map the unused EFC's in an upgrade and try them that way.

In either case, you could probably find the codes tonight instead of waiting for someone else to do it for you.

wwwoholic · Post by **wwwoholic** » Sun Sep 05, 2004 10:04 pm

Mark Pierson wrote:In either case, you could probably find the codes tonight instead of waiting for someone else to do it for you.

You are right and I'm one lazy bastard. I't just I saw many warnings on this site regarding some codes wrecking havoc on TVs. I was afraid to accidentally break a PlayStation. Another reason - it is essentially a combination device i.e. game console + DVD. AFAIK Sony often uses multiple device numbers for multifunction electronics. So, it is potentially much more than 256 codes.

Post by **The Robman** » Sun Sep 05, 2004 10:21 pm

You're concerns would be valid with a TV, but I think you're OK with a playstation. Plus, I think from Sony's point of view, it's just a DVD player, so I'm guessing that all the commands use the same protocol and device code(s).

wwwoholic · Post by **wwwoholic** » Wed Sep 08, 2004 3:59 am

Well, if the mountain will not come to Mohammed, Mohammed goes to WalMart... I'm uploading a new Sony_PS2_VIDEO-1550.txt with all the buttons on SCPH-10420U remote. Enjoy.

Post by **The Robman** » Wed Sep 08, 2004 6:25 am

Did you find any extras?

wwwoholic · Post by **wwwoholic** » Wed Sep 08, 2004 11:45 am

Well, as I suspected Sony uses two different sub-devices (73 and 218). This alone was enough for my laziness to kick in. So, instead of going through all 512 codes I have bought a remote, learned all the keys and returned it to the store. Not nice, I know, but thirty bucks...

Anyway, besides having complete set of buttons present on PS2 Controller this remote adds Open/Close and Reset/On/Off buttons. The latter one works differently depending on the time it is pressed. I believe I'll be able to use delays to achieve discrete on/off for my toads.