Nexeed
    • Introduction
    • User manual
      • Getting started
        • Device registration overview
          • Registering a device
          • Self-registration of devices
        • Device claiming
          • Adding a ctrlX Core device
          • Adding a Rexroth connectivity unit device
      • Device overview
        • Setting the filter for the search
        • Device details
        • Edit device properties
        • Roll out artifacts on one or more devices
        • Rolling out a distribution
      • Device groups
        • Creating a device group
      • Machine overview
        • Create, edit and delete machines
        • Adding machines and devices via CSV file import
        • Structure of the CSV import file
      • Activity overview
      • Distribution overview
        • Managing distributions
        • Managing commands in a distribution
    • Operations manual
      • Overview
      • System architecture and interfaces
        • Element descriptions
        • Network connections overview
      • System requirements
        • General system requirements
        • Ingress controller
        • idm/idm-device-administration-app
        • idm/idm-software-management-app
        • idm/idm-device-monitoring-app
        • idm/idm-device-master-data-mgmt-app
        • idm/idm-device-app
        • idm/idm-solution-app
        • idm/idm-webapp-backend
        • idm/idm-device-tunnel-app
        • idm/idm-artifact-repository
        • bci-app/opensearch
        • bci-app/opensearch-dashboards
        • bci-app/valkey
        • bci-app/nginx
        • bci-kube/nexeed-ansible-operator
      • Migration from previous versions
      • Setup and configuration
        • Installation guide
          • How to initialize OpenSearch
          • How to create MACMA tenants with basic authentication
          • How to configure tenants for artifact-related use cases
        • Configuration
          • Detailed configuration parameters
          • Recommendations for service meshes
      • Start and shutdown
      • Regular operations
        • Whitelist new certificate
      • Failure handling
        • Device Portal data is out of sync
        • How to synchronize devices and machines to OpenSearch
        • Synchronize communication id mapping to key-value store (Redis/Valkey)
      • Backup and Restore
      • Logging and monitoring
      • Known limitations
    • Developer guide
      • Communication ID
      • Adding diagnostic functionality to devices
      • Add command processing to devices
      • Add the backup/restore functionality to devices
      • Reducing data consumption of device communication
      • Access through a custom application
    • Artifact Repository guide
      • Introduction
      • Providing artifacts for roll-out
        • Establishing a connection to the Device Portal
        • Uploading and managing artifacts in the repository
      • Downloading artifacts
      • Sending commands
    • API documentation
    • Glossary
Device Portal
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Direct Data Link
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Device Portal
  • User manual
  • Getting started
  • Device claiming
  • Adding a Rexroth connectivity unit device

Adding a Rexroth connectivity unit device

Rexroth Connectivity Unit (RCU) devices can be added as follows:

Requirements

  • User role DP_DEVICE_CREATE

  • CSV file configured in accordance with Device Portal requests

Procedure

  1. Click Select in the Rexroth Connectivity Unit (RCU) tile.

    Add Device View
  2. Click Browse… to select the CSV file.

    DevicePortal_BulkClaiming_ValidationSuccess

    If the file does not meet the specifications, the relevant errors are displayed.

    DevicePortal_BulkClaiming_ValidationError

    DevicePortal_BulkClaiming_ValidationError
  3. Click Add devices to add them to the tenant.

    DevicePortal_BulkClaiming_Success

One or more Rexroth Connectivity Unit devices have been added to the Device Portal. The devices can now be managed in the Device Overview view.

Structure of the CSV import file

The information for the CSV file can be found on the relevant type plate of the device.

To be able to correctly add the Rexroth Connectivity Unit to the Device Portal, the CSV file must meet the following boundary parameters:

  • Formatting:

    • File extension.csv

    • Semicolon used as a separator between columns

    • Encoding: UTF-8 (with Excel - Office 365, save as CSV UTF-8)

  • Content:

    • Maximum 1000 rows

    • Device ID (= serial number) and Secret (= IMEI) can be found on the device label

    • Characters permitted for device ID: A-Z a-z 0-9 _ -. :

    • Characters permitted for device name and description: A-Z a-z 0-9 ä Ä ö Ö ü Ü ß ? + -. : / ( ) * = #

    • Name: If no name if specified, the device ID is used as the name

  • CSV file structure

    Column name Description

    device_identifier (mandatory)

    Serial number of the device with an additional character

    The serial number can be found as a barcode on the packaging and on the rating plate of the device.

    secret (mandatory)

    IMEI number of the device

    The number can be found on the packaging and on the rating plate of the device.

    device_name

    Device name that appears in the Device Overview view. The device names can be used to search in the Device Portal.

    device_description

    Device description

Claiming RCU Example CSV file

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses