How do you figure out which setup codes to use?
Posted: Mon Feb 06, 2012 12:40 am
Lately I've been uploading a bunch of upgrades. So, much in fact that I've got the process down to about twelve to fifteen minutes per upgrade if I have all my ducks in a row. And, actually its been fun trying to optimize time, so that I can eventually get it under ten minutes. However, there's a little road block that took this process and expanded it to an hour, actually two if you count the nap I had to take to clear my head.
The issue is with my last submitted upgrade. The is the first upgrade which I tried to implement "the correct" setup code as opposed to using the arbitrary "2013" which I've been using in the past.
Now I don't want to sound like a little girl crying about double-standards. Even though somewhere deep inside me, there's one moping about her big brother whose able to stay out till all hours of the night while she's stuck at home at 9 p.m. Apparently, using a signature setup code was an okay practice for the Slingbox RMDU files but it isn't prudent using it for the handheld remotes.
I understand the value in using the appropriate setup code. It will broaden the target audience that these uploads will help, so I tried my best to do it with this upgrade. Unfortunately with all the wasted time, I decided to cut my losses and just do one more the old way.
So, back to the problem. This upgrade calls for the following device/sub-device combination; 128.0, 128.1, 128.4, 128.9, 144.0, and 176.0. While this is only six combinations, when I split the values to try and fit it into the Panasonic Mix Combo, it doesn't because it would need a seventh field. So, a second device upgrade would be necessary.
This is where I had the problem, because now I felt like King Solomon having to divide a baby half. Except, I was actually under duress of trying to figure out which half to give to each parent. And after looking at the results of the Lookup tool, I found that there was at least twenty different combinations which it could have been split up. But, after racking my brain, I just couldn't figure out which was the "correct" one.
My final conclusion was use my arbitrary setup code, because to get the bulk of the functions into one upgrade there was no predefined setup code which could have addressed it. There were some which were close but if someone were to use this upgrade as a reference for the EFCs then some of the codes would have been invalid. So, using my arbitrary setup code, I figured the user would have to do their own setup code research and then make their own decision to split it they way they want.
Alright, so, I'm figuring there is no standard of splitting up an upgrade. But, I wanted to get a consensus of how the rest of you would have composed it. That way I can get an understanding of how each of you would have handled it, and I can use it as a guideline for the next time this happens to me.
Here are the files for reference.
The issue is with my last submitted upgrade. The is the first upgrade which I tried to implement "the correct" setup code as opposed to using the arbitrary "2013" which I've been using in the past.
Now I don't want to sound like a little girl crying about double-standards. Even though somewhere deep inside me, there's one moping about her big brother whose able to stay out till all hours of the night while she's stuck at home at 9 p.m. Apparently, using a signature setup code was an okay practice for the Slingbox RMDU files but it isn't prudent using it for the handheld remotes.
I understand the value in using the appropriate setup code. It will broaden the target audience that these uploads will help, so I tried my best to do it with this upgrade. Unfortunately with all the wasted time, I decided to cut my losses and just do one more the old way.
So, back to the problem. This upgrade calls for the following device/sub-device combination; 128.0, 128.1, 128.4, 128.9, 144.0, and 176.0. While this is only six combinations, when I split the values to try and fit it into the Panasonic Mix Combo, it doesn't because it would need a seventh field. So, a second device upgrade would be necessary.
This is where I had the problem, because now I felt like King Solomon having to divide a baby half. Except, I was actually under duress of trying to figure out which half to give to each parent. And after looking at the results of the Lookup tool, I found that there was at least twenty different combinations which it could have been split up. But, after racking my brain, I just couldn't figure out which was the "correct" one.
My final conclusion was use my arbitrary setup code, because to get the bulk of the functions into one upgrade there was no predefined setup code which could have addressed it. There were some which were close but if someone were to use this upgrade as a reference for the EFCs then some of the codes would have been invalid. So, using my arbitrary setup code, I figured the user would have to do their own setup code research and then make their own decision to split it they way they want.
Alright, so, I'm figuring there is no standard of splitting up an upgrade. But, I wanted to get a consensus of how the rest of you would have composed it. That way I can get an understanding of how each of you would have handled it, and I can use it as a guideline for the next time this happens to me.
Here are the files for reference.