GuardPoint Pro - Split Com Engine Application Notes

What is Split Com Engine?
Split com engine always uses the communication engine of GuardPoint Pro to run independently as a windows service regardless if GuardPoint Pro front end is running.
Many Split com engines can run on a single PC, providing GPP with the capability to run in excess of 500 controller networks for very large applications

Activating the ServiceCom 
- The ServiceCom feature requires ServiceCom (SC) on the dongle
- In the GPP.ini look for serviceCom = 0, change to 1 and save.
- Under GPP install folder folder there should be a folder named "secComServiceInstall" created by the setup.
- In the "secComServiceInstall" folder look for these 2 files: 
- secComService.exe.Config
- InstallSecComService.bat (note: do not confuse with InstallSecComServiceSvc.bat)
- Open secComService.exe.Config with notepad and look at the value of "applicationPath".

By default it is "C:\Program Files (x86)\GuardPointPro" 
In case you have installed GPP on a different folder, modify this value accordingly.

Example: 
If GPP is installed on C:\Program Files (x86)\GPP_Split, the relevant line on the .Config should be:
<add key="applicationPath" value="C:\Program Files (x86)\GPP_Split"/>
On the same file set the required baud rate at this line:
<add key="commBaudRate" value="38400" />

The default is set to 38400 but you can set to 9600 or else according to your controllers (note: the baud rate setting on GuardPointPro.ini is not relevant for ServiceCom).
- Run InstallSecComService.bat
This file installs the "secComService" on your PC and starts it. 
This step should take about 1-2 minutes and show the windows command screen. 
If all goes well, the service should be up and running.

To confirm, go to Windows Task Manager > Services tab > Verify that the "secComService" is running. In case you want need to stop or start the service you can do it from this window via the right-click.

The communication with the controller(s) starts about 15 seconds after the service is started. 
You can confirm communication by looking the green/red comm LEDs on the controller. 
The comms with the controller(s) is running even when the GPP server is down.
- Run GPP and verify good communication via the Diagnostics screen.

Independence test
- Stop the service and re-check on GPP Diagnostics. 
All controllers should not communicate and give red X. 
Restart the service and after 15 sec. 
verify that comms are back.
- Exit GPP server and verify that comms are still on by looking at the comms LEDs.
GPP Split mode - Setting up full redundancy
Requirements: GPP version 2.4.605 with two dongles having SQL & Service Com (SC) one on each PC.

Instructions:
1. In the computer screen define the backup server with its name and IP. 
Multicast address should be fixed to 239.0.0.60 for all servers and workstations (unless advised otherwise by your network administrator). Set its type to "Redundant Server" as in this image:

2. On Communication Engine screen define a new engine. 
Set it as a Redundant to the main engine and make a note of its myNetGroupID value shown on the right under the Description box. 
In the example shown here it is set to "2":

3. Install GPP on the redundant PC. 
On the GPP INI file, see that it is set to Split mode by setting the ServiceCom entry to 1. 
In the service folder, SecComServiceInstall, open the configuration file secComService.exe.Config and set it to the same value shown on the myNetGroupID in the previous step. 
See image:

4. On the redundant PC Install the service by executing InstallSecComService.bat
This will auto start the secComService right after its installation process.

5. Now, assuming that both services are up and running, the service on the redundant machine is running in backup mode, waiting to see if the main secComservice has failed. 
Once it does, the redundant service takes over the communication within 90 seconds from the main service's failure.

Note: a short time after (up to about 1 minute after it took over the comms) it also:
a. Starts its own GPP server in "Log Off" mode. 
b. Kills the GPP on the main machine (if indeed it is still running at that time on the main PC).

How to test:
1. Start both services, start the GPP on the main machine, see that comms is fine. 
A Comms. check can be done by looking at the comms. LEDs blinking green-red, or by passing a card / shorting an active input and getting the relevant event on the screen.

2. Stop the secComService on the main machine. This can be done via Task Manager - Services. 
Comms. should be stopped immediately. 
Wait approximately 2 minutes and see (via the comms LED) that comms. is back.

3. Wait another minute and see that the GPP started on the backup machine.

4. Go back to the main machine and see that GPP is down/closed