Page 8 of 17
Posted: Thu Dec 06, 2007 3:21 pm
by unclemiltie
Cap'n
I have not had time to load the remote with anything since I'm trying to (1) rent a short-term apartment, (2) buy a house, (3) get prepared for Christmas, (4) fly a couple of trips across the country to go back to Rochester, (5) arrange the moving of my stuff and (6) keep up with the new job.
sorry that I've not been able to keep up, I was hoping that some of the others would be able to pick up the slack, which Binky has done on the LDKP and taking pieces of the extender and doing fun stuff with the non-extended remote. I can't realistically see how things are going to change in the short term until I get into a house here in CA. But, I'm trying to keep on top of things.
-bill
Posted: Thu Dec 06, 2007 3:33 pm
by Nils_Ekberg
unclemiltie wrote:I have not had time to load the remote with anything since I'm trying to (1) rent a short-term apartment, (2) buy a house, (3) get prepared for Christmas, (4) fly a couple of trips across the country to go back to Rochester, (5) arrange the moving of my stuff and (6) keep up with the new job.
-bill
I know where you are coming from.
Slightly different circumstances for me but the same concept which is why I have not been on here much lately.
Posted: Thu Dec 06, 2007 3:55 pm
by greenough1
unclemiltie wrote:Cap'n
I have not had time to load the remote with anything since I'm trying to (1) rent a short-term apartment, (2) buy a house, (3) get prepared for Christmas, (4) fly a couple of trips across the country to go back to Rochester, (5) arrange the moving of my stuff and (6) keep up with the new job.
sorry that I've not been able to keep up, I was hoping that some of the others would be able to pick up the slack, which Binky has done on the LDKP and taking pieces of the extender and doing fun stuff with the non-extended remote. I can't realistically see how things are going to change in the short term until I get into a house here in CA. But, I'm trying to keep on top of things.
-bill
Bill,
If you can say in words, what you're thinking the issue might be with the extender regarding device selection (and possibly it's effects on macro execution), I might be able to spend sometime with the code.
good luck juggling multiple balls...
Best,
jeff
Posted: Thu Dec 06, 2007 4:09 pm
by speaker.guy
I moved to Rochester in December once 43 years ago.
Good luck!
Posted: Thu Dec 06, 2007 5:19 pm
by Mark Pierson
unclemiltie wrote:I have not had time to load the remote with anything since I'm trying to (1) rent a short-term apartment, (2) buy a house, (3) get prepared for Christmas, (4) fly a couple of trips across the country to go back to Rochester, (5) arrange the moving of my stuff and (6) keep up with the new job.
So what's the problem???
Just kidding... with all that going on it's a small miracle you even bother to check in here!
Posted: Thu Dec 06, 2007 5:28 pm
by vickyg2003
So what's the problem???
Just kidding... with all that going on it's a small miracle you even bother to check in here!
He can't help himself, he's sick and a carrier too!
Posted: Thu Dec 06, 2007 8:33 pm
by Capn Trips
All of you guys (and gals) are worthless and weak!
Try 30 years in the Navy! (OK, it's only been 28, but it FEELS like 30)
TWENTY-ONE addresses (that's TWENTY moves for those of you mathematically challenged!
) in those 28 years.
(and I've hated EVERY ONE, so I feel your pain.)
OK, enough of that.
Bill,
It was just a question, not a demand. I am the first one to appreciate the awesome work that goes on here and to appreciate that it is all done in "free" time which none of use really has to spare, so I try to be careful and precise byt trying to make my requests NOT sound like demands.
"No time" is a perfectly acceptable answer. Whenever it's "gotten around to" is fine with me, I just crave information in the absense of tangible results.
Posted: Fri Dec 07, 2007 11:04 pm
by greenough1
Binky and unclemiltie,
I've uploaded a simple IR file
HERE.
Binky, your ISP keeps bouncing my emails to you from comcast.net.
Take the above file and upload and activate. I setup on TV and CBL a simple DSM for key selection on phantom2 followed by a simple macro.
AUX, DVD and AUD only have default keyset selection macros on them.
I played a bit more and think I see what's going on. If a device button has a macro on it, it takes 2 presses of that device button before it'll execute, unless it's the very first key press after activation.
This doesn't apply to keys that only have the keyset selction macros. pressing these activate properly. Does this help to sort out the issue?
Best,
jeff
Posted: Sun Dec 09, 2007 10:57 am
by binky123
vickyg2003 wrote:Captain, its not THAT curious. I read the extender ASM code, and UncleMiltie is saving the last HT key into the saved Device register AND the active Device Register. But when he processes a key, he sets the Active Device Register. After a punch through key, most remotes restore the Saved Register to the active register, so I would think the restored device will vary depending on the last PseudoHT key was processed. I don't have much time available these days. When I'm at home I'm very busy. Too bad I can't do this at work, where I'm currently bored to tears.
I looked into this switching device issue. I took the default .IR file created from assembling the v0.02 file. Replaced the CBL macro to do X_TV;1;2;3 temporary device selection. I then uploaded into the 3A00 remote, Pressed AUX(which sets the default AUX keysets) and then pressed CBL. First time, AUX LED would light up. Second keypress of CBL, resulted in TV LED lit.
I added a line in the .asm file
Code: Select all
Ret2ROM: LD R_DevX,#FF ;cancel temp device selection
LD R_DevA,R_Dev ;restore current Device to active Device
RET ;return control to the ROM
and re-ran my above test and the second and subsequent keypresses of CBL resulted in the AUX LED lighting up.
I did some more testing and looking at the code and R_Dev is set whenever the O_ Keyset is used. It isn't set anywhere else. Some of the issues we are seeing may be related to our use of R_Dev. I'm not sure what the solution is as I'm not that familiar with extenders.
Posted: Sun Dec 09, 2007 3:38 pm
by greenough1
Thanks Binky as you've essentially duplicated the problem we (I) observed in the 3A33 remote on the 3A00.
jeff
Posted: Mon Dec 31, 2007 6:39 am
by Capn Trips
A plaintive cry for help from the wilderness of those who kknow nothing about programming or assembly or ...
I have finally been able to devote some time to this during the holiday break and have been trying valiantly to make this extender work, but several problems continue to plague.
Activation and Deactivation work fine.
L/DKP and ToadTog work fine.
Haven't tried DSM or Pause.
The device selection issue remains a real pita. Specific example:
All keysets assigned to CBL except Vol keys assigned to AUD. I operate CBL device normally, all is fine. I press a Vol button, and the CBL device's volume is operated. SUBSEQUENT presses of Vol buttons operates the AUD device's volume. The next press of a button mapped to CBL executes that function on the AUD device, but subsequent button operations are directed to the CBL device. So the button assignments don't kick in until AFTER the first press of a button in that particular group, as opposed to WITH that same button press.
Multiplexer doesn't work. I set up a keymove as described in the read me, but all I get is a momentary flicker of the device button, but nothing changes. The remote continues to control the originally-assigned device. Never having used Multiplexer before, I may be doing it wrong, but I don't see what to change in IR's Special Protocol Functions setup sheet for this.
Here's the file with those symptoms.
Bill, if you ever regain some control over your time (or anybody else who can understand this extender programming stuff - Vicky? Binky?) I would be SOOOOOOOO grateful for another attack at sorting this thing out, since I'm stuck right now. Although my 8910 has enough devices, it does NOT have enough upgrade memory when extended, nor do my 1994, 2117, nor 6131. I have to use a JP1.X, and the 1055 (JP1.2) doesn't have that important "D" button.
Posted: Mon Dec 31, 2007 10:31 am
by unclemiltie
Things will be getting back to "normal" in about a week and this is on the list of things that I want to get back to. In the mean time, if anyone else is willing to take a look at it, PM me and I'll make sure you have the latest versions of everything.
-bill
Posted: Fri Jan 04, 2008 7:22 pm
by vickyg2003
Has the issue with device settings been solved yet? Or are certain keys reverting to TV Cbl etc? The Comcast 1067 has that behavior when not extended. It is dependent on whether the current Device is TV or Cable or AUX on how the punch thru works. Its very much like what was described here.
Posted: Fri Jan 04, 2008 11:08 pm
by Capn Trips
vickyg2003 wrote:Has the issue with device settings been solved yet?
Nope.
vickyg2003 wrote:Or are certain keys reverting to TV Cbl etc? The Comcast 1067 has that behavior when not extended. It is dependent on whether the current Device is TV or Cable or AUX on how the punch thru works. Its very much like what was described here.
Well, the symptom I now see is somewhat different than had been described a few pages ago (PIP keys would throw the remote into TV mdoe, and Transport keys would throw it into VCR mode even when unintended). The current symptom is that when different keysets are assigned to different devices, the "change" to the device does not occur UPON pressing the key assigned to a different device, but AFTER that keypress.
Example: All keysets are assigned to CBL except for Vol assigned to AUD.
I press channel selections, menu, PIP, transport keys all correctly operate the CBL device. I press a Vol key and upon the FIRST press, it still operates the CBL device, but on SUBSEQUENT presses, it operates the AUD device. Similarly, after making a few Vol adjustments, the next press of a non-Vol key (like Play or Ch+) operates the AUD device and only SUBSEQUENT presses will operate the CBL device as intended.
So it's like the Keyset-related device assignment occurs AFTER the pressed key has executed its currently assigned function, not before.
So the logic that the I see the extended remote following on a keypress is:
(1) What device is the key that was LAST pressed assigned to?
(2) Execute the function assigned to the currently-pressed button for the device identified in (1)
The next button you press follows the same behaviour. If I alternate Vol with Ch button presses, I will always operate the WRONG device.
Posted: Sat Jan 05, 2008 5:37 am
by vickyg2003
Capn, pull out your 1067 and put some batteries in it and you will see your previous problem. Press TV and the transport keys punch through to Aux. I'm 90% sure that its not the device table that's getting overwritten, but rather the extender is hitting the native punch thru behavior and the patch to try to fix that is making the problem worse.
I think I managed to avoid that in the 1067 extender, as the LED's were lighting correctly and the TV wasn't responding when not in TV mode. But my testing is only light.
You said LKP and DKP were working correctly. I am assuming that a keymove or macro doesn't trigger this behavior, only the "do normal" routine.
Do we have the previous version of this, or knowing the people that are working on this, I'm sure the patch is well documented and can be rolled out.
Which Atlases are exhibiting this behavior?
Does this behavior occur after a KM, or only after an native key?