Documentation Home Page eHS Toolbox Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.

Generic Machine Conf File Writing Conventions - efs_cpuConfFileConventionsGenericMachine

Writing Convention

In order to use the feature of autoconfiguration for communications port inside the Generic Machines block, the *.conf file used must follow a set of writing conventions:

Machine description must follow the template: MACHINE : Replacing MACHINE with one of the supported machine type: PMSMVDQ, PMSMSH or IM_SM.

Machine port description should finish with the the following suffixes :

  • PMSMVDQ1_In for DataIn port            (Must be a DataIn port)
  • PMSMVDQ1_Config for config LoadIn port      (Must be a LoadIn port)
  • PMSMVDQ1_Out for DataOut port          (Must be a DataOut port)


Multiple machines must be distinguished by the Slot, Section and Subsection fields : To identify the different communication ports of a machine block we need to know which eHS those machines are connected to. Here's an example of four machines connected to two different eHS

  1. DataIn1 PMSMVDQ1_In 5 A 1 NA -1 32
  2. DataIn2 PMSMVDQ2_In 5 A 2 NA -1 32
  3. DataIn3 PMSMVDQ3_In 6 A 1 NA -1 32
  4. DataIn4 PMSMVDQ4_In 6 A 2 NA -1 32

All ports with Slot and Section 5 A will be associated to the first eHS and all ports with Slot and Section 6 A will be associated to the second eHS. The Subsection number identifies to which extra input port of eHS the machine is connected to in the firmware model.


Table of Contents

Example

The following section is an example of a *.conf file following the writing conventions and the result of using autoconfiguration inside the Generic Machine General tab.

The resulting Communications tab for the Dual PMSM Variable VDQ Machine Core 1, notice the the communication port numbers set accordingly to the *.conf file.

The resulting Communications tab for the Quad Generic Machine Model Machine Core 1, notice the communication port numbers set accordingly to the *.conf file.


If you require more information, please contact https://www.opal-rt.com/contact-technical-support/.

OPAL-RT TECHNOLOGIES, Inc. | 1751, rue Richardson, bureau 1060 | Montréal, Québec Canada H3K 1G6 | opal-rt.com | +1 514-935-2323
Follow OPAL-RT: LinkedIn | Facebook | YouTube | X/Twitter