Until now, the RCC contained a filter to prevent a user from accidentally uploading a SECURE MODE TCF (T:LAN Configuration File) to a STANDARD MODE T:LAN. This implementation was carried out as follows:
| Scenario | TCF File | T:LAN Mode | Result | Reason |
| A | SECURED TCF | SECURED T:LAN | Allow | Expected Behaviour |
| B | STANDARD TCF | STANDARD T:LAN | Allow | Expected Behaviour |
| C | SECURED TCF | STANDARD T:LAN | Warn User & Block | To Prevent Communication Issues |
| D | STANDARD TCF | SECURED T:LAN | Warn User & Allow if ACKed | Asks User whether or not to proceed |
Starting with RCC Version 3.11.0.695, the behaviour has now been modified to:
| Scenario | TCF File | T:LAN Mode | Result | Reason |
| A | SECURED TCF | SECURED T:LAN | Allow | Expected Behaviour |
| B | STANDARD TCF | STANDARD T:LAN | Allow | Expected Behaviour |
| C | SECURED TCF | STANDARD T:LAN | Warn User & Block | To Prevent Communication Issues if T:LAN Running OS<BN7589 |
| C | SECURED TCF | STANDARD T:LAN | Warn User & Allow if ACKed | If T:LAN Running OS>=BN7589, Then The User Will Be Asked Whether Or Not To Proceed |
| D | STANDARD TCF | SECURED T:LAN | Warn User & Allow if ACKed | Asks User whether or not to proceed |
The change in behaviour is in scenario C. If the T:LAN has been loaded with BN7589 (or newer), then the user will be warned regarding the step he is about to perform but the operation will be allowed to proceed if the user ACKed the request.
NOTE:
BN7589 and up contain a
check to prevent restoring the OPL group settings and OPL Server
Records if the unit is not in SECURE MODE. Older versions do not have
that check and might cut off the user from the unit if restoring a
SECURE TCF to a STANDARD MODE T:LAN.