Wire Ampacity Lookup
Audit actual installation current against independently verified same-edition/temperature/conductor ampacity reference. Independently verified caller edition/site/specimen reference, no fabricated table. Caller independently establishes units, regime, calibration and applicability; this does not establish design-code compliance, authenticity, operational safety, treatment efficacy or a validated forecast.
Description
Ampacity concerns a conductor's current-carrying conditions under an applicable specification.
Ampacity concerns a conductor's current-carrying conditions under an applicable specification.1
A numerical crosswalk needs independently matched installation conditions and does not install an electrical-code table. Use this tool to compare an observation with an exact caller-supplied numeric reference.
When to use Wire Ampacity Lookup
Use this tool to compare an observation with an exact caller-supplied numeric reference. Establish the SI units or caller unit basis, load signs, measurement interval, model conditions and independently chosen coefficients or references.
How to use Wire Ampacity Lookup and understand its results
- Establish the SI units or caller unit basis, load signs, measurement interval, model conditions and independently chosen coefficients or references.
- Enter callerAmpacityIds, callerAmpacityValues, queryAmpacityId, observedAmpacityValue, using the field meanings and rules below, then run the tool.
- Read callerMatchedReferenceValue, signedObservedMinusReference. Interpret the fields using their units, signs and evidence conventions below.
- If input validation fails, correct the reported field and run again. Before applying the result, check reference scope, model assumptions and any missing evidence or placeholder values.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerAmpacityIds | Caller ampacity ids | list of string | Required |
| callerAmpacityValues | Caller ampacity values | list of number | Required |
| queryAmpacityId | Query ampacity id | string | Required |
| observedAmpacityValue | Observed ampacity value | number | Required |
Enter nonempty aligned caller reference IDs and numeric reference values, an exact query ID and an observed value on the same unit and protocol basis. Reference values and the observation are finite signed numbers; there is no nonnegative check here and they need not be integers. IDs must be unique and nonblank, with at most 128 UTF-16 units each. The implementation uses case-sensitive exact matching without trimming, returns the matched reference value and subtracts it from the observation. An absent query or duplicate key fails. No regional dataset is installed, retrieved or authenticated.
reference=values[indexOfExact(queryId,ids)]; signedDifference=observed−reference Use the exact units, boundary rules, ordering and missing-evidence conventions above.
| Output field | Meaning | Value type |
|---|---|---|
| callerMatchedReferenceValue | Caller Matched Reference Value; follow the units, sign, ordering and evidence convention stated above | number |
| signedObservedMinusReference | Signed Observed Minus Reference; follow the units, sign, ordering and evidence convention stated above | number |
{
"input": {
"callerAmpacityIds": [
"a",
"b"
],
"callerAmpacityValues": [
2,
4
],
"queryAmpacityId": "b",
"observedAmpacityValue": 5
},
"output": {
"callerMatchedReferenceValue": 4,
"signedObservedMinusReference": 1
}
}Limitations and assumptions
The numerical reference, unit basis and observation come from the caller. No authoritative regional table, standard edition, calibration or management rule is installed, retrieved or verified.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse evidence arrays fail validation; the specific bounds and alignment requirements are stated above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful result reporting false, no matches or missing evidence.
Alternative or Complementary methods
Use Protection Coordination Time Calculator for this related task: Protection coordination compares upstream and downstream operating times with a chosen margin.
Use Motor Starting Voltage Drop Calculator when its separate inputs and assumptions fit the question: A balanced motor-current approximation combines circuit resistance, reactance and power factor.
References
-
Wire Ampacity Lookup — tool.io
Similar or alternative tools
- Protection Coordination Time Calculator
Protection coordination compares upstream and downstream operating times with a chosen margin.
- Motor Starting Voltage Drop Calculator
A balanced motor-current approximation combines circuit resistance, reactance and power factor.