IMETER

by DrDiodac in Design > Software

98 Views, 0 Favorites, 0 Comments

IMETER

Instructables · DrDiodac

iMETER ideas — Kelvin cable QA concepts

Learn the measurement story: per-core resistance, length-based thresholds, and a webhook/data-console path. Product site and commercial firmware stay proprietary.

Education slice Not full commercial source

Product site Public GitHub DrDiodac

Intro

iMETER is DIODAC / iSystem’s intelligent cable test system for multi-core resistance QA. The live product is imeter.isystem.app. The public GitHub tree is a documentation / education-oriented slice — not a promise of full shipping firmware.

License: Proprietary for commercial Software and firmware. This Instructable teaches concepts and how to explore the public materials — do not redistribute closed binaries.



Supplies


  1. Multimeter or Kelvin / 4-wire capable instrument (bench learning)
  2. Sample multi-core cable with known length
  3. Browser for the product site data console demo
  4. Optional: ESP32 + ADS1220 class hardware if you are on a licensed hardware path
  5. Git (to browse the public repo tree)


Read the Public README — Know the Boundary


Open iMeter-v2.0.00. Note: Kelvin four-wire concept, webhook JSON pipeline, Bluetooth barcode scanning lineage, and that distribution SSOT is the product host.

Step 2 Walk the product physics / marketing page

Visit imeter.isystem.app. Use the physics / Engineer Bay materials as enrichment — they explain why length-based thresholds matter for pass/fail.

Step 3 Bench a simple per-core check

On a scrap cable, measure each core’s resistance (2-wire is a teaching start; 4-wire Kelvin is the production method). Record length and note how ohms scale roughly with length for a given AWG.

Production iMETER automates thresholds and traceability — your notebook is the learning stand-in.

Step 4 Explore the data console demo

Open the site’s data console (data.html when available) to see how bench results become reviewable records. Relate that to webhook JSON pipelines in the README.

Step 5 Related tools

Cable documentation: WireAI / CAD. Hub: isystem.app. Licensing / hardware quotes: product site contact.

Conclusion

You should understand iMETER’s job (per-core QA + traceability) and the public/education boundary. For builds that need full firmware, go through the commercial product path — not a random GitHub dump.

imeter.isystem.app

DrDiodac

Profile

© 2026 DIODAC ELECTRONICS / iSystem Development · Education Instructable — proprietary product remains separate