Shuttletec Satella 2: need help modifying protocol

Post by **vickyg2003** » Tue Oct 27, 2015 7:22 am

The Robman wrote:I increase R01 to make it ignore the first fixed byte.

command bytes = cbyte

So you initially set it to 3 device bytes, 2 command bytes to get the flags right so that the IR engine would set the data in the buffer?

Then you started with that generated data as the basis for your custom protocol.

In the data portion you changed the data to have 1 cbyte
then in the procedural assembly
increasing R01 and increasing Cbytes to 2
and jumping to the set and transmit
gets you a 32 bit signal.

chuliu · Post by **chuliu** » Tue Oct 27, 2015 8:14 am

Hi, it seems the new file used rsb and not complement.
I ticked lsb and complement and I am asking friend to test.

Thanks.

chuliu · Post by **chuliu** » Tue Oct 27, 2015 11:23 am

My friend confirmed that record button put the satella 2 into off mode.
Thanks.

There is some final tweak to be done, if you can make it, that would be perfect.
If not, just change the setup code to C2010 and that would be fine, too.

The setup code of the device upgrade was set to S1298 to make use of the realistic remote skin, and its functions mapped to the buttons so that it correctly point to the buttons on the skin. For example, lock function is mapped to last-ch button, satellite tv function mapped to custom 27 button.

Reason for using S1298 for a realistic skin is that there are too many functions to fit in the default skin from slingplayer as well as simply for better looks.

Now on the skin there is no record button. I cannot use it when it is not on the remote. If you can change it to other button, it is perfect.

I think there is a trigger function for power?
If so, can we change the assembler so that pressing power turns the device into off mode, while pressing on some other button turns the device to standby?

In fact, I think I used up all the buttons on the remote skin.
Maybe we can make two versions of the device upgrade.
One with ability to power it off and the other put it in standby?
My original file servers the second purpose.
We need one with power button able to turn off the device.

Thanks.

chuliu · Post by **chuliu** » Tue Oct 27, 2015 11:44 am

I just found out we have one button left, white, to put the standby power to it.
Then we can use power button for power off. That is 100% perfect.

Post by **The Robman** » Tue Oct 27, 2015 12:57 pm

vickyg2003 wrote:
The Robman wrote:I increase R01 to make it ignore the first fixed byte.
command bytes = cbyte

So you initially set it to 3 device bytes, 2 command bytes to get the flags right so that the IR engine would set the data in the buffer?

Then you started with that generated data as the basis for your custom protocol.

In the data portion you changed the data to have 1 cbyte
then in the procedural assembly
increasing R01 and increasing Cbytes to 2
and jumping to the set and transmit
gets you a 32 bit signal.

For this one, I didn't start with a blank sheet like that, I started with the official NEC executor and stripped stuff out of it.

If I had started from scratch, I would have set it to 3 device, 2 command bytes, then in the code I would change the 3rd byte from $32 to $31. In the assembler itself I would increase R11 to change it back to 2.

Post by **The Robman** » Tue Oct 27, 2015 2:26 pm

Here's the trouble with using something other than the record button. Not only do the buttons have different codes in each remote but chances are that the register that holds the current button can be different too. That's why they (ie, UEI) created a subroutine to check for the RECORD button. That routine will have the same address all the time (ie, $0133 in S3C8+ remotes, $0120 in old S3C8 remotes) so it can be used in protocol executors.

I know the button code for POWER in the Slingbox is $01, but I am not positive if the current button register is still R79. Assuming that it is, I have updated the RM upgrade:

https://www.hifi-remote.com/forums/dload ... e_id=13650

3FG · Post by **3FG** » Tue Oct 27, 2015 4:38 pm

Rob,
IMO the better way to handle this is to define a new OBC for the power off function, and test in the executor for the corresponding hex value. If the test succeeds, change the hex value to match the standby function and also change the repeat behavior. This approach is largely independent of the details of the IR engine and button numbers, and only really requires that the unit has free OBCs.

Post by **The Robman** » Tue Oct 27, 2015 4:45 pm

Duh, that's a good idea, I'll try something this evening.

chuliu · Post by **chuliu** » Tue Oct 27, 2015 6:16 pm

Hi Rob,
The latest file still doesn't have lsb and complement ticked. This time I cannot tick them because it can't be ticked.

Thanks.

Post by **The Robman** » Tue Oct 27, 2015 8:27 pm

chuliu wrote:Hi Rob,
The latest file still doesn't have lsb and complement ticked. This time I cannot tick them because it can't be ticked.

Thanks.

RM is doing something to uncheck them because they were checked. But please, re-validate it before you use a file because I don't know why they keep coming unchecked again.

I am about to try and create a new file...

Post by **The Robman** » Tue Oct 27, 2015 9:15 pm

Here ya go...
https://www.hifi-remote.com/forums/dload ... e_id=13650

This version has separate STANDBY and POWER (long) buttons.

And I figured out why those things keep getting unchecked, every time you update the protocol code RM unchecks them again.

chuliu · Post by **chuliu** » Wed Oct 28, 2015 2:02 am

Hello, I want to report that it all worked out.
Everything works as expected.
My friend and I cannot thank you enough.
Many thanks!!!

Post by **The Robman** » Wed Oct 28, 2015 7:07 am

Great, glad it worked and thanks for letting us know.

Alan, if you want to formalize this upgrade, here is the PB file that I used to create the version of NEC1:
https://www.hifi-remote.com/forums/dload ... e_id=13649

The assumption here is that the device doesn't use any OBCs in the range 32 thru 63, which is quite common strangely enough. So, I use the bit that they are avoiding as a long hold flag. To set a button to have a long hold, just add 32 to its OBC. So, if POWER was OBC 1, using OBC 1 would have a short hold and using OBC 33 would give a long hold.

In RM you need to use manual settings with the first byte being the number of repeats that you want, and the next 2 bytes are the normal NEC1 device codes. If the device only has one device code, set the second to its complement (ie, 255 - the device code). Of course, if you add this to your version of protocols.ini that would be simpler for you. If you need the entry, I will try to come up with one later.

chuliu · Post by **chuliu** » Mon Nov 02, 2015 10:46 pm

I have a question. Does the no-repeat issue apply to slingbox only or remote using samsung chip as a whole?

If I want to use my jp1 remote to put the s2 in off mode, do I need a manual protocol?

Thanks.

Post by **vickyg2003** » Tue Nov 03, 2015 3:52 am

chuliu wrote:I have a question. Does the no-repeat issue apply to slingbox only or remote using samsung chip as a whole?

If I want to use my jp1 remote to put the s2 in off mode, do I need a manual protocol?

Thanks.

You can hold down a key on a real remote, so you can put the s2 in off mode by just holding down the key.

The repeat issue does come up on a real remote, when we put keys in macros. Macro keys behave just like they do on a slingbox. When I'm helping slingbox users with repeat issues, I put a button in a macro so that I can see how it repeats.