Contact Us
Electronic product development is a broader process than schematic drawing. Fetrion; It handles hardware architecture, PCB design, embedded software, prototype tests and production preparation within the same project.
The product's operating environment, supply structure, inputs and outputs, communication needs and mechanical boundaries are the starting point of the design. Signal and power integrity, electromagnetic compatibility goals, and manufacturability are considered together in the schematic and board layout.
Embedded software; It combines product functions such as sensor reading, communication, control scenarios and error management with hardware. In IoT projects, data transfer and remote update requirements via MQTT/HTTPS are planned according to the project scope. Interfaces and expected behaviors are defined before the prototype.
The prototype phase is used to evaluate design assumptions through measurement and functional testing. AOI, ICT or functional testing approach is planned depending on the product. Verification and reporting of site conditions inform subsequent design decisions.
The DFM/DFA approach allows assembly and manufacturing needs to be evaluated during design. Equivalent options and EOL/NRND risks are discussed in component procurement. For the offer, you can share the target usage, estimated production quantity, mechanical dimensions and existing technical documents, if any.
During the transition to production, Gerber or the selected production data format, drilling files, BOM, layout coordinates and assembly drawings are checked. Firmware version, programming method and functional test acceptance criteria are included in the scope of delivery. Tracking hardware-software revision makes it easier to match changes in the field and production batches.
EMC design; return paths are considered along with filtering, ports, shielding and cable conditions. Pre-compliance measurements can indicate design risks early. CE marking covers the technical file, conformity assessment and producer responsibility according to the use of the product and applicable legislation; Only the PCB drawing or a single test result is not considered sufficient.
The service scope of the project can be determined by discussing the required design, software, prototype or production stages.
The purpose of the product, operating conditions, inputs and outputs, size limits and estimated production quantity provide a good start.
DFM, the suitability of the design to the production processes; DFA discusses the feasibility of component layout and assembly operations. PCB rules, paneling, soldering and access conditions are evaluated together with the manufacturer.
Generally, board manufacturing and hole files, BOM, component layout data, assembly drawings and revision information are required. Programming file and test instructions are added according to product scope; The manufacturer's data requirements are verified.
No. PCB design is part of the compliance studies. The final product's housing, cables, power supply and usage environment also affect the evaluation. Applicable legislation and verification plan are determined on a product-by-product basis.
PCB is a printed circuit board on which electronic components are placed and connected via conductive paths. Embedded software, on the other hand, executes certain functions on hardware such as microcontrollers. For a working electronic product, the card, software, power supply and usage conditions are designed together.
It does not cover itself. Hardware and software deliveries, source files and tests should be defined separately within the scope of the project.
It is useful to start when determining functions and acceptance criteria; test access may affect board and software design.
Share your current infrastructure and needs; Let's determine the scope of measurement, hardware and software together.
Request a Project Quote