This project provides SolarNode plugin that can collect data from CanadianSolar CSI-50KTL-CT series inverters.

The plugin can be installed via the Plugins page on your SolarNode. It appears under the Datum category as CanadianSolar KTL-CT Inverter Data Source.

This datum generates a datum stream with the following properties:

Here is an example datum, expressed in simplified JSON form:

{
	"created": "2023-03-16 19:46:43.195Z",
	"nodeId": 123,
	"sourceId": "/INV/1",
	"localDate": "2023-03-16",
	"localTime": "15:46",
	"temp": 44.8,
	"watts": 45800,
	"frequency": 60,
	"ambientTemp": 36.7,
	"apparentPower": 45800,
	"dcPower1": 15408.629,
	"dcPower2": 15491.25,
	"dcPower3": 15212.35,
	"dcVoltage1": 634.1,
	"dcVoltage2": 637.5,
	"dcVoltage3": 636.5,
	"dcPower": 15409,
	"current_a": 52.5,
	"current_b": 52.6,
	"current_c": 52.8,
	"dcVoltage": 636.0333,
	"voltage_a": 291.2,
	"voltage_b": 293,
	"voltage_c": 290,
	"efficiency": 0.0988,
	"voltage_ab": 505.5,
	"voltage_bc": 502.6,
	"voltage_ca": 503.1,
	"reactivePower": 3300,
	"wattHours": 600613000
}

Once installed, a new CanadianSolar KTL-CT Series Inverter component will appear on the Settings page on your SolarNode. Click on the Manage button to configure devices. You'll need to add one configuration for each device you want to collect data from.

Each device configuration contains the following overall settings:

Modbus Port

This is the service name of the Modbus component configured elsewhere in SolarNode. You must configure that component with the proper connection settings for your Modbus network, configure a unique service name on that component, and then enter that same service name here.

Source ID

This value unique identifies the data collected from this device, by this node, on SolarNetwork. Each configured device should use a different value.

Sample Maximum Age

SolarNode will cache the data collected from the device for at least this amount of time before refreshing data from the device again. Some devices do not refresh their values more than a fixed interval, so this setting can be used to avoid reading data unnecessarily. This setting also helps in highly dynamic configurations where other plugins request the current values from the device frequently.

The warn property is an enumeration of the following possible values:

The permFault property is an enumeration of the following possible values:

The vendorEvents property is a bit set of the following possible values:

This plugin will map specific fault codes into the SunSpec events property: