Skip to main content

Start with the operating contract

CoreCharge publishes the complete v1.51 cabinet command semantics so buyers and engineering teams can keep purchased hardware integrable beyond a single software deployment. Production access remains controlled, while frame grammar, CRC, commands, parameters, workflows and test fixtures are public.

Public documentation boundary

This release is operationally useful documentation with synthetic fixtures. It does not expose production credentials, certify every hardware model or replace model-specific UAT and an authorized connectivity profile.

What this public layer answers​

  • What responsibilities belong to the station, platform, payment provider and operator.
  • The exact ASCII frame, CRC calculation, all v1.51 commands, directions and field order.
  • Which states must be reconciled across device, rental, payment and return records.
  • How hardware compatibility should be demonstrated for a specific model and firmware release.
  • Which software capabilities have public evidence and which still require project confirmation.
  • Which integration artifacts are available to machines as well as people.

What this public layer does not contain​

  • Assigned production network locations and ports.
  • Credentials, secrets, certificates, provisioning values or tenant identifiers.
  • Real firmware locations, private release artifacts or unrestricted service tooling.
  • Production payloads, customer records or real device identifiers.
  1. Read the trust principles.
  2. Select a station family and open a compatibility review.
  3. Implement the frame, transport and CRC.
  4. Follow the end-to-end flows and checklist.
  5. Review the software feature matrix.
  6. Download the command catalog and AsyncAPI contract.
  7. Request assigned connectivity values only after scope, identity and security ownership are approved.

Evidence vocabulary​

StateMeaning
DocumentedA public page describes the capability or contract.
Schema availableA machine-readable shape exists, but it is not a production endpoint.
TestableAn approved fixture or sandbox can exercise the behavior.
VerifiedEvidence identifies model, firmware, environment, date and result.
Production-approvedNamed owners approved the exact deployment and operating boundary.

These states are deliberately separate. A documented field is not proof that a specific station, firmware build or payment account is production-ready.