1. Manuals
  2. Brands
  3. Centrica Manuals
  4. Network Hardware
  5. Panoramic Power
  6. Programmer's manual

Centrica Panoramic Power Programmer's Manual

Modbus tcp
Hide thumbs Also See for Panoramic Power:
Table of Contents

Advertisement

Quick Links

Download this manual
Panoramic Power
Modbus TCP Programmer's Guide
Gen 4/4+ Bridge
Firmware v476 / February 2022

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Panoramic Power and is the answer not in the manual?

Questions and answers

Related Manuals for Centrica Panoramic Power

Summary of Contents for Centrica Panoramic Power

  • Page 1 Panoramic Power Modbus TCP Programmer’s Guide Gen 4/4+ Bridge Firmware v476 / February 2022...

  • Page 2: Table Of Contents

    Contents Introduction and overview ......................3 Hardware & Networking requirements ..................4 Supported Hardware ..........................4 Supported LAN networks ........................... 4 Assigning a fixed Bridge IP address ......................4 Assigning a Slave address .......................... 4 Bridge configuration ..........................4 NTP requirements ............................5 Modbus parameters ..........................

  • Page 3: Introduction And Overview

    Introduction and overview This document covers the operation and interface definition of the Panoramic Power Bridge when working in the stand-alone mode. In this mode, the Bridge implements a Modbus TCP/RTU protocol which sends sensor’s current readings to a local server. The local server acts as a Modbus master server and the Bridge acts as a Modbus TCP/RTU slave.

  • Page 4: Hardware & Networking Requirements

    Hardware & Networking requirements Supported Hardware • Sensors: PAN10, PAN12, PAN14 and PAN42. • The Modbus interface also supports reading the Bridge’s pulse inputs (Gen4 and above) • The Modbus TCP solution is supported by Gen3 and above and requires firmware v470 or higher.

  • Page 5: Ntp Requirements

    NTP requirements To operate properly, the Bridge needs to get the real time clock (RTC). Since the Bridge has no battery-powered hardware RTC, it gets the time using a standard NTP server. The Bridge gets the NTP time, as part of the boot process, using the following process: 1.

  • Page 6: Bridge Modbus Software Model

    Bridge Modbus Software Model Modbus Register Map This section is for use by the Modbus Host programmer. The table below shows the Bridge register map as reflected to the Modbus Master: Type Functional Register # Size (16 bit Description Format Comments Code (Dec)
  • Page 7 Type Functional Register # Size (16 bit Description Format Comments Code (Dec) words) 2009+20N Reading RSSI [dBm] INT16 2010+20N Sensor HW version UINT16 2011+20N Sensor FW ver. - Major UINT16 2012+20N Sensor FW ver. - Minor UINT16 Next 8 registers are for PAN42 sensors. N = Slot No. 0-31 2013+20N - Vs-rms [V] FLOAT32...
  • Page 8 Type Functional Register # Size (16 bit Description Format Comments Code (Dec) words) Event Timestamp – Timestamp of the latest SAG / SWELL event message received from the sensor. Unix Epoch SAG / SWELL A UNIX Epoch time is the number of 3517+18n - Event Timestamp UINT32...

  • Page 9: Sensor Slot Allocation Example

    a. Table 1.2 – Input registers 2001-2010 +20N – Sensor main readings – An array of 32 slots x 20. b. Table 1.3 - Input registers 3001-3004 +4N – Extended parameters - Array of 32 slots x 4 registers each c.

  • Page 10: Sensor Readings

    • We can also see another sensor (S/N 55555555) which is received by the Bridge but has not been allocated to any slot. This sensor data will be ignored when the Bridge is in Modbus TCP mode. In ‘PowerRadar connected mode’ or ‘combined mode’ all sensor data is simultaneously sent to PowerRadar regardless of the assignment.

  • Page 11: Pulse Counter Registers

    When reading the data, the status register should be analyzed first. Based on its content the other registers should be processed as shown in the table: Status Code Meaning Slot Unassigned This slot has no sensor S/N allocation. All other registers in this slot can be ignored.

  • Page 12: Sensor Calibration Keys (Not Pan42)

    Sensor Calibration keys (not PAN42) Each Panoramic sensor is calibrated during manufacturing and a unique calibration key is generated for every sensor. This key is used to calibrate the sensor raw measurements to achieve optimal accuracy. When working in PowerRadar mode, raw measurements are calibrated in the cloud. In stand-alone mode, however, the calibration is done on the Bridge itself, utilizing a unique calibration key.

  • Page 13: Set Networking Mode

    Set networking mode 1. Navigate to the ‘Network Setup’ tab and set the Bridge networking mode 2. Note that only ‘Ethernet’ and ‘Wi-Fi’ networks support the stand-alone Modbus TCP mode. Stand-alone Modbus RTU mode can work alongside any network mode. Note that when ‘Wi-Fi’...

  • Page 14: Set Connection Mode

    Set Connection mode 1. Navigate to the ‘Connection Setup’ tab to set the Bridge connection preferences. 2. By default, the Bridge is configured to connect to PowerRadar 3. Check ‘Enable Stand Alone Modbus mode’ to enable the Modbus mode option. 4.

  • Page 15: Define Bridge Ui Accessibility

    Define Bridge UI accessibility For enhanced security, the Bridge UI is accessible by default only during configuration mode, using a wired-connected laptop. It is possible to change that configuration, making the UI accessible from any laptop in the same LAN as the Bridge. While less secure, this mode can be useful during testing and sensor setup when multiple frequent changes are made to the Bridge UI.

  • Page 16: Assign Sensors To Slots

    Assign sensors to slots Any sensor to be used by the Modbus interface must first be allocated to specific location (slot) within the Bridge. Once allocated, this sensor readings are guaranteed to always be in a fixed register address. Readings from sensors that were not assigned to a slot, will not be provided via the Modbus interface (but will continue to be sent to PowerRadar if ‘Connect to PowerRadar’...
  • Page 17 Assign a sensor to a slot 1. Navigate to the ‘Sensors’ tab 2. Choose an empty slot and press the ‘+’ icon. For PAN42 sensor, make sure the following two slots are also available (PAN42 sensor requires 3 empty consecutive slots). 3.

  • Page 18: Delete A Sensor From The List

    5. For PAN42: Figure 10: Add PAN42 Sensor Pop-up a. Type the sensor’s serial number. The sensor is registered in 3 slots (for 3 phases) b. Press the Save button. The sensor is now assigned to the slot. New readings will be shown in this screen and made available via the Modbus TCP/RTU interface.

  • Page 19: View Sensor Readings

    View Sensor Readings Sensor readings are available in the ‘Sensors Tab’. Each allocated sensor will display the last received reading. A new reading will override the previous reading. 1. Navigate to the ‘Sensors’ tab. This Tab is accessible only when ‘Connection Setup’ > ‘Enable stand-alone Modbus mode’...
  • Page 20 Scroll Right for additonal readings: Figure 12: Sensor’s list – Additional readings...

  • Page 21: Configure The Bridge Pulse Interface

    Configure the Bridge Pulse interface 1. Navigate to the ‘Pulse Setup’ tab 2. Enable pulse input 1, 2 or both 3. Enabled pulses are made available for Modbus TCP/RTU based on the ‘Connection Setup’ > ‘Enable stand-alone Modbus mode’ value and are sent to PowerRadar based on the ‘Connection Setup’...

  • Page 22: Bridge Led Configuration For Stand-Alone Modes

    Bridge LED configuration for stand-alone modes The Bridge contains three hardware LED indicators that change based on Bridge operations. For a full list of led indication states, please refer to the Gen 4+ Bridge Manual. The information below refers to changes in LED behavior in stand-alone mode. In a ‘Standalone mode’...

Table of Contents