I had the strangest IR conflict happen today when I was programming a customer's MX 700 remote. The system uses a Samsung SIR-TS360 HD receiver, a Harman/Kardon AVR 330 receiver, and a Samsung HLP series TV.

I found out the hard way that the IR code for the number 4 on the SIR-TS360 receiver also shuts the Harman/Kardon AVR 330 off. Temporarily I used the work around of using macros/favorites for any channels involving a 4. For example, if one channel was 41, I would use a macro to go to channel 39 and then press the channel up button 2 times.

My client was happy with the temporary work around, but I'm hoping I can do something to allow him to press a 4 when controlling his satellite receiver so his H/K AVR 330 does not shut off.

Any thoughts would be appreciated.

~matt

This message was edited by mjmontagne on 09/06/04 22:41 ET.

Most SAT receivers have multiple remote addresses, the samsung doesn't?

How would I change the default "address" for the SAT receiver? Is this done in the IR Database of the MX700 Editor software? I presume I would still choose the SIR-TS360 as the model number, but I would change the code number in the "Enter Code Number" field.

Thanks much for your reply

~Matt

If you could change the samsung, I personally don't know, but Sony, RCA, and Hughes SATs all can. If you did change it, you probably would need to learn the new commands from the oem remote.

I just ran into the same issue with a TS160 and the AVR330. Anyone have a solution for this issue? I don't think the code for the TS160 can be changed because it's not an RF remote. I don't think that would solve the problem anyway. Changing those codes has to do with addressing the remote and it's associated receiver, not the ir code set used.

In certain cases its but known to help:

[Link: tivocommunity.com]

Perhaps it depends on the gear that you are using. However, generally, the ability to change the address on a satellite receiver is not an RF or IR issue; you're not changing the transmission frequency of the remote but rather the codeset that the remote sends out.

[EDIT: Sorry - didn't clue in until now that you were referring to the ability register the ID (serial number) of a Samsung RF remote with the receiver. You're quite correct that you can't do this with an IR remote.]

In the case of my Motorola gear, the receiver and remote have 4 different preprogrammed codesets or "addresses": 000, 001, 002, and 003 with a default of 000. To switch to a different codeset, I would invoke the "Set Remote Control Address" menu option on the receiver and the receiver then prompts me to hit the "Enter" key on my remote. At that point, I would change the "address" on the remote to, say, "001", hit the "Enter" button, and the receiver figures out the new codeset that I am using in the remote based on the code the remote sent when I hit "Enter."

In most cases, the Motorola codeset in a "universal remote" sends codes for address "000". If I change the address on the receiver to "001", I would then have to teach the "001" codeset button by button to the universal remote before could use it.

The procedure above may vary from manufacturer to manufacturer but the end result is the same.

Greg

This message was edited by g.n. on 09/05/04 00:54 ET.

The TS160 does not support code changes. Any other suggestions?

That all depends on whether the AVR330 is getting turned off by a duplicate code in the codesets or by a dirty code (either learned or in the database).

If pressing the 4 key on the TS160 OEM remote has no effect on the AVR330, it's probably a dirty code and relearning the key should solve the problem.

On the other hand, if the TS160's 4 key shuts the AVR330 down as well, that's a tougher problem to solve. One solution is to use an MX-800 and the MRF-200 with its addressable blasters (or some other form of IR routing) to isolate one or both of the affected components.

Of course, you could always put a macro on the 4 key that sends not only the "4" but also an "On" command to the AVR330... :-)

Greg

I wish it was a dirty code, but the 4 key on the ts160 remote shuts down the avr330. I have worked around it so far using macros i.e. if I want to jump to 647 i go to 650 and use channel down to get back to 647. However I do custom install, and this really isn't an acceptable solution. I'll probably just have to avoid this component mix.

What about trading in the MX700 for a MX800. You could use the same program and then turn on the IR routing. A little more money for the remote, but then you don't have any programming costs, and the remote will be identical for the client.

to put a little closure on this...

I recently swapped out the H/K receiver for a Denon 985s and the system works as advertised. This little conflict took at good deal of our time/resources--as a result, we'll probably stick with Denon AVRs for our installations from here on out.

Thanks for your help on this.

~matt

For those conflicting component configutations, I agree with Diesel's suggestion of using a MX-350/650/800/850/3000 in conjunction with an MRF-250/300. This way, the individual IR emitters can be addressed for each device and there should be no "crosstalk" since the emitters were toned down.

I don't believe the IR database can support different unit IDs/addresses. They only use the default ID/address as far as I understand.

Thank you,
Damon DG
= = = = =
Control Systems Consultant & Programmer
Subcontracting To Custom Installers