For Live data, Historical data logging, Datalogging to MQTT broker, and Alarms & Notifications you'll need to set up a data source and add variables. This article shows you how to do this for communication via Mitsubishi's MELSEC.

For help and solutions with issues, see MELSEC data source issues and solutions.

• Prepare the machine
• Add a data source
• Add variables
• Live data, Historical data logging, Alarms & Notifications

• Remove a data source

Prepare the machine

The machine needs to be prepared to enable communication.

Add a data source

The machine will need to be added as a MELSEC data source.

1. Go to Fleet Manager > Devices and click on your device name.
2. In the left menu, go to Data sources.
   • Tip: You can switch between the Card view , with useful data source information at a glance, and the List view . For more information, see Data sources overview FAQ.
3. Click onAdd data source and select MELSEC.
4. Enter the requested information (details below) and click on Add.

   Field	Description
   Name	Enter a name for the data source.
   Identifier	The identifier is entered automatically and ensures that every data source remains unique, even if they share the same name.
   IP address	Enter the IP address of your machine. Leave empty for localhost, if you're using an IXagent, or if you're adding this data source for a Docker container on a SecureEdge Pro.
   Port	Enter the Port No. that you configured in your machine. In GX Works 2 this is called Host Station Port Number.
   MELSEC Serie	The Mitsubishi MELSEC series to which your machine belongs. If you're unsure, please consult the Mitsubishi website. "QnUCPU" is Mitsubishi's notation for every MELSEC-Q Series machine with CPU type Q..U..CPU, for example Q04UDVCPU or Q26UDEHCPU.
   Transport protocol	Select the same protocol that you configured in your machine (TCP/UDP).
   Network No. and PC No.	If configured in the machine, enter the correct settings here. If not, leave the default settings. Applicable when using a custom MELSEC machine network.
   Request destination module I/O No. and Request destination module station No.	If configured in the machine, enter the correct settings here. If not, leave the default settings. Applicable when using a specific I/O module for communication.
   Authentication type	The Ethernet connection in the machine may be password protected. Enter the password or leave it empty if no password is configured on the machine.
   Polling sleep time	The edge gateway will continuously request data from the machine. This then enables you to log aggregated values, like the average value or the maximum value that occurred, and to trigger alarms when certain conditions are met. The polling sleep time is the time that the edge gateway waits before asking data again, after it just received data from the machine. A polling sleep time of 100ms is recommended to minimize CPU load on the edge gateway and machine. In the rare case that you are experiencing a high CPU load on the machine, you can increase this setting to reduce the load further. Make sure it's shorter than your shortest logging interval to prevent missing data.
   Error grace period	Supported hardware SecureEdge and SecureEdge Pro, firmware 5.0 and up (upgrade) IXrouter3, firmware 3.25 and up (upgrade) IXrouter2 (unsupported) In rare situations, mainly during the startup period of a PLC, the PLC might already accept communication attempts from the edge gateway, but it may not be fully ready yet. It might then return errors or 0-values instead of the actual values. This may result in no data (missing data) or incorrect data being read. The error grace period can be configured to bridge this moment and only start polling variables after the configured time, granting the PLC sufficient time to fully start up and maintaining the reliability of the machine data. An error grace period of 0 seconds (Off) is recommended. In the rare case that you are experiencing no data (missing data) or incorrect data during startup you can increase this setting to bridge that period.
   Use custom broker	Leave this unchecked unless you are following instructions for Datalogging to MQTT broker.

Add variables

Once you've added a data source, you can start adding variables.

5. The Variables tab of your data source should have automatically opened.
   • If it didn't: Go to Fleet Manager > Devices, click on your device name, go to Data sources, click on your data source, and go to the Variables tab.
6. Click onAdd variable.
7. Enter the requested information (details below) and click on Add.

   Field	Description
   Name	Enter a name for the variable.
   Identifier	The identifier is entered automatically and ensures that every variable remains unique, even if they share the same name.
   Type	Select the variable's data type (bool, int, float, etc).
   Device type	Select the variable's device type (register type).
   Device No.	Enter the variable's address. The address notation (decimal or hexadecimal) depends on the selected device type. Device type Device No. notation SM - Special relay Decimal SD - Special register Decimal X - Input Hexadecimal Y - Output Hexadecimal M - Internal relay Decimal L - Latch relay Decimal F - Annunciator Decimal V - Edge relay Decimal B - Link relay Hexadecimal D - Data register Decimal W - Link register Hexadecimal TS - Timer (Contact) Decimal TC - Time (Coil) Decimal TN - Timer (Current Value) Decimal TS - Retentive timer (Contact) Decimal TC - Retentive timer (Coil) Decimal SN - Retentivetimer (Current Value) Decimal CS - Counter (Contact) Decimal CC - Counter (Coil) Decimal CN - Counter (Current Value) Decimal SB - Link special relay Hexadecimal SW - Link special register Hexadecimal DX - Direct access input Hexadecimal DY - Direct access output Hexadecimal Z - Index register Decimal R - Block switching method Decimal ZR - Serial number access method Hexadecimal
   Factor	Multiplies the value. Leave empty if the data type is boolean. For information on where this factor is and isn't used, see How to use factors in Live Data and Historical data.
   Unit	Displayed behind the value (e.g. kg).

8. Repeat the previous steps for every variable you want to add or click Import from CSV-file near the top right corner to add variables in bulk instead.
   • The structure of the CSV file is explained here: Import variables: CSV file structure.
   • Using Export to CSV-file and Import from CSV-file enables you to easily copy variables from one device to another device. Alternatively, you can also use device templates.

You have now made the changes in the IXON Cloud, but these are not yet active in your device. You will need to push your changes to your device for them to take effect.

9. Click on Push device config in the top right corner.

Live data, Historical data logging, Alarms & Notifications

Now that the data source and variables have been set up, you can continue below.

10. Click below to continue in the feature specific articles.
    • Live data
    • Historical data logging
    • Datalogging to MQTT broker
    • Alarms & Notifications

Remove a data source

Deleting a data source is permanent and cannot be undone. All logged data that is linked to this data source or its variables will also be permanently removed.

1. Go to Fleet Manager > Devices and click on your device name.
2. In the left menu, go to Data sources.
3. Click on the data source you wish to remove.
4. In the top right, open More optionsand select Remove data source.