Overview:
An issue has been identified in Forcefield 8 when programming a TS1066 or TS1067 NAC in 8 Door mode, where door numbering is currently handled incorrectly. Doors 1-4 are shown as doors 5-8, and doors 5-8 are shown as doors 1-4.
All the items on the Door/Lift page are correct, which includes for example, the Door Id text (next to the Door/Lift "Num" box), and Name and Description, etc. The issue is with all the sub-pages under the "Programming" button that show the values for the swapped around door number as mentioned above.
So all the items under these sub-menus circled in GREEN are what are swapped around:
Patch available:
A patch can be available on request from your Distributor for this issue. Note that this patch is not a public release, so is only provided on request. For sites that wish to operate on a public release of Forcefield, the workaround mentioned further below still applies.
However if you would like further information on the patch, please see the following article:
Forcefield patch from 8.1.0 B32 to 8.1.1 B3 instructions
Workaround:
Using CTPlus for all door hardware programming:
The current recommended workaround for this issue is to do all hardware programming editing from CTPlus, and then read programming back into Forcefield, using the "Get Data from Panel" feature.
(NOTE: When using the "Get Data from Panel" feature, you should not tick the "Clear Forcefield's Panel Data Before Get" option, unless you specifically want to clear Forcefield's data, but this may unlink profiles / access as well if done)
Remember that the doors will appear the correct way around if viewing programming in CTPlus. It is only in Forcefield that the door programming is swapped around as described above.
Suggested workflow:
- Initial programming of the doors would be done in CTPlus.
- Programming would be read into Forcefield using the "Get Data from Panel" feature.
- To achieve correct door naming when cards are badged, the doors in Forcefield should then be named and given their Door ID in the CORRECT order (so named as doors 1-8, not with any swapping around of the order) as the Door ID and Name fields on the Door/Lift page are correct. Remember it is only the items under the "Programming" sub menus that are swapped around.
- Any further programming should then be done in CTPlus again (ensuring that CTPlus always has a current copy of what is in the panel first), and then programming read back into Forcefield using the "Get Data from Panel feature. Forcefield will still maintain the correct door names entered in Forcefield.
Using Forcefield to edit door programming:
If you need to use Forcefield to edit door programming, then in Forcefield you will need to always view / program Doors 1-4's Programming sub-pages by editing Doors 5-8, and view / program Doors 5-8's Programming sub-pages by editing Doors 1-4.
But remember that the fields on the "Doors/Lift" page itself are the correct way around, it is just all the items under the "Programming" submenus that are swapped around.
WARNING:
We recommend against using Forcefield for editing this programming, and if you do, you should also thoroughly test the operation, and retrieve the programming into CTPlus to verify that you have programmed it to the correct doors, and that the operation is as intended.
It is also not advised that end customers be doing any door hardware programming, this should always only be done by a Licensed Security Installer.
Events:
When a door is badged, the event will also show correctly as the right door, but it will not show the correct Reader on that door, as Forcefield will be looking at what reader is under the swapped around door. So you may see an event something like is shown below, with the "[Rdr: ??]" or even an incorrect reader name shown.
Here's an example of what you may see:
In this example, the Door Id "FF NAC Door 5 DWI" is correct, but the Reader "[Rdr:?? 1]" is unknown.
This is to be expected, and is a symptom of this door swap around issue in Forcefield at this stage.
Extra Information:
Current latest Forcefield version that this issue has been identified in:
- Forcefield 8.1.0 B32 (also present in Forcefield 8 versions before this)
To enquire about the patch for this issue (mentioned earlier in this article), please reach out to your local Distributor.