Control response time

When controlling assets (EV's, batteries), the SmartgridOne Controller sends a command to the device, which then needs time to process this command and adjust its state accordingly. This is known as the control response time. The time needed for this, and the time it takes for the SmartgridOne Controller to send a new command, depends on the following factors:

• The type of device (e.g., battery, EV charger, heat pump)
• The settling check
• Limitation on the RS485 bus
• The scheduler interval

When your SmartgridOne Controller is active in ancilllary services, a fast response time is crucial. On this page, we will explain how these factors influence the control response time and how you can optimize it for your specific use case.

The type of device

Different types of devices have inherently different response times due to their technical characteristics and communication protocols:

Battery and/or solar inverters (including hybrid inverters)

• Typically fast response times (1-5 seconds)
• Response time mainly depends on the inverter's internal controls
• May have built-in ramp rates for power transitions

EV Chargers

• Medium response time (5-15 seconds)
• Response depends on:
  • Communication protocol (OCPP, Modbus, proprietary)
  • Vehicle's charging capabilities
  • Current charging state
• Must respect minimum charging current requirements

Heat Pumps

• Slower response times (30-180 seconds)
• Gradual power adjustments to protect the compressor
• Response time affected by:
  • Operating mode (heating/cooling)
  • Current temperature conditions
  • Internal protection mechanisms

Relays and Switches

• Fast response times (1-5 seconds)
• Typically used for simple on/off control

The 'Settling Check'

When working with multiple device brands, protocols, and models, patience becomes essential. Although devices like batteries, inverters, and EV chargers typically respond quickly to commands, they need time to update their measurements and send them back to the Controller.

Two key factors affect response times:

1. Energy meters may send data at slower rates, which means they don't immediately reflect the latest device actions
2. Devices often need time to ramp up and stabilize to reach their target states

This is where settling checks become important. A settling check is a waiting period that ensures devices have fully reached their commanded states before new decisions are made. Think of it as letting the dust settle after a change. Without this mechanism, our control system could react to temporary states during the transition period. This would lead to unnecessary corrections - similar to trying to balance on a wobbling platform while constantly overcorrecting, making the situation worse.

Our implementation monitors three crucial aspects: First, it verifies that measurements are recent and reliable, ensuring we're not reacting to outdated information. Second, it tracks how power flows change over time, confirming that devices are responding as expected. Finally, it respects the inherent delays in device responses, giving equipment the time it needs to reach stable operation.

Consider a site with two devices: a modern battery system and an older heat pump. When we send a command to reduce power consumption by 5kW:

The battery responds almost immediately, but the heat pump's older control system takes longer to adjust and report its new state. Without settling checks, we might misinterpret this delay as a failure to respond and send additional commands, potentially destabilizing the system. Instead, our controller patiently waits for all devices to report stable states before making any new decisions. The timeline for this exact flow then looks like this:

This measured approach might seem overly cautious, but in the world of power systems, stability and equipment longevity far outweigh the appeal of rapid-fire adjustments.

Choosing the settling check mode

The settling check is configured in the commissioning interface under the advanced settings, with the setting "Settling check mode" in the section "Data & scheduler". There are four modes:

• Always check for settling (the current default): the most stable option. Every run of the control loop waits until all controlled devices have settled.
• Only check for settling if oscillating setpoints are detected: a balance between stability and speed. The control loop only waits for the devices when it detects that its setpoints start to oscillate.
• Use a state estimator instead of a settling check: the fast and stable option, which will become the default in the future. The control loop does not wait for the devices. Instead, it estimates the actual power of every device from its measurements, its setpoints and the changes it observes in the grid power, and calculates the next setpoints from those estimates. Choose this mode when the response time matters, for example for ancillary services.
• Never check for settling: the control loop runs as fast as possible, without waiting for the devices and without estimating their state. Only for situations where open loop control is acceptable, for example when the SmartgridOne Controller is used exclusively through an external API and exceeding the grid limits is not an issue. This is the default on a cloud SmartgridOne Controller.

The setting "Maximum settling time (seconds)" (30 by default) caps how long the control loop waits for settling before it proceeds anyway.

Click here to see the instructions

1. Open the settings page and click "Go to advanced settings":

2. Open the section "Data & scheduler" and change the "Settling check mode":

3. Click on 'Save' at the bottom of the section.

See also Advanced settings.

Limitation on the RS485 bus

When multiple devices are connected to the RS485 bus, the control response time can be affected due to the inherent limitation of RS485 communication - only one device can communicate at a time.

As devices take turns communicating over the bus, each additional device increases the overall communication cycle time. This can lead to slower response times for all connected devices.

For optimal performance:

• Limit the number of devices to 5 or fewer per RS485 bus
• Use RS485 expansion accessories when connecting more devices

Scheduler interval

The scheduler interval determines how often the SmartgridOne Controller checks for new commands and sends them to the devices. A shorter interval allows for faster response times, while a longer interval can lead to delays in command execution. Check if the scheduler interval is set to a reasonable value for your use case. The default interval is 1 second (10 seconds on a cloud SmartgridOne Controller), but you can adjust it in the advanced settings:

Click here to see the instructions

1. Open the settings page and click "Go to advanced settings":

2. Open the section "Data & scheduler" and change the "Scheduler run period (seconds)":

3. Click on 'Save' at the bottom of the section.