Want to change device ID in Proceed/PAV upgrade

[rdeodhar]

I'm using a custom protocol upgrade to control my Proceed/PAV preamplifier. The file is available in the Files section at:

https://www.hifi-remote.com/forums/dload ... ile_id=511

I'm having trouble ever since I bought a new LCD TV. Whenever the TV comes on cold, it causes the Proceed to go into a tizzy because of spurious IR commands.

The PAV uses RECS80 with address 5. I want to try and change the device address in the protocol to see if that helps. Unfortunately, I don't know how the device address is specified in the protocol.

The KM settings look like this:

Protocol Name: Manual Settings
Device1: 10
Device2:
Device3:
Raw Fixed Data:

Protocol ID: 01 45
Fixed Data: 50

PID:
2nd Command Byte: None
Signal Style: LSB
Bits/Dev: 4
Bits/Cmd: 6


Any help would be appreciated.

- Rajiv

[Mark Pierson]

The PAV uses RECS80 with address 5. I want to try and change the device address in the protocol to see if that helps.

Can you specify a different address on the PAV itself? If not, changing it in the protocol won't do you any good.

[rdeodhar]

Yes, the PAV can be set to use a different address (and its menus can be navigated by either a remote or front-panel buttons to guard against locking oneself out.)

[johnsfine]

The PAV uses RECS80 with address 5.
...
Device1: 10

That Device1 number controls the address. But I'm not sure what the mapping is. Device1 can be any number from 0 to 15. You're saying that it is address 5 when Device1 is 10. But that still leaves many possibilities for the underlying rule.

If it is easy to test, there are only 15 other possibilities, so try some and find the one that works.

The obvious guess is the Device1 value is always double the address. That might be right, but I wouldn't rely on that.

[rdeodhar]

Thanks for the tip.

Yes, changing Device 1 changes Fixed data, which changes the device address. The mapping is non-obvious:

Device1 --- Fixed Data --- Device address set in PAV
10 --- 50 --- 5 (default original)
0 --- 00 --- 0
2 --- 40 --- 4
4 --- 20 --- 2
6 --- 60 --- 6
8 --- 10 --- 1
12 --- 30 --- 3
14 --- 70 --- 7

I believe the high-order 3 bits of the Device1 value are bit-reversed to yield the upper nibble of the Fixed Data, which is also the Device address.

Weird.

At the moment using device address 4 appears to solve the problem but I really need the TV to go cold before I can be sure.