NexBlue_Edge_OCPP_Configs&Features.xlsx

	A	B	C	D	E	F	G	H	I	J	K
1	NexBlue_Edge_OCPP_Configs&Features
2	Brand:	NexBlue
3
4	README：
5	Introduction	NexBlue-CP-OCPP Charging point(EVSE) and central system OCPP protocol, configuration features supported by charging point.
6		Our charger is compliant with OCPP 1.6 Security Profiles 1 and 2.
7
8
9	Background Color	White	Supported
10		Blue	Deviation from the standard protocol						AuthorizeRemoteTxRequests
11		Green	Not yet, to be supported
12		Orange	Not supported
13
14
15	Configuration
16	Item	Sector	OCPP clause	Core Profile field	Required / optional	Accessibility	Type	Unit	Description	Default Setting Value	Remark
17	1	Core Profile	9.1.1	AllowOfflineTxForUnknownId	optional	RW	boolean		If this key exists, the Charge Point supports Unknown Offline Authorization. If this key reports a value of true, Unknown Offline Authorization is enabled.	FALSE	RW
18	2	Core Profile	9.1.2	AuthorizationCacheEnabled	optional	RW	boolean		If this key exists, the Charge Point supports an Authorization Cache. If this key reports a value of true, the Authorization Cache is enabled.		RW, to be supported
19	3	Core Profile	9.1.3	AuthorizeRemoteTxRequests	required	R	boolean		Whether a remote request to start a transaction in the form of a RemoteStartTransaction.req message should be authorized beforehand like a local action to start a transaction.	TRUE	Curretly R, RW to be supported
20	4	Core Profile	9.1.4	BlinkRepeat	optional	RW	integer	times	Number of times to blink Charge Point lighting when signalling		Not supported
21	5	Core Profile	9.1.5	ClockAlignedDataInterval	required	RW	integer	seconds	Size (in seconds) of the clock-aligned data interval. This is the size (in seconds) of the set of evenly spaced aggregation intervals per day, starting at 00:00:00 (midnight). For example, a value of 900 (15 minutes) indicates that every day should be broken into 96 15-minute intervals. When clock aligned data is being transmitted, the interval in question is identified by the start time and (optional) duration interval value, represented according to the ISO8601 standard. All "per-period" data (e.g. energy readings) should be accumulated (for "flow" type measurands such as energy), or averaged (for other values) across the entire interval (or partial interval, at the beginning or end of a Transaction), and transmitted (if so enabled) at the end of each interval, bearing the interval start time timestamp. A value of "0" (numeric zero), by convention, is to be interpreted to mean that no clock-aligned data should be transmitted.	0	RW
22	6	Core Profile	9.1.6	ConnectionTimeOut	required	RW	integer	seconds	Interval *from beginning of status: 'Preparing' until incipient Transaction is automatically canceled, due to failure of EV driver to (correctly) insert the charging cable connector(s) into the appropriate socket(s). The Charge Point SHALL go back to the original state, probably: 'Available'.	30	RW
23	7	Core Profile	9.1.7	ConnectorPhaseRotation	required	RW	CSL		The phase rotation per connector in respect to the connector’s electrical meter (or if absent, the grid connection). Possible values per connector are: NotApplicable (for Single phase or DC Charge Points) Unknown (not (yet) known) RST (Standard Reference Phasing) RTS (Reversed Reference Phasing) SRT (Reversed 240 degree rotation) STR (Standard 120 degree rotation) TRS (Standard 240 degree rotation) TSR (Reversed 120 degree rotation) R can be identified as phase 1 (L1), S as phase 2 (L2), T as phase 3 (L3). If known, the Charge Point MAY also report the phase rotation between the grid connection and the main energymeter by using index number Zero (0). Values are reported in CSL, formatted: 0.RST, 1.RST, 2.RTS	Unknown,Unknown,Unknown	phase rotation not supported
24	8	Core Profile	9.1.8	ConnectorPhaseRotationMaxLength	optional	R	integer		Maximum number of items in a ConnectorPhaseRotation Configuration Key.		Not supported
25	9	Core Profile	9.1.9	GetConfigurationMaxKeys	required	R	integer		Maximum number of requested configuration keys in a GetConfiguration.req PDU.	30	R
26	10	Core Profile	9.1.10	HeartbeatInterval	required	RW	integer	seconds	Interval of inactivity (no OCPP exchanges) with central system after which the Charge Point should send a Heartbeat.req PDU	86400	RW
27	11	Core Profile	9.1.11	LightIntensity	optional	RW	integer	%	Percentage of maximum intensity at which to illuminate Charge Point lighting	100	to be supported
28	12	Core Profile	9.1.12	LocalAuthorizeOffline	required	RW	boolean		whether the Charge Point, when offline, will start a transaction for locally-authorized identifiers.	TRUE	RW
29	13	Core Profile	9.1.13	LocalPreAuthorize	required	RW	boolean		whether the Charge Point, when online, will start a transaction for locally-authorized identifiers without waiting for or requesting an Authorize.conf from the Central System	FALSE	RW
30	14	Core Profile	9.1.14	MaxEnergyOnInvalidId	optional	RW	integer	Wh	Maximum energy in Wh delivered when an identifier is invalidated by the Central System after start of a transaction.		Not supported
31	15	Core Profile	9.1.15	MeterValuesAlignedData	required	RW	CSL		Clock-aligned measurand(s) to be included in a MeterValues.req PDU, every ClockAlignedDataInterval seconds	Current.Import,Current.Offered,Voltage,Power.Active.Import,Energy.Active.Import.Register, Temperature	RW
32	16	Core Profile	9.1.16	MeterValuesAlignedDataMaxLength	optional	R	integer		Maximum number of items in a MeterValuesAlignedData Configuration Key.	8	R
33	17	Core Profile	9.1.17	MeterValuesSampledData	required	RW	CSL		Sampled measurands to be included in a MeterValues.req PDU, every MeterValueSampleInterval seconds. Where applicable, the Measurand is combined with the optional phase; for instance: Voltage.L1	Current.Import,Current.Offered,Voltage,Power.Active.Import,Energy.Active.Import.Register, Temperature	RW
34	18	Core Profile	9.1.18	MeterValuesSampledDataMaxLength	optional	R	integer		Maximum number of items in a MeterValuesSampledData Configuration Key.	8	R
35	19	Core Profile	9.1.19	MeterValueSampleInterval	required	RW	integer	seconds	Interval between sampling of metering (or other) data, intended to be transmitted by "MeterValues" PDUs. For charging session data (ConnectorId>0), samples are acquired and transmitted periodically at this interval from the start of the charging transaction. A value of "0" (numeric zero), by convention, is to be interpreted to mean that no sampled data should be transmitted.	60	RW
36	20	Core Profile	9.1.20	MinimumStatusDuration	optional	RW	integer	seconds	The minimum duration that a Charge Point or Connector status is stable before a StatusNotification.req PDU is sent to the Central System.	0	RW
37	21	Core Profile	9.1.21	NumberOfConnectors	required	R	integer		The number of physical charging connectors of this Charge Point.	1	R
38	22	Core Profile	9.1.22	ResetRetries	required	RW	integer	times	Number of times to retry an unsuccessful reset of the Charge Point.	2	RW
39	23	Core Profile	9.1.23	StopTransactionOnEVSideDisconnect	required	RW	boolean		When set to true, the Charge Point SHALL administratively stop the transaction when the cable is unplugged from the EV.	TRUE	RW
40	24	Core Profile	9.1.24	StopTransactionOnInvalidId	required	RW	boolean		whether the Charge Point will stop an ongoing transaction when it receives a non- Accepted authorization status in a StartTransaction.conf for this transaction	TRUE	RW
41	25	Core Profile	9.1.25	StopTxnAlignedData	required	RW	CSL		Clock-aligned periodic measurand(s) to be included in the TransactionData element of StopTransaction.req MeterValues.req PDU for every ClockAlignedDataInterval of the Transaction	""	RW
42	26	Core Profile	9.1.26	StopTxnAlignedDataMaxLength	optional	R	integer		Maximum number of items in a StopTxnAlignedData Configuration Key.	0	to be supported
43	27	Core Profile	9.1.27	StopTxnSampledData	required	RW	CSL		Sampled measurands to be included in the TransactionData element of StopTransaction.req PDU, every MeterValueSampleInterval seconds from the start of the charging session	""	RW
44	28	Core Profile	9.1.28	StopTxnSampledDataMaxLength	optional	R	integer		Maximum number of items in a StopTxnSampledData Configuration Key.	8	R
45	29	Core Profile	9.1.29	SupportedFeatureProfiles	required	R	CSL		A list of supported Feature Profiles. Possible profile identifiers: Core, FirmwareManagement, LocalAuthListManagement, Reservation, SmartCharging and RemoteTrigger.	Core,FirmwareManagement,LocalAuthListManagement,Reservation,SmartCharging,RemoteTrigger	R
46	30	Core Profile	9.1.30	SupportedFeatureProfilesMaxLength	optional	R	integer		Maximum number of items in a SupportedFeatureProfiles Configuration Key.		Not supported
47	31	Core Profile	9.1.31	TransactionMessageAttempts	required	RW	integer	times	How often the Charge Point should try to submit a transaction-related message when the Central System fails to process it.	1	to be supported
48	32	Core Profile	9.1.32	TransactionMessageRetryInterval	required	RW	integer	seconds	How long the Charge Point should wait before resubmitting a transaction-related message that the Central System failed to process.	30	to be supported
49	33	Core Profile	9.1.33	UnlockConnectorOnEVSideDisconnect	required	RW	boolean		When set to true, the Charge Point SHALL unlock the cable on Charge Point side when the cable is unplugged at the EV.	TRUE	RW
50	34	Core Profile	9.1.34	WebSocketPingInterval	optional	RW	integer	seconds	Only relevant for websocket implementations. 0 disables client side websocket Ping/Pong. In this case there is either no ping/pong or the server initiates the ping and client responds with Pong. Positive values are interpreted as number of seconds between pings. Negative values are not allowed. ChangeConfiguration is expected to return a REJECTED result.	0	RW
51	35	Local Auth List Management Profile	9.2.1	LocalAuthListEnabled	required	RW	boolean		whether the Local Authorization List is enabled	TRUE	RW
52	36	Local Auth List Management Profile	9.2.2	LocalAuthListMaxLength	required	R	integer		Maximum number of identifications that can be stored in the Local Authorization List	48	R
53	37	Local Auth List Management Profile	9.2.3	SendLocalListMaxLength	required	R	integer		Maximum number of identifications that can be send in a single SendLocalList.req	48	R
54	38	Reservation Profile	9.3.1	ReserveConnectorZeroSupported	optional	R	boolean		If this configuration key is present and set to true: Charge Point support reservations on connector 0.	TRUE	R
55	39	Smart Charging Profile	9.4.1	ChargeProfileMaxStackLevel	required	R	integer		Max StackLevel of a ChargingProfile. The number defined also indicates the max allowed number of installed charging schedules per Charging Profile Purposes.	8	R
56	40	Smart Charging Profile	9.4.2	ChargingScheduleAllowedChargingRateUnit	required	R	CSL		A list of supported quantities for use in a ChargingSchedule. Allowed values: 'Current' and 'Power'	Current,Power	RW
57	41	Smart Charging Profile	9.4.3	ChargingScheduleMaxPeriods	required	R	integer		Maximum number of periods that may be defined per ChargingSchedule.	24	R
58	42	Smart Charging Profile	9.4.4	ConnectorSwitch3to1PhaseSupported	optional	R	boolean		If defined and true, this Charge Point support switching from 3 to 1 phase during a Transaction.	FALSE	to be supported
59	43	Smart Charging Profile	9.4.5	MaxChargingProfilesInstalled	required	R	integer		Maximum number of Charging profiles installed at a time	10	R
60
61
62	Custom Message	Accessibility	Description		Default Setting Value	Note
63	Cst_BackendUrl	RW	Change the Central system URL, eg: wss://ocpp-toolkit-api.monta.app. After the changes, 'RebotRequired' response is triggered, and it will take effect after restarting.		" "	Only for NexBlue's internal use		Cannot be modified while charging
64	Cst_ChargeBoxId	R	Change the Charge box ID, default as SN. After the changes, 'RebotRequired' response is triggered, and it will take effect after restarting.		" "	Only for NexBlue's internal use
65	Cst_rssi_values	R	The signal strength of the WiFi/Cellular based on the connectivity.		-99	Only for NexBlue's internal use
66	Cst_NotNetworkMeterValueSampleInterval	RW	Sampling interval for metervalue when the charger is offline.		0	Only for NexBlue's internal use
67	Cst_FreeVendActive	RW	Plug in to start charging and unplug to stop.		FALSE	Only for NexBlue's internal use
68	Cst_FreeVendIdTag	RW	When the value is empty, it is represented as "A0000000".		"A0000000"	Only for NexBlue's internal use
69	Cst_CaCert	RW	Certification		" "	Only for NexBlue's internal use
70	Cst_ReconnectInterval	RW	The interval of reconnection		30	Only for NexBlue's internal use
71	Cst_PreBoot Transactions	RW	Whether or not a transaction can be initiated before the BootNotification successfully completes.		FALSE	Only for NexBlue's internal use
72	Cst_Silent Offline Transactions	RW	If the EVSE goes offline, whether or not it can continue to charge without sending StartTx / StopTx to the server when going online again.		FALSE	Only for NexBlue's internal use
73	Cst_Authorization Timeout	RW	How long the EVSE tries the Authorize request before it enters offline mode.		20	Only for NexBlue's internal use
74	Cst_MeterValueCacheSize	RW	How many data can be cached in MeterValue.		1	Only for NexBlue's internal use
75	Cst_StopTxnDataCapturePeriodic	RW	Whether or not to enable stop Txn Data timer logging.		FALSE	Only for NexBlue's internal use
76	Cst_ModemMeterValueSampleInterval	RW	Sampling interval for metervalue when the charger is connected to cloud via 4G. Default close.		0	Only for NexBlue's internal use
77	Cst_ModemState	R	Whether or not the charger is connected to cloud via 4G.		""	Only for NexBlue's internal use
78	Cst_lock_state	R	Obtain the lock status: "True" indicates that the lock is engaged, while "False" signifies that it is disengaged.		""	Only for NexBlue's internal use
79	Cst_NetworkState	R	Whether or not the charger is connected to cloud		""	Only for NexBlue's internal use
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100