Depence R4
  • Depence R4 Documentation
  • Getting Started
    • Installation
      • Update
      • Start Options
    • Projects
    • System Requirements
    • Graphics Hardware
  • Program Overview
    • Workspaces
    • Windows
    • Supported File Formats
      • Supported 3D-Model Import Formats
      • Supported Image / Texture Formats
    • Camera & Navigation
    • Render Views
      • Quad View
      • Background Image
    • Shortcuts
    • Fixture Manager
    • Auto Backup
  • Construction
    • Scene Graph & Grouping
      • 3D Hierarchy Filters
      • Group Objects
    • Object Extensions
      • Depending Visibility
      • Spline Arrange
      • Reflector
    • Layers
    • Editor Tools
      • Selection
      • Move Objects
      • Rotate Objects
      • Transformation
      • CAD Editor Snapping
    • Splines
      • Draw a Spline
      • Circle Spline
      • Rectangle Spline
      • Star Spline
      • Formular Spline
    • Nurbs
    • Add Fixtures and Objects
      • Fixture Hang Tool
    • Connect Dependencies
      • Manual Connect
      • Distributors
      • Auto Connect
      • Disconnect
    • Terrain
      • Terrain Sculpting Tool
      • Terrain Painting Tool
      • Terrain Mass Placement Tool
    • Atmosphere
    • Crowds
    • Import 3D Models
      • Tips & Tricks for 3D modeling
    • Arealights
    • Materials
      • PBR Material
        • DMX Control
        • DMX Matrix
        • Chroma-Key
      • Water Material
      • Video-Wall Material
    • Video Sources
      • Camera Video Source
      • Media-Player
      • NDI Video Source
    • My Library
    • Fixtures
      • Lighting Fixtures Settings
      • Modular Fixtures
      • DMX Motors
      • Channel Patch
      • Patching and Multiple DMX Address
      • Replace a fixture by another one
    • Laser
      • Connect Pangolin Beyond
      • Connect Lasergraph DSP
    • Firework
      • Firework by DMX
      • Timeline workflow
        • Alignment
        • Arrange Events
        • Stepper
        • Spline-Positions
      • Build custom Effects
        • Generic Firework Objects
        • Shell
        • Stars
        • Tail
        • Crackle
        • Cake Box
    • Decals
    • MVR
    • Drones
  • Show & Animation
    • Selection Groups
    • Schematic Views
    • Repository
      • Team Management
      • Scenes
        • Scene Fade / Delay Path
      • Audio & Video Files
      • Sequences
      • Playlists
      • MsgCues
      • Scripts
      • Profiles
      • Virtual Masters
    • Programmer
      • Table View
      • Full Open
      • Release/Clear
      • Value Editors
        • Value
        • Position
        • Color Mix
        • Effects
          • Wave FX
          • Color FX
          • Position FX
      • Panorama Alignment
      • Post Selection
      • Store a Scene
      • Palettes
        • Store values in Palette
        • Use a Palette
        • Edit Palette Values
    • Selection Tool
    • Show Sequencer
      • Track Types
        • Repository Scene Track
        • Any Scene Track
        • Fixture Group Tracks
        • Sequence Track
        • Audio Track
        • Video Track
        • DMX-Stream Track
        • MsgCue Track
        • Script Track
        • Multimedia Stream Track
        • Master Track
        • Speed Master Track
        • Intensity Master Track
        • Parameter Tracks
        • Marker Track
        • OSC Track
        • OSC Track
      • Editor
      • Scene Event - Blocks
      • Loop Region
      • Keyframe Animations
        • Easing Options
        • Spline Mode
        • Rail Rotation
      • Camera Animation
      • Sequencer Settings
      • Automatic Light Control (ALC)
      • Using MIDI keyboard.
  • Rendering
    • Video Rendering
      • Render H.264
      • Render Image Sequence
      • Physics and Framerates
      • Synchronize Pangolin Beyond for Video Rendering
    • Image Rendering
      • Long Exposure Rendering
    • Render Settings
      • Scene
      • Lighting
      • Laser Render Settings
      • Fountain
      • Post-FX
    • Virtual Reality
  • Plot & Documentation
  • Hardware & Control
    • Connect to vServer or vNano/wecs
    • Connect a Console
    • Modules
      • NDI
      • Logic Module
        • Logic Module Items
          • External Devices
          • Tools
          • Events
          • Outputs
          • Conditions
          • Inputs
          • Status
          • Tracker
          • Transformation
          • Converter
          • Container
          • Logic Test
          • Syncro Cloud
        • Group Items on a Group Panel
        • Connect a digital Wind Anemometer
        • Connect an analog Wind-Anemometer to a v:Server
        • Routing different DMX universes to the 4 XLR outputs of the vServer
        • Connection example for recording DMX values via the 4 DMX XLR connectors of the vServer.
        • Assign DMX universes to different ArtNet nodes or other Devices.
      • Scheduler
        • Day Schedule
        • Week Schedule
        • Year Schedule
      • ModBus
      • Synchronization
      • Viz-Key
        • Install Viz-Key Driver
        • Connect Depence to a grandMA3 session
        • Potential Issues and Limitations
      • vServer Test Period
    • Live-Panel
    • Scripting
    • Editing the scheduler with the additional 'ShowOrganizer' program
  • Tips & Tricks
    • Network Settings
    • How to use a DeskDough?
    • Using Variables
    • How to export MVR to grandMA3
    • Control Atmosphere by DMX
    • Camera Remote Control
    • Log files
  • Performance
    • Scene Organization
    • Lighting
    • Other optimizations
  • Release Notes
    • Version 4.0.6
    • Version 4.0.5
    • Version 4.0.0
Powered by GitBook
On this page
  • Description
  • Add ModBus Units
  • Send ModBus Values
  • Receiving ModBus Values
  • Routing to Virtual Master
Export as PDF
  1. Hardware & Control
  2. Modules

ModBus

PreviousYear ScheduleNextSynchronization

The integration and management of ModBus values, whether from sensors or other units, into a DMX system are crucial. By employing specific techniques and procedures, as demonstrated in our examples, you can efficiently receive and process these values. Proper handling of DMX addressing and device assignments is vital to ensure all data is routed and utilized correctly.

Description

With Depence 3 and the vServer 4, you can connect SPS Units that support the Modbus Protocol for controlling devices like frequency converters or pumps, or for querying sensor values.

For this, patched DMX channels are connected with ModBus output modules, or ModBus input modules are connected with patched DMX channels.

As prescribed by the ModBus protocol (please refer to specialized literature on ModBus for further information), you can send binary (QX) or analog values (QW or QD) to the respective ModBus modules, or receive binary (IX) or analog values (IW or ID) from the corresponding ModBus modules.

Add ModBus Units

You can address multiple ModBus Units (CPU) and configure them individually. Each ModBus CPU is addressed over the network using a network IP address. The network port for ModBus is static and standardized, set to 502.

Send ModBus Values

To send a Pump On/Off DMX channel and a Pump Speed channel via ModBus, follow the procedure shown in the illustration. First, create a new ModBus Unit using the "Add Unit" feature and enter the IP address set on the CPU. Now, drag and drop a SelectionGroup with the corresponding devices from the SelectionGroup window into the ModBus Output table. For a binary switch (On/Off), set the operand to QX and for an analog PumpSpeed channel, set the operand to QW. In the Memo column, set the appropriate ModBus memory area; for example, for the QX, set the Memo address to 0.0 (Word 0 Bit 0) and for the Pump Speed (QW) to address 20. Continue with other devices as previously described.

Receiving ModBus Values

If you wish to receive ModBus values, such as sensor readings for water level, dry-run protection, temperature, or humidity, follow these steps:

All incoming values must be routed to a DMX address. To do this, a device capable of accepting this DMX value must be located at the respective DMX address. Only in this way can the values be further processed later in the "Logic Module" or "Live Panel".

In our example, a sensor value for dry-run protection (binary) IX and a water level value (analog) IW have been defined. Use the "AddNew" option below the ModBus Input table to add the corresponding entry. In our example, we routed the incoming values for "Dry Protect" to DMX address Universe 5 and Address 500 (5.500) and for the "Water Level" to 5.501. It is advisable to simply patch 2 single-channel PAR spots to these addresses in order to work with the input values further.

Routing to Virtual Master

In the following LogicModule connection example, you can see how the "Dry Protection" input value from ModBus, written to DMX address 5.500, has been linked and used with a "Virtual Master."

For safety reasons, the input value is passed through a hysteresis. This allows for precise determination of the switching point for analog values. The 'not' function, if necessary, inverts the value (depending on the state received from ModBus) and then forwards it to the virtual master. The Virtual Master then needs to be connected to the appropriate Pump On/OFF channels in the "Channel Settings" (see the next illustration)

These two devices act as dummies on addresses 5.500 and 5.501 to store the ModBus input values.
Connecting the Pump On/OFF channel with the Virtual Master "DryProtection".