Skip to main content
TKE DDE Configuration/Testing Checklist
- Last updated
-
-
Save as PDF
-
Server Applications
Installed Applications
- MS SQL
- LocalSync
- ServerManager
- TKEInterface
BluSKY Verification
In Setup>Facility>Banks
- Elevator banks are setup as TKE Destination
- Elevator banks have unique numbers corresponding to TKE documentation
- Elevator Banks have cars according to TKE documentation
In Setup>Facility>Cars
- Each car has a unique number corresponding to TKE documentation. You must configure all cars, even when they are not needed for the function of the system
- The first car in the bank has correct floors served by its bank
- Each floor has the correct landing number according to the TKE documentation
In Setup>Destination Keypads
- Each keypad assigned to a correct floor
- Each keypad has an IP address according to TKE documentation
- Each keypad has a name that clearly associates it with the bank, floor and unique keypad number
- If the keypad has a Wiegand controller, check that it is configured
In Setup>Interfloor Matrix
- Each keypad has a floor/schedule pair for each floor in its bank
- For the commission, all floors in every keypad have "Always Off" schedule. This makes floors public and will not lock the building when connecting to TKE
Test Cards
- At least two cards are ready for testing
- At least two persons have assigned above cards and access levels that have assigned floor schedules
- One person has all the floors in the building. Another person has some floors in the building
Server
- Server is created in BluSKY
- Elevator banks are assigned to the server
- Server role is correctly assigned to the server
- Sync status and data upload are enabled
- Data download batch size is set to 500
In Setup>DDE Diagnostics
- System name is visible in DDE Diagnostics screen
- Remote server name is visible in DDE Diagnostics screen
- Elevator Banks and Elevator manufacturer are visible in DDE Diagnostics screen
- Elevator Keypads are visible in DDE Diagnostics screen
- Bank floor stops are visible in DDE diagnostics screen
- Each Floor stop has a correct landing number in parenthesis according to TKE unique numbers
In Control>Elevators
- Elevator Banks are visible in RTC Elevators screen
- All floors are visible per each bank
- All floors have correct names
- All floors are "On Schedule"
Server Verification
Server
- Operating system has all the latest updates
- Windows MSMQ and Telnet features are enabled
- Both NIC Cards are clearly named. One to BluB0X network, another to TKE Elevator. TKE side has IP address 192.168.0.250 and subnet mask 255.255.255.0
- Persisting routing to NIC card is applied (See DDE Routing)
SQL Server
- The latest version of SQL Server (from OPS folder) is installed with dual login mode
LocalSYNC
- The latest version of LocalSync is installed with the Administrator account
- Correct RemoteServerId is specified in LocalSync.exe.config file
- Start Local Sync in Console and verify that there are no errors. (Ignore Inner Exception: Rest API request failed)
- Verify that LocalSync created BluB0X and BluB0XLogs databases in the SQL Server
- Stop LocalSync in the console and start in service mode
ServerManager
- The latest version of the server manager is installed
- Correct RemoteServerId is specified in ServerManager.exe.config file
- Start ServerManager in console mode and verify that there are no errors
- Stop ServerManager in the console and start in service mode
TKEInterface
- The latest version of TKE Interface is installed
- Correct RemoteServerId is specified in TKEInterface.exe.config file
- Correct SignalRUrl is specified in TKEInterface.exe.config file ( <add key="SignalRUrl" value="https://signalrhub.blub0x.com/signalr"/>)
Bench Testing
- Prepare a test simulator computer. Set the IP address of it corresponding to the subnet of TKE controller.
- Start TKE Simulator and configure it to the floors/Banks/kiosks according to TKE documentation
- Connect NIC card of the test simulator computer to the TKE side NIC card of the server
- Start TKE simulator on the test simulator computer
- Start TKEInterface in console mode
- No red line errors in the console screen
- Verify that you can see startup dialog in DDE diagnostics screen
- Verify that all matrixes are coming down from the server to the test simulator
- Click on Heartbeats checkbox in DDE diagnostics screen. Verify that you can see the heartbeats from and to the server
- Uncheck the Heartbeats checkbox. Verify that heartbeats stop showing in DDE diagnostics screen
- Change one of the matrixes in the BluSKY and verify that the change came down to the test simulator
- Simulate a card swipe on the test simulator and verify that TKE Interface replies correctly
- Check "Show Person Floors" checkbox. Swipe the card and verify that allowed floor matrix sent to the test simulator is correct
- Disconnect the cable between the test simulator and server. Wait until TKE interface reports that TKE Group(s) is offline
- Verify that this message is visible in Console and also in DDE diagnostics screen
- Reconnect the cable back. Verify that applications reconnected, keypad matrixes were resent, heartbeats started and card swipes are working properly
- Stop the TKE Interface in console mode
- Restart TKE interface in service mode
- Verify all communication again including matrixes, heartbeats and card swipes
- Verify that card swipes are showing up in the Events and Event History Screens
Building Commissioning
- Remote server is connected and reachable from the internet through TeamViewer
- Local Sync, ServerManager and TKEInterface services are running with Automatic startup
- Start DDE Diagnostics screen in BluSKY and navigate to the System/Server/Elevator bank
- Stop and restart TKEInterface service. Verify that you see the startup communications in DDE Diagnostics screen
- Swipe a card at each keypad on every floor and in every elevator bank. Verify that the correct keypad number is reported in the DDE diagnostic screen
- Connect TKE side NIC Card of the server to the TKE Layer 3 switch
- Verify that the TKE Interface is connected to TKE bank controllers
- Verify that heartbeats are coming and going
- Verify that the keypad matrixes where sent and you can change them
- Verify that the floors open
- Verify that card swipes open the correct floors for that card
- Open Elevators RTC screen. Verify that you can open a floor and place it back to schedule
- Do all other verification required by TKE and building management
- Change the keypads FloorMatrix to the schedules required by the building
- Verify that floors are open or secure according to the applied schedules
DDE Routing
