Electronics and Embedded Systems Design Services
Describe your circuit, PCB or embedded firmware requirements. Scope, deliverables and acceptance criteria are agreed before work begins.
Engineer: Mohammad Norouzian Azizi
Discuss your projectTurn a technical need into a reviewable scope
If you need electronics design for a product, a prototype or an existing board, describe the goal and constraints. Mohammad Norouzian Azizi works independently on electronic hardware and embedded firmware. The scope depends on requirements, available documentation and feasibility. An enquiry does not automatically constitute an accepted project.
Areas of work
- Circuit and PCB design: review power and interface requirements, develop schematics, select components and lay out boards within agreed fabrication and assembly constraints.
- STM32 and ESP32 firmware: C and C++ development, sensor and actuator interfaces, and coordination between firmware and existing hardware.
- Communications and test tools: work with interfaces such as UART, RS-485 and networking, together with project-specific evaluation tools.
- Prototyping and debugging: review a design or investigate observed behaviour. Physical testing requires access to the board, suitable instruments and an agreed procedure.
This page is not a component listing or a promise of a ready-made product. For purchases, consult the actual inventory in the store.
Public project experience
These examples come from the published engineering portfolio. They describe contributions to previous work, not a promise of identical results for a new project.
- Car-wash controller and I/O boards: design of central-controller, I/O and operator-panel boards with isolated inputs and relay outputs for industrial equipment. The portfolio provides images and explains the contribution.
- Communications and audio systems: board revisions, firmware, connection handling and computer-based evaluation tools. The profile distinguishes the hardware and software contributions.
- Charging and power-management circuits: hardware revisions for charging, power conversion, protection and microcontroller-based monitoring. Review the published examples to assess the relevance of that experience.
How a project proceeds
- Describe the goal, current development stage and constraints.
- Review technical requirements, feasibility, exclusions and any additional information needed.
- Agree the scope, price, schedule, milestones and acceptance criteria before work begins.
- Develop and review the design against the agreed scope. Requirement changes may affect both scope and schedule.
- Hand over the agreed deliverables and evaluate them using the agreed evidence and tests.
A fixed price, completion date or successful hardware test cannot be guaranteed before the project is reviewed.
What can be delivered?
Depending on the agreement, deliverables may include schematic and PCB source files, firmware, a bill of materials, setup documentation and test evidence. Deliverables are defined by the agreed project scope. Source ownership and handover, tool licences, prototype fabrication and assembly, and the level of testing must be agreed explicitly. Calculations, simulations and measurements on a physical board are distinct forms of evidence.
Questions before commissioning work
What information helps at the start?
Explain the use case, required power supply and interfaces, mechanical and environmental requirements, available hardware or code, development stage and expected deliverables. Include your preferred timing and approximate budget if known.
Can an existing board or codebase be reviewed?
Describe the issue and the documentation you can provide. Feasibility depends on lawful access to source files, the quality of the documentation and whether the issue can be reproduced.
Are source and manufacturing files included?
File types, tool versions, licences and usage rights are agreed before starting. No additional file or right should be assumed outside that agreement.
How much will it cost and how long will it take?
A proposal follows review of the scope, complexity, dependencies and required tests. This page does not quote a fixed price or deadline.
Should I send confidential material immediately?
No. Start with a non-confidential description and leave out passwords, keys, customer data and restricted files. The contact form is a private enquiry channel, separate from the public discussion forum.
Discuss your project
Use the existing contact form with a project-enquiry subject. Include the goal, required hardware and interfaces, current stage, expected deliverables and your preferred reply details. The form records a message in the site's private inbox. Its acknowledgement does not establish that the message has been read or that a project has been accepted.
Discuss your project View profile and portfolio
For independent learning, see the electronics reference guide and embedded systems learning path.