Limit profiles: the numbers behind every check
Every threshold a check uses lives in a limit profile: what the profile holds, the profiles that ship, what the verify flag means and how a check against the standard is recorded, and how to adapt a profile to a test plan.
Every threshold in one place
No check in the analyzer has a number written into it. A voltage window, a timeout, an attenuation limit or a CAN period comes from the active limit profile, a JSON document of named entries. Each entry has a value, a unit, a note on where the value comes from and, while it has not been checked against the standard, a verify flag. Change a value and the open session is checked again at once.
| Key prefix | What it holds | Used by |
|---|---|---|
| cp. | Control Pilot state windows, PWM frequency, duty cycle ranges, edge times, the SLAC retry step, the delay around PowerDelivery | CP-01 to CP-10 |
| pp. | Cable coding resistor ranges and the charger's PP measuring circuit | PP-01, PW-01 |
| pw. | Overcurrent margin, settling time, time to stop, contactor opening time, nominal voltage | PW-01 to PW-03, IS20-03, IS20-04 |
| slac. | Number and spacing of the sounds, TT_EV_atten_results, attenuation, attempts, match time | SL-03 to SL-08 and the SLAC verdicts |
| sdp. and tcp. | SDP retry pacing and response time, TCP retransmissions | SD-01, SD-02, SD-06, TC-03 |
| tim. | The message, Ongoing, sequence and setup timeouts of ISO 15118-2 and DIN SPEC 70121 | TIM-01 to TIM-04, TIM-06 |
| dc. | Pre-charge tolerance and timeout | DC-01 |
| pki. | The largest certificate in TLS 1.2 and TLS 1.3 chains | PK-02 |
| can., chademo. and gbt. | CAN periods, silence and stalls, the CHAdeMO and GB/T margins and the GB/T handshake time | CAN-01, CAN-02, CH-02, CH-03, GB-01 to GB-06 |
| align., capture. and tools. | When an alignment is accepted, when a capture counts as cut short, when a timer counts as close | The Alignment tab, the verdict, the Timers tool |
The Checks tab lists, for each check, the limits it used with their values. Every timer and timeout shows every timing value of the active profile.
The shipped profiles
| Profile | Based on | What differs |
|---|---|---|
| IEC 61851-1 and ISO 15118-2 defaults | IEC 61851-1:2017 for the Control Pilot and currents, ISO 15118-2 and ISO 15118-3 for timing, lab practice where no standard gives a number | The base every other profile is derived from |
| SAE J1772 and J3400 (North America) | The defaults | The contactor opening time after C to B is 3 s instead of 100 ms (flagged), and the nominal voltage for turning a schedule into a current is 240 V instead of 230 V |
| Open-RTH remote test harness | The defaults | rig.stopsBeforeEnergy is 1, so a session that stops before the energy transfer with no refusal and no error before it reads Stopped before energy by design; the message timeouts are 3 s longer for the MQTT relay |
J3400 keeps the J1772 Control Pilot and carries ISO 15118 or DIN SPEC 70121 for DC, so it shares the North American profile. A derived profile changes only what its standard sets differently, so the two cannot drift apart unnoticed.
Open-RTH relays the V2G messages between a car and a charger at two sites over MQTT, but no power, so every session stops at or before pre-charge and each answer arrives 1 to 3 s late. Its profile reads that stop as the end of the run and names the errors from the stop on (the request the rig did not relay, its timeouts) as the rig's. Another rig that works the same way needs only rig.stopsBeforeEnergy set to 1 in a copy of the defaults.
The analyzer suggests a profile for each session: the North American one when the EVSEID is registered in the United States, Canada, Mexico or Puerto Rico, or when the charger names a supply of 120, 208, 240 or 277 V. Below the verdict it says which profile the checks used, and one click checks the session with the suggested one.
Verify flags and recorded checks
- A value flagged verify comes from a secondary source and has not yet been checked against the text of the standard. Learn pages that quote such a value carry a Verify badge.
- Limits lists the flagged values grouped by the document that settles them, for example ISO 15118-3 for the SLAC timers and ISO 15118-2 or DIN SPEC 70121 for the message timeouts.
- Mark as checked, with the clause or table and your name, takes the flag off. The entry keeps who checked it, when and against what, and the corrected value if it changed. An exported profile carries that record.
- Some values are lab practice by nature, such as the attenuation threshold and the overcurrent margin. IEC 61851-1 only says the car stays at or below the limit; how much overshoot a lab tolerates is a decision of the test plan.
A result is only as good as the values behind it. Before you quote one, check the values its checks used against the edition of the standard in your test plan, or record why your lab uses a different value.
Adapting a profile to a test plan
- Start from the shipped profile closest to the market you test for, and Duplicate it under a name that says which test plan it serves.
- Change the values your plan sets differently: a stricter response time, a narrower pre-charge tolerance, the attenuation your coupling normally shows, the PP measuring circuit of the charger under test.
- Record every value you checked against the standard with Mark as checked, so the list of flags shows only what is still open.
- Add custom checks for rules of the plan that no built in check covers, as one line conditions such as name = "ChargingStatusRes" and responseMs > 250. They add findings and never change the verdict.
- Export JSON and keep the file with the test plan. Import JSON loads it on another machine, and the command line runner takes it with --profile, so a pipeline judges with the same numbers as the bench.
Reset to defaults brings the draft back to the shipped values.
What a profile does not change
- Which checks run: that follows from the protocol on the wire.
- The verdict categories and how they are chosen, apart from the few values the verdict reads itself, such as when a SLAC step counts as stalled (slac.stepTimeoutS) and when a capture counts as cut short (capture.incompleteTailS).
- How a message is decoded.
Sources
- SPEC.md of this tool, sections 9.1, 15.7 (FR-TOOL-10) and 15.8 (FR-STD-01)
- IEC 61851-1:2017, the Control Pilot and current values of the default profile
- SAE J1772, the values the North American profile changes
- Argonne Open-RTH, README: stops at or before PreCharge, relay time