--- title: Profinet Acyclic slug: manufacturing-connect-edge/profinet-acyclic docTags: createdAt: 2022-06-30T20:01:55.000Z --- Review the following information for setting up and configuring the Profinet Acyclic driver. # Manufacturing Connect Edge Compatible Series | Compatibility parameter | Compatible items | | ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Driver type** | Ethernet | | **Validated devices by PROFINET profiles** | [PROFIdrive](https://www.profinet.com/profinet-explained/profidrive) - [Siemens SINAMICS variable frequency drive](https://www.siemens.com/global/en/products/drives/sinamics.html)
[PROFIenergy ](https://www.profinet.com/profinet-explained/profienergy)- [Siemens SIMOCODE pro](https://www.siemens.com/us/en/products/automation/industrial-controls/sirius/sirius-monitor/simocode.html) | To set up and configure this device in Manufacturing Connect Edge, you will need to do the following: - Step 1: Set up and Configure the PLC Device - Step 2: Set up the PLC Device in Manufacturing Connect Edge DeviceHub - Step 3: Configure the List of Registers # Step 1: Set up and Configure the PLC Device If the device is configured for Ethernet access, find its network parameters. Otherwise, use software on your computer to configure the device for Ethernet access. # Step 2: Set up the PLC Device in Manufacturing Connect Edge DeviceHub Configure the following parameters when you [Connect a Device](docId\:RFVIJdxz7DBAd8mwbismA) with this driver. Update default values to the specific set up of your device. | Parameter | Value | | ---------------------- | ---------------------------------------- | | **Type** | Profinet | | **Driver** | Profinet Acyclic | | **Network Address** | The device address you defined in Step 1 | | **Network Port ** | 34964 | | **Network Interface** | eth0 | | **Vendor ID** | 128 | | **Device ID** | 1 | | **Slot Number** | 0 | | **Subslot** | 1 | | **Api** | 0 | Refer to the following table for a description of the registers. The driver also supports two optional [application profiles](https://www.profinet.com/profinet-explained/profinet-application-profiles): `PROFIdrive` and `PROFIenergy`. | Register Type | Description | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Generic Data Records | Reads Generic Data records. Enter the record index as the tag address. | | I\&M Records | Reads Identification & Maintenance records. Enter the I\&M record index as the tag address. | | Profile: PROFIdrive | PROFIdrive is the standard profile for drive technology in the connection of drives and encoders via PROFINET IO. Enter the PROFIdrive PNU parameter as the tag address. | | Profile: PROFIenergy | PROFIenergy is a manufacturer- and device-neutral profile for energy management with PROFINET. Enter the PROFIenergy measurement ID as the tag address. | :::hint{type="info"} This driver only supports reading tag values. ::: # Step 3: Configure the List of Registers When you [Add Tags](docId\:iOaNZd2AwqnkuppgeE3Eh) to the connected device, refer to the following register table and tag parameters. Refer to the following additional resources: - [Device and Tag Metadata Use Case](docId\:f-B720niVlLBer44RfyHN) - [Tag Formula Variables](docId\:PWd-7P-kZjXkt_pYAwAOw) ## Register Table |
**Name** | **Data Type** | **Address Format in Manufacturing Connect Edge** | **Min Address** | **Max Address** | **Description** | | -------------- | ------------- | ------------------------------------------------ | --------------- | --------------- | --------------- | | PNU | auto | DDDD | 0 | 65535 | Parameters | ## Tag Parameters - **Name**: Select a register name from the drop-down list. Available options depend on the names in the register table. - **Value Type**: Select a data type from the drop-down list. Available options depend on the register name selected. - **Polling Interval**: Enter a value in seconds. This determines how often the tag should poll the register for data. - **Tag Name**: Enter a name for the tag. - **Description** (Optional): Enter a description for the tag. - **Address**: Enter a tag address. The value must in the decimal format within the allowed min/max range. Omit the leading zeros. The device might use the decimal (D), hexadecimal (H), or octal (O) address format. See the Register Table at the bottom of the dialog box. For Bit tags, append the bit address without the bit separator. The lowercase letters in the address format indicate how many digits you should enter in the Bit address. - **Count**: Enter the number of register values to read. A count higher than 1 will generate an array of values from the address value configured and respective subsequent address values. - **Tag Formula**: Enter a formula for the tag to process the generated data. Two variables are permitted: `value` (current tag value) and `timestamp` (current tag UNIX time in milliseconds). The following math functions are available: - sin - cos - sqrt - tan - power: power(`x`) performs the operation `10^x`. - log: log(`x`) is the natural logarithm (the logarithm is in base `e`). - exp: exp(`x`) performs the operation `e^x`. - **Only Publish on Change of Value**: Select the checkbox to publish NATS messages only when the *value *parameter changes to a new one value. *Change of Value* only applies to boolean, numeric (such as int or float), and simple string data types. It does not apply to complex types, such as JSON or array. Poll-once topics are not affected by *Change of Value* settings. These topics will still only see a single message. - **Meta Data**: Metadata summarizes basic information about data. This feature allows you to define key-value pair data for the device output payload later on. It can then be used to find, use, and reuse particular instances of data. :::hint{type="info"} **Note**: If you use special characters in meta data key names, the special characters are replaced with underscore characters in the payload. This can cause two key names to be combined into one. For example, configuring the key names a\*\*b and a&\&b will cause only one key name to be created (a\_\_b). :::