Review a model document before using an example.

Copy this checklist into your project note, or print the page. Leave unresolved fields marked “unverified” and keep the reference beside each conclusion.

Project record

Project / reference: ______________________________

Exact model and suffix: ______________________________

Document publisher and title: ______________________________

Revision / date: ______________________________

Source URL or file reference: ______________________________

Software version, if used: ______________________________

Review date / reviewer: ______________________________

Document check

[ ] The model and suffix match the source being reviewed.
[ ] The document revision or date is recorded, or marked unverified.
[ ] Supply limits and current conditions have source references.
[ ] Connector view, pin numbering, directions and signal levels are identified.
[ ] Serial settings and frame layout are recorded from the applicable source.
[ ] The validation rule and model-specific distance unit are identified.
[ ] Returned status, measurement flags and deadline conditions are recorded separately.
[ ] Observed behavior is labelled by evidence: document, source code, generated-byte check or physical measurement.
[ ] Missing information and conflicting references remain open questions.

Keep the evidence attached

For an ErdiLRF example, record the exact library version and model definition. Link the source behind an interpretation so it can be checked again when the code or document changes.

Generated inputs can check a parser assumption. A physical measurement record needs its own setup, conditions and observations. Keep each conclusion attached to the evidence that supports it.

Open questions

Question: ______________________________

Model / revision involved: ______________________________

Source location checked: ______________________________

What remains unverified: ______________________________

Next evidence needed: ______________________________

Send a focused documentation question

Email tommy@erdimail.com with the exact model, document revision and the unresolved point. Include the relevant page or a short byte example when applicable. Remove passwords, access tokens and unrelated customer information before sharing a file or trace.

References

ERDI TECH LTD · ERDILRF technical resources

Contact: Tommy Yu · tommy@erdimail.com

Website: erdilrf.com

Prepared with AI assistance. References are linked; no hardware measurements are reported on this site.

‍