openydt-flow-park-access

Original：🇨🇳 Chinese

Translated

SOP for Vehicle Entry/Exit Operation Process of AIKE Smart Parking Open Platform (End-to-end Orchestration for Entry/Exit). This skill is applicable when users want to complete the full entry/exit of a vehicle, simulate the real physical entry/exit process, run through the entire link of 'Supplement/Capture Entry → Correction' or 'Exit Capture → Correction → Fee Inquiry → Payment', or ask questions like 'How does a vehicle enter/exits the parking lot?', 'Entry/exit process', 'Entry/exit SOP', 'How to move a vehicle into/out of the parking lot', 'Simulate vehicle entry/exit', or encounter stuck/debugging issues during entry/exit (e.g., vehicle fails to enter after capture or correction, capture returns error code 908, unsure how to proceed to the next step). This skill is a cross-domain orchestration layer that connects multiple commands from parking (supplement/correction/inventory), device (capture), and trade (fee inquiry/payment), and clarifies cross-command hard constraints (paired exit, capture device, channel release mode, token validity) and failure handling. Boundary: For querying a single record, checking on-site vehicles, locking vehicles, or calling a single command, please directly use the corresponding domain skills openydt-record / openydt-device / openydt-billing instead of this process skill.

6installs

Sourcexiaowen-0725/openydt-cli

Added on2026-05-31

NPX Install

npx skill4agent add xiaowen-0725/openydt-cli openydt-flow-park-access

SKILL.md Content (Chinese)

View Translation Comparison →

openydt-flow-park-access — Vehicle Entry/Exit Operation Process (SOP)

CRITICAL: You MUST use the Read tool to read
../openydt-shared/SKILL.md
before starting to understand general conventions such as authentication / profile / signature / status code / rate limit / security. This skill only focuses on the orchestration of "how to move a vehicle into/out of the parking lot according to real physical processes" and does not repeat the parameter tables of each command — refer to the corresponding domain skills for specific input and output parameters.

When to Use This Skill (Division of Labor with Domain Skills)

Use this skill: Need to complete end-to-end entry/exit of a vehicle, simulate real entry/exit, run through the entire link, unsure which command to call first, or encounter an error in a certain step and don't know how to proceed.
Use domain skills (do not use this process): Only query a single record / check on-site vehicles / lock vehicles / want to call a single command →
```
[[openydt-record]]
```
(parking record domain),
```
[[openydt-device]]
```
(device domain),
```
[[openydt-billing]]
```
(payment domain).

Security Premise: Entry/exit involves write operations (supplement, capture, correction, payment, inventory), only practice in the test environment; preview the signed request with
--dry-run
for each write command first, then add
--yes
after confirmation. See the security conventions in openydt-shared.

Two Concepts Must Be Understood First

1. The two entry paths are essentially different:

	(a) Supplement Entry	(b) Capture Entry (Simulate Real Physical Process)
Command	`supplement-parking-record-in`	`channel-snap` → (if license plate is incorrect) `correct-car-on-channel`
Nature	Forced entry, vehicle will definitely enter	Entry not guaranteed
Capture Log	No capture record generated	Generated (it is simulating capture)
Applicable Scenario	Vehicle has actually entered but the platform missed it, need to supplement an entry record	Practice real entry physical process: Capture → Recognition → Correction

2. Channel Release Mode (The Most Counterintuitive Point): In capture entry,

correct-car-on-channel

successful correction ≠ vehicle will definitely enter. Whether the vehicle actually enters depends on the release mode of the channel — if the channel is set to "Prohibit temporary vehicles from entering", the vehicle will not enter the parking lot even after correction. This is by design: The capture link strictly simulates real physical release logic. Therefore, must verify whether the vehicle is actually on-site after correction (see below), do not assume entry is completed after correction.

Entry Process

First determine which path to use: Just want the record to include this vehicle (forced) → (a) Supplement; Want to practice real capture, recognition and correction process → (b) Capture.

(a) Supplement Entry (Forced, Vehicle Will Definitely Enter)

(Optional)
```
openydt parking check-channel-exist-car
```
to confirm whether there is already a vehicle in the current channel to avoid duplicate supplements.
```
openydt parking supplement-parking-record-in --yes
```
: Pass
```
parkCode
```
,
```
carCode
```
,
```
enterTime
```
,
```
channelCode
```
,
```
carCodeType
```
,
```
carCodeColor
```
,
```
parkOrArea
```
. The response returns the newly generated
```
parkingCode
```
.
If
recordType
/
enterCarType
are not passed, the CLI will automatically fill them with the default value
1
according to the platform documentation, no need to fill manually.
Completed. Supplement entry is forced entry, and the record takes effect immediately. For parameter details, see
```
[[openydt-record]]
```
.

(b) Capture Entry (Simulate Real Physical Process, Entry Not Guaranteed)

Capture:
```
openydt device channel-snap --yes
```
(pass
```
parkCode
```
,
```
channelCode
```
) to trigger a capture at the entry channel.
Prerequisite: The channel has a capture device; otherwise, it returns
resultCode=908 Device not found
, switch to a channel with a device.
Check License Plate: See if the captured license plate is the target license plate.
- If it is the target license plate → Proceed to the release judgment before Step 3.
- If not → Correction:
```
openydt parking correct-car-on-channel --yes
```
  (pass
```
parkCode
```
  ,
```
channelCode
```
  ,
```
newCarNo
```
  =target license plate,
```
correctTime
```
  ).
  If it reports "Session expired", it means there is no capture session available for correction on the current channel, you need to successfully execute
  channel-snap
  first before correction.
Verify Whether the Vehicle Actually Entered (Critical): Use
```
openydt parking get-park-on-site-car
```
(pass
```
parkCodeList
```
+
```
enterTimeFrom
```
/
```
enterTimeTo
```
, time range is required) to check on-site vehicles.
- On-site → Entry successful.
- Not on-site → Most likely because the channel release mode prohibits temporary vehicles from entering, correction will not allow it to enter; switch to (a) Supplement entry, or switch to a channel with allowed release mode.

Exit Process

The main path is "Exit Capture → Correction → Fee Inquiry → (Optional) Payment", use inventory exit as a fallback when the normal path is not feasible.

Exit Capture:
```
openydt device channel-snap --yes
```
(
```
parkCode
```
,
```
channelCode
```
=exit channel).
Prerequisite: The exit has a capture device, and it usually needs to be the paired exit of the entry channel; otherwise,
channel-snap
returns
908
and subsequent correction reports "Session expired". If no device / non-paired exit makes it unfeasible, skip to "Fallback: Inventory Exit" below.
Correct Channel Vehicle:
```
openydt parking correct-car-on-channel --yes
```
, correct the vehicle to be exited to the target license plate (
```
newCarNo
```
+
```
correctTime
```
).
Fee Inquiry (Confirmation Step):
```
openydt trade get-park-fee
```
(pass
```
carCode
```
+
```
parkCode
```
).
- Check
```
data.shouldPayValue
```
  in the response (Unit: Yuan,
```
1
```
  means 1.00 Yuan, not 1 cent) to confirm whether there is arrears / the amount to be paid.
- At the same time, obtain
```
parkingCode
```
  ,
```
chargeDate
```
  ,
```
otherAttr.chargeBillToken
```
  /
```
chargeBillNumber
```
  for the next payment step.
Payment must be completed within 10 minutes after fee inquiry, otherwise the token/bill will expire.
Payment (Optional, Ask First Then Execute):
- First ask the user "Do you need to pay? What payment method to use?" — Payment is a real write operation, do not execute it silently.
- Default recommended payment method is "Cash" or specified by the user; specific codes for
```
paymentMode
```
  /
```
payOrigin
```
  can be found in the online appendix
```
/Api/appendixData
```
  (enumerations are not built into the catalog).
- After confirmation:
```
openydt trade pay-park-fee --yes
```
  , pass
```
parkingCode
```
  ,
```
chargeDate
```
  ,
```
actPayCharge
```
  (≤
```
shouldPayValue
```
  , unit: Yuan),
```
payOrigin
```
  ,
```
paymentMode
```
  , unique
```
billCode
```
  obtained in Step 3, and
```
otherAtrr
```
  in
```
--body
```
  . For complete payment mechanism (with coupons, reconciliation, billCode uniqueness), see
```
[[openydt-billing]]
```
  .

Fallback: Inventory Exit — When the normal capture exit path is not feasible (no capture device at exit / non-paired exit), use
openydt parking inventory-car --yes
(
parkCode
,
enterTimeEnd
,
carNo
/
carNos
/
parkingCodes
,
remark
) as a supplementary method to inventory the vehicle out. Use
openydt parking get-inventory-record
to check inventory records. For command details, see
[[openydt-record]]
.

Cross-Command Hard Constraints and Quick Troubleshooting

Phenomenon / Constraint	Meaning	Handling
`channel-snap` returns `resultCode=908 Device not found`	The channel has no capture device	Switch to a channel with a capture device
`correct-car-on-channel` reports "Session expired"	No capture session available for correction on the channel	Successfully execute `channel-snap` first then correct
Vehicle not on-site after correction in capture entry	Channel release mode prohibits temporary vehicles from entering	Switch to supplement entry, or switch to a channel with allowed release mode
Capture exit path not feasible	No device at exit / non-paired entry exit	Use fallback `inventory-car` for exit
Amount Understanding	`shouldPayValue` / `actPayCharge` are in Yuan	Do not treat `1` as 1 cent
Fee Inquiry Token	Payment must be completed within 10 minutes after fee inquiry	Re-inquire fee if timed out

Command Attribution (See Domain Skills for Parameters)

Entry supplement / correction / on-site verification / inventory →
```
[[openydt-record]]
```
Capture
```
channel-snap
```
→
```
[[openydt-device]]
```

Fee inquiry

get-park-fee

/ Payment

pay-park-fee

→

[[openydt-billing]]

Entry/exit is a cross-domain process; input parameters, output parameters, and enumeration values of single commands are all subject to the above domain skills, this skill only connects them in the correct order and constraints.",