JP1 Remotes

RichardP wrote:Over to Nils then!

I have suspected that there is something not quite right about using M keys, they do have some effect on the current screen selection when used in a macro, maybe there is another register which is used internally by these keys for some reason. In my case I have been able to code round the unexpected screen changes, usually by changing the order of commands in the macro.

I will have to check that one out. Seems odd that that would happen but I believe you

I think since DSM and L/DKP share some common functionality and depend on key interupts there may always be a conflict executing LKP from within a DSM.

There is however, one possibility and that is that interrupts are not being sensed correctly in L/DKP so lets try replacing the 01F9 protocol with the following:

00 00 01 E4 03 4A F0 4A 56 4A 0F F6 32 93 56 03
07 38 3A 26 C3 03 76 2D 08 EB 0C F6 2D 7D FB 1F
76 6B 20 6B F6 8B 1C C6 C0 25 00 F6 01 0D 56 6B
7F E6 F1 7F 6F 76 6B 80 EB 09 76 6B 20 6B F5 38
03 B0 03 A4 03 C3 2B 0D 87 43 2D A6 9B 9C 3B 05
82 9B C4 3A EE AF

It worked once after programming, but then same behaviour as before.

egn wrote:It worked once after programming, but then same behaviour as before.

Wierd that it worked once then went back to old behavior. I will have to try this myself when I get home from work to see what it is acting like.

By the way, just to make sure I am chasing the right thing, does the LKP work on it's own when it is not executed from a DSM?

Hi Nils,

as I followed the recommendation of Richard to simplify the LKP is directly on the the M-key. I now tested again and discovered that the problem also happens on a non-shifted M-key. I also tried with the direct discrete codes which are contained in the LKP and found no problem, except every 4-5 times it happens that a keypress doesn't cause the correspondig action. I have to check again if this is related to the device.

But in general there seems to be a problem that occassionallly a keypress is lost. Once the remote didn't issue any channel+, channel- command, but it worked again after I reselected the device.

The problem is not to critical so take your time.

Thanks,
Emil

Emil

I can not reproduce this behavior at all no matter how many different ways I try it. I even used the same buttons you did (Shift-M4 and shift-8) with and without DSM's

I am wondering if some how you ToadTogs may be stepping on something. For one, check and make sure the the keymove on the SAT Shift 4 is really the toadtog you expect. It just struck me odd that you used TT's on lines 3 & 4 for 0 and jumped to 5 for a TT below on line 16.

Also, double check all the Xshifts that you are using. Remember, that not all buttons in the 8060 can be Xshifted since they conflict with other shifted buttons.

Nils_Ekberg wrote: I am wondering if some how you ToadTogs may be stepping on something. For one, check and make sure the the keymove on the SAT Shift 4 is really the toadtog you expect. It just struck me odd that you used TT's on lines 3 & 4 for 0 and jumped to 5 for a TT below on line 16.

It is not the ToadTog on SAT SHIFT-4, it is the LKP that is on SAT SHIFT-M4. This LKP contains two bare discrete codes for moving the screen up and down. So there is no further magic beside the LKP on the key. As I wrote above, the same problem happend as I reprogrammed the same LKP to the normal SAT M2 key. So the SHIFT is not responsible. With the native discrete codes on the M keys it works with occasional hic-hups.

I will test the following things:
1. I will program double the key codes on the LKP to see whether this helps.

2. I will try the same with two other key codes to find if it is related to the controlled device. May be it is blocked by the repeated command issued with the long press. Here you cannot avoid to send more than one code.

Emil

Emil

I think you may have missed my point on the SAT Shift 4. I think you meant it to be a LKP but you are using the TT protocol (VCR/1800). It looked to me like it was formated the same as other LKP you have.

I do realize you are having the problem on the SAT Shift-M4 but I can not duplicate it.

I started looking at the other keymoves you have and noticed the above. Any error in keymoves and macros when ececuted can cause other problem. That is why I suggested looking at it and the other keycodes. If you have any keymoves or macros pointing to buttons that don't exist or have errors they can cause unpredictable results.

SHIFT-4 was a LKP previousely but now it is a ToadTog that implements a toggle of two discrete codes. I have just taken the exampe you have provided in the ToadTog.txt. That this looks like the LKP is just because I have adjusted the timing values of the LKPs to be 5.

In the meantime I have rearranged a lot and will be able to test this in a few hours.

OK, just wanted to make sure.

Let me know how you make out.

Emil

Still trying to figure out what is going on with you configuration I was reading through your IR file and came up with a couple of questions that may or may not lead me to something.

1) Do you expect the Power macro to work in every device?

There is only a keymove for the button in it in SAT/CBL and VCR so it may do nothing in other devices or pickup other defaults for
SHIFT-DiscreteOFF or DiscreteOFF. If there is nothing on the 3 levels of the button it will only act as a short pause.

2) I also assume you only want the SHIFT-DiscreteON on to work in SAT device if you are already in SAT.

COMMENT: By the way, if the XSHIFT-DiscreteON and OFF are working for you fine but there is some question wether they should work or not as they are on the high end of button codes. If they are working fine ignore this.

Nils,

sorry, I didn't find time to test yet. May be this evening.

Regarding your questions:
1) Yes, finally it should work on every device. I just playing around and making everything work with the SAT device first. This is the device which is mainly used and I use this to test whether my family is able to work with the remote. Step by step I will add the other devices. For some of the devices I will install upgrades containing definitions for SHIFT-DiscreteOFF, others will have explicit keymoves in IR only, and other will have nothing defined.

2) The SAT device is a special device as it is a PC containing 4 digital SAT cards and running LinuxVDR and working as PVR. This device runs permanently and therefor will not be turned off by the user.

Regarding the XSHIFT keys, they are all working fine. There seem to be al lor more key definitions missing in your list. In KM you find a lot of buttons for teletext which are not in your list.

Emil

egn wrote:There seem to be al lor more key definitions missing in your list. In KM you find a lot of buttons for teletext which are not in your list.

Emil

The Teletext buttons fall into the same catagory as the other buttons which change their appearence but remain in the same physical location. They are mapped onto the tape transport button codes. You will also find that they trigger the 8060s animations for Stop, Pause, Play, Fast Forwards and Rewind which is not ideal, but I don't use teletext very much so its not a big issue to me.

Richard

The buttons may be mapped to the transport by default, but the names are at least available as phantom keys in KM. You should be free to assign this phantom keys to any physical key you like.

Emil

Just another idea:

If you can keep track about the current screen you could send different IR commands depending on what screen you currently are. It should be possible to do this with ToadTog. Better would be a protocol like I have proposed it for the scan functionality.

Emil