Modules with Old Configurations

The ILG configuration file contains the modules activation state.

If a configuration is restored with modules in deactivated state, the modules will not stop running instantly. However, they might not be started the next time ILG starts. It is important to check the Modules page, if a configuration is restored, to make sure that all modules are running and that they are activated.

If an old configuration is loaded and ILG adds new modules, it can be necessary to manually activate these new modules that have the Status "New". For instructions for activating modules, refer to the Activating a Module with an old Configuration chapter.

It is not recommended to use ILG with modules not running, however in some cases it can be possible. For cases where it can work, see the list below.

Module

Function

Case where it can be safe to turn off the module

a Connected to the same host running ILG

ProcessControl

Runs the tightening process

If Avantguard or SQS is used

ToolManager

Handles the controller connections

If Avantguard or SQS is used

ProxyService

Required for ILP support

If ILP is not used

PointsenseVolumeControl

Required for ILP support

If ILP is not used

MqttAdapter

Required for ILS support

If ILS is not used

NutEagleSensorDriver

Required for ILS support

If ILS is not used

TurckSensorDriver

Required for ILA support

If ILA is not used

ProjectorDriver

Required for IPG support

If IPG is not used

TighteningTracker

Monitors the ILG process

HttpAdapter

Core module in ILG

Never

WebsocketAdapter

Core module in ILG

Never

LicenseManager

Core module in ILG

Never

VolumeControl

Core module in ILG

If ILP is used

PositioningService

Core module in ILG

Never

RelativePositioningService

Core module in ILG

Never

TighteningDirectionService

Core module in ILG

Never

BarcodeExaminer

Core module in ILG

Never

BarcodeReader

Required for USB connected scannersa

TeachingService

Core module in ILG

Stacklight