Nils_Ekberg wrote:By the way Ken, there is a wat to lengthen the signal by modifying the protocol but first make sure it not related to macro speed. Try adding a pause. If it is not in a macro then we can look at the device protocol.
The problem I'm talking about concerns regular keypresses. After installing the extender, my DVR doesn't respond to 10-20% of my keypresses. I'm suspecting that the remote isn't transmitting the signal long enough (I read something in some thread once about the dish boxes not liking short signals). That is of course only a presumption.
How do I modify the protocol in order to experiment?
Ken, there are a few threads on the subject in this forum so try a search on protocol or duration. I will also see if maybe the extender can help by slowing things down a little.
Nils_Ekberg wrote:Ken, there are a few threads on the subject in this forum so try a search on protocol or duration. I will also see if maybe the extender can help by slowing things down a little.
Okay, found that. I used the device combiner and built an upgrade for my dvr, with a duration of 1 everything seems to work consistently.
One odd problem I've got now is that my TV mode (builtin code 0702) seems to not work the same under the extender. For instance, with the extender on, my menu button transmits nothing. My TV device key has the standard macro on it.
kenyarnall wrote:One odd problem I've got now is that my TV mode (builtin code 0702) seems to not work the same under the extender. For instance, with the extender on, my menu button transmits nothing. My TV device key has the standard macro on it.
Ideas?
Ken
Upload the IR file and I will try to look at it a little later. I am getting my butt kicked in scrabble right now
Upload the IR file and I will try to look at it a little later. I am getting my butt kicked in scrabble right now
I think I understand the problem. On the screen you are choosing for O_TV, the menu button acts as a scroll key too. The scrolling isn't happening now. The menu button works correctly in other screens (after pressing scroll).
I tried putting Scroll; Scroll at the end of my TV device macro, but it only scrolls once. A delay problem, maybe?
kenyarnall wrote:I think I understand the problem. On the screen you are choosing for O_TV, the menu button acts as a scroll key too. The scrolling isn't happening now. The menu button works correctly in other screens (after pressing scroll).
I tried putting Scroll; Scroll at the end of my TV device macro, but it only scrolls once. A delay problem, maybe?
ken
Each scroll in a macro will only scroll one screen at a time which is the same as the regular remote but two should scroll 2 if there is more than two screens. I will check that out.
Making the MENU, MAIN PIP and SURROUND act like the regular remote is what I am working on now.
Nils_Ekberg wrote:Making the MENU, MAIN PIP and SURROUND act like the regular remote is what I am working on now.
Actually, I think I may have just been confused by the screen --- the menu button doesn't seem to work on that PIP screen with or without the extender.
Having the scrolling work would be nice, I guess --- as long as I can still put a macro on the PVR VOD button on the cbl/ht device --- I've wanted that since the day I got this remote, and was thrilled to be able to with the extender installed!
Ken
ps I put an X_TV in between the scroll commands in the macro, and it still only scrolled one screen. I'll try more delay later on to see if it is a delay problem, or something else (seems like delay is unlikely, since there's no signal to transmit.)
Don't knock yourself out with the scroll in macro testing. It may not be working the way I thought it would. I will have to tinker with it. In the mean time we are stuck using the manual scroll.
Mine is BJ1. My guess is yours is newer and maybe they worked on the sensitivity issue and that is what is causing the problem. I will have to dig a little. I wonder if Ken's is the same as yours or mine since maybe we just have a revision problem and it may be as simple as a different flag value. Maybe I can do a more generic test.
I also remember you saying that the only time the motion does not reactivate is when it is completely asleep. Is that true?
Nils_Ekberg wrote:Mine is BJ1. My guess is yours is newer and maybe they worked on the sensitivity issue and that is what is causing the problem. I will have to dig a little. I wonder if Ken's is the same as yours or mine since maybe we just have a revision problem and it may be as simple as a different flag value. Maybe I can do a more generic test.
I also remember you saying that the only time the motion does not reactivate is when it is completely asleep. Is that true?
Correct, it's wont turn on the backlight from rest, but the motion sensor will keep the backlight on after i press a button to wake it up. I also notices not all button will wake it up.
I have to say, since beta 3, my remote has not missed a single IR transmission. It is quite functional now =)
