Paul,
In the release notes:
Build 279 Enhancements:
New option to force all lock/unlock key entry fields to display like passwords without revealing the value of the key. Useful for when you are controlling a customer’s PC via a remote login and need to enter a key that is not supposed to be revealed to the customer. This option is on by default but can be switched off using Edit->Properties->Tuning Tool->Read/Flash->”Display lock/unlock key entry fields with a password mask.”
Various remote options can now be embedded in a *.ctz or *.coz tune file which will be used to control remote Black Box Flashing, they are ignored during pass-thu flashing. The remote options are available on the [F3: Tune]->[F4: Properties]->[Remote] tab page:
[Set Key] which will ask you to enter a key to be used to unlock the remote controller.
[Clear Key] which will remove the key from the file.
The key is encrypted before being stored in the file.
Try Alt Keys which forces FlashScan/AutoCal to try additional known keys to unlock the controller.
Assume Lock May Be Faulty which forces FlashScan/AutoCal to attempt to unlock the controller even if a lock is not detected.
High Speed (VPW Only) which will attempt to flash the controller using high speed mode (the default value for this option is “checked”).
The remote options listed above can be managed for BBX Quick Setup files in the “Quick Setup Properties” window, available via the Quick Setup right-click menu option: “Quick Setup Properties”.
Adding/removing BBX controllers in the [F5: BBX] tab page now works more intuitively.
Is that a feature to embed a stock tune file to remote unlock any "custom key" locked controller ?
Thanks