» StarterKit

Modul: connect.cloud
Connection to machines.cloud. A cloud solution from STW for display of machine data.

Modul: ui.web.stw
The ui.web.stwThe ui.web.stw module (=machines.insight; formerly known as VDS) is a web-based config-uration interface with which many relevant sys-tem parameters can be set and data output. It provides mechanisms to read and process data from the CAN bus. This further processing can take place, for example, in a “Cockpit”, so that CAN data can be visualised directly to the user in graphs, scales and status displays. Another possibility is to set up a “LogJob”, which automatically records the data and prepares them for further processing. The module is also used to set up all required “LogJobs” that are used for the data point model of the connect. cloud module.

Modul: gateway.codesys
The gateway.codesys module is available for CODESYS 3.X and CoDeSys 2.3 and, after activa-tion, provides a service with which the CODESYS programming environment (CODESYS-IDE) is able to access a control unit via the device. This process represents a simple illustration for the developer, as if he were directly on site.
The connection to the control unit is not es-tablished directly with the workstation, but with the gateway.codesys module. Here an Ethernet, CAN or RS232 connection can ex-ist between the devices. The gateway.code-sys module is then largely connected to the
workstation via, for example, Ethernet, WLAN or PPPoE. This makes it possible, for example, to ac-cess a workstation from a remote location via the Internet (via VPN), on-site via CAN, and then the desired control unit.

» BaseKit

Modul: ctrl.cmd
The ctrl.cmd module constitutes an interface with which defined tasks in the system can be implemented and information retrieved. For example, it receives instructions to start and stop other systems, changes system values, e.g. the PIN code for the SIM card used, and provides information on current system statuses.

Base: Functions can only be triggered from the tor web interface.

» AdvancedKit

Modul: ctrl.cmd
The ctrl.cmd module constitutes an interface with which defined tasks in the system can be implemented and information retrieved. For example, it receives instructions to start and stop other systems, changes system values, e.g. the PIN code for the SIM card used, and provides in-formation on current system statuses.

Base: Functions can only be triggered from the tor web interface.
Advanced: Functions can also be triggered via CAN and USB.

Modul: ui.web
The ui.web module is an extension to the func-tionality of the ui.web.stw module, but which is more about module configuration than system configuration. This web-based solution provides access to all configurable tor modules and sends information back to them.

Base: Position determination, input of machine information and PIN
Advanced: Input of network settings, CAN set-tings

» DataKit

Modul: can.recorder

The can.recorder module is an extensively con-figurable instrument for collecting raw data via CAN according to adjustable criteria.
The following configurations can be made:

• Recording of CAN 1 and/or CAN 2
• Filtering of CAN messages
• Storage interval of individual messages
• Memory space
• Ongoing storage and ring storage
• Trigger event
  • Memory full
  • Trigger via CAN

Four can.recorders can be operated in parallel. This allows data to be collected for various pur-poses.

The data of the individual devices are transferred to a WMT server via an encrypted connection and can be downloaded there by the customer.

Modul: data.sync
The data.sync module is used to transport data automatically from the device per configurable trigger or manually via the ui.cmd module. A further mechanism allows data to be transport-ed into the device. Here the type of data is not specified. For example, recorded data from the can.recorder module can be sent by the device or control unit updates and user manuals sent to the device.

» ServiceKit

Modul: can.dialog
With the help of the can.dialog module, CAN messages can be sent to the CAN bus of the machine via tor. The possible applications are not limited, so that it can be used to “flash” con-trol units and to parametrise CAN nodes by SDO protocol or for customer-specific applications.