CONTROL LOCK TAP
Currently Version 1.1
This TAP is intended to allow users to set up a code which can lock and unlock the operation of the Toppy Remote Control Unit (RCU) and front panel, including the standby buttons. It has only been tested on the TF5800, but should work on all Topfield PVRs.
Download the TAP from here, unzip the file, and install “ControlLock.tap” in the “ProgramFiles/Auto Start” directory of your Toppy as the first in load order (easiest done with TAP Commander, in my opinion). Reboot the Toppy. On boot, the controls are not locked. Ignore the sample “ControlLock.ini” file at this stage.
To lock the RCU & front panel controls, enter the default lock sequence of “Menu” followed by “PiP Switch” (for TF5800, “Sat” for other models), you will get a brief message that the controls are locked, and the Toppy display will return to the state prior to pressing “Menu”. Alternatively the controls can be locked using the release code sequence, but this can put severe restrictions on the codes that can be used for normal viewing purposes – see below. It does, however, allow you to check that you have remembered the code correctly before it is too late.
Enter the default release code sequence “1”, “2”, “3” to unlock the RCU and front panel controls, which will also put up a brief message to say that the controls are now unlocked. A time of 4.5 seconds is allowed for entering the full release code.
For assessment purpose you can start the TAP from elsewhere, but the Toppy will still respond the key presses processed by any TAPs before Remote Lock in the load order.
The TAP can only be closed down using TAP Commander (or similar), or rebooting the Toppy.
The colours used for the various display elements can be changed using a “skin” file called “ControlLock.mcf” in “ProgramFiles/Settings/Skins/”. If this is not found, “EMJBTaps.mcf” is used, if present. If neither is found, a default colour scheme is used. A copy of a MyStuff skin file can be used, though only the following elements are used:
· “Background=” (normal background)
· “Highlight=” (background for selected menu entry)
· “TextForeground=” (normal text)
· “TextHighlightedForeground=” (selected menu entry text)
· “Frame=” (border round warning/info messages)
and all other entries are ignored. The keywords above should be followed by the red, green & blue values (separated by commas) in the range 0-255 with no spaces or final comma (e.g. 255,0,0 for red, 255,255,0 for yellow etc).
In the normal lock key sequence of Menu followed by Pip Switch/Sat, the Pip Switch/Sat can be changed to any other key except Exit. However if you use Up, Down, or Ok, your use of the standard Toppy menu will be affected so these are not recommended, and if you use OK, Menu, White, Archive, Red, or Green your use of TAP Commander will be affected so these are best avoided also.
The release code can be any sequence of keys, except “Exit” and “Standby” can only be used if manually generating the “.ini” file. However use of “Standby” has not been tested and could cause problems. Otherwise the choice of the release code should not affect any other TAP or any firmware function.
If you intend to use the release code for locking the controls (as opposed to Menu + other key), note that the first 2 key presses will not be intercepted and will be passed on to other TAPs & native Toppy functions. Numeric keys will be interpreted as channel change requests (if valid) while viewing live, and as instructions to jump while watching a recording. Depending on your use, this is likely to drastically reduce the code options. You will either need to use otherwise unused keys, or key pairs that together have no net effect (e.g. Mute/Mute, Info/Info, Ok/Ok, V-/V+ etc).
The easiest way of changing the release code is to access the configuration menu via TAP Commander, in which case you just press the keys you want in the following order:
1. Key to follow “Menu” to lock the controls
2. First key of the code
3. Second key of the code
4. Third key of the code.
and repeat this sequence till you have the settings you want, and then press “Exit”. The settings are then saved in a “ControlLock.ini” file in “ProgramFiles/Settings” for use after subsequent reboots. This rather quirky means of selecting the keys avoids the use of Up/Down for menu item selection, and thus allows them to be used within the code.
Alternatively you can edit the ControlLock.ini file, entering the key codes for the three key presses as decimal values (given, for example in http://members.optusnet.com.au/toppytools/keys.html). The sample in the download zip file sets second locking key to “Play” and the release code to “4”, “5”, “Menu”.
Deletion of “ControlLock.ini” sets the code back to Pip Switch/Sat, 1, 2, 3 at the next reboot.
One side effect is that the hardware forced shutdown of a hung Toppy no longer works. Hopefully this only applies if the Toppy hangs (i.e. crashes) while the controls are locked, but I not been able to test this. Hopefully without the controls being used the Toppy is less likely to crash anyway.
If you are using the TF5000 Display TAP you may see “OFF” briefly displayed on the front panel when pressing the “Standby” key, but I have not found any other oddities.
The automatically generated “ControlLock.ini” file includes the key names as well as the codes, so if you can readily access your Toppy from a PC etc you can determine the current code settings. Alternatively you can load a new “ControlLock.ini” file (such as the one in the download zip file or a back-up copy), and enter the “magic” code “7”,”8”,”9” to cause it to be read (but absence of an “.ini” file will not cause reversion to “1”,”2”, “3”).
Otherwise the only solution is to reboot the Toppy (which will only be possible by switching off at the mains), so it will come up with the controls enabled. You can then either
1. Enter the configuration menu from TAP Commander and choose the settings you want
2. Delete the “ControlLock.ini” file to reset the release code to the default “1”, “2”, “3” (using the native Toppy Archive or Altair etc), and reboot your Toppy again.
Alpha 1: Initial Issue, published as “Remote Lock”, unable to lock Standby buttons
Alpha 2: Name changed to Control Lock to reflect the locking of the front panel controls
Locking of “Standby” function added.
Alpha 2a: Corrects failure to lock << & >> keys.
Alpha 3: Adds “Menu” + other key as alternative means of locking the controls
Alpha 3a: Corrects failure to lock << & >> keys when using new locking method.
V1.0 Adds support for “skins” + minor presentation changes.
V1.1 Correction of skin colour error + minor cosmetic changes
Now supports Remote
Extender TAP & RemExt patch operation to make
more keys available to
You use this TAP at your own risk – the author cannot accept any responsibility for problems arising.
Feedback as below, please.
Via the relevant toppy.org.uk thread, please.
To simonc & Firebird for help with locking out the Standby commands, and feedback from users pointing out problems with using earlier versions.