Constant-Current LED Driver Checker

Read the tool instructions in Markdown and the request/response schemas in OpenAPI. These public calculation APIs run the same models as the web and offline calculators. No account, API key or Turnstile is required.

• Constant-Current LED Driver Checker — Full tool instructions (Markdown)
• OpenAPI contract
• Agent site index

Constant-Current LED Driver Checker

POST /api/tools/v1/driver-match
Content-Type: application/json

One series string of identical modules at a declared target operating current. Voltages are V, currents mA, power W and tolerance percent. Use the complete module Vf range for the intended current, bin and temperature, and the driver CC region at that setting. Typical or reference-only datasheet values are not guaranteed limits. CC+CV is evaluated only in its CC region; CV-only is unsupported.

driver-match

Constant-Current LED Driver Checker

Supply the eight required numeric/type inputs. Optional powerLimitW is output power after derating. currentTolerancePct and moduleMaxCurrentMa must both be supplied or both omitted/null. The response contains the entered operating point, voltage/power envelopes, current checks, count interval and explicit unchecked warnings. No hardware certification is implied.

{
  "ledCurrentMa": 700,
  "vfMinV": 9,
  "vfMaxV": 10.5,
  "seriesCount": 4,
  "regulation": "cc",
  "driverCurrentMa": 700,
  "driverMinV": 24,
  "driverMaxV": 48,
  "powerLimitW": null,
  "currentTolerancePct": null,
  "moduleMaxCurrentMa": null
}

Open links.tool for the calculator or links.markdown for full instructions. links.share is null because no encoded share-state format is defined. Copy/save exports a text report and Print/PDF exposes current inputs and calculation details. The calculator runs locally in the browser; these actions do not submit an inquiry or call the calculation API. Preserve all warnings. Bench verification of start-up, ripple, dimming, thermal conditions and insulation is outside the model.

Request limits and errors

Send uncompressed application/json with strict types and no query parameters. Indoor lighting bodies are limited to 16 KiB; driver-match bodies to 16 KiB; battery bodies to 16 KiB; voltage bodies to 16 KiB; resistor bodies to 16 KiB; DMX bodies to 1024 KiB and 1000 fixtures; pixel bodies to 64 KiB, 64 run rows, 128 outputs and 2000000 channels. DALI bodies are limited to 64 KiB, 24 rows and 512 devices. Illuminance bodies are limited to 16 KiB and 400 planned points. Photometry bodies are limited to 1024 KiB with up to 4 files and 16 by 721 query directions per file. Lighting-cost bodies are limited to 64 KiB with up to 20 groups in each scenario. Body reading expires after 5 seconds. Complete success JSON is bounded to 4 MiB. GET/HEAD return 405; OPTIONS returns 204. Source responses are no-store. Anonymous browser CORS permits POST/OPTIONS and Content-Type with credentials omitted.

Tool POST requests and ordinary page requests share 120 requests per 60 seconds per IP/Cloudflare location; mitigation lasts 60 seconds. Heavy tool use can temporarily block pages from the same source. This is not an independent or globally exact API quota. Inquiry/search use their existing separate rule. Tool POST requests do not inherit the company-page or verified-bot exemption.

Cloudflare can return 403/429/5xx before the application, sometimes as HTML without CORS or Retry-After. Check HTTP status and Content-Type before parsing JSON. A browser may see only a network error. Do not present an error or an older result as a successful new calculation.