Motion Knowledgebase (kb.motion.cloud)
  • Welcome!
  • Motion Hub (Hardware)
    • Installation
    • Networking
      • Motion Hub Networking
      • BACnet/IP Networking
      • Modbus TCP Networking
    • Powering On & Off
  • Motion Platform (Software)
    • Apps
      • What are "Apps"?
      • App Types
      • Creating a Mosaic App
      • Configuring a Mosaic App
      • Deleting an Existing Motion App
    • Tiles
      • What's a "Point"?
      • What's a "Tile"?
      • Tile Types
      • Tiles: Read-Only vs. Read+Write
      • Creating Point-Based Tiles
        • Discover BACnet Points (& Creating BACnet Tiles)
        • Configuring Modbus TCP Points (and creating Modbus Tiles)
      • Configuring Motion Tiles
    • Devices
      • What are "Devices"?
      • Supported Protocols
      • Viewing Your Devices
      • Add a BACnet Device
      • Add a Modbus Device
    • Alarms
      • Alarms View
      • Current Alarms
      • Alarm History
      • Alarm Details
      • Clearing/Acknowledging Alarms
      • Auto-Clear Alarms
    • Accessing the Platform
      • Web Browser
      • Mobile Apps (iOS+Android)
    • Schedule Configurations
      • Creating Schedules
      • Enable/Disable/Configure Schedules
      • Deleting a Schedule
  • Account+Security
    • Password Management
    • Two-Factor Authentication (2FA)
Powered by GitBook
On this page
  1. Motion Hub (Hardware)
  2. Networking

Modbus TCP Networking

Networking for Modbus TCP is very straightforward. The Motion Hub must simply be able to communicate with the IP address of the given Modbus TCP device over the network to which the Motion Hub is connected.

Unlike other protocols, Modbus does not provide discovery mechanisms, and so you must simply know the IP address of the Modbus device with which you want to communicate via Motion.

PreviousBACnet/IP NetworkingNextPowering On & Off

Last updated 2 years ago