Upgrade Size Limit

Post by **vickyg2003** » Thu Dec 03, 2009 7:25 am

It seems to me that I read that there is an upgrade size limit for the slingboxes. 108 sticks in my mind, but I can't find the reference. Does the sizelimit include both the device upgrade and the protocol, or are each seperate?

Post by **The Robman** » Thu Dec 03, 2009 10:11 am

I think the limit is closer to 200 bytes, but I don't remember for certain. The size limit is for the bin file itself, so it includes both the device upgrade and the protocol upgrade. So sometimes you can bring an upgrade back under the size limit by deleting a few buttons.

binky123 · Post by **binky123** » Thu Dec 03, 2009 11:25 am

They use a byte for length with 3 byte header so my guess is 255-3=252 is the byte limit for a single upgrade. The upgrade can contain both an device upgrade and a protocol upgrade.

I believe the XMP/016C protocol is around 178 bytes.

Post by **The Robman** » Thu Dec 03, 2009 9:39 pm

The XMP protocol is built to most Slingboxes, but it doesn't work very well, even though it is identical to the version in remotes. I suspect that the Slingbox hardware is sending the signal out faster than a remote would, so I usually need to slow it down to make it work.

Also, the official UEI version of the XMP executor uses 2 variable bytes, which doubles the size of the device upgrade. In reality, only one of the two variable bytes is the OBC, the other byte is always zeroes. So, when I have to make a custom version of this executor for the Slingbox I always re-work it to use 1 variable byte.