Glow with the Show ears

[The Robman]

I have created an executor that replicates this signal, including the checksum.
http://www.hifi-remote.com/forums/dload ... e_id=25262

[ishootstuff]

Looks like I need to get a remote. It's the passholder blockout month

[The Robman]

I have created an executor that replicates this signal, including the checksum.
http://www.hifi-remote.com/forums/dload ... e_id=25262

I haven't had time to do a write-up on how this works yet, but basically the executor takes 8 fixed bytes of data, this is to allow for some of the longer signals. So what you do is either enter decimal device codes for the first few bytes, or just enter them as raw data, and then pad out the remaining 8 bytes with zeroes. For example, if you want to generate the signals that start with 0x90, enter "90 00 00 00 00 00 00 00", and if you want to generate the signals that start with 0x91 0x0E, enter "91 0E 00 00 00 00 00 00" in the raw data field.

With the current version, you'll have to create a separate upgrade for each codeset based on the fixed data that it uses, but you can use the same executor (protocol upgrade).

My next task is to create a combo version where you can combine the different codesets into one.

[The Robman]

for those interested in the protocol itself, here's some info.

The frequency is about 38kHz.
Logical ONE is +0 -400
Logical ZERO is +400 -0

There are no leadin or leadout pairs and the signal does not repeat.

Each byte of data is preceded by a ZERO and followed by a ONE, making 10 bits per byte in total.

The signal is LSB, but the executor is MSB, which means it accepts data in an MSB format but transmits the signal in LSB format.

The first nibble of the first byte is always "9" and the second nibble is a zero-based count of data bytes (ie, 0=1 byte, 1=2 bytes, etc).

For the executor itself, I had to manually send the data one bit at a time and I created a loop to send the data one byte at a time. The executor calculates the checksum while it sends the data bytes.

To send the fixed data, the executor grabs the length from the first byte and sends the required number of fixed bytes, then it moves on to send the OBC and checksum bytes.

My testing found that the device was quite fussy about getting the frequency and burst timings exactly right.

[jward]

I have created an executor that replicates this signal, including the checksum.
http://www.hifi-remote.com/forums/dload ... e_id=25262

Thanks. I'll have to try this out.

[The Robman]

I just added a combo version to the zip

[The Robman]

Did anyone try this out yet?

[The Robman]

Nobody tried it?

[UKTracey]

Hi from the UK.
I've been purchasing Glow with the Show ears recently and have a collection enough for the family on next visit to Disney and so am going to attempt at programming them with a JP1.3 remote controller.

total novice here so any very basic step by step instructions really appreciated if anyone able to help.

The remote will be here by end of April but wanted to have a go with getting the code ready .... I am sure it isn't going to be quite as straightforward as that, but I made it here and so onwards

This is the remote I purchased:
https://www.ebay.co.uk/itm/224585386364

Thanks in advance of any help you can give me

[The Robman]

Unfortunately, that isn't a good remote for this purpose. I wrote the executor for the Glow With the Show Ears and I only wrote a version for the Samsung S3C8 processor, the URC-1067BC4 uses the MAXQ610 processor.