Developing upgrade for the Panasonic PT-AE500E projector

[Mog]

I don't know why, but DCBUF+5 always has a zero value
The fixed data gets sent correctly, and the checksum is fine

So, regardless of the key pressed, I always get the same 7-byte sequence

I have posted my KM file here: Panasonic_DPGumby.txt
And my IR file here: ToplineNew.IR

I'm sure there's an obvious reason why, but I just can't see it

[Mark Pierson]

So, regardless of the key pressed, I always get the same 7-byte sequence

I'm not familiar with the workings of the Topline, but I wonder if it has to do with the warning message that IR displays:

Note: This remote contains a bug that prevents device upgrades from working if they use upgraded protocols.
Workaround: Set up devices that use upgraded protocols as "Device Button Restricted".

If that's the case, then select the upgrade and click the [Edit] button on IR's Devices tab. In the "Works with:" drop-down, select "TV", and uncheck "Include in device independent section as well."

[Mark Pierson]

Here's a thread regarding Device Button Resticted.

In the restrictions box, you have to select the device button you have assigned the device to operate from (not the device type if you have reassigned that button) and also make sure the check box for 'Include independent selection' is NOT ticked. Don't know what it means, but when it is ticked you still get the bug in the remote appearing - it sends whatever is programmed onto the '0' key whatever is pressed.

Since your upgrade has nothing defined on the '0' button, KM pads it (and all the other undefined numeric buttons which comprise a single "group") with $00, which might explain why all you're seeing are zero values.

[mr_d_p_gumby]

It sounds like Mark may have identified the problem you're having. 8)

I have disassembled the PT-AE100 protocol in PB, and get the following:

Code: Select all

FF17	20 11	LFF17:	INC	R11	
FF19	E4 05 09		LD	DCBUF+6,DCBUF+2	
FF1C	B4 06 09		XOR	DCBUF+6,DCBUF+3	
FF1F	B4 07 09		XOR	DCBUF+6,DCBUF+4	
FF22	B4 08 09		XOR	DCBUF+6,DCBUF+5	
FF25	8D 01 46		JP	0146H	

The Check byte style remains 'off'
I am happy that I can see four bytes being checksummed, and placed at the end of the byte stream.

Just for future reference, the Decoder in PB only analyzes the flag & data bytes in the protocol header. It does not try to figure out the machine code that is executed. That's why the Checkbyte remained 'off' when you decoded the protocol. If you were to turn on the Checkbyte option, PB adds code to the generated protocol. If you then decoded that generated protocol, the Checkbyte would be 'off'. In these cases, PB needs an assist from a human who can look at the disassembly and tell that the Checkbyte option is required.

[mr_d_p_gumby]

I just realized that the protocol I gave you yesterday is including the first two device bytes in the checkbyte. Here it is with that fixed...

Code: Select all

Upgrade protocol 0 = 01 C9 (P8/740)
 0D 1A 51 A9 8B 20 DB 00 A2 45 A0 03 22 44 A2 00 
 3C 00 63 B5 5D 85 56 E0 02 30 04 45 63 85 63 E8 
 86 66 3C 08 57 A9 11 20 DB 00 A2 91 A0 01 26 56 
 90 04 A2 B4 A0 02 22 44 C6 57 D0 E9 A6 66 E0 07 
 D0 D1 A9 11 20 DB 00 A2 86 A0 61 22 44 22 06 90 
 B2 60
End

I'll update the PB file in the diagnosis area if you want an updated copy.

[Mog]

Thanks to one and all!

It's all working now, I can control the PTAE500 from my Topline8

Earlier in this thread, you may recall that I mentioned that I had
'some other less standard devices' to sort out!

I never thought that this device would prove so difficult.
However, I have learnt how to use all of your great tools, and the 'features' of the Topline8 that I have to contend with, which is great.

Hopefully, I will be able to sort out the other devices without (as much? ) help

Anyway, thanks again for all the help - I really appreciate it!