BeamGage Multiple Processes and Local Port Communication

BeamGage is a multiple process application with three process types which run when BeamGage is operating: Spiricon.ConsoleService.exe, Spiricon.DataServer.exe, and Spiricon.Version5.exe. These processes can be viewed in Windows Task Manager under the Processes tab.

Spiricon.ConsoleService.exe is a Windows service process that launches the BeamGage connections to cameras. Spiricon.DataServer.exe is the process which acquires data from cameras. Spiricon.Version5.exe is the main BeamGage application.

BeamGage requires local (not network or internet) port access to communicate between its multiple processes. This allows for a great amount of flexibility when using multiple camera or multiple analyzer configurations. By default, the port range is TCP 10100-11100. This can be reconfigured if these ports are already in use by another program or system.

If BeamGage cannot communicate with the Spiricon.ConsoleService.exe when it is in fact running, this typically indicates that the TCP communication is being blocked by a firewall or another program is already using those ports. If this is the case, then in the firewall settings (for both Windows Firewall and McAfee) it will be necessary to create a local firewall exception for that port range. Network and internet exceptions will not help and would create an unnecessary vulnerability on your PC. Depending on the firewall in use, you may be required to reboot the PC after making firewall changes.

You may need the assistance of your IT administrator to access port and firewall settings if necessary.