JP1 Remotes

xnappo · Expert Joined: 30 Dec 2003 Posts: 861

Hi All,

Is it conceptually possible to create a version of the pause protocol that can be canceled on a button press?

Without knowing this particular assembler, it looks like the protocol just delays using opcodes rather than a timer or something - can I just insert a check to see if a button has been pressed somehow?

I use it to do a commercial skip timer and it would be useful to be able to cancel when a tricky short commercial break comes on.

Thanks,
xnappo

Nils_Ekberg · Posted: Wed Jan 16, 2008 9:58 am Post subject:

All of the pause protocols that I am familiar with use the same routine to do the pause. The routine is one that is built into the remote and simply sits in a loop doing nothing based on a numeric time value that is set in the special protocols in IR and passed to the routine. A quick review of the routine shows no way to interrupt it until the timer expires.

However, what it really sounds like you are asking for is how to interrupt the macro sending the command to the device not the pause.

Post what the macro looks like and we can see if we can come up with a recommendation.
_________________
Nils
Files Section
Diagnosis File Section

xnappo · Expert Joined: 30 Dec 2003 Posts: 861

Hmm, the pause protocol I am using is not using anything built into the remote. Here is the code:

FF00: 00 00 DB 00H, 00H
FF02: 01 DB 01H
FF03: E4 03 C2 LD RC2, R03
FF06: C6 C0 00 00 LDW RC0, #0000H
FF0A: 0A FE DJNZ RC0, FF0AH
FF0C: 1A FC DJNZ RC1, FF0AH
FF0E: 2A FA DJNZ RC2, FF0AH
FF10: AF RET

Here is my macro:
FWD
FWD
FWD (go to 3x FWD)
SHIFT-L2 (pause protcol call)
PLAY

Looking at the pause protocol, it seems like if there were a register I could read that indicates a button has been pressed, then I could check for that in between the DJNZs and jump to FF10 if a button press has occured.

Thanks,
xnappo

Nils_Ekberg · Posted: Wed Jan 16, 2008 10:26 am Post subject:

I was looking at the pause protocols that are supplied with the extenders and you are using the generic one. If you tell me what remote you are using I will see if there is a register to test.
_________________
Nils
Files Section
Diagnosis File Section

xnappo · Expert Joined: 30 Dec 2003 Posts: 861

mr_d_p_gumby · Posted: Wed Jan 16, 2008 1:25 pm Post subject:

The extender protocols call internal routines, and sometimes do not work correctly because of that. The generic pause you are using does the timing locally. There is no register that you can check, but you could call an internal routine to check if the key is still down. If the carry bit is set upon return, then a button is still down.

CALL 010Ah
JRC xxxx
_________________
Mike England

JP1 Group at Yahoo!, JP1 Files Area

xnappo · Expert Joined: 30 Dec 2003 Posts: 861

mr_d_p_gumby · Posted: Wed Jan 16, 2008 9:03 pm Post subject:

xnappo · Expert Joined: 30 Dec 2003 Posts: 861

Bummer, doesn't seem to work. I tried a few different combinations. Putting the check between every count seemed to make it pause forever. Here is what I think should work - but it doesn't seem to recognize key presses:

FF00: 00 00 DB 00H, 00H
FF02: 01 DB 01H
FF03: E4 03 C2 LD RC2, R03
FF06: C6 C0 00 00 LDW RC0, #0000H
FF0A: 0A FE DJNZ RC0, FF0AH
FF0C: F6 01 0A CALL 010AH
FF0F: 7B 04 JR C, FF15H
FF11: 1A F7 DJNZ RC1, FF0AH
FF13: 2A F5 DJNZ RC2, FF0AH
FF15: AF RET

Does that look right? Is R03 the value passed in to the protocol?

BTW - kudos to Mark or whoever wrote the built in disassembler in IR - makes it really easy to just write in microcode.

Thanks,
xnappo

xnappo · Expert Joined: 30 Dec 2003 Posts: 861

Nils_Ekberg · Posted: Fri Jan 25, 2008 4:02 pm Post subject:

Try these

xnappo · Expert Joined: 30 Dec 2003 Posts: 861

Thanks Nils. The first one didn't work, but the second is CLOSE!

Using it as you posted makes it immediately exit - so I changed the JRNE to JREQ (which makes sense?)

But... Now it exits the pause if I hit a button, but if I *don't* hit a button it pauses 'forever'. I thought maybe it was just due to the extra opcodes, but I waited a long time (3 minutes) and it still didn't exit.

I assume the CALL opcode saves the registers to the stack? Or is RC2 getting corrupted? Here is the code right now:

Nils_Ekberg · Posted: Sat Jan 26, 2008 11:47 am Post subject:

RC2 is definitely corrupted and will always equal something after coming back from the CALL. Sorry I didn't notice that.

Try this:

xnappo · Expert Joined: 30 Dec 2003 Posts: 861

Sweet! I got it to work. I had to save off RC2. Here is what I did - is there a more elegant way?

Nils_Ekberg · Posted: Sat Jan 26, 2008 11:50 am Post subject:

In my opinion, if it works it is elegant. Laughing

You could just try the last test and see if that works and if not go with what you got to work.
_________________
Nils
Files Section
Diagnosis File Section