LogoLogo
Contact Uscybus.io
Connectware 1.7.2
Connectware 1.7.2
  • Getting Started
    • Introduction
    • Installing Connectware
      • System Requirements
      • Acquiring your License Key
      • Installing Connectware on Docker
      • Installing Connectware on Kubernetes
    • Connectware Admin UI
    • Basic Components of Connectware
    • Connecting your First Machine
      • Your First Service Commissioning File
  • Documentation
    • Services
      • Structure of Commissioning Files
        • version
        • description
        • metadata
        • parameters
        • definitions
        • resources
          • Cybus::Connection
          • Cybus::Endpoint
          • Cybus:Mapping
          • Cybus::Container
            • Docker problem with network changes
          • Cybus::Link
          • Cybus::IngressRoute
          • Cybus::User
          • Cybus::Role
          • Cybus::Volume
          • Cybus::File
          • Rules Objects
          • Cybus::Server
          • Cybus::Node
      • ServiceID
      • Inter-Service Referencing
      • Deviation
      • Working with Service Commissioning Files
      • Service Details View
      • Sample Service Commissioning Files
        • Modbus
          • “Bearbeitungszentrum BAZ” - Single File
          • “Bearbeitungszentrum BAZ” - Multiple Files
          • “Bearbeitungszentrum BAZ” - Single File and Custom Topics
          • “Bearbeitungszentrum BAZ” - Agent Mode
        • Machine Condition Monitoring : OPC UA + InfluxDB + Grafana Dashboard
          • “Machine Condition Monitoring Example” - Single File
        • Machine Utilization Example (Multi file service composition) : Modbus TCP + InfluxDB + Grafana + MSS
          • “Machine Utilization Example” - Machine Connectivity
          • “Machine Utilization Example” - Dashboards with role based access permission
          • “Machine Utilization Example” - Push data to MSSQL Database
      • API Definition
    • Resources
      • Containers
      • Volumes
      • Connections
      • Endpoints
      • Mappings
      • Servers
      • Nodes
      • API Definition
    • User Management
      • Users and Roles View
      • Users
      • Roles
      • Permissions
      • Password Policy Rules
      • Default Admin User
      • MQTT Users
      • Adding a MQTT Publish Prefix for Users
      • Multi-Factor Authentication
      • Long lived JSON Web Tokens
      • Access Permissions for Admin-UI
        • UI Access
        • Minimum Access Role Pages
      • API Definition
    • Client Registry
      • Implicit Flow
      • Explicit Flow
      • Granting Access
      • API Definition
    • Certificates
    • Explorer
    • Workbench
      • Flows in Git Repositories
    • System Status
      • Info
      • Metrics
      • Status
      • Retrieving More System Information
      • System Health
      • API Definition
    • Backup and Restore
      • Volumes
      • User Database
    • Configuration
      • Environment Variables
      • LDAP Configuration
      • MFA Configuration
    • Agents
      • Installation
      • Registration
      • Usage
      • Monitoring
    • Industry Protocol Details
      • ADS
        • AdsConnection
        • AdsEndpoint
      • BACnet
        • BacnetConnection
        • BacnetEndpoint
      • EtherNet/IP
        • EthernetIpConnection
        • EthernetIpEndpoint
      • Focas
        • FocasConnection
        • FocasEndpoint
      • Generic VRPC
        • GenericVrpcConnection
        • GenericVrpcEndpoint
      • Hottinger Baldwin Messtechnik (HBM)
        • HbmdaqConnection
        • HbmdaqEndpoint
      • Heidenhain DNC
        • HeidenhainConnection
        • HeidenhainEndpoint
      • HTTP/REST
        • HttpConnection
        • HttpEndpoint
      • HTTP Server
        • HttpServer
        • HttpNode
      • InfluxDB
        • InfluxdbConnection
        • InfluxdbEndpoint
      • Kafka
        • KafkaConnection
        • KafkaEndpoint
      • Modbus/TCP
        • ModbusConnection
        • ModbusEndpoint
      • MQTT
        • MqttConnection
        • MqttEndpoint
      • MSSQL
        • MssqlConnection
        • MssqlEndpoint
      • OPC DA
        • OpcdaConnection
        • OpcdaEndpoint
      • OPC UA
        • OPC UA Client
          • OpcuaConnection
          • OpcuaEndpoint
        • OPC UA Server
          • OpcuaServer
          • OpcuaNode
        • OPC UA Object Types
        • OPC UA Server References
          • OpcuaReferenceNode
          • OpcuaObjectNode
      • Profinet
        • ProfinetConnection
        • ProfinetEndpoint
      • Siemens SIMATIC S7
        • S7Connection
        • S7Endpoint
      • Shdr
        • ShdrConnection
        • ShdrEndpoint
      • Sinumerik
        • SinumerikConnection
        • SinumerikEndpoint
      • Sopas
        • SopasConnection
        • SopasEndpoint
      • SQL
        • SqlConnection
        • SqlEndpoint
      • Werma WIN Ethernet
        • WermaConnection
        • WermaEndpoint
      • Systemstate
        • SystemstateConnection
        • SystemstateEndpoint
      • API Definition
    • Connectware Licensing
    • Changelog and Upgrade Guide
      • Upgrading from 1.x to 1.7.0
      • Upgrading from 1.x to 1.5.0
      • General changes from 0.x to 1.0
        • Upgrading from 0.x to 1.0
Powered by GitBook
LogoLogo

Cybus

  • Terms and Condition
  • Imprint
  • Data Privacy

© Copyright 2025, Cybus GmbH

On this page
  • Example Configuration
  • Received data for tiers
  • Received data for rssi
  • Received data for all
  • Received data for raw

Was this helpful?

  1. Documentation
  2. Industry Protocol Details

Werma WIN Ethernet

PreviousSqlEndpointNextWermaConnection

Last updated 8 months ago

Was this helpful?

The Werma WIN system is a wireless communication system for making simple machine state information available for digital processing. The system especially enables connected stacklights. With the Cybus Connectware, the Werma WIN data can easily be made available in your shopfloor data structure.

The Werma WIN system consists of the following components:

Werma WIN Ethernet Master

The master acts as an access point to the wireless sensor system. Its ethernet port must be reachable by the Cybus Connectware. In order to commission the data acquisition, the IP address of the ethernet master must be known. A single master is used for managing access to multiple slaves.

Werma WIN Slaves

Each machine / stack light is equipped with a dedicated slave. Each slave is identified by its mac address, which can be found out by inspecting the Cybus logs or with the Werma WIN Windows Configuration tool. Every slave provides the following data points:

  • RSSI: an indicator for the wireless signal strength of this particular slave.

  • Tiers (t1,t2,t3,t4): represent the state of the up to four digital switches. A tier is usually associated with a specific color. Tiers may carry one of the following values: ‘on’, ‘off’, or ‘blink’.

State updates from slaves can be triggered asynchronously at fixed time intervals as well as on state changes of any of the tiers.

Werma WIN Easy Software

For system setup and configuration and especially the association between master and slaves, you need to use the Werma WIN Windows Software that is shipped with the hardware.

Werma WIN Shopfloor Manager

The proprietary shopfloor management application from Werma can be used in conjunction with the Connectware. Because a Werma WIN Ethernet Master does not allow multiple concurrent connections, the Cybus Werma Proxy Service can be used to distribute data simultaneously.

The Cybus Connectware Werma protocol maps the proprietary Werma WIN Protocol into MQTT/JSON.

Example Configuration

The following example demonstrates how to configure a simple Werma connection and endpoint that subscribes to a device specified by its MAC address.

wermaConnection:
  type: Cybus::Connection
  properties:
    protocol: Werma
    connection:
      port: !ref host
      host: !ref host
      password: !ref password
      connectionStrategy:
        initialDelay: 1000
        maxDelay: 10000
        incrementFactor: 2

wermaSubscribe:
  type: Cybus::Endpoint
  properties:
    protocol: Werma
    connection: !ref wermaConnection
    subscribe:
      mac: !ref macAddress

Received data for tiers

{ 'timestamp': '<unix timestamp in ms>', 'value': "'on'|'off'|'blink'" }

Received data for rssi

{ 'timestamp': '<unix timestamp in ms>', 'value': '<float>' }

Received data for all

{
    'timestamp': '<unix timestamp in ms>',
    'value': { 't1': "'on'|'off'|'blink'", 't2': "'on'|'off'|'blink'", 't3': "'on'|'off'|'blink'", 't4': "'on'|'off'|'blink'", 'rssi': '<float>' },
}

Received data for raw

The raw data is forwarded as received from the Werma WIN Ethernet master without any further processing or decoration.

Connection Properties
Endpoint Properties