Compatibility is an evidence record
A transport match or similar message vocabulary is not enough to declare two systems compatible. The review must identify the exact hardware and software boundary.
Public station families
CoreCharge's public website currently presents 4, 6, 8, 12, 16 and 24-slot station formats. The table below records documentation scope, not a production compatibility certification.
| Station format | Public product signal | Protocol profile | Verification state |
|---|---|---|---|
| 4-slot | Product family is publicly listed | Profile assignment pending | Content-owner review required |
| 6-slot | Product family is publicly listed | Profile assignment pending | Content-owner review required |
| 8-slot | Product family is publicly listed | Profile assignment pending | Content-owner review required |
| 12-slot | Product family is publicly listed | Profile assignment pending | Content-owner review required |
| 16-slot | Product family is publicly listed | Profile assignment pending | Content-owner review required |
| 24-slot | Product family is publicly listed | Multi-board review may apply | Content-owner review required |
Compatibility record template
Every verified row should contain:
| Field | Required evidence |
|---|---|
| Commercial model | Exact public model name and product page |
| Controller revision | Hardware revision recorded by an authorized owner |
| Firmware release | Version identifier and release date |
| Transport profile | Approved transport and authentication profile name |
| Message contract | Versioned public or partner contract identifier |
| Power-bank class | Standard or approved fast-charge class |
| Slot topology | Slot count and any controller expansion topology |
| Test scope | Connect, status, rental, return, offline recovery and exception handling |
| Result | Pass, conditional pass or fail with evidence link |
| Evidence date | UTC date and named approving role |
Required compatibility tests
- Establish an authenticated non-production connection using an approved profile.
- Correlate station identity without exposing raw identifiers in the report.
- Confirm periodic and on-demand station status semantics.
- Exercise rental preparation, authorization boundary, release result and timeout behavior.
- Exercise return detection, acknowledgement and abnormal-return handling.
- Confirm reconnect, duplicate-message and out-of-order behavior.
- Confirm slot, battery, lock and charge-state mappings for the tested hardware.
- Record unsupported operations and firmware-specific differences.
Current gaps
- Exact commercial model-to-protocol mappings need product-owner approval.
- Firmware families and minimum supported releases need engineering ownership.
- Fast-charge class mappings require hardware evidence, not document inference.
- Partner test fixtures and an authenticated sandbox are not included in this public documentation release.