Hi,

I have a Pace Sat receiver tds850nv ( HD with HD (!) for viasat)

It is not in the PEP2 db.

In the dvb there are quite some Pace receivers,
but also many (a lot) Pace sat sat receiver codesets.

What is the preferred way of working to properly identify the device,
in terms of codeset or a similar model, or both?
(Is there a way to see which codeset a model entry in the db is based on?)

The only ways I've found so far is cumbersome and, frankly, annoying to the point where I'd rather spenf my time doing something else.

Any ideas?

You have a few choices....

1:Testing each one
2:Searching on this forum for an XCF that may have your model
3:Learning it yourself, which is not as arduous as you would think.

gt

The situation with codesets and mystery numbers is almost as bad for the myriad B&O sets in the factory DB (Pace: 167; B&O 57).

I've been using B&O stuff for over 25 years and have owned almost everything they've made in that period, but could not relate the codesets to specific devices easily. Although many isolated functions worked as expected, each seems to contain mystery functions and omit wanted functions!

Eventually I gave up and created a hidden macro page with buttons that combined multiple codeset functions and specific learnt codes. Life was good, linking to that, until PEPv2 came along... ;-)

Meaning: Copying each to myDatabase and start experimenting from there.


I haven't succeded in that so far.
Here a remote-neutral database of codes would really help.


But only gives me the codes on the remote.
( As another example, my Yamaha dvd-S540 has no eject key,
nor does the dvd-s550 in the db, but the sister model from Philips has the code,
and it also works on the S540.
It would be great if I could remember the model designation of the Philips model.)


So here is some wishful thinking:

4. Learn one key, and let PEPv(x) find the codeset for you.

5. Make it possible to test at least the 'off' code from the db, without copying.

6. A lot more aliases in the db, so all models could be found.
- Maybe then I would also be able to find my one year old LG Full-HD LCD 42LY95...


Surely, Philips must have some idea of how this basic functionality for a universal remote is supposed to be done with minimum hazzle?

Finding the right codeset is one of those disagreeable tasks that one wastes more time trying to avoid, than if one addresses it head on.

My situation is a little different because I support many users. I have decided that the best plan is to create a custom device that has all of the codes. Once I have this device, it is very easy to reuse it in another program. It turns out that this technique works in PEP2, the links method fails.

...or you could find another user who already has the device defined and have them export the device from the V1 or V2 database using PDBExport. You then simply import the device and function codes using PDBImport.

...I'm really at a loss why folks don't seem to embrace the ability to contribute and manage an archive of user device definitions (with codes) using export and import utilities...

Although the files area of this BBS has hex codes to cut and paste, and also XCF files to dig through, and PEP2 will let you mount another users entire database to pull data from - Wouldn't it just be easier to have a collection of user generated individual device export files such that a desired device could be individually downloaded in its entirety and imported directly into the database with a single command?

It could be as easy as this: Go to the files area, download ACME_TV101.PDE, and run "PDBImport ACME_TV101.PDE" to load it directly into your database. It could be that simple...

Yeah - I wrote PDBExport and PDBImport - but I'm giving them away so this suggestion doesn't really benefit me in any way. RON7 has also worked up a toolset which does exports and imports so other folks also think this is worthwhile...

All we need is a dedicated export/import files area on this BBS and folks could start contributing their device definitions... No more hex codes, no more XCF files, etc...

Long term , Export/Import is for sure the way to go.

PEPV2 can check for upgrades of the db,
It will be interesting to see if that is per device, or if it replaces the whole db.

But to build those entries, I'd like to know if there more codes than the remote can send. And to test this, I'd like to know the codeset ...

Individual Device Export/Import is here NOW and its free! ...and it works with both PEP V1 and V2 interchangeably.

The export files are also user editable and readable if you want to scavenge codes!

[Link: netefb.com]

I could not find the file PDBIMPORT.EXE in the PDBTools zip file. Any help to find it is much appreciated since I like to try this tool.
Thanks
Rene

I also need PDBImport, not much use without it!

Please can someone post?

TIA

zerodayz