About Platform Services

Under its Services container, every station has a PlatformServices container. A few platform configuration items in a host are not directly accessible in a Workbench platform connection to a controller—that is, via the Commissioning Wizard or any of the platform views. Instead, you must have a station installed on the host (any station), and the station must be running.

PlatformServices is different from all other components in a station in the following ways:

It acts as the station interface to specifics about the host platform (whether host controller or a PC).
It is built dynamically at station runtime—you do not see PlatformServices in an offline station.
Any changes you make to PlatformServices or its child services are not stored in the station database.
Instead, changes are stored in other files on the host platform, such as its platform.bog file.

NOTE: Do not attempt to edit platform.bog directly; always use PlatformServices’ views.

Included services are a TcpIpService and LicenseService, which provide station (Fox) access to windows used in platform views, for instance the TCP/IP Configuration window. These services support installations where all configuration must be possible using only a browser connection (and not Workbench connected to the host’s platform daemon).

Using Workbench, you open a station (Fox) connection to that station, and configure these platform-related items by accessing services under the station’s PlatformServices container.

About Platform Services

Related Links