Skip to main content

PNC Design Tutorial

This tutorial designs three PNCs (Partial Network Clusters) for a zonal vehicle and follows how that design is recorded in each PAIO editor, in this order: System editor, Signal, Interface, VFB, Machine Configuration, and the SYSTEM panel. At the end you export the finished model to AUTOSAR ARXML and confirm the PNC mappings in the result.

The finished PNC example topology

The vehicle you build in this tutorial. At the top is the HPC running on the AUTOSAR Adaptive Platform together with its built-in backbone switch, in the middle are three zone ECUs, and at the bottom are ten end ECUs attached to three CAN FD buses.

What You Build​

You express a vehicle-level requirement with three PNCs: "when a door opens, wake only the Comfort network; the park assist network comes alive only in reverse gear; the trailer network runs only while a trailer is attached."

PNCIdentifierWakeup trigger
PNC_Comfort17Door unlock, door open
PNC_ParkAssist18Reverse gear. The HPC requests it.
PNC_Trailer19Trailer attached

Who This Is For​

This tutorial is for engineers who design AUTOSAR vehicle networks with PAIO. It assumes you know roughly what a PNC is but not which PAIO screen takes which input. You do not need a prepared project. Chapter 2 starts from a PAIO window with no project open.

What You Need​

ItemValue
PAIO version0.6.0
AUTOSAR releaseR25-11
Screen1920×1080 or larger. The PNC dialog and the Machine Configuration dialog are wide.
LicenseAn active license and a server connection. Needed only in Chapter 12 (ARXML export).

Chapter Flow​

ChapterWhat you doEditor used
1. Example and Design GoalsDerive three PNCs from the vehicle scenario and identify the five layers a PNC spans—
2. Topology DesignCreate the project and place the nodes, clusters, backbone switch, and coupling portsSystem editor
3. PNC Definitions and Connector PNC PropertiesDefine the three PNCs, enter gateway, wakeup, and filter mask values on the connectors, then fill in the NM cluster and NM node values that carry the PNC bitsSystem editor, PNC dialog, communication cluster dialog
4. Signals, PDUs, Frames, and I-PDU GroupsCreate and map the CAN frames, I-Signal I-PDUs, signals, and NM-PDUs, then create the eight per-PNC Rx/Tx I-PDU Groups and bind them to the PNCsSignal, PNC dialog
5. Interfaces and SOME/IP ServicesCreate the service interfaces and the SOME/IP deployment, then bind the instances to the connectorsInterface, System editor
6. VFB and VFC (PortGroup)Create one composition and its atomic SWCs per node and connect them, then group the SWC ports that take part in a function into a PortGroup (= VFC)VFB
7. PNC Dialog — Per-PNC BindingsBind the VFCs, I-PDU Groups, physical channels, service instances, and wakeup frames for each PNCPNC dialog
8. Reviewing PDU GROUPS, MATRIX, and NM VECTORCross-check the design in the three viewer tabsPNC dialog
9. AP Machine — NM Handles and FunctionGroupsAdd three FunctionGroups and the State Management values to the HPC, then create three NM network handles and map them to the FunctionGroup statesVFB, Machine Configuration
10. PARA Platform Import and PNC Request PortsImport PARA, then attach the ara::nm ports and the handle mappings to the application AAVFB, Interface, Machine Configuration
11. System Editor and ValidationCheck the SYSTEM panels, read the VALIDATION panel, and fix the reported itemsSystem editor, VFB, Interface, VALIDATION panel
12. ARXML ExportExport the finished design and confirm the PNC mappings in the resultEDITOR view, XML editor
AppendixDesign checklist, project file structure, model fragments, and common problems—

Each chapter builds on the result of the previous one, so follow them in order. The Before You Begin section at the start of every chapter states what the model must contain when you start that chapter. There is only one place where you go back. The NM-PDU references in the NM configuration of Chapter 3 can be filled in only after you create the NM-PDUs in Chapter 4, so you return to Chapter 3 once after finishing Chapter 4. Both chapters point this out at the relevant step.

Note. This tutorial starts from a PAIO window with no project open and builds the model from scratch. For repetitive input (42 signals, 14 compositions, 33 PortGroups, and so on), one representative item is shown as a full procedure and the rest are given as value tables. You enter the table items yourself by repeating the same operation. On some screens the number of items in the screenshot differs from the number in the project you build, and those chapters state the difference up front in Before You Begin.

Next Steps​

Start with Example and Design Goals.