IoT (Internet of Things) interface to Modbus devices

T6130


Collections: BACnet, Metering, MODBUS

Category: BACnet, IoT, Modbus RTU, Modbus TCP, RS-485, T6130

Type: BACnet


  • Cimetrics also offers an OEM-customized version of this product. Click here for more information.

    Cimetrics also offers an module version of this product. Click here for more information.

    The T6130 provides a IoT (internet of things) interface for Modbus RTU and/or Modbus TCP devices for the ThingWorx IoT platform. The T6130 configuration is done over Ethernet through onboard web pages of the product and can therefore be managed from a remote location. Configuration is simple and the device is up and running in minutes.

    Mapping between Modbus registers and IoT objects requires the creation of a template. An engineer who is familiar with the Modbus register map of the target Modbus devices creates a template for each device using a proprietary Windows tool, which has drop down menus for easy object name creation and engineering unit selection. An appropriate template is loaded into the T6130 during the configuration process.

    This product features:

    Flexible connections
    • IoT connectivity using 10/100 Ethernet
    • Interfaces to 2 Modbus RTU/TCP devices
    • Easy to use template builder Windows utility for mapping

    Manageability
    • Build-in web server with secure login
    • Status page for diagnostics
    • Easy & informative naming convention
    • Automated ThingWorx connectivity

    Agility
    • Multi-vendor Modbus device support

  • Communication: 
    • Prococols - Modbus RTU, Modbus TCP, TCP/IP 
    • Web browser configuration 

    Operation and Environment: 

    • Adaptor Input Power: 100 to 240 VAC @ 10 W, 50/60 Hz
    • Operating temperatures: 7 to 40C
    • Dimensions: 5.0 x 5.9 x 1.2 inches
    • Connections: Ethernet RJ45, modular screw terminal, DC power, standard RS485 three wire connections
    • System LED: power LED and data LED

    Ethernet:
    • TCP/IP over Ethernet RJ45 standard
    • IEEE 802.3 10/100 Mbps
    • 10BaseT, 100BaseT,  RJ45 connectors
    • Half/Full duplex
    • 100m (max) CAT5 cable length.

    Modbus:
    • RS485 three wire connections for Modbus RTU
    • 10BaseT, 1 External Modbus TCP via shared Ethernet port

    Options:
    • wall bracket kit
    • DIN rail mounting kit

  • Bring Modbus data into ThingWorx ecosystem 

     b6130 net 120406

    Lost of buildings and facilities have a large number of Modbus devices which need to be brought up to an Internet of Things ThingWorx ecosystem. To address that need, Cimetrics offers a templatized protocol converters T6130. The T6130 acts as a Modbus to IoT interface - taking Modbus register data and exposing it to ThingWorx platform, just as Cimetrics’ B6130 device. It also includes sample templates from the range of known meters so there is often no need to spend time choosing what registers to expose from each device. In addition the T6130 allows the users to create their own loadable templates to map a Modbus RTU or Modbus TCP device into ThingWorx platform. T6130 includes examples of some Modbus devices templates to give first time user best practices when choosing names, units and descriptions. All BACnet objects are meaningfully named and standardized for easier reading and integration into Building Automation Systems.

    Configuration steps include using a Windows tool to create a template (the tool has drop down menus for easier name creation and choosing units),  specifying a meter's IP address (if it is a TCP/IP meter), specifying the device’s Modbus ID, and loading a template created/supplied with the tool. The configuration can be saved to a .csv file for record keeping and data analysis.


  • Manual - Provided with purchase of product.

Product Q&A

Ask a Question
0
Q: How do I use the U+4 with a BACnet client?

A: The U+4 hardware is an intelligent USB to fieldbus interface. This allows you to use your PC's USB port to connect to an MSTP (RS485) network. The U+4 (along with a BACnet client like the Cimetrics BACnet Explorer) can now communicate with a BACnet/MSTP network to write and read values.

The following needs to be done for a connection;

- In your LAN properties, select your NIC interface and get into Properties | uncheck the Cimetrics BACstac protocol

- Install the driver for the U+4 on your PC

- Plug the device into your PC (In the USB port).Once the U+4 is plugged into the PC in the USB slot, this will add an extra Local Area Connection in your Network Places that corresponds to the U+4. In order to configure settings, you would need to select this Local Area Connection.

Once you are in the Local Area Connection, RT Click | Properties |Configure | Advanced, you will see all the options given below. Please configure according to your use.


Card Speed:

Select needed Baud rate(in the range from 1200 to 115200 bps) from the list

Filter:

-"Directed BACnet NPDU only" - to receive only directed or Broadcast NPDU. (accepted by any BACstac version). MS/TP information is absent.

Node Address:

Set address of this node in the range [0-254]. IMPORTANT Note: Master node must be in the range [0-Max_master]

Node Type:

Select "Master Node".

Master Mode takes part in token passing and is needed for the BACstac. In this mode, you would be able to completely discover the MS/TP network by using the BACnet Explorer.


Max_info_frames[1-10]:

Leave at default settings.

Max_master[1-127]:

Leave this at the default settings.


Once the above settings are done, you should be able to start the BACnet Explorer and discover devices from a BACnet/MSTP network.

1
Q: How does the U+4 Field interface get its power?

A: The U+4 Device draws its power from the USB cable and hence will not require any other power source.

2
Q: How do I use the U+4 with the BAS-o-Matic to sniff a network?

A: The U+4 hardware is an intelligent USB to fieldbus interface. This allows you to use your PC's USB port to connect to an MSTP (RS485) network for sniffing the MSTP Network. This sniffing can be done with the help of the Cimetrics Sniffing software called as the BAS-o-Matic.

The following needs to be done for a connection;

  • Install the driver for the U+4 on your PC
  • Plug the device into your PC (In the USB port).Once the U+4 is plugged into the PC in the USB slot, this will add an extra Local Area Connection in your Network Places that corresponds to the U+4. In order to configure settings, you would need to select this Local Area Connection.
Once you are in the Local Area Connection, RT Click | Properties |Configure | Advanced, you will see all the options given below. Please configure according to your use.

Card Speed:

Select needed Baud rate(in the range from 1200 to 115200 bps) from the list

Filter:

Use the filter option to select what kind of packets you want to capture or receive:
  • "All" - to receive all packets (including all types of MS/TP frames and error notifications)
  • "All BACnet data" - to receive all MS/TP frames transporting BACnet NPDU.
  • "Directed BACnet data" - to receive MS/TP frames with BACnet NPDU, destined only to our Node Address and Broadcasts.
  • "Directed BACnet NPDU only" - to receive only directed or Broadcast NPDU. (accepted by any BACstac version). MS/TP information is absent.
Node Address:

Set address of this node in the range [0-254]. IMPORTANT Note: Master node must be in the range [0-Max_master]

Node Type:

Select "Monitor Node". The "Monitor" mode can be used for Bas-o-matic only. This mode would be used if you are using the fieldbus interface purely for sniffing purposes only.


Max_info_frames[1-10]:

Leave at default settings.

Max_master[1-127]:

Leave this at the default settings.


Once the above settings are done, you should be able to start the BAS-o-Matic and start capturing communications from a BACnet/MSTP network.


Related Items