Zaptec Go OCPP Native Non-standard implementation guide
The Zaptec Go OCPP Native Non-standard implementation guide provides detailed information on the Zaptec Go's native OCPP implementation. Specifically, it highlights the characteristics, variations, and extensions that are unique to this implementation compared to the standard OCPP protocol. This guide is intended for integrators, developers, and operators to facilitate a clear understanding and successful interaction with Zaptec Go charging stations.
1. Configuration Key Names & Values
1.1. FreeChargingIdTag
| Field | Value |
|---|---|
| Required/optional | required |
| Accessibility | RW |
| Type | CiString20Type |
| Description | idToken used as part of StartTransaction.req when no other idToken is specified. This SHOULD only be used by the Charge Point when FreeCharging is enabled. |
1.2. FreeCharging
| Field | Value |
|---|---|
| Required/optional | required |
| Accessibility | RW |
| Type | boolean |
| Description | Whether the Charge Point will start charging without requiring idTag authorization. |
1.3. LockCablePermanently
| Field | Value |
|---|---|
| Required/optional | required |
| Accessibility | RW |
| Type | boolean |
| Description | Whether the Charge Point SHALL lock the cable in place after insertion, and thereafter act as if the cable is permanently attached. If true, then the UnlockConnectorOnEVSideDisconnect configuration key SHALL be false and read-only. |
1.4. PowerActiveImportDeltaForEagerMeterValueSample
| Field | Value |
|---|---|
| Required/optional | required |
| Accessibility | RW |
| Type | integer |
| Unit | W |
| Description | Maximum change in Power.Active.Import since the last MeterValue related to MeterValuesSampledData before a new Sample.Periodic is sent and MeterValueSampleInterval is reset. A value of 0 disables this behaviour. Example: If set to 200 and MeterValueSampleInterval is 3600, and Power.Active.Import was 300 during the last sample, then if it becomes > 500 or < 100, it will send a new Sample.Periodic immediately and reset the interval. |
1.5. UseAuthorizationKeyWithoutDecoding
| Field | Value |
|---|---|
| Required/optional | required |
| Accessibility | RW |
| Type | boolean |
| Description | Alters the charger's validation and use of AuthorizationKey. If false: Tries to decode hex-encoded AuthorizationKey and rejects invalid ones (per RFC 7617 and 5234). If true: Uses it directly as HTTP Basic Auth password with similar validation but no decoding. Default: false if not previously set, else true. |
Updated 17 days ago