DVICO TVIX HD M-5100SH

[vickyg2003]

i have tested rob's upgrade, but the repeat comes too fast.
i compared it with orig. remote. and there it is very fast too.

Wait up, so you're saying the original remote repeats too fast also? That's what we've been trying to replicate, so that would have been very useful to know up front.

That's what I suspected all along. All repeating keys are too fast for me too. I've changed all my Nec2 devices to Nec1 simply to get rid of my repeating.

If the FF FD time from Vicky's upgrade is still too fast, we would need to write some assembler code to introduce a larger delay.

While that is the kind of solution that interests me. I still think a helper upgrade would be the way to go. Creating a secondary device/protcol comination where the primary only repeating on the vol/ch/fwd/rwd and the secondary has repeating on arrow keys would work nicely. A shifted Arrow would be the repeating arrow, for use with his title selection since there is no paging, when close using the main arrow would provide one move at a time.

Friday Please answer these question.

What are your physical restrictions when it comes to pressing the keys?

Are your fingers slow? Do you have a limited range of motion?

Are you physically able to do a shift, arrow key?

[friday]

i am sorry that i said it not befor, but from the first day i never used the original remote.

the FF FD is not to fast, but the repeat comes to early as i said.

you mean a delay between the first click and the start of repeat?

that would be great

Do you have a limited range of motion?

yes, normaly i can reach all buttons. but in some position (laying in bed) i cant.

most of time i have the remote in my left hand. but in bed i can´t reach the above keys with my fingers. so the shifted-keys are not really helpful for me.
of course i do have shifted-keys for my 3rd device. but i do this only 1 time. mostly my assistent do
but in use i often navigate through my large videolist. then is a fast repeat helpfull. but i also change often the setups for different movies (divx, avi, mkv, dvd). and then is the problem with confirming, that i never hit "yes"

[The Robman]

Unfortunately, I don't know how to do this with the HCS08 processor, so I would need Mike's help.

Here's what needs to be done.

1) Setup the protocol as "non repeating"
2) CALL the IR engine to send the first occurrence
3) If the button still held, delay by a certain amount
4) Change the protocol to "repeating"
5) JUMP to the IR engine to send repeating signal.

[vickyg2003]

Rob,

Unfortunately, I don't know how to do this with the HCS08 processor, so I would need Mike's help.

Or I would need yours, . I just popped in to ask you to do this in general terms, and there is your post.

Step 3 is the kicker. You basically need to do the LKP function without all the buffer stuffing at that point, and that doesn't translate well because although these are all HCS08 Processors, they are different chips and the interrupts work a little differently on each remote.

I can try it on one of my HCS08's and then see if I can figure out how to do this on the Dreambox.

[The Robman]

There must be a way to do it, because this is needed for the XMP (aka "Dreambox") and DirecTV executors. Try PINGing Mike to see if he's available.

[vickyg2003]

There must be a way to do it, because this is needed for the XMP (aka "Dreambox") and DirecTV executors.

I just opened KM 9.17 and switched to DirecTV for the URC-8820 and got a big red message that said this protocol code is not available for this remote. If there is generic code for the HCS08, where would I find it?

[The Robman]

This is from protocols.ini

Code.HCS08= 20 06 17 2F 11 08 0B B8 04 60 0E 45 23 46 02 60 \
03 45 21 43 35 A7 CD FF 6E 4F BE 61 3A A2 58 24 \
04 BB A2 BB A2 58 24 02 BB A2 3B A2 EF 48 48 48 \
48 B7 62 AD 3E 4E 60 A2 AD 25 4E 61 A2 AD 1E 4E \
62 A2 AD 1B AD 1B 45 05 DC 35 6A 45 39 6C 00 60 \
03 45 10 68 CD FF 74 CD FF 92 25 D7 81 AD 00 AD \
00 45 01 2C 35 6C 38 A2 24 03 45 02 58 35 6A 38 \
A2 24 05 45 02 58 35 6C AE 6A CC FF 65

[mr_d_p_gumby]

Unfortunately, I don't know how to do this with the HCS08 processor, so I would need Mike's help.

Here's what needs to be done.

1) Setup the protocol as "non repeating"
2) CALL the IR engine to send the first occurrence
3) If the button still held, delay by a certain amount
4) Change the protocol to "repeating"
5) JUMP to the IR engine to send repeating signal.

1) Same flag bits as S3C8
2) JSR $FF5F
3) JSR $FF92, carry set if button still down; delay could be done with JSR $FF74 with time in uS loaded in H:X. If that's not long enough, maybe try calling the delay loop at $FFA1 with values in X and A (A is outer loop count).
4) Same flag bits as S3C8
5) JSR or JMP $FF5F again.

Hope this helps. (I'm a little short of time at the moment, but I'll try to help out more if you guys get stuck.)

[vickyg2003]

Thanks Mike, I had alredy found the keyboard interrupt routine from the example protocol that Rob had posted, but it was nice to get confirmation.

Rob or Mike, this protocol has a very nice delay before the repeating starts, BUT it only sends the repeating part after the delay, the lead-in, lead-out part. I would think after that much of a delay, we'd really need to resend the whole signal because the device might not be listening any longer.

Upgrade protocol 0 = 01 FF (HCS08) Tvix 5000 DELAYED REPEAT (PB v4.01)
20 15 23 47 11 C5 4C 08 08 01 21 03 45 01 21 01
1A D4 FD 11 A7 08 CB 3F 62 3F 63 6E 03 AA CD FF
5F 45 10 4D CD FF 74 3B A3 F7 CD FF 92 25 01 81
6E 4D A3 CC FF 5F
End

Rob/Mike Can you tell me in English how I might do a repeat of the whole signal before I start repeating?

Friday, can you confirm that the protocol above does NOT work for repeating?

[The Robman]

I think it would be OK to send the whole signal after the delay.

[vickyg2003]

I think it would be OK to send the whole signal after the delay.

, Now there is an understatement. It might not be necessary if the upgrade repeats for Friday. However, I strongly suspect that the TVIX will no longer be listening by the time the time the repeat starts.

I think that with a delay this long I should proceed as if this is a brand new keypress. The question is HOW! Does it have something to do with DCBuff? Does it have something to do with protocol flags? Both?
The assembly language is easy, its the concepts of the invisible signals that is killing me. The vocabulary alone is killing me.

[friday]

vicky your protocol doesn´t do anything
the tvix is not responding on any key

[vickyg2003]

Hmmm, I wonder what I did. It was very late last night when I was working on this, and I was concentrating on the timing, I should have been more careful. I'll work on this again tonight, but I think this might take me more than an evening to get you something more to test.

[friday]

no problem, take your time

[The Robman]

I think it would be OK to send the whole signal after the delay.

, Now there is an understatement. It might not be necessary if the upgrade repeats for Friday. However, I strongly suspect that the TVIX will no longer be listening by the time the time the repeat starts.

I think that with a delay this long I should proceed as if this is a brand new keypress. The question is HOW! Does it have something to do with DCBuff? Does it have something to do with protocol flags? Both?
The assembly language is easy, its the concepts of the invisible signals that is killing me. The vocabulary alone is killing me.

When you jump to the IR engine after the delay, it will either send the data again or it won't. If it doesn't, and you want the data a 2nd time, you could call the Ir engine before you jump to it.

In S3C8 code, it would look like this...
1) CALL $0146 (IR engine) - send data first time
2) CALL $010A - test for button hold
3) JRNC exit - if not, exit
4) LDW RRF8,#2904H - load the delay time
5) CALL $0158H - execute the delay
6) CALL $010A - test for button hold
7) JRNC exit - if not, exit
8) CALL $0146 (IR engine) - send data second time
9) OR R29,#01h - turn on the repeat flag
10) JP $0146 (IR engine) - jump to the IR engine and exit