1.12 Generating Project Reports¶
Simplifier Manager can automatically generate project reports. The project report contains general information about the project, its settings, and the nodes in it. It also contains automatically calculated safety values and response times within the system, and the checksum for the whole configuration (described in chapter 1.9.1).
Note
A project report can be generated for projects that are not compiled; however, the configuration checksum will not be included.
To generate a report for a project, press the Print Report button in the toolbar, press Ctrl+P, or go to Project → Print report.
Figure 1.51: The print report toolbar button.
This brings up the dialog for generating project reports, where some settings that affect the generated document can be changed.
- Include project errors
- All — include errors, warnings, and messages from the error list.
- Errors only — include only errors.
- Errors and warnings — include errors and warnings (but not messages).
- Double-sided — alternates the page numbers so the document can be printed double-sided. This should only be used if the document should be printed to paper.
- Include logic pages — includes the logic diagrams for each node in the generated report. Uncheck this to omit the logic from the generated report.
- Logic page orientation
- Landscape — the logic pages for each node lie horizontally. This makes it easier to read the report in a PDF reader (such as Adobe Acrobat).
- Portrait — the logic pages for each node stand upright. Select this option if logic pages are not correctly rotated by the printer when being printed to paper.
Figure 1.52: The dialog for generating project reports.
Note
If the project report should be saved as PDF (and not printed to paper), the Double-sided setting and the Logic page orientation setting should be left as they are.
Pressing Generate generates the document and displays it in a new window.
1.12.1 Saving a project report as a PDF file¶
To save a project report as a PDF file, press the Print icon in the top-left corner of the generated document, as shown in Figure 1.53.
This brings up the Windows printer dialog, where Microsoft Print to PDF can be selected as the printer. Selecting this as the printer opens a file dialog where the PDF can be saved. For more information about Microsoft Print to PDF, contact Microsoft support.
Figure 1.53
Note
Printing with Microsoft Print to PDF can take from a couple of seconds to several minutes, depending on the number of pages in the document. To view the printing progress, right-click the printer icon in the Windows taskbar and click Microsoft Print to PDF, as shown in Figure 1.54. This opens the Microsoft Print to PDF printer queue, where the progress can be seen.
Figure 1.54
1.12.2 Printing project reports¶
To print a project report to paper, follow the instructions in chapter 1.12.1, but select a printer instead of Microsoft Print to PDF.
Note
If the printed document does not look right, try saving the report first as a PDF (as described in chapter 1.12.1), and then print the PDF from a PDF viewer application, such as Adobe Acrobat.
1.12.3 Project report content¶
The project report consists of a main page, describing the project in general, and a section for each node in the project.
The footer for each page contains the project name, a page number, and the configuration checksum.
Note
If the checksum is not shown, close the Print document, make sure the project is compiled, and generate a new report.
For each node, a summary is generated, containing a picture of the node (as configured in the node settings), and which I/Os and memories are used.
Figure 1.55: Summary of a node in a project report.
An I/O dependency grid is also generated for each node (shown in Figure 1.56), where the input/output dependencies can be seen. The automatically calculated PFH-d and reaction time values are also stored here.
Figure 1.56: Input/output dependency grid, with calculated PFH-d value, and maximum reaction time for every affecting input.