--- title: Mitsubishi Melsec-L-ASCII (Gen1.3) slug: manufacturing-connect-edge/mitsubishi-melsec-l-ascii-gen13 docTags: createdAt: 2022-05-26T20:56:06.000Z --- Review the following information for setting up and configuring the Mitsubishi Melsec-L-ASCII (Gen1.3) driver. # Manufacturing Connect Edge Compatible Series | Compatibility parameter | Compatible items | | ------------------------------ | ------------------------------------------------------------------------------------ | | **Driver type** | Ethernet | | **Validated devices/series** | [MELSEC-L](https://www.mitsubishielectric.com/fa/products/cnt/plcl/items/index.html) | | **Replaced with Gen 2 driver** | [Mitsubishi Q/L Ethernet](docId\:q3Qc28u89gcRAVwxfSSzM) | 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 :::hint{type="info"} **Note**: Only one connection is allowed per port defined in the PLC. See the steps below to view and edit the open ports on the PLC. ::: If the device is configured for Ethernet access, find its network parameters. Otherwise, follow the steps below. **To configure your device:** 1. Note down the following information and refer to it when needed. **** **Device**: Mitsubishi Melsec L26CPU-PBT When creating a new project file in the software or reading from the PLC, the device model is **L02CPU-P**. **Communication I/F**: Ethernet. Refer to the following figure. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/gRz60BXfAJV2QWrAGE0vE_mitsubishi-melsec-l-binaryreference.png" size="80" width="818" height="873" caption="Reference image of device" position="center" darkWidth="818" darkHeight="873" showCaption="true" indent="2"} 2. Connect the device to your PC using a USB. 3. Launch GXWorks2 Software, and click **Online > Read from PLC**. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/2ZhK2CZSv4E3ZsM4fFtaK_mitsubishi-melsec-l-binary-read.png" size="80" width="657" height="468" caption="Read from PLC option" position="center" darkWidth="657" darkHeight="468" showCaption="true" indent="2"} 4. Select the PLC series. 5. Set up connection, and then click **Connection Test**. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/47Klh3cO5AS_SOAe5ohtj_mitsubishi-melsec-l-binary-connection.png" size="80" width="666" height="481" caption="Connection test option" position="center" darkWidth="666" darkHeight="481" showCaption="true" indent="2"} 6. From the Navigation panel, click **Parameter > PLC Parameter > Build in Ethernet Port Setting**, and set up the parameters. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/CtnzGvEWogGGQSxaK_k_A_mitsubishi-melsec-l-binary-parameters.png" size="80" width="834" height="582" caption="Port setting parameters" position="center" darkWidth="834" darkHeight="582" showCaption="true" indent="2"} 7. From the Navigation panel, click **Connection Destination > connection1**. 8. Click **Find CPU (Build-in Ethernet port) on Network**, then pick up the target device. 9. Click **Connection Test **after set up is complete. ::Image[]{src="https://api.archbee.com/api/optimize/SSUUxKZUk9bFTEPNn_6Zo/BJ6YOw9Y4VGwap5pCpbBM_mitsubishi-melsec-l-binary-destination.png" size="80" width="1032" height="573" caption="Connection test option" position="center" darkWidth="1032" darkHeight="573" showCaption="true" indent="2"} 10. Power off and launch the device again to activate any setting changed in the device. # 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** | Mitsubishi | | **Driver** | Mitsubishi Melsec-L ASCII (Gen1.3) | | **Network Address** | The device address you defined in Step 1 | | **Port** | 5002 | | **Station ID** | 255 | # 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** | **Value Type** | **Address Format** | **Min Address** | **Max Address** | **Description** | | -------- | -------------- | ------------------ | --------------- | --------------- | ----------------------------- | | X | bit | HHHH | 0 | 65536 | Input Relay | | Y | bit | HHHH | 0 | 65536 | Output Relay | | M | bit | DDDDD | 0 | 65535 | Internal Relay | | SM | bit | DDDD | 0 | 2047 | Special Relay | | L | bit | DDDDD | 0 | 32237 | Latch Relay | | F | bit | DDDDD | 0 | 32237 | Annunciator | | V | bit | DDDDD | 0 | 32237 | Edge Relay | | B | bit | DDDDD | 0 | 32237 | Link Relay | | TS | bit | DDDDD | 0 | 25471 | Timer Contact | | TC | bit | DDDDD | 0 | 25471 | Timer Coil | | SS | bit | DDDDD | 0 | 25471 | Retentive Timer Contact | | SC | bit | DDDDD | 0 | 25471 | Retentive Timer Coil | | CS | bit | DDDDD | 0 | 25471 | Counter Contact | | CC | bit | DDDDD | 0 | 25471 | Counter Coil | | SB | bit | DDDDD | 0 | 32237 | Special Link Relay | | S | bit | DDDD | 0 | 8191 | Step relay | | DX | bit | DDDD | 0 | 8191 | Direct Input | | DY | bit | DDDD | 0 | 8191 | Direct Output | | D | word | DDDD | 0 | 9999 | Data Register | | W | word | DDDD | 0 | 8191 | Link Register | | TN | word | DDDDD | 0 | 25471 | Timer Current value | | SN | word | DDDD | 0 | 25471 | Retentive Timer Current value | | CN | word | DDDDD | 0 | 25471 | Counter Current value | | SD | word | DDDD | 0 | 2047 | Special register | | R | word | DDDD | 0 | 9999 | File Register | | ZR | word | DDDDDD | 0 | 999999 | File Register | | Z | word | DD | 0 | 20 | Index Register | ## 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). :::