Hello everyone.

I have both a TSU 9400 and a TSU 9300, and I use PEP II. I use just one file, and download it into both types of remotes. However, the Apple TV buttons (both hard buttons and virtual) DO work on the 9400 but DO NOT work on the 9300. I've tried everything I can think of to get the 9300 buttons to work, with no success.

The only thing I can think of at this point is that possibly I should have separate PEP files for each remote type. Could this possibly solve it?

Ed

Maybe, maybe not.
I do know there is a difference between the IR engine on the 9300 and the higher-numbered models.

What happens when you save your 9300 configuration as a Pack and Go EXE. Do you get a popup window about actions being removed?

I don't have a 9300 to test with so no idea as to why the standard NEC codes do not work.

Make sure that the component in PEP2 is not configured to use an extender. I assume that if you have 2 remotes you have 2 rooms. If the component is mapped to an extender, that is likely your issue. Simply duplicate the component and change the extender config as needed.

To my knowledge, there is no reason an NEC code which is what atv is should NOT work on the 9300.

Also note that you will need to change the project type in PEP2.

The 9300 does not support ProntoScript as well.

I would recommend 2 different files because of this.

Ed, Any feedback from my answers above?

Thanks,
Lyndel

Thanks for all the info and ideas, Lyndel. I’ve been away for a few days and could not get back to this until now. I plan on looking into it today. What I might try first is to make a separate file for the 9300. I just got the 9300 two weeks ago, and it was new in the box. I do notice that the scroll wheel works, something that never worked on my 9400s. (Does this have to do with Prontoscript, something I’ve never understood)?

Anyway, I’ll let you know what happens after I try everything mentioned in your comments.

The scroll wheel will work on the 9400 if you assign actions to it in PEP2 or write script that manages the scroll events.

Saving as a Pack and Go exe resulted in no pop up about actions being removed.

No components are configured to use as extenders.

Project type was 9400. I changed it to 9300, saved it, and downloaded to the 9300; no change - ATV codes still not working.

I might try starting a clean, very basic file for the 9300 only, with very few components. My current configuration has a lot going on.

Do you have any ProntoScript in your configuration file?

There is NO reason why NEC codes for ATV should not work. Please email me the file that is not working as I'd like to have a look.

Thanks,
Lyndel

Turns out that Ed has a component in MyDatabase that is referenced for 2 of his 3 ATV devices. This component is using Raw Learned codes (Format FFFF vs 0000).

The TSU9300 does not support this format.

As such, converting the codes to the ones posted here should work perfectly.

[Link: remotecentral.com]

Please see the warning on Page 3 about Reboot_Fault_B and Reboot_Fault_C. These are no longer reboots and cause a factory reset that can brick the ATV.

I got confirmation from OP that the codes I have posted in the thread above worked beautifully on the TSU9300.