tor

tor – terminal for on-site- and remote-operations

Interfaces, cloud connection, data centre

Flexible telemetry and data acquisition solutions – developed for use in mobile applications.

Fields of use

Continuous recording of machine data
Short-term use for sporadic errors
Online access for troubleshooting, maintenance and updates
Display of machine data via web interface
Accompaniment of prototypes and new developments
Predictive maintenance
Cloud connectivity

tor – Variants

tor is available in various expansion stages to cover the requirements of a wide range of appli-cation scenarios.

From the device, which is equipped as Starter only with the software of the device manufactur-er STW, up to a fully equipped Complete variant with which all needs of a modern telemetry solu-tion can be covered.

The functional scope of tor created by us is made available via kits and comprises the following variants.

Kit	Starter	Base	Data	Complete
StarterKit
BaseKit
AdvancedKit
DataKit
ServiceKit
DevKit

The following additional option can be selected for each variant:

machines.insight (STW)

tor – Kits with modules

All tor functionalities are implemented in modules, which come in the following kits. A module always represents a summary of programs (apps) and data that are required for a field of application. Details on the field of application and the functionality of a module can be found on its page.

» 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

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

Technical data

Teleservice Modul ESX®-TCG-4

Power supply	9 ... 32 V DC
Dimensions	174 x 117.4mm (without SMA connectors)
Processor	ARM Cortex A7, 32bit controller, NXP i.MX 6UltraLite, 696MHz
RAM*	1 512 MB DDR3L-SDRAM
EEPROM	128 kB (64 kB free to use)
eMMC Memory*1	8 GB (4 GB free to use)
RTC	Real time clock with internal gold cap for maintaining time for approx. 7 days and system wakeup function
Security*²	TPM2.0 Trusted Platform Module (opt.)
Operating temperature	40°C … +85°C / -40°F … +122°F (internal operating temperature) for further information please refer to the user manual of the TCG-4
Acceleration sensor	Measuring ranges +/-2g or +/-4g or +/-8g or +/-16g (configurable) in 3 axis (X, Y, Z) System wakeup function

4G Modem	Option 1) EMEA (EU): • 4G: Six-band LTE Cat. 1 (B1/B3/B5/B7/B8/B20) • 3G: Tri-band HSPA+ (B1/B5/B8) • 2G: GSM 900/1800 Option 2) North America (US): • 4G: Tri-band LTE Cat. 1 (B2/B4/B12) • 3G: Tri-band HSPA+ (B2/B4/B5) Option 3) Global: ^2 • 4G: LTE Cat. 4 (FDD: B1/2/3/4/5/7/8/12/13/18/19/20/26/28) (TDD: B38/B39/B40/B41) • 3G: B1/2/4/5/6/8/19 • 2G: B2/3/5/8 SIM card options: • 2FF Mini SIM card, can be accessed through a clip at the side of the housing. • Alternative:2 MFF2 eSIM card, can be placed on the PCB (opt.)
GNSS	Standard) Dedicated GNSS receiver: • Simultaneous GPS / GLONASS with max. 10Hz update rate, BeiDou, Galileo, SBAS, QZSS • 5V bias power supply for external, active GNSS antenna, current limited Option) GNSS receiver integrated in cellular modem:^*2 • GPS, GLONASS, BeiDou, Galileo, QZSS, 1Hz update rate
Wi-Fi / Bluetooth	IEEE 802.11 b/g/n – 2.4GHz 64-, 128-, 256-bit WEP, WPA and WPA2.0 TKIP or AES keys Power Class 1 (+18dBm) IEEE 802.11 s mesh network support ^*2 Bluetooth 4.2 (Bluetooth Smart ready: Bluetooth Classic & BLE) Power Class 1.5 (+11.7dBm)
LPWAN*²	Option 1) Europa: LoRaWAN (LoRaWAN class A client transceiver) Option 2) USA: LoRaWAN (LoRaWAN class A client transceiver) Option 3) Wireless M-Bus (client transceiver)
4 x CAN	CAN 2.0B, high / low-speed, max. 1Mbps, listen only mode possible CAN1 wakeup function (optional)^2 CAN3 galvanic decoupled (optional)^2
2 x RS232	Serial interface with programmable baud rate up to 230400baud 2nd serial interface can be RS485 on request^*2
Ethernet	ETH 1 - 10/100-Base-T Half-/Full-Duplex
BroadR-Reach^*2	ETH 2 - 100-Base-T1 (BroadR-Reach)
USB	USB 2.0
4 x Digital Input	Digital Input
4 x Multifunction-Input^*2	Analog Voltage (0...36V) / Current Input (0...24mA) - configurable by software; Digital Input
2 (3)^*2 x Digital Outputs	High side switch, max. 300 mA