ToU Mode
ToU Mode in Detail
Running Rules
- When the inverter's working mode is set to ToU mode but no time group is set, the inverter runs in General Mode, and the export power follows the external parameter (Inverter Configuration - Power Control - Export power).
- If time groups are set, the export power set in the ToU sub-mode is used within those time groups; unset periods still run in General Mode, and the export power follows the external parameter (Inverter Configuration - Power Control - Export power).
- When two time groups overlap or one fully contains the other, the overlapping period runs according to the setting with the earlier start time (i.e., first set, first effective). Avoid delivering overlapping time groups.
- After an export power (
exportLimit) is set in ToU mode, the external anti-reverse-current setting no longer takes effect; however, when external anti-reverse-current is enabled, output control (soft/hard) still takes effect.
Working Modes (workMode)
The format is high byte#low byte:
| Mode | Description |
|---|---|
| 4#1 | General Mode |
| 4#2 | Battery Force Charge |
| 4#3 | Battery Charge |
| 4#5 | Feed-in Priority |
| 4#6 | Battery discharge |
Time Group Fields
There are 24 time groups per day (96 for 15-minute granularity) (timeGroupId: 0~23/95), and dates are distinguished by planId:
| Field | Description | Options/Range |
|---|---|---|
| planId | ToU plan ID | 1: Today 2: Tomorrow |
| timeGroupId | ToU time group ID, 24 in total | 0~23/95 |
| timeGroupEnableFlag | Time group enable flag | 0: Off 1: On |
| startTime | Start time | 00:00~23:59 |
| endTime | End time | 00:00~23:59 |
| workMode | Working mode | See "Working Modes" |
| parameters | Sub-mode parameters | See "Sub-mode Parameters" |
Sub-mode Parameters (parameters)
note
Parameter conversion (gain) is handled uniformly by the OpenAPI; when a parameter does not match the working mode, the mismatched parameter is filtered out directly.
| Parameter | Description | Range | Unit |
|---|---|---|---|
| exportLimit | Export power | [-1 × system rated power, 5 × system rated power] | kW |
| chargeLimit | Charge power limit | Single unit [0, 1000] Master [0, 5000] | kW |
| chargeCutoffSoc | Charge cutoff SOC | [100, 1000] | % |
| noPv | PV generation | 0: Allow PV generation 1: Disable PV generation | - |
| inverterOutputLimit | Inverter output control | Single unit [0, 1000] Master [0, 5500] | kW |
| dischargeCutoffSOC | Battery discharge cutoff SOC | [100, 1000] | % |
The parameters available under different working modes are as follows:
| Parameter | General Mode 4#1 | Battery Force Charge 4#2 | Battery Charge 4#3 | Feed-in Priority 4#5 | Battery discharge 4#6 |
|---|---|---|---|---|---|
| exportLimit | ✓ | ✓ | ✓ | ✓ | ✓ |
| chargeLimit | - | ✓ | ✓ | - | - |
| chargeCutoffSoc | - | ✓ | ✓ | - | - |
| noPv | - | ✓ | - | - | - |
| inverterOutputLimit | - | - | - | - | ✓ |
| dischargeCutoffSOC | - | - | - | - | ✓ |
Delivery Rules
- Delivering a work plan is an asynchronous API: it returns a
recordIdon success, and you need to query the execution result viarecordId. - ToU time groups must be delivered all 24/96 groups at once (one day's plan) and always overwrite the existing configuration on the device; for unused slots, set the enable flag (
timeGroupEnableFlag) to0and send them as well. - Time groups have a today/tomorrow concept: if you want the device to keep working according to a set of ToU modes, deliver the data for both days (48/192 groups in total). The device automatically moves tomorrow's plan to today for execution at day rollover, in a continuous loop.
- Time groups delivered via the Solinteg cloud platform (monitoring platform / OpenAPI platform) are cached in the cloud.
- Delivery duration depends on the datalogger version: the first-generation datalogger (Duocom) takes about 1 minute, and the second-generation datalogger (R2MD) takes about 5 seconds. It is recommended to use ToU-related features together with the R2MD.
- Tasks that time out (device not responding for a long time) will be marked as failed and can be retrieved via the result query API.
Reading the Current Configuration
warning
Only the second-generation datalogger reports and supports reading the ToU configuration on the inverter; the first-generation datalogger does not. Therefore, when reading the configuration via the OpenAPI, the cloud-cached configuration is always returned.
Users of the first-generation datalogger please note: the cloud configuration is unreliable in this case and does not truly reflect the device's ToU configuration.
- If ToU has never been set via the monitoring platform/OpenAPI, the query result is an empty array.
- All APIs require authentication, and the current user must have operation permission on the device; otherwise a permission error is returned.
Related APIs
| API | Description |
|---|---|
POST /tou/cmd/send/{deviceSn} | Deliver an inverter work plan, returns a recordId |
GET /tou/cmd/status/{taskId} | Query the delivery result by recordId: SUCCESS / SETTING (processing) / FAILED |
GET /tou/query/{deviceSn} | Read the device's current ToU time groups (48/192 groups) |