DEVICE DRIVER | MITSUBISHI

This highly configurable Mitsubishi IIoT Adapter for CNCnetPDM enables you to acquire and output all items that can be read from Mitsubishi CNC controllers on machines other than from Citizen or Mazak. It also allows you to write data to these devices by your own applications on a remote PC for instance to set or change parameters or common variables. Here you can find a list of sections with all possible commands that you can use with the driver: Sections

CNCnetPDM Mitsubishi IoT Interfaces

Output example

DOWNLOAD | LICENSING | SETUP CNCNETPDM | SETUP MITSUBISHI | READ DATA | WRITE DATA | ADJUST ITEMS | TIPS | TROUBLESHOOTING | ADAPTED CONTROLLERS | UPGRADE DRIVER

The IIoT Adapter enables to dynamically define an own set of items for data acquisition (up to 30) that can be enabled and disabled on a per machine basis by an INI file that is automatically created for each machine configured. This INI file also allows you to define your own tag names for acquired data.

• Make sure that you have a network connection from your PC to the machine and get data, use the MitsubishiM70M80 utility to do so. In case you use a firewall on your PC or company network please also open TCP Port 683 there.
• To directly read/write data from/to machines with Mitsubishi controllers connected to CNCnetPDM with your applications you can use our free Open Source Client (C-Sharp)

FIG 1: Mitsubishi M80 CNC Operator Panel

DOWNLOAD DRIVER

• Note: This device driver mandatorily requires CNCnetPDM Version 8.0.0.0 or higher.

LICENSING

This device driver requires the most recent version of CNCnetPDM and also works with a free license. However, in this mode you only get output for the first item configured in your INI file. With any other license you are able to output the result of up to 30 functions per reading cycle, see licensing for details.

SETUP CNCNETPDM

• Download CNCnetPDM and install it as described in the quick-start-guide.
• Download the Mitsubishi driver, extract all content of mitsubishi_dll.zip into the folder where you have CNCnetPDM installed.
• Edit CNCnetPDM.ini and add a new device as described in the quick start guide point 6. If you already have an entry in section [RS232] for a machine with a Mitsubishi controller you can simply copy and paste this line and change its content. You may comment out the previous entry by prepending a semicolon ‘;’ if it’s the same machine.
• Change the line as follows:

FIG 2:    Configure device Mitsubishi in CNCnetPDM.ini

For Mitsubishi controllers the following 3 parameters are important

1. Right to the IP Address of the controller enter number 683 (=port)
2. Right to the DNS Hostname of your machine enter the Mitsubishi number as configured, see section ‘MITSUBISHI SETUP’.
3. Change the driver name to mitsubishi.dll

[RS232]
1 = 1000;19200;8;N;1;MITSUBISHI #1;192.168.1.100;683;0;mitsubishi;1;0;none;none;0;mitsubishi.dll

MITSUBISHI SETUP

• Extract all contents of mitsubishi_dll.zip to the directory where CNCnetPDM is installed.
• In this folder open file melcfg.ini with a text editor and scroll down to section [HOSTS] (1).
• melcfg.ini comes with predefined entries for up to 54 machines, every line in section [HOSTS] contains Mitsubishi machine number (the number after TCP), IP Address and TCP Port of a single machine.
• Replace the default IP Address 192.168.1.100 with the IP Address of your controller (2), note down the machine number (3) and save the file. If, for example, the IP Address of your first controller is 192.168.1.2 the line should look like
  TCP1=192.168.1.2,683

FIG 4: Adjust melcfg.ini file

READ DATA

• Start CNCnetPDM, foreground program is sufficient (Start thread)
• CNCnetPDM automatically copies the original mitsubishi.dll and appends the machine number as configured in the INI file, e.g. mitsubishi_1000.dll for machine 1000.
• In addition an INI file with the same name is created by the device driver, e.g. mitsubishi_1000.ini for your first machine.
• Double click CNCnetControl, if your device number is 1000 and the device name is MITSUBISHI #1 the output should be similar to the one below:

FIG 5: CNCnetControl (Mitsubishi)

The machine (1) shows up as connected (2) which is good. On the right side (3) you see the acquired data:

• The line starting with O contains most of items defined in the INI file of the device (e.g. Mitsubishi_1000.ini). If you didn’t change the ini file you get something like the following:

1000 12/05/2023 02:04:32 PM O STATN| 5| STATT| Error| MODEN| 2| MODET| ****| PRGCU| 1| PRGMN| 4712| SEQCU| 1| FEEDR| 0| SPSPD| 0| ALMST| 0| TOOL1| 0| TOOL2| 0| ALMTX| No alarm|  10000000002

Every item has a tag name followed by its tag value. All tag value pairs are delimited by pipe ‘|’ symbols. This allows CNCnetPDM to create OPC UA or MTConnect output or a database record for every item.

With an unmodified INI file the initial items are:

FIG 6:    IDs, names and description of items

• Note: If you already have a machine specific INI file you can add the following sections to acquire alarm data and read/write common variable 100 (Part System 1):

[12]
Partsystem = 1
Axisflag = 0
ParameterNumber = 100
Datatype = T_DOUBLE
Command = M_SSEC_CMVRS_DAT(x)
Active = 1
Name = CV100
Comment = Common variable #100 Part System 1
Output section = 3

[13]
Partsystem = 1
Axisflag = 0
ParameterNumber = 10
Datatype = T_ALM
Command = M_SSEC_CUR_ALARMS
Active = 1
Name = ERR
Comment = Current alarm messages Part System 1
Output section = 2

WRITE DATA

This device driver allows you to create items or change data at the controller by using writable commands with note ‘RW’ or ‘W’ in column R/W of their documentation f.i. common variable 100 - 199 M_SSEC_CMVRS_DAT(x).

• Note: Please use our diagnostic tool to read & write data first to check if a writing operation succeeds.

To write to a controller for security reasons a section with the respective command has to exist in your machine INI file. With an unmodified machine INI file you can use command 12 (Reads common variable 100) for testing. For commands with an (x) parameter the driver allows to write data for any valid parameter number e.g. with M_SSEC_CMVRS_DAT(x) you can set all common variables from 100 - 199.

The most simple way to test writing operations is to use CNCnetControl:

To change the value of common variable 100 click on the machine (1) in the left area followed by button [Command] (2). In the dialog window enter Number 12 (3). As command text use 1|0|100|4.055 (4). Items in the command text are part system, axis number, parameter number and new parameter value delimited by pipe ‘|’ characters. Clicking on [OK] (5) executes the command. If successful the output of tag CV100 changes to the new value.

FIG 7:    Set new value for common variable 100 with CNCnetControl

You can also write data by using the CNCnetPDM MTConnect API with your own applications ( see Free Open Source Client C#) or the MTConnect Agent Tester. In this case commands have to be input by using the following format (for the above example):

* device|1000|command|12|1|0|100|4.055

• * device|1000 = Select device number 1000
• command|12 = Command number 12
• 1|0|100|4.055 = Part system 1, axis flag 0, parameter 100, new value 4.055

All items have to be delimited by using a pipe ‘|’ character.

Results of all writing operations are written to the devices log file log_devicenr_date.txt in subfolder \log of the CNCnetPDM directory.

ADJUST ITEMS

This device driver also enables you to dynamically select, group, enable or disable items and change their names. The INI file (e.g. mitsubishi_1000.ini) automatically created by the device driver for every machine contains sections that allow you to control its behavior.

Section [GENERAL] contains information about global parameters used by the driver on startup, usually there’s no need to change the preset values for Axisflag and System. Commands defines the number of commands you’d like to execute, maximum value = 30.

Numeric section [0] defines how you’d like to detect if the controller is accessible. If this command does not succeed the driver assumes that the controller is not accessible. In this case all other commands are not executed.

Description of a numeric section:

FIG 8: Description of INI file section (Mitsubishi)

To change commands, switch items on or off or alter its name while CNCnetPDM is running open the ini file with a text editor, make the desired changes and save the file. To apply the changes immediately you can click on the machine in CNCnetControl on the left side followed by clicking buttons ‘Close’ and ‘Open’ above the section ‘Devices’.

TIPS

• An overview of all sections that lead to pages that contain commands belonging to the specific section can be found here.
• It is recommended to start with simple commands in sections like Operation Status or CNC Information.
• If you enter a wrong data type for output of data in the INI file you may get data but the values are incorrect.
• If you want to add additional items first adjust the number of commands in section [GENERAL]. Then, copy and paste the last numeric section and adjust the section number and it’s content. 

TROUBLESHOOTING

• If the machine shows a red icon, state disconnected and you get just output E = 0 the machine is not reachable at all. This has nothing to do with the Mitsubishi API, it’s a network issue, DNS Hostname or IP Address is wrong.
• If the machine also shows a red icon, state disconnected but you just get output E = 1 the machine is reachable by 'Ping' but the API does not respond to commands, check your Mitsubishi setup (melcfg.ini) and the parameters used in CNCnetPDM.ini (esp. Port number). You can also use the tool MitsubishiM70M80.exe to check if the machine replies to commands.
• If you do not get any of the preconfigured items please make sure that CollectOrders is set to 1 in section [General] of CNCnetPDM.ini. If you forced items to sections 2 or 3 set CollectQuality and CollectFeeder to 1.
• If specific items are not acquired check first with MitsubishiM70M80.exe that you get output. Also make sure that the numeric section of the item in the device drivers ini file is activated and has an entry for ‘Name’, inactive or items with empty names are not acquired.  

CONTROLLERS

The program was tested and works in production environments with the following controllers:

Series M800 M80

Machining center & Lathe system

• M850W
• M830W
• M850S
• M830S
• M80W
• M80 TypeA
• M80 TypeB

Series E80 C80

Machining center & Lathe system

• E80 TypeA
• E80 TypeB
• C80 TypeA
• C80 TypeB

Series M70

Machining center & Lathe system

• FCA70P-2A
• FCA70P-4A
• FCA70P-2B
• FCA70P-4B

Series M700

• 720M
• 730M
• 750M
• 720L
• 730L
• 750L

Series C6/C64 Series

• C6L
• C6T
• C64M
• C64L
• C64T

Series C70

• M system
• L system

Series M70V

Machining Center & Lathe system

• TypeB
• TypeA

Series M700V

Machining Center & Lathe system

• M720VS
• M730VS
• M750VS
• M720VW
• M730VW
• M750VW

UPGRADE DRIVER

If you already have a previous version of the driver installed and would like to upgrade to the most recent version proceed as follows:

1. Stop any CNCnetPDM background service or foreground program that uses the device driver.
2. Backup (copy) melcfg.ini to a folder of your choice.
3. Extract all content of mitsubishi_dll.zip into the folder where you have CNCnetPDM installed, overwrite the existing files.
4. Delete all mitsubishi_NNNN.dll (NNNN = machine number) files. If you already have created adapted INI files for specific devices do NOT delete the mitsubishi_NNNN.ini files.
5. Adjust the controller IP addresses in the new melcfg.ini template (recommended) OR restore (copy) melcfg.ini from your backup folder to the directory where you have CNCnetPDM installed, overwrite the existing file.
6. After restarting CNCnetPDM upgraded device driver versions for all machines are automatically created.

• Setup and usage of Mitsubishi Device Driver (PDF 270KB)