Writing of electronic design competition technical reports

Electronic competition technical reports are one of the types of scientific and technological reports. Why choose this type of report to introduce separately? This is because students participating in electronic competitions or science exhibitions must submit a technical report, and in electronic competitions, out of 150 points, the technical report accounts for 50 points. Engineering students have relatively poor technical writing skills. They have to complete this work within 3 days (including designing and producing works). It is indeed difficult and intensive. Students often feel that they have no idea where to start, resulting in poor technical report writing skills. Low, so it is necessary to introduce students to technical report writing methods and techniques.

It should be noted that if the content, format, layout, and font size of the technical report are required in the competition topic, it should be written according to the requirements; if there are no requirements in this regard, the technical report must be written. The report is flexible and the following content is for reference only.

In fact, the genre and structure of technical reports and scientific papers are basically the same. Therefore, technical reports can refer to the format of scientific papers, namely: title, author, abstract, keywords, introduction, body, conclusion, acknowledgments, Appendix, references.

Since these contents have been introduced in the section on writing scientific papers, they will not be repeated here. I only put forward a few suggestions for writing electronic competition technical reports:

(1) Due to space restrictions, the number of scientific papers published in journals is generally controlled between 3,000 and 5,000 words, while technical reports The word limit can be relaxed.

Given that electronic competitions are system-level questions that require a lot of writing, and some also require a program list or component list, the number of words should be equivalent to that of a graduation thesis, about 15,000 words. .

(2) Scientific papers have a rigorous structure and standardized writing, which are the basis of scientific writing. They can be learned and imitated when writing technical reports, but they should not be applied rigidly. The format requirements for scientific papers should be used flexibly. For example, important items such as abstract, keywords, appendices, references, and acknowledgments should be noted in text, while important items such as title, author, introduction, main text, and conclusion should not be noted in text. It is explained only as a step in writing a layout technical report. Some of these steps can be omitted, such as introductions, acknowledgments, etc., which are not required. You can decide whether to adopt these steps according to the situation.

(3) The title of the technical report should be clearly stated on the cover, occupying 1 to 2 lines. The title should be straightforward and eye-catching, for example: "Technical Report on the Design and Production of Simple Digital Storage Oscilloscope." Sometimes you can add subtitles if necessary. The author, unit, instructor, date, etc. should be indicated under the title. These items can be written according to requirements. For example, if some require the work to participate in the review anonymously, the author's unit cannot be marked.

(4) The focus of the technical report is the main text, which also consumes the most pen and ink. The text part should cover the second and third level headings (or columns).

Take "Technical Report on the Design and Production of Simple Digital Storage Oscilloscope" as an example. It is recommended to design the title like this:

Table of contents (separate page number)

Abstract and key Keyword (Chinese and English)

About 300 to 500 words

Abstract and KeyWord (English)

1. Design tasks (or design topics) and requirements (or technical indicators)

1.1 Design tasks (can be extracted from the design task book)

1.2 Technical indicators (can be extracted from the design task book)

Excerpt from the design brief)

1.3 Problem analysis (if it is a competition topic, you can evaluate the key points, difficulties, and practical value of the topic; if it is an exhibition work, you should explain the innovation)

2． Comparison and demonstration of plans

2.1 Comparison and selection of various plans

Plan one: XXX

Plan two: XXX

Plan Three: Then we discuss the characteristics, ease of implementation, and cost-effectiveness of each plan, analyze the various plans, compare their advantages and disadvantages, and finally explain which plan was chosen for this work and why. The reasons for the final adoption of the solution can be explained from several aspects such as meeting the requirements of technical indicators, cost performance, and current actual conditions (components, equipment). Some systems need to allocate technical indicators and provide corresponding explanations.

2.2 Plan Demonstration

Demonstrate the selected plan and analyze the working principle with the help of illustrations, flow charts, tables, etc. The demonstration should be as detailed as possible, and evaluation should also be done The level reached by this program and the current status of technology at home and abroad. Focus on using mathematics to derive arguments, which is more rigorous.

3． System hardware design

According to the selected overall block diagram, design and select each main circuit respectively. The content should include:

3.1 Overall design of the system (design ideas, design steps), systematic calculations.

3.2 Design of unit circuit (or functional module) and calculation of unit parameters.

3.3 Analysis of the function and working principle of the unit circuit (unit specific circuit diagram).

3.4 Design and implementation of the play part (if the play part is completed, this part should be highlighted, which is a good score).

3.5 Electrical schematic diagram (can be included in the appendix).

4. System software design

Software design includes microcontroller and CPLD.

4.1 Overall program flow chart

4.2 Flow chart of each functional module

4.3 Program list (can be included in the appendix)

5. Assembly of the system

5.1 PCB board diagram (can be included in the appendix)

5.2 Machine structure diagram and process description

5.3 Panel Figures and descriptions of adjustable parts

6. System debugging

Test various indicators according to the requirements of the question, and pay attention to the points for collecting points. When testing each indicator, the definition or meaning of the indicator should be given (such as strict definitions of sensitivity and signal-to-noise ratio). Then test them one by one. 6.1 Circuit test plan (method)

Develop a test plan (method) based on system functions and indicators, usually in the form of a block diagram.

6.2 Testing Instruments

Choose appropriate testing instruments, such as: use a DC voltmeter for DC voltage testing (preferably use a multi-digit meter); choose dozens of voltmeters for AC voltage testing. Use a low-frequency millivolt meter below kilohertz, and use a high-frequency millivolt meter above a few hundred kilohertz; use a frequency meter for frequency testing; use an oscilloscope for waveform testing. Indicate the name, model and test accuracy of the instrument.

6.3 Test results

Test items according to the requirements. Each item must indicate the test conditions, such as input signal, output signal, power supply voltage; test equipment and other needs Indicate the conditions: then list the data (in some cases, multiple measurements need to be made, and this should also be noted); finally, describe the technical indicators achieved, compare them with the technical indicators required by the design, and explain the accuracy of the final test indicators. .

6.4 Test of the performance part

The test of the performance part can be used as a separate item to highlight the key points and increase the weight of the paper.

7. Shortcomings of the system circuit and directions for improvement (or conclusions)

References (separate page number)

Acknowledgments (separate page number)

Appendix (circuit diagram and Relevant design documents)

Appendix 1 General Electrical Schematic

Appendix 2 Printed Circuit Board Diagram

Appendix 3 Program List

Appendix 4 Component List

The titles at all levels written above do not have an introduction part. If you want to add an introduction part, you can put the serial number "1" in front of the introduction, and then the sequence number of the above title will be postponed.

The writing of the above technical report does not specify the requirements for typesetting and font size. If the competition title or exhibition project has regulations on typesetting, it should be completed in accordance with the specified requirements; if there are no requirements on typesetting, it is recommended to follow the electronic format The paper writing requirements of industrial publishing houses are as follows.

Electronic Industry Press paper writing requirements:

(1) Title No. 2 boldface, centered, occupying 3 lines, with 2 lines of space above;

(2) Author, in the center, No. 4 imitates the Song Dynasty;

(3) Author's unit and postal code, small No. 4 italics;

(4) Abstract, keywords, No. 5 italics;

(5) Text size 5 font, 40 lines per page (40 lines/page), 40 words per line (40 characters):

Figure sequence and title fonts are small 5 The number is Song font, centered directly below the figure;

Table sequence and table title font are in small size 5 boldface, centered directly above the table;

The font in the figure or table The text is in Song Dynasty;

The table must be closed, with thick lines for the table frame and thin lines for various lines in the table;

A new table header is required when the table spans two pages. , and put the words "(continued table)" in small 5 black in the upper right corner;

Notes and footnotes are in Song font number 6;

Mathematical formulas are generally arranged in the middle, and pay attention to formulas and letters The writing methods such as italics/uppercase and lowercase should be consistent.

(6) General physical quantity symbols, variables and operators (such as / carry /, o, b, <, etc.) are in italics, vector symbols are in black italics, and complex quantities are marked with "—" directly above the italics. "; Symbols of measurement units, trigonometric functions, abbreviations in formulas, temperature scale symbols, national standards, numerical values, etc. must all be in traditional Chinese.

(7) References, small 5 Song font, format:

Serial number, author, book title, other responsible persons (mainly translators), place of publication, publisher, Year and month of publication