bluelog Neo

Remote Power Control license (RPC) bluelog Neo data sheet

Last modified:

Remote Power Control (RPC) bluelog Neo

Item no. 557.490 – 557.496, 557.499

Remotely reduce the feed-in power of a system for energy trading.

RPC_logo.jpg



Description

Remote Power Control (RPC) can be used to remotely reduce the feed-in power of a system, such as for energy trading. This is done in parallel with the grid operator's feed-in management without influencing its control commands. The controller interprets the power control setpoints, for example, from an energy trader, and prioritizes their transmission to the system. The smaller setpoint command value always takes precedence.

Additionally, RPC facilitates the retrieval of master data and measured values, including legally required data for the actual feed-in within the context of energy trading.

Features

  • Communication via Modbus TCP interface

  • Interface certified according to VDE-AR-N 4110 / 4120

  • Visualization and long-term logging/archiving of power control events in meteocontrol’s remote monitoring portal VCOM

  • Certified plant controller and energy trading interface combined in one device

  • Compatible with a wide range of energy traders

  • Encrypted communication in conjunction with the integrated OpenVPN Client

Requirements

  • bluelog Neo with a PV, Battery, or Hybrid Control license

  • Active power and feed-in management (power control) are handled by the bluelog controller.

  • OpenVPN license.

  • When using the license, the OpenVPN connection to the energy trader is established directly via the bluelog. A VPN configuration in the router is therefore not necessary.

Overview of licenses

The license depends on the maximum AC power of the plant in kW. When ordering, please provide the 14-digit hardware serial number of the bluelog controller.

Item no.

License (maximum AC active power of the plant)

557.490

Remote power control (RPC) license bluelog Neo ≤ 0.2 MVA

557.491

Remote power control (RPC) license bluelog Neo ≤ 1 MVA

557.492

Remote power control (RPC) license bluelog Neo ≤ 3 MVA

557.493

Remote power control (RPC) license bluelog Neo ≤ 5 MVA

557.494

Remote power control (RPC) license bluelog Neo ≤ 10 MVA

557.495

Remote power control (RPC) license bluelog Neo ≤ 20 MVA

557.496

Remote power control (RPC) license bluelog Neo ≤ 50 MVA

557.499

Remote power control (RPC) license bluelog Neo Utility

Communications scheme

Communication scheme

VPN encrypted communication

To ensure secure VPN data transmission to the energy trader, there is no need for an extra VPN router. All that is required is the OpenVPN license to activate the integrated OpenVPN client on the bluelog Neo. If you wish, we will also gladly assist you in requesting the required VPN certificates from the energy trader.

Item no.

License

557.400

OpenVPN bluelog Neo license

428.098

Certificate for energy trading system

Modbus specification

Communication parameters
  • Slave ID (Client ID): 10

  • Port: 502

  • Delay: 1,000 ms

General register definition
  • If a device does not deliver a measured value, a missing value will be sent instead. See table “Data types” below.

    • Missing values int: 0x80000000 | float: 0x7FC00000

  • Read values: Function code 03 - Read holding registers

  • Write values: Function code 16 - Preset multiple registers

  • Register and byte order:

    • The word order is LOW register before HIGH register (Little Endian)

    • The byte order is HIGH byte before LOW byte (Big Endian) → 0xCCDDAABB

Example

Command with mbpoll

The first line shows a write command (setpoint) from the energy trader to limit the feed-in of active power to 30%. The second line is an activation command to turn on the power.

rpc_modbus-specification_neo (1).svg
Example setpoint via Remote power control


Data types

Abbreviation

Description

Missing values

U16

16-bit unsigned integer

0xFFFF

U32

32-bit unsigned integer

0xFFFFFFFF

I16

16-bit signed integer

0x8000

I32

32-bit signed integer

0x80000000

F32

32-bit float

0x7FC00000

String

  • String, ASCII encoding.

  • If the whole length of the field is used, then the end of the string will be filled with 0x00.

  • If a value (for example model name) does not fit in the register, then it will be cut off.

0x00

Interface registers

This PDF provides an overview of the registers:

Remote-Power-Control_bluelog Neo_registers_en_2026-02-17.pdf