Sony STR-K670P Receiver

[jborn]

1. Device: Sony HT-DDW670 STR K670P
2. Type of device: Receiver / Home Theater in a Box
3. Year: Purchased in 2006 First available on amazon March 1, 2005
4. JP1 Remote model: RadioShack 15-2116 8-IN-ONE
5. JP1 user? Plan to be
6. Still have original remote? Yes
7. Checked the file section? Yes
8. Checked Pronto file section (at R/C)? Yep
9. Partially working setup code? Currently Can't even turn on and off
10. Learning remote question? Not really.. Would rather find a pre built set of codes, but will go down this route if necessary.

Just learning how to use this JP1 stuff, but I'd like to be able to download a code file that doesn't require me to set something that disables the OEM remote. I bring that up because one thread I saw said if the normal sony setup doesn't work switch from 3 to 1.

Thanks for all the help in advance.

[Capn Trips]

You can search the files and try various upgrades (there are PLENTY of them for Sony gear), but although you express hesitation to do so, the simplest and easiest way is to learn and decode the OEM remote signals YOU PRECISELY WANT and build a subsequent upgrade. It should take about 10 minutes to learn enough signals to fill up your memory, then another 20 minutes or so to transfer the decoded data into either KM or RM. You may have to do this 2 or 3 times to get every OEM button learned, but in an hour and a half, you'll have a working upgrade, rather than countless hours and/or days waiting/hoping somebody does this for you or to stumble upon a pre-made upgrade that meets your criteria.

Everything else (using pre-built files) would be, to a degree, trial and error until you figure out what unit code your HTIB is set to.

Those files are MOSTLY useful for:
(1) JP1 users who do NOT have learning remotes;
(2) Finding functions that are not available on OEM remotes - usually stuff like discrete on/off and input selects.

If you have trouble determining what to do with the learned info, just save the learned IR file and upload it to the diagnistic area and post a link to it here and someone will quickly help you (unless the learns are really undecypherable - which is the exception rather than the rule - and the "help" will require and expert, which is also usually pretty quick, but there's a smaller group of those guys)

[zaphod7501]

When (or if) you look at upgrade files, realize that most newer Sonys use what is termed AV-2 mode and notes in upgrades may mention this. I don't know if they've added any more categories on yet newer receivers and as Capn Tripps pointed out there are lots of Sony receiver upgrades (and many of them are for the newer AV2 modes).

An STR-K670P would not strictly be an HTIB (Home Theater In A Box) since it is a standalone receiver/amp.

Even learning a couple of buttons would verify the protocol used by the OEM remote so almost any existing upgrade file could be converted by changing the device and subdevice numbers in RM or KM. (it's not always that simple however)

Some of the OEM remotes have the ability to change themselves from AV1 to AV2 (check your manual).

[johnsfine]

1. Device: Sony HT-DDW670 STR K670P

For Sony devices your best resource is:

http://www.hifi-remote.com/sony/

I'd like to be able to download a code file that doesn't require me to set something that disables the OEM remote. I bring that up because one thread I saw said if the normal sony setup doesn't work switch from 3 to 1.

You can make your JP1 upgrade file for whatever Sony code set you like. Switching the Sony device may be needed for less capable universal remotes (including a JP1 remote without the JP1 cable) but with JP1 it is easier to make the JP1 remote fit the device than make the device fit the remote.

the simplest and easiest way is to learn and decode the OEM remote signals YOU PRECISELY WANT and build a subsequent upgrade. It should take about 10 minutes to learn enough signals to fill up your memory,

Learning and decoding a FEW select signals might help you understand the Sony page I mentioned above, and how your device fits the info on that page.

But (for Sony) learning a LOT of your original remote signals is a waste of time. Learn enough (assuming any are required) to see where your device fits relative to the data on that page. Then use the rest of the data from there. In the unlikely event that your original remote has any signals not covered by that page, learn and decode those as well (and tell us).

If the text on that page of Sony info fits facts you know about your Sony device well enough, you might know which set of device numbers is needed without learning any signals. But as long as learn/decode is easy, you might as well try that in order to be sure of your understanding.

Even learning a couple of buttons would verify the protocol used by the OEM remote so almost any existing upgrade file could be converted by changing the device and subdevice numbers in RM or KM. (it's not always that simple however)

I'm not sure which possible "not always that simple" Zaphod is worrying about. Usually it is that simple:
1) Pick almost any upgrade for a similar Sony device.
2) Use one learned/decoded signal to verify a device/subdevice against the Sony page above.
3) Use that Sony page for the other Sony device/subdevice values used by the same Sony code set.
4) Fix the device/subdevice info in the selected upgrade file based on 2 and 3. The OBC info in the upgrade should already be correct.
5) If a few functions you want are missing fill in their info from that web page or from learn/decode.

The "not simple" case I can think of is that there is more than one way to create a Sony combo upgrade in JP1. The method used by the upgrade you start with determines the range of different device/subdevice values your upgrade can use. If you need more, start with either a different existing upgrade or from scratch selecting a Sony combo protocol.

One thing might be non obvious about that Sony Page:

Over each table of function numbers there is a header line, such as
Sony:16; 48
with a list of device numbers (16 and 48). This means that all the functions in that table are either device 16 or device 48. So if you decoded one command in that table and it was device 48 you know device 16 is not used and all the other commands in that table are device 48.
A second table in the same section says:
Sony:13; 45
The choice of device number is locked together for all the tables in a section. So as soon as you decoded that one signal of device 48, you not only know all the commands in the first table use device 48, but also that all the commands in the second table use device 45.

Any given Sony device may be missing several of the commands in each table. But if the command isn't missing it will use the device number and OBC that you find as I've just described.