MELS2-ACTE-P-E 13JF65
SH(NA)-080155-A(0104)MEE
SW2D5C-ACT-E
When exported from Japan, this manual does not require application to the Ministry of Economy, Trade and Industry for service transaction permission.
HEAD OFFICE : MITSUBISHI DENKI BLDG MARUNOUCHI TOKYO 100-8310 TELEX : J24532 CABLE MELCO TOKYO NAGOYA WORKS : 1-14 , YADA-MINAMI 5 , HIGASHI-KU, NAGOYA , JAPAN
MODEL
MODEL CODE
MX Component Version 2 Programming Manual
Before using this product, please read this manual and the relevant manuals introduced in this manual carefully and pay full attention to safety to handle the product correctly.
The instructions given in this manual are concerned with this product. For the safety instructions of the programmable controller system, please read the CPU module user's manual.
In this manual, the safety instructions are ranked as "DANGER" and "CAUTION".
! DANGER
CAUTION
!
Indicates that incorrect handling may cause hazardous conditions, resulting in death or severe injury.
Indicates that incorrect handling may cause hazardous conditions, resulting in medium or slight personal injury or physical damage.
Note that the ! CAUTION level may lead to a serious consequence according to the circumstances.
Always follow the instructions of both levels because they are important to personal safety.
Please save this manual to make it accessible when required and always forward it to the end user.
[Design Instructions]
! DANGER
• When performing data changes or status control from the personal computer to the running PLC, configure up an interlock circuit outside the PLC system to ensure that the whole system will operate safely.
In addition, predetermine corrective actions for the system so that you can take measures against any communication error caused by a cable connection fault or the like in online operations performed from the peripheral device to the PLC.
! CAUTION
• Read the manual carefully before performing the online operations (especially forced output and operating status change) which will be executed with the personal computer connected to the running CPU module.
Not doing so can damage the machine or cause an accident due to misoperation.
Japanese Manual Version SH-080152-A This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent
licenses. Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property
When using Windows NTR Workstation 4.0 and WindowsR 2000 Professional, MX Component may be installed and used only on the administrator's authority.
(2) About Ethernet communication, computer link communication and CPU COM communication on MicrosoftR WindowsR 95 Operating System
(a) Making Ethernet communication using TCP/IP and UDP/IP on WindowsR 95 of the version older than OSR2 will cause a memory leak. When performing continuous operation on WindowsR 95, use WindowR 95 OSR2 or later.
(b) On WindowsR 95, communication using the COM port, e.g. computer link communication or CPU COM communication, will cause a memory leak.
Therefore, do not perform continuous operation.
(3) About installation
(a) When performing overwrite installation, install the software in the folder where it had already been installed.
(b) If you install the MELSEC board driver or GX Developer into the personal computer where MX Component has already been installed, communication using a specific path (e.g. ASCII packet of the AJ71E71) may result in a receive, device number or other error.
If any of these phenomena has occurred, perform overwrite installation of MX Component again.
(4) Precautions for performing installation and uninstallation on a dual boot machine where two different operating systems are installed in a single IBM-PC/AT compatible personal computer
On a dual boot machine having Windows NTR Workstation 4.0 (hereafter referred to as OS1) and WindowsR 95/98 (hereafter referred to as OS2), note the following points when MX Component was installed on OS1 first and MX Component was then installed over the same folder on OS2.
(a) If MX Component is uninstalled first on the OS2 side, uninstallation does not delete the control DLLs and ACT folders, and they remain within the IBM- PC/AT compatible.
To delete the control DLLs and ACT folders, perform uninstallation also on the OS1 side.
(b) If MX Component is uninstalled first on the OS1 side, the control DLLs and ACT folders are deleted.
In this case, MX Component may not operate properly or cannot be uninstalled on the OS2 side.
Install MX Component again on the OS2 side to operate MX Component properly or uninstall it on the OS2 side.
(5) About start menu
When you have uninstalled MX Component, the item may remain in the start menu.
In that case, restart the IBM-PC/AT compatible personal computer.
Therefore, do not set the above functions when making communications with the PLC CPU.
(7) About transmission speed
As the transmission speed of the QCPU(Q mode) and QCPU(A mode), you can set 9600bps, 19200bps, 38400bps, 57600bps or 11520bps.
For the QnACPU of version 9707B or later, you can set the transmission speed of 9600bps, 19200bps or 38400bps.
For the QnACPU of other versions, you can set 9600bps or 19200bps.
The transmission speeds of the ACPU (except A2USHCPU-S1), FXCPU and motion controller CPU are fixed to 9600bps. (The A2USHCPU-S1 may be set to 19200bps.)
(8) About use of the Q4ARCPU
(a) When using the UDP/IP protocol of Ethernet communication, use the Q4ARCPU whose year and month of manufacture is "0012" or later and the QE71 whose function version is B or later.
(b) The duplexing function cannot be used.
(9) Restrictions on use of the FXCPU
(a) For the index registers (Z, V) of the FXCPU, data cannot be written to 2 or more consecutive points using WriteDeviceBlock(). (Data may be written to only one point.)
(b) When the FXCPU is used, access to the TN devices (timer present values) or CN devices (counter present values) is not permitted if the device numbers specified are split across 199 or earlier and 200 or later.
(10) About clock data of the PLC CPU
(a) For the ACPU (including the motion controller CPU), clock data setting may be made only when the PLC CPU is in the STOP status.
For the QCPU (Q mode), QCPU (A mode), QnACPU and FXCPU, clock data setting may be made if the PLC CPU is in the RUN status.
(b) For the A0J2HCPU, A2CCPU and A2CJCPU, setting cannot be made as they do not have the clock function.
(c) For the ACPU, setting can be made independently of whether the clock setting special relay "M9028" is ON or OFF. (Note that the special relay
"M9028" turns OFF after execution.)
For the QCPU (Q mode), QCPU (A mode) and QnACPU, setting can be made independently of whether the clock setting device "SM1028" is ON or OFF.
(d) Among the FXCPUs, setting may be made for only the FX1N (clock built-in), FX1NC (clock built-in), FX1S (clock built-in), FX2N (clock built-in), FX2NC (clock built-in), FX2 (when RTC cassette is fitted) and FX2C (when RTC cassette is fitted).
(e) Note that an error for transfer time will be produced in clock setting.
(b) Set "SW2" of the communications setting switches of the E71 module to OFF (binary).
(12) Simultaneous access when using Q series-compatible Ethernet module
The following conditions should be satisfied when communication is to be made simultaneously from multiple IBM-PC/AT compatibles to the same module using the TCP/IP protocol.
• The Q series-compatible Ethernet module is of function version B or later.
• Using GX Developer Version 6.05F or later, set "MELSOFT connection" in the Ethernet parameter "open system".
(13) About target existence check starting interval 1 of Ethernet module
If close processing (Close) is executed from the IBM-PC/AT compatible, the Ethernet module may not perform close processing (Close).
One of its causes is the open cable.
If open processing (Open) is executed from the IBM-PC/AT compatible with the Ethernet module not performing close processing (Close), open processing (Open) from the IBM-PC/AT compatible is not terminated normally until the Ethernet module makes a target existence check and executes close processing (Close).
If you want to terminate open processing (Open) early from the IBM-PC/AT
compatible, shorten the target existence check starting interval setting of the Ethernet module.
(The target existence check starting interval setting of the Ethernet module defaults to 10 minutes.)
1: It can be set for the E71 of AJ71E71-S3 or later.
(14) Replacement of Ethernet module
If you changed the Ethernet module during Ethernet communication due to debugging, failure or like, the other node (IBM-PC/AT compatible) must be restarted.
(Since the Ethernet addresses (MAC addresses) differ between devices)
(15) Software version of CC-Link master/local module
As the CC-Link master/local module used in CC-Link communication or CC-Link G4 communication(only when the AJ65BT-G4 is used), use the module of software version "N" or later.
The module of software version "M" or earlier will not operate properly.
(16) Software version of CC-Link G4 module
As the CC-Link G4 module used in CC-Link G4 communication(only when the AJ65BT-G4 is used), use the module of software version "D" or later.
The module of software version "C" or earlier will not operate properly.
(17) About relaying from the MELSECNET/10 loaded station
When the module is loaded to the AnNCPU or AnACPU, it is recognized as a MELSECNET(II) module.
When the connected station is the AnNCPU or AnACPU, set the relayed network as MELSECNET(II).
In addition, set the station number to "0" when making access to the control station.
MELSECNET/10.
(b) On any computer link modules other than the UC24 and C24, remote
"PAUSE" operation will result in an error for all connections.
(c) For the QC24, note that the illegal case of specifying the first I/O number of a nonexisting module and reading/writing U \G will not return an error if the software version of the module is "k" or earlier.
(d) In any connection form (direct coupling, relaying) where the target station of the UC24 or C24 is the QnACPU, an error is returned if clock data read/write is executed.
(19) Precautions for USB communication
Frequently disconnecting/reconnecting the USB cable or resetting or powering ON/OFF the PLC CPU during communications with the PLC CPU may cause a communications error which cannot be recovered.
If it is not recovered, completely disconnect the USB cable once and then reconnect it after 5 or more seconds have elapsed.
(If this error occurs at the initial communication after the above operation, the function will be performed properly in and after the second communications.) (20) Precautions for GX Simulator communication
Before executing the monitor utility, communication setting utility or user program, make sure that GX Simulator and GX Developer are operating.
In addition, do not terminate the GX Simulator and GX Developer while the user program is running.
If you do so, you will not be able to terminate the user program normally.
(21) About forced termination of processes during communication
If communication is being made with the same type of control open for multiple processes, forcing one process to be terminated by Task Manager or the like may stop the other processes at the communication function execution area.
(22) About sample programs, test programs and sample sequence programs (a) Sample programs, test programs
The sample programs are attached for your reference to create user programs.
The test programs are attached to conduct communication tests.
Use these programs on your own responsibility.
(b) Sample sequence programs
The sample sequence programs attached to MX Component assume that only an IBM-PC/AT compatible personal computer and Ethernet modules exist in the network.
Depending on your system configuration and parameter settings, the programs must be modified. Make corrections to make the programs optimum for your system.
Also, use the sample sequence programs on your own responsibility.
with the PLC CPU on the lower layer.
AAAA Starting
source
1) QJ71
E71 QCPU (Q mode)
2) QJ71
E71
5) QJ71
E71 4)
QJ71 E71 QCPU (Q mode) 3)
QJ71 E71
1) 2) 3) 4) 5)
Ethernet Ethernet
Without setting
1) Unlocking QJ71E71 password enables access to PLC CPUs in this range.
: Accessible : Inaccessible Enter password to
unlock.
QCPU (Q mode) QCPU
(Q mode)
No. Remote Password With setting (AAAA) Without setting With setting (AAAA) With setting (BBBB)
(24) Resetting PLC CPU during TCP/IP connection setting
If you reset the PLC CPU during TCP/IP connection setting (during opening) using MX Component, a communication or receive error will occur at the time of communication after that. In that case, close the application that uses MX Component and then perform open processing again.
(25) Security of the Internet/intranet when using VBScript
MX Component does not have the Internet/intranet security function.
When you need the security function, make setting on the user side.
(26) Precautions for use of MicrosoftR Access 2000
(a) When you paste the ACT control to an Access 2000 form and double-click the ACT control or choose the custom control in the property, the following error message will appear but this does not affect the operation of ACT control.
(Other error message may appear.)
(b) When you paste the ACT control and display the properties, the property names displayed may be broken.
As this phenomenon occurs for only the property indication, there will be no problem in the property functions.
In such a case, perform operation in the following procedure.
1) Close Excel 2000.
2) Delete *.exd in the Excel 8.0 folder of the temp folders.
3) Restart Excel 2000.
(b) The size of the ACT control can be changed but this does not affect the operation of MX Component.
To restore the size, set the Height and Width properties of ACT control to
"24" again.
(28) Precautions for use of MicrosoftR WindowsR Millennium Edition Operating System
It is not recommended to use MX Component with the "system restoring function" made invalid by the operating system.
If the free space of the system drive becomes less than 200MB, the "system restoring function" is made invalid by the operating system. When using WindowsR Me, reserve a 200MB or more free space for the system drive.
(29) About error at communication start
A communication error may occur within the preset time-out period at a
communication start, e.g. when the communication diagnostic button is pressed, at a monitor start, or at the execution of any function.
These errors are assumed to be detected before a time-out error.
(Example: Connection cable not connected, at PLC power-off) (30) About Ethernet communication
(a) When access is made to the QnACPU, AnUCPU, QCPU (A mode) or motion controller CPU via the E71, the device range is equivalent to that of the AnACPU.
(b) When making access to the PLC CPU through Ethernet communication, the functions may not be executed depending on the PLC CPU status.
1) When the protocol is TCP/IP (target module: E71, QE71)
The functions can be executed only when the communication target PLC CPU is in the RUN mode.
An error is returned if the PLC CPU is in other than the RUN mode.
2) When the protocol is UDP/IP (target module: E71, QE71)
The functions cannot be executed until the communication target PLC CPU is RUN once.
An error is returned if the PLC CPU has not been RUN once.
(c) The communication line is broken if the CPU becomes faulty or the Ethernet module is reset during Ethernet communication (when the protocol is
TCP/IP).
In that case, perform line close processing (Close) and then execute reopen processing (Open).
(Example) When MX Component uses TCP/IP and GX Developer uses UDP/IP
Q series-compatible E71 (Station number: 1) (TCP/IP) station number for MX Component: 2
(UDP/IP) station number for GX Developer : 3 IBM-PC/AT compatible
GX Developer(UDP/IP) MX Component(TCP/IP)
Set different station numbers as the (TCP/IP) station number for MX Component and (UDP/IP) station number for GX Developer. If they are set to the same station number, an error will occur on the Ethernet module side.
(31) About switch settings of E71 and QE71
If the four lower digits of the error code that occurred during Ethernet communication using the E71 or QE71 is not indicated in the E71 or QE71 manual, check the DIP switch (SW2) setting of the E71 or QE71.
If the DIP switch is not set correctly, a difference has occurred in the packet format (ASCII/binary) and therefore the error code returned from the module cannot be recognized correctly.
(32) Instructions for relaying the MELSECNET(II)
When access is made to the QnACPU, AnUCPU, QCPU (A mode) or motion controller CPU via the MELSECNET(II), the device range is equivalent to that of the AnACPU.
(33) Restrictions on use of the FXCPU
(a) When the FXCPU is used, access to the TN devices (timer present values) or CN devices (counter present values) is not permitted if the device numbers specified are split across 199 or earlier and 200 or later.
(b) As the FXCPU does not have a PAUSE switch as the PLC CPU, an error is returned if remote pause is specified in SetCpuStatus.
(c) Note that specifying the first I/O number of a nonexisting module and executing the WriteBuffer( ) method will not return an error.
(d) For the index registers (Z, V) of the FXCPU, data cannot be written to 2 or more consecutive points using WriteDeviceBlock(). (Data may be written to only one point.)
control
Installing MX Component registers the ActUMsg control, ActUWzd control, ActMnet2BD control and ActAFBD control, but do not use them.
(36) Precautions for use of Act(ML)QJ71E71TCP, Act(ML)AJ71QE71TCP and Act(ML)AJ71E71TCP controls
(a) Provide an interval longer than the sequence scan time of the Ethernet module loaded station from when the Open method is executed until the Close method is executed.
(b) Provide an interval of at least 500ms from when the Close method is executed until the Open method is executed again.
(37) Precautions for use of EXCEL VBA
Do not set the page feed preview function in the application that uses EXCEL VBA.
Doing so can cause a memory leak or OS basic operation (file operation, printing or other) fault.
(38) Serial communication function of Q00J/Q00/Q01CPU
When the following conditions are all satisfied, communication between the personal computer and the Q00J/Q00/Q01CPU is made at 9600bps speed.
1) The connected CPU is the Q00CPU or Q01CPU
2) The serial communication function of the connected CPU is valid.
3) The personal computer side baud rate setting differs from the Q00J/Q00/Q01CPU side baud rate setting.
To increase the communication speed, match the personal computer side baud rate with the Q00J/Q00/Q01CPU side baud rate.
(39) Precautions for starting multiple Excel files on WindowsR Me
Note that WindowsR Me has been confirmed to stop if you run multiple Excel files which use many control objects.
This phenomenon is not attributable to this product.
(a) Conditions on which this phenomenon has been confirmed to occur
Graphic driver : Matrox make MGA Mystique display driver
OS : WindowsR Me (English version)
Number of controls pasted to Excel files : A total of 150 or more controls used in the whole BOOK
<Other devices checked by Mitsubishi (reference)>
CPU : PentiumR 166MHz
Memory : 64MB
Hard disk : 8GB (free space 6GB)
driver is not compatible with Windows Me.
(c) How to judge whether the phenomenon is the same or not
After changing the used graphic driver for the standard VGA driver, delete the temporary data (*.emf) left in the temporary folder.
After that, try starting multiple Excel files.
The phenomenon seems to be the same if it does not occur by changing the driver for the standard VGA driver.
(d) Corrective action
If this phenomenon occurs, the temporary data (*.emf) will be left in the temporary folder of the system.
You have to delete the remaining temporary data (*.emf) manually.
The temporary folder of the system is normally in C:\Temp.
After that, take either of the following actions.
1) Use the graphic card and display driver which support WindowsR Me.
2) Reduce the number of control objects pasted to the Excel files.
(40) Precautions for COM communication or TCP/IP communication on ASP page and application 1
If the ASP page opens COM or TCP/IP communication earlier than the
application, communication in the same path cannot be made on the application until the ASP page is closed. Therefore, note the following points.
(a) COM or TCP/IP communication should be opened on the application earlier.
After it has been opened on the application, communication can be made on both the application and ASP page until it is closed.
(b) When COM or TCP/IP communication has been opened on the ASP page, always close the communication.
1 The application indicates any of the user applications created using the MX series and MELSOFT products.
(41) Precautions for connecting personal computer and serial communication module
(a) When QJ71C24-R2 of function version A is used
An MX Component application can use only either of CH1 and CH2.
When the MELSOFT product, such as GX Developer or GOT, is using one channel, the application cannot use the other channel.
When the QJ71C24-R2 of function version B is used, the application can use both channels.
(b) When AJ71QC24-R2 or A1SJ71QC4-R2 is used The MX Component application can use only CH1.
It cannot use CH2.
thoroughly in advance to ensure correct use.
CONTENTS
SAFETY PRECAUTIONS...A- 1 REVISIONS ...A- 2 Operating Instructions ...A- 3 CONTENTS...A-12 About Manuals ...A-15 How to Use This Manual...A-16 Abbreviations and Terms in This Manual...A-17
1 OVERVIEW 1- 1 to 1- 3
1.1 Outline of ACT controls... 1- 1 1.2 ACT control and Function Lists ... 1- 2 1.2.1 ACT control list ... 1- 2 1.2.2 Function list... 1- 3
2 ABOUT THE ACT CONTROLS 2- 1 to 2-16
2.1 Settings Made for Use of the ACT controls... 2- 1 2.1.1 When using MicrosoftR Visual BasicR 6.0... 2- 1 2.1.2 When using MicrosoftR Visual C++R 6.0... 2- 3 2.1.3 When using VBA ... 2- 7 2.1.4 When using VBScript ... 2- 9 2.2 Programming Procedures... 2-10 2.2.1 When using Visual BasicR ... 2-10 2.2.2 When using Visual C++R ... 2-11 2.2.3 When using VBA ... 2-12 2.2.4 When using VBScript ... 2-13 2.3 Device Types... 2-14 2.4 Accessible Devices and Ranges ... 2-16
3 DETAILS OF THE ACT CONTROLS 3- 1 to 3-54
3.1 Details of the ACT Controls ... 3- 1 3.2 Details of the Properties... 3- 2 3.3 Lists of Properties Possessed by the ACT Controls ... 3- 7 3.3.1 ActEasyIF, ActMLEasyIF control ... 3- 8 3.3.2 ActQJ71E71TCP, ActMLQJ71E71TCP control ... 3- 9 3.3.3 ActQJ71E71UDP, ActMLQJ71E71UDP control ... 3-11 3.3.4 ActAJ71QE71TCP, ActMLAJ71QE71TCP control ... 3-13 3.3.5 ActAJ71QE71UDP, ActMLAJ71QE71UDP control ... 3-14
3.3.10 ActQnACPU, ActMLQnACPU control ... 3-20 3.3.11 ActACPU, ActMLACPU control ... 3-21 3.3.12 ActFXCPU, ActMLFXCPU control... 3-22 3.3.13 ActQJ71C24, ActMLQJ71C24 control... 3-23 3.3.14 ActAJ71QC24, ActMLAJ71QC24 control... 3-27 3.3.15 ActAJ71UC24, ActMLAJ71UC24 control ... 3-29 3.3.16 ActAJ71C24, ActMLAJ71C24 control... 3-31 3.3.17 ActQCPUQUSB, ActMLQCPUQUSB control ... 3-33 3.3.18 ActCCG4QnA, ActMLCCG4QnA control ... 3-35 3.3.19 ActCCG4A, ActMLCCG4A control ... 3-36 3.3.20 ActMnet10BD, ActMLMnet10BD control ... 3-37 3.3.21 ActMnetHBD, ActMLMnetHBD control... 3-41 3.3.22 ActCCBD, ActMLCCBD control ... 3-48 3.3.23 ActAnUBD, ActMLAnUBD control ... 3-52 3.3.24 ActLLT, ActMLLLT control ... 3-53 3.3.25 ActQCPUQBus, ActMLQCPUQBus control... 3-54
4 FUNCTIONS 4- 1 to 4-38
4.1 Programming Instructions... 4- 1 4.2 Details of the Functions (Dispatch Interface) ... 4- 3 4.2.1 Open (Communication line opening)... 4- 3 4.2.2 Close (Communication line closing) ... 4- 4 4.2.3 ReadDeviceBlock (Device batch-read) ... 4- 5 4.2.4 WriteDeviceBlock (Device batch-write) ... 4- 7 4.2.5 ReadDeviceRandom (Device random-read)... 4- 9 4.2.6 WriteDeviceRandom (Device random-write)... 4-11 4.2.7 SetDevice (Device data setting) ... 4-13 4.2.8 GetDevice (Device data acquisition) ... 4-14 4.2.9 ReadBuffer (Buffer memory read) ... 4-15 4.2.10 WriteBuffer (Buffer memory write) ... 4-17 4.2.11 GetClockData (Clock data read)... 4-19 4.2.12 SetClockData (Clock data write)... 4-21 4.2.13 GetCpuType (PLC CPU type read) ... 4-23 4.2.14 SetCpuStatus (Remote control)... 4-27 4.2.15 EntryDeviceStatus (Device status monitor registration) ... 4-29 4.2.16 FreeDeviceStatus (Device status monitor deregistration) ... 4-32 4.2.17 OnDeviceStatus (Announces event) ... 4-33 4.3 Details of the Functions (Custom Interface)... 4-34 4.3.1 Open (Communication line opening)... 4-34 4.3.2 Close (Communication line closing) ... 4-34 4.3.3 ReadDeviceBlock (Device batch-read) ... 4-34 4.3.4 WriteDeviceBlock (Device batch-write) ... 4-34 4.3.5 ReadDeviceRandom (Device random-read)... 4-35
4.3.9 ReadBuffer (Buffer memory read) ... 4-36 4.3.10 WriteBuffer (Buffer memory write) ... 4-36 4.3.11 GetClockDSata (Clock data read) ... 4-36 4.3.12 SetClockData (Clock data write)... 4-37 4.3.13 GetCpuType (PLC CPU type read) ... 4-37 4.3.14 SetCpuStatus (Remote control)... 4-37 4.3.15 EntryDeviceStatus (Device status monitor registration) ... 4-38 4.3.16 FreeDeviceStatus (Device status monitor deregistration) ... 4-38 4.3.17 OnDeviceStatus (Announces event) ... 4-38
5 SAMPLE PROGRAMS 5- 1 to 5-14
5.1 Visual BasicR Sample Program ... 5- 1 5.2 Visual C++R Sample Programs ... 5- 3 5.2.1 Dispatch interface... 5- 3 5.2.2 Custom interface ... 5- 5 5.3 VBA Sample Programs... 5- 6 5.3.1 Excel Sample Program ... 5- 6 5.3.2 Access Sample Program ... 5- 8 5.4 VBScript Sample Program... 5-10 5.5 ASP Sample Program... 5-12
6 ERROR CODES 6- 1 to 6-11
6.1 Error Codes Returned by the ACT controls ... 6- 1 6.2 Error Codes Returned by the CPUs, Modules and Network Boards ... 6- 9 6.3 HRESULT Type Error Codes ... 6-10
Related Manuals
Manual Name Manual Number
(Model Code) MX Component Version 2 Operating Manual (Startup)
Provides procedures for installing and uninstalling MX Component and for browsing the operating
manual. (Sold separetely)
IB-080153 (13JU10)
MX Component Version 2 Operating Manual
Gives how to perform setting and operation of each utility on MX Component. (Sold separetely)
SH-080154 (13JU11) Type A70BDE-J71QLP23/A70BDE-J71QLP23GE/A70BDE-J71QBR13/A70BDE-J71QLR23
MELSECNET/10 Interface Board User's Manual(For SW3DNF-MNET10)
Describes the features, specifications, part names and setting of the MELSECNET/10 board, and the installation, uninstallation and others of the driver. (Sold separetely)
IB-0800035 (13JL93)
Type A80BDE-J61BT11 Control & Communication Link System Master/Local Interface Board User's Manual (For SW4DNF-CCLINK-B)
Describes the features, specifications, part names and setting of the CC-Link master board, and the installation, uninstallation and others of the driver. (Sold separetely)
IB-0800175 (13JR28)
Type A80BDE-J61BT13 Control & Communication Link System Local Interface Board User's Manual (For SW4DNF-CCLINK-B)
Describes the features, specifications, part names and setting of the CC-Link local board, and the installation, uninstallation and others of the driver. (Sold separetely)
IB-0800176 (13JR29)
Type A80BDE-A2USH-S1 PLC CPU Board User's Manual (For SW1DNF-ANU-B) Describes the features, specifications, part names and setting of the CPU board, and the installation,
uninstallation and others of the driver. (Sold separetely)
IB-0800174 (13JR27)
MELSECNET/H Interface Board User's Manual(For SW0DNC-MNETH-B)
Describes the features, specifications, part names and setting of the MELSECNET/H board, and the installation, uninstallation and others of the driver. (Sold separetely)
SH-080128 (13JR24)
Note: The MX Component Version 2 Operating Manual (Startup) and MX Component Version 2 Operating Manual are contained in the CD-ROM together with the software package as a set.
When you want to purchase the manual alone, it is optionally available as the printed matter of the manual number (Model code) in the above table.
(1) To know the feature and ACT control lists (Chapter 1)
Chapter 1 gives the ACT control outline and ACT control lists.
(2) To use the ACT controls on Visual BasicR or Visual C++R (Section 2.1)
Section 2.1 provides how to make settings on Visual BasicR and Visual C++R to use the ACT controls.
(3) To know the programming procedure (Section 2.2) Section 2.2 contains programming procedures.
(4) To know the device types to be specified in the functions (Section 2.3) Section 2.3 lists the device types.
(5) To know the details of the ACT controls (Chapter 3) Chapter 3 provides the details of the ACT controls.
Read this chapter when creating a program.
(6) To know the details of the functions (Chapter 4) Chapter 4 gives the details of the functions.
Read this chapter when creating a program.
(7) To know how to use the sample programs (Chapter 5)
Chapter 5 provides the sample programs and how to use them.
Use them as reference when creating a program.
(8) To know the definitions of the error codes (Chapter 6)
Chapter 6 lists the error codes returned by the ACT controls and the error codes returned by the CPUs, modules and network boards.
(9) To know the accessible devices and ranges
The MX Component operating manual contains the accessible devices and ranges.
Refer to the MX Component operating manual.
Generic Term/Abbreviation Description
MX Component
Generic product name for product types SWnD5C-ATC-E and SWnD5C-ACT-EA.
(n denotes version 0 or 2)
-EA denotes a multiple license product.
IBM-PC/AT compatible Abbreviation of the IBM PC/AT or its compatible personal computer PC CPU module Abbreviation of the MELSEC-Q series compatible PC CPU module
(CONTEC CO., LTD. make).
GX Developer Abbreviation of Type SW D5C-GPPW-E/SW D5F-GPPW-E GPP function software package
GX Simulator Abbreviation of Type SW D5C-LLT-E/SW D5F-LLT-E Ladder Logic Test tool function software package
MELSECNET/10 board Abbreviation of Type A70BDE-J71QLP23/A70BDE-J71QLP23GE/A70BDE- J71QBR13/A70BDE-J71QLR23 MELSECNET/10 interface board
MELSECNET/H board Abbreviation of Type Q80BD-J71LP21-25/Q80BD-J71LP21G/Q80BD-J71BR11 MELSECNET/H board
CC-Link board Abbreviation of Type A80BDE-J61BT11 CC-Link system master/local interface board and Type A80BDE-J61BT13 CC-Link interface board
CPU board Abbreviation of Type A80BDE-A2USH-S1 PLC CPU board
AnNCPU
Generic term of the A0J2HCPU, A1SCPU, A1SCPU-S1, A1SCPUC24-R2,
A1SHCPU, A1SJCPU, A1SJHCPU, A1NCPU, A2CCPU, A2CCPUC24, A2CCPUC24- PRF, A2CJCPU, A2NCPU, A2NCPU-S1, A2SCPU, A2SCPU-S1, A2SHCPU,
A2SHCPU-S1, A3NCPU and A1FXCPU
AnACPU Generic term of the A2ACPU, A2ACPU-S1, A2ACPUP21/R21, A2ACPUP21-S1, A3ACPU and A3ACPUP21/R21
AnUCPU Generic term of the A2UCPU, A2UCPU-S1, A2USCPU, A2USCPU-S1, A2ASCPU, A2ASCPU-S1, A2ASCPU-S30, A2USHCPU-S1, A3UCPU and A4UCPU
QnACPU Generic term of the Q2ACPU, Q2ACPU-S1, Q2ASCPU, Q2ASCPU-S1, Q2ASHCPU, Q2ASHCPU-S1, Q3ACPU, Q4ACPU and Q4ARCPU
ACPU Generic term of the AnNCPU, AnACPU and AnUCPU
QCPU (A mode) Generic term of the Q02CPU-A, Q02HCPU-A and Q06HCPU-A
QCPU (Q mode)
Generic term of the Q00JCPU, Q00CPU, Q01CPU, Q02CPU, Q02HCPU, Q06HCPU, Q12HCPU and Q25HCPU
Note that especially when the CPU is indicated as a different model, the Q00JCPU, Q00CPU and Q01CPU are described as the Q00J/Q00/Q01CPU, and the Q02CPU, Q02HCPU, Q06HCPU, Q12HCPU and Q25HCPU as the Q02/Q02H/Q06H/Q12H/
Q25HCPU.
FXCPU Generic term of the FX0, FX0S, FX0N, FX1, FX1N, FX1NC, FX1S, FX2, FX2C, FX2N and FX2NC series
Motion controller CPU Generic term of the A171SHCPU, A172SHCPU, A173UHCPU, A173UHCPU-S1, A273UHCPU and A273UHCPU-S3
PLC CPU Generic term of the QCPU(Q mode), QCPU(A mode), QnACPU, ACPU, FXCPU and motion controller CPU
C24 Generic term of the A1SCPUC24-R2, A1SJ71C24-PRF, A1SJ71C24-R2,
A1SJ71C24-R4, A2CCPUC24, A2CCPUC24-PRF, AJ71C24-S6 and AJ71C24-S8 UC24 Generic term of the AJ71UC24, A1SJ71UC24-R2, A1SJ71UC24-R4 and
A1SJ71UC24-PRF
QC24 Generic term of the AJ71QC24, AJ71QC24-R2, AJ71QC24-R4, A1SJ71QC24-R2 and A1SJ71QC24-R2
QC24N Generic term of the AJ71QC24N, AJ71QC24N-R2, AJ71QC24N-R4, A1SJ71QC24N and A1SJ71QC24N-R2
QC24(N) Generic term of the QC24 and QC24N
Q series-compatible C24 Generic term of the QJ71C24 and QJ71C24-R2
E71 Generic term of the AJ71E71, AJ71E71-S3, A1SJ71E71-B2, A1SJ71E71-B5, A1SJ71E71-B2-S3 and A1SJ71E71-B5-S3
QE71 Generic term of the AJ71QE71, AJ71QE71-B5, A1SJ71QE71-B2 and A1SJ71QE71- B5
Q series-compatible E71 Generic term of the QJ71E71 and QJ71E71-B2
Ethernet module Generic term of the E71, QE71 and Q series-compatible E71
CC-Link G4 module Generic term of the AJ65BT-G4 GPP function peripheral connection module and the AJ65BT-G4-S3 GPP function peripheral connection module
Computer link communication (Serial communication)
Abbreviation of communication made with the PLC CPU using the computer link module
Described as serial communication especially in communication that uses the QC24(N) or Q series-compatible C24.
Ethernet communication Abbreviation of communication made with the PLC CPU using the Ethernet module CPU COM communication Abbreviation of communication made by connecting the IBM-PC/AT compatible to the
RS-232C or RS-422 connector of the PLC CPU
CPU USB communication Abbreviation of communication made by connecting the IBM-PC/AT compatible to the USB connector of the QCPU (Q mode)
MELSECNET/10 communication
Abbreviation of communication made with the PLC CPU using the MELSECNET/10 board
MELSECNET/H communication
Abbreviation of communication made with the PLC CPU using the MELSECNET/H board
CC-Link communication Abbreviation of communication made with the PLC CPU using the CC-Link board CC-Link G4 communication Abbreviation of communication made with the PLC CPU using the CC-Link G4
module
CPU board communication Abbreviation of communication made with the PLC CPU using the CPU board Q series bus communication Abbreviation of communication made with the PLC CPU on the same base using the
PC CPU module
GX Simulator communication Abbreviation of communication made with the GX Simulator
Utility setting type Abbreviation of user program creation using the communication settings utility Program setting type Abbreviation of user program creation without using the communication settings utility ACT controls Generic term of the ActiveX controls offered by MX Component
Microsoft Windows, Microsoft Windows NT, Microsoft Visual Basic and Microsoft Visual C++ are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries.
Ethernet is the registered trademark of Xerox Corporation.
Other company and product names herein may be either trademarks or registered trademarks of their respective owners.
SPREAD
Copyright(C) 1999 Far Point Technologies, Inc.
1 OVERVIEW
This chapter provides the function outline of the ACT controls offered by MX Component.
1.1 Outline of ACT controls
These controls are used to create user programs for communication with a PLC CPU.
This enables the user to make communication without being aware of the hardware and communication protocol on the other end.
GX Developer + GX Simulator (offline debugging) CPU board equivalent
to A2USHCPU-S1
You can make communication with the specified PLC easily without being aware of the communication protocol.
IBM-PC/AT compatible
Computer link communication (Serial communication)
Ethernet communication
CPU COM communication
RS-232C Computer link module
(Serial communication module)
Ethernet board
Ethernet
Ethernet module
RS-232C/RS-422 conversion, RS-232C ACPU, QnACPU, QCPU(Q mode),
QCPU(A mode), FXCPU, motion controller CPU
CPU USB communication USB
QCPU (Q mode)
MELSECNET/10 communication
CC-Link communication
CC-Link G4 communication
CPU board communication
GX Simulator communication
GX Developer: SW5D5C-GPPW-E or later GX Simulator : SW5D5C-LLT-E (Ver. B) or later Must be purchased separately.
MELSECNET/10 module MELSECNET/10
CC-Link
CC-Link module
(Software version "N" or later)
CC-Link G4 module RS-232C/RS-422 conversion
CC-Link (Software version "D" or later)
CC-Link module
(Software version "N" or later) MELSECNET/10
board
CC-Link board MX Component
PC CPU module
MELSECNET/H communication MELSECNET/H MELSECNET/H MELSECNET/H module
board
Q series bus communication On the same base
(Q mode)
1
1.2 ACT control and Function Lists
The following sections give the lists of ACT controls and functions.
1.2.1 ACT control list
The following table lists the ACT controls included in each DLL offered by MX Component.
Included Control Name DLL Name
For VB, VC++, VBA For VBScript Application
ActMulti.DLL ActEasyIF ActMLEasyIF Used to make communication settings easily on the communication settings utility to make communication.
ActQCPUQ ActMLQCPUQ
ActQCPUA ActMLQCPUA
ActQnACPU ActMLQnACPU
ActACPU ActMLACPU
ActPcCom.DLL
ActFXCPU ActMLFXCPU
Used to make communication via the serial port of the corresponding PLC CPU.
ActQJ71C24 ActMLQJ71C24
ActAJ71QC24 ActMLAJ71QC24 ActAJ71UC24 ActMLAJ71UC24 ActComLk.DLL
ActAJ71C24 ActMLAJ71C24
Used to make communication via the computer link module (serial communication module).
ActQJ71E71TCP ActMLQJ71E71TCP ActQJ71E71UDP ActMLQJ71E71UDP ActAJ71QE71TCP ActMLAJ71QE71TCP ActAJ71QE71UDP ActMLAJ71QE71UDP ActAJ71E71TCP ActMLAJ71E71TCP ActEther.DLL
ActAJ71E71UDP ActMLAJ71E71UDP
Used to make communication via the Ethernet module.
ActPcUsb.DLL ActQCPUQUSB ActMLQCPUQUSB Used to make communication via the USB port of the PLC CPU.
ActCCG4QnA ActMLCCG4QnA
ActCcG4.DLL
ActCCG4A ActMLCCG4A
Used to make communication via the CC-Link G4 module.
ActMnet10BD ActMLMnet10BD
ActMnetHBD ActMLMnetHBD
ActCCBD ActMLCCBD
ActBoard.DLL
ActAnUBD ActMLAnUBD
Used to make communication with or via the network board.
ActLLT.DLL ActLLT ActMLLLT Used to make communication with the GX Simulator.
ActPcQbf.DLL ActQCPUQBus ActMLQCPUQBus Used to make Q series bus communication with the PC CPU module.
1
1.2.2 Function list
The following table lists the features of the functions and the functions available for the ACT controls.
(1) Function list
Refer to "CHAPTER 4 FUNCTIONS" for full information on the functions.
Function Name Feature
Open Opens a communication line.
Close Closes a communication line.
ReadDeviceBlock Batch-reads data from devices.
WriteDeviceBlock Batch-writes data to devices.
ReadDeviceRandom Randomly reads data from devices.
WriteDeviceRandom Randomly writes data to devices.
SetDevice Sets one device.
GetDevice Acquires the data of one device.
ReadBuffer Reads data from buffer memory.
WriteBuffer Writes data to buffer memory.
GetClockData Reads clock data from PLC CPU.
SetClockData Writes clock data to PLC CPU.
GetCpuType Reads PLC CPU type.
SetCpuStatus Remote run/stop/pause of PLC CPU.
EntryDeviceStatus Registers device status monitor.
FreeDeviceStatus Deregisters device status monitor.
OnDeviceStatus Announces event.
(2) Functions available for the ACT controls
Refer to "CHAPTER 4 FUNCTIONS" for full information on the functions available for the ACT controls.
2 ABOUT THE ACT CONTROLS
This chapter explains the settings made for use of the ACT controls, the programming procedures, the device types and the accessible ranges.
2.1 Settings Made for Use of the ACT controls
This section describes the setting operation performed for use of the ACT controls.
2.1.1 When using Microsoft
RVisual Basic
R6.0
Perform the following setting operation when using Visual BasicR .
(1) Setting the include file
1) Start Visual BasicR and choose the [Project]-[Add Module]
menu.
2) Choose the <<Existing>> tab and select "ActDefine.bas".
"ActDefine.bas" is stored in <User specified folder>-<Act>-
<Include> at the time of installation.
3) Registering "ActDefine.bas" adds it to Modules.
2
(2) Registering the ACT controls
1) Choose the [Project]-[Components] menu.
2) Select the <<Controls>> tab and choose the DLL which includes the ACT controls you want to use.
3) The ACT controls included in the selected DLL are added to the toolbox.
2
2.1.2 When using Microsoft
RVisual C++
R6.0
Perform the following setting operation when using Visual C++R .
(1) Setting the include file
1) Start Visual C++R and choose the [Tools]-[Options] menu.
2) Choose the <<Directories>> tab and set "Include files" in
"Show directories for:".
3) Double-click the item to be set, and browse the include file.
"ActDefine.H" is stored in <User specified folder>-<Act>-
<Include> at the time of installation.
(2) Registering the ACT control
1) Right-click the form to choose "Insert ActiveX Control".
2) Select the ACT control you want to use.
3) The selected ACT control is pasted to the form.
(3) Adding the member variable
1) Click the form to choose "Class Wizard".
2) When the left dialog box appears, choose the <<Member Variables>> tab.
Choose the member variable adding control ID and click the Add Variable button.
3) When the left screen appears, read the information and click the OK button.
4) Check the class checkbox and click the OK button.
(To the next page.)
(From the previous page)
5) Enter the member variable name and click the OK button.
6) Make sure that the member variable has been registered.
2.1.3 When using VBA
Perform the following setting operation when using VBA.
(1) When using Microsoft
RExcel 2000
1) Boot Excel 2000 and choose the [View]-[Toolbars]-[Control Toolbox] menu.
2) Click the button of the displayed Control Toolbox. As this displays a menu, choose the ACT control you want to use.
3) Paste the selected ACT control to a sheet.
4) Choose the [Tools]-[Macro]-[Visual Basic Editor] menu to start Visual Basic Editor.
5) Perform programming on Visual Basic Editor.
(2) When using Microsoft
RAccess 2000
1) Boot Access 2000 and make the database form active.
2) Click the button of the toolbox. As this displays a menu, choose the ACT control you want to use.
3) Paste the selected ACT control to a sheet.
4) Choose the [Tools]-[Macro]-[Visual Basic Editor] menu to start Visual Basic Editor.
5) Perform programming on Visual Basic Editor.
2.1.4 When using VBScript
Create HTML or ASP using the notepad, commercially available text editor, HTML creation tool or like.
Refer to the commercially available references and so on for the grammars of HTML and ASP.
Also refer to the HTML and ASP sample programs installed in MX Component.
2.2 Programming Procedures
This section gives the procedures of creating a user application.
2.2.1 When using Visual Basic
RWhen using Visual BasicR , create a user application in the following procedure.
Make settings using the utility setting type?
Yes
No
<Utility setting type>
Start the communication settings utility and make communication settings in accordance with the wizard.
Refer to the operating manual.
<Program setting type>
Create a form and paste the ACT controls for corresponding communication.
Set the properties of the pasted ACT controls.
Refer to Section 2.1.1.
Perform programming using the functions offered by the corresponding ACT control.
Refer to the operating manual.
Perform debugging using the PLC monitor utility?
No
Yes
Completion of user application Create a form and paste the ACT control to the form. (ActEasyIF control)
Set the property of the pasted control.
(Set only the logical station number)
Refer to Section 2.1.1.
Refer to the operating manual.
Refer to the operating manual.
Refer to the operating manual (startup).
Install MX Component.
Power on the IBM-PC/AT compatible and start Windows .
Start Visual Basic .
Register the ACT control to Visual Basic .
Refer to Chapters 3, 4.
Start Visual Basic .
Add the ACT controls to Visual Basic .
2.2.2 When using Visual C++
RWhen using Visual C++R , create a user application in the following procedure.
Make settings using the utility setting type?
Yes
No
<Utility setting type>
Start the communication settings utility and make communication settings in accordance with the wizard.
Refer to the operating manual.
<Program setting type>
Create a form and paste the ACT control for corresponding communication.
Set the properties of the pasted ACT control.
Refer to Section 2.1.2.
Perform programming using the functions offered by the corresponding ACT control.
Refer to the operating manual.
Perform debugging using the PLC monitor utility?
No
Yes
Completion of user application
Using Class Wizard, define the pasted ACT control as a dialog member.
Create a form and paste the ACT control to the form. (ActEasyIF control)
Set the property of the pasted control.
(Set only the logical station number)
Refer to Section 2.1.2.
Using Class Wizard, define the pasted ACT control as a dialog member.
Refer to the operating manual.
Refer to the operating manual.
Refer to the operating manual (startup).
Install MX Component.
Power on the IBM-PC/AT compatible and start Windows .
Refer to Chapters 3, 4.
Start Visual C++ .
Register the ACT control to Visual C++ .
Start Visual C++ .
Add the ACT control to Visual C++ .
2.2.3 When using VBA
When using VBA, create a user application in the following procedure.
Make settings using the utility setting type?
Yes
No
<Utility setting type>
Start the communication settings utility and make communication settings in accordance with the wizard.
Refer to the operating manual.
<Program setting type>
Set the properties of the pasted ACT control.
Perform programming using the functions offered by the corresponding ACT control.
Refer to the operating manual.
Perform debugging using the PLC monitor utility?
No
Yes
Completion of user application Set the property of the pasted control.
(Set only the logical station number)
Refer to Section 2.1.3.
Refer to the operating manual.
Refer to the operating manual.
Refer to the operating manual (startup).
Install MX Component.
Power on the IBM-PC/AT compatible and start Windows .
Refer to Chapters 3, 4.
Start Microsoft Excel 2000 or Microsoft Access 2000.
Start Visual Basic Editor and create applications.
Generate the ActEasyIF control so that MX Component may be utilized on VBA.
Refer to Section 2.1.3.
Start Microsoft Excel 2000 or Microsoft Access 2000.
Start Visual Basic Editor and create applications.
Generate the corresponding communication control so that MX Component may be utilized on VBA.
2.2.4 When using VBScript
When using VBScript, create a user application in the following procedure.
Make settings using the utility setting type?
Yes
No
<Utility setting type>
Start the communication settings utility and make communication settings in accordance with the wizard.
Refer to the operating manual.
<Program setting type>
Perform programming using the functions offered by the corresponding ACT control.
Refer to the operating manual.
Perform debugging using the PLC monitor utility?
No
Yes
Completion of user application Set the property of the pasted control.
(Set only the logical station number)
Refer to Section 2.1.4.
Refer to the operating manual.
Refer to the operating manual (startup).
Install MX Component.
Power on the IBM-PC/AT compatible and start Windows .
Refer to Chapters 3, 4.
Create a home page using the text editor and HTML editor.
On the home page, generate the ActMLEasyIF control so that MX Component controls may be utilized using VBScript.
Set the properties of the pasted ACT control.
Refer to the operating manual.
Refer to Section 2.1.4.
Create a home page using the text editor and HTML editor.
On the home page, generate the corresponding communication control so that MX Component controls may be utilized using VBScript.
2.3 Device Types
This section explains the devices that may be specified for the functions.
POINT
(1) For the functions (ReadDeviceBlock, WriteDeviceBlock, ReadDeviceRandom, WriteDeviceRandom, SetDevice and GetDevice), specify the devices in the form of "device name + device number".
For the device numbers, note the differences between octal, decimal and hexadecimal numbers.
(2) When specifying bit devices for ReadDeviceBlock or WriteDeviceBlock, specify the device number as a multiple of 16.
(3) Only the devices indicated in this section are supported.
Do not use unsupported devices.
(1) Common
The following device types are common to all communication paths.
Device Device Name Device No. Type Representation Remarks
Function input FX Decimal Bit —
Function output FY Decimal Bit —
Function register FD Decimal Word 4 words/1 point 1
Special relay SM Decimal Bit —
Special register SD Decimal Word —
Input relay X Hexadecimal Bit Octal for FXCPU
Output relay Y Hexadecimal Bit Octal for FXCPU
Internal relay M Decimal Bit 2
Latch relay L Decimal Bit 2
Annunciator F Decimal Bit —
Edge relay V Decimal Bit —
Link relay B Decimal Bit —
Data register D Decimal Word —
Link register W Hexadecimal Word —
Contact TS Decimal Bit —
Coil TC Decimal Bit —
Timer
Present value TN Decimal Word —
Contact CS Decimal Bit —
Coil CC Decimal Bit —
Counter
Present value CN Decimal Word For FXCPU, 200 or more is 32-bit data.
Contact SS Decimal Bit For ACPU, use timer to specify.
Coil SC Decimal Bit For ACPU, use timer to specify.
Retentive timer
Present value SN Decimal Word For ACPU, use timer to specify.
Link special relay SB Hexadecimal Bit —
Link special register SW Hexadecimal Word —
Step relay S Decimal Bit 2
Bit: Bit device Word: Word device 1: For batch operation, operation is performed continuously in units of one word.
For random operation, only the first one word is read.
2: For the QCPU (A mode) and ACPU, the M, L and S devices have the same regions independently of the device setting in the parameters.
Device Device Name Device No. Type Representation Remarks
Accumulator A Decimal Word 5
Z Decimal Word 5
Index register
V Decimal Word 5
R Decimal Word 3
File register
ZR Decimal Word —
Extended file register ER \R Decimal Word 4
Link input J \X Hexadecimal Bit 4
Link output J \Y Hexadecimal Bit 4
Link relay J \B Hexadecimal Bit 4
Link special relay J \SB Hexadecimal Bit 4
Link register J \W Hexadecimal Bit 4
Direct link 6
Link special register J \SW Hexadecimal Word 4
Special direct buffer
memory 7 9 U \G Hexadecimal
/decimal Word 4, 8
Bit: Bit device Word: Word device 3: To specify the extended file register, describe "\" between the block number part and file register part.
Specifying R specifies R of block No. 0.
Specifying ER0\R returns an error.
Specifying ER \R does not enable extension representation (indirect specification, digit specification).
4: For direct specification, describe "\" between the direct specification part and device specification part.
5: Cannot be used when E71 is relayed.
6: For J , specify the network number.
7: Specify the special module I/O number (hexadecimal) for U , and the buffer memory address (decimal) for G . (Example: Specify "U20\G100" when the special module I/O number is 200H and the buffer memory address is 100.) 8: FXCPU cannot be used.
9: In a multi-QCPU configuration, an error will occur if the shared memory of the host QCPU is specified.
Also, independently of the host or other CPU, an error will occur if write to the shared memory is performed.
(2) For CC-Link communication only
For CC-Link communication only, the devices in the following table can be used when own board access is made. They cannot be used for other communication paths.
Device Device Name Device No. Type Representation Remarks
Special relay SM Bit Decimal Special relay of own board
Special register SD Word Decimal Special register of own board
Link special register (for CC-Link) SB Bit Hexadecimal Link special relay of own board Link special register (for CC-Link) SW Word Hexadecimal Link special register of own board
Remote input X Bit Hexadecimal RX
Remote output Y Bit Hexadecimal RY
Link register W Word Hexadecimal —
Remote register
(write area for CC-Link) WW Word Hexadecimal RWw
Remote register
(read area for CC-Link) WR Word Hexadecimal RWr
Buffer memory ML Word Hexadecimal Buffer memory of own station CC-Link
module
Random access buffer MC Word Hexadecimal Random access buffer in buffer memory of own station CC-Link module
Automatic refresh buffer MF Bit Hexadecimal Automatic refresh buffer of own station CC-Link module
(3) About device extension representation
The following table indicates whether the device extension representations are usable or not for the available CPUs.
They cannot be used with ReadDeviceBlock and WriteDeviceBlock.
When the ActAJ71E71TCP, ActMLAJ71E71TCP, ActAJ71QE71TCP or ActMLAJ71QE71TCP control is used, device expansion representation is unusable.
Target CPU Device Extension
Representation QCPU (Q mode)
QCPU
(A mode) QnACPU ACPU FXCPU Motion
controller CPU Digit specification
(example: K4M0) 2 Bit specification (example: D0.1) 3 Index qualification (example: M100Z0) 4
1
: Usable : Unusable 1: Unusable when QE71 is relayed.
2: FX/FX, DX/DY and T/C/ST (contact, coil) cannot be specified.
3: Z, V, T/C/ST (present value) cannot be specified.
4: FX/FX, DX/DY, T/C/ST (contact, coil), Z and S cannot be specified.
2.4 Accessible Devices and Ranges
Refer to the MX Component operating manual for the accessible devices and ranges for corresponding communication.
3 DETAILS OF THE ACT CONTROLS
This chapter describes the details of the ACT controls, the details of the properties, and the possessed property list.
3.1 Details of the ACT Controls
The following table lists the definitions and usable setting types of the ACT controls.
Control Name
For VB, VC++, VBA For VBScript
Definition
Usable Setting Type ActEasyIF ActMLEasyIF Can communicate with any communication path.
Use the communication settings utility to set the information for communication. U ActQJ71E71TCP ActMLQJ71E71TCP Used for Ethernet communication where the connected module is the Q series-
compatible E71 (TCP/IP communication). P
ActQJ71E71UDP ActMLQJ71E71UDP Used for Ethernet communication where the connected module is the Q series-
compatible E71 (UDP/IP communication). P
ActAJ71QE71TCP ActMLAJ71QE71TCP Used for Ethernet communication where the connected module is the QE71
(TCP/IP communication). P
ActAJ71QE71UDP ActMLAJ71QE71UDP Used for Ethernet communication where the connected module is the QE71
(UDP/IP communication). P
ActAJ71E71TCP ActMLAJ71E71TCP Used for Ethernet communication where the connected module is the E71
(TCP/IP communication). P
ActAJ71E71UDP ActMLAJ71E71UDP Used for Ethernet communication where the connected module is the E71
(UDP/IP communication). P
ActQCPUQ ActMLQCPUQ Used for CPU COM communication where the connected PLC CPU is the
QCPU (Q mode). P
ActQCPUA ActMLQCPUA Used for CPU COM communication where the connected PLC CPU is the
QCPU (A mode). P
ActQnACPU ActMLQnACPU Used for CPU COM communication where the connected PLC CPU is the
QnACPU. P
ActACPU ActMLACPU Used for CPU COM communication where the connected PLC CPU is the
ACPU (including motion controller CPU). P
ActFXCPU ActMLFXCPU Used for CPU COM communication where the connected PLC CPU is the
FXCPU. P
ActQJ71C24 ActMLQJ71C24 Used for computer link communication where the connected module is the Q
series-compatible C24. P
ActAJ71QC24 ActMLAJ71QC24 Used for computer link communication where the connected module is the
QC24(N). P
ActAJ71UC24 ActMLAJ71UC24 Used for computer link communication where the connected module is the UC24. P ActAJ71C24 ActMLAJ71C24 Used for computer link communication where the connected module is the C24. P ActQCPUQUSB ActMLQCPUQUSB Used for USB communication where the connected PLC CPU is the QCPU (Q
mode). P
ActCCG4QnA ActMLCCG4QnA Used for CC-Link G4 communication where the connected module is the
AJ65BT-G4 (QnA mode). P
ActCCG4A ActMLCCG4A Used for CC-Link G4 communication where the connected module is the
AJ65BT-G4 (A mode). P
ActMnet10BD ActMLMnet10BD Used for MELSECNET/10 communication. P
ActMnetHBD ActMLMnetHBD Used for MELSECNET/H communication. P
ActCCBD ActMLCCBD Used for CC-Link communication. P
ActAnUBD ActMLAnUBD Used for CPU board communication. P
ActLLt ActMLLLt Used for GX Simulator communication. P
ActQCPUQBus ActMLQCPUQBus Used for Q series bus communication.
U : Utility setting type P : Program setting type
3
3.2 Details of the Properties
The following tables give the details of the properties which must be set to create a user application.
POINT
When entering a property value directly into the property window of Visual BasicR or Visual C++R , change a character string such as a hexadecimal number or CPU type into a decimal property value.
Property Name (Type) Description
ActLogicalCtationNumber
(LONG) Logical station number set on the communication settings utility.
Specify the network number on the MELSECNET/10(H). (Specify "0x00" when specifying the own station.)
Specify as follows for multidrop connection (via Q series-compatible C24, QJ61BT11).
ActIntelligentPreferenceBit value Description
0x00 Specify the own network.
0x01 Specify another network of multidrop destination.
ActNetworkNumber (LONG)
Specify the station number for MELSECNET/10(H) or CC-Link. (Specify "0x00" when specifying the own station.)
Handled as the own station when access to the CPU of the CPU board is made.
Specify as follows for multidrop connection (via Q series-compatible C24, QJ61BT11).
ActIntelligentPreferenceBit value Description
0x00 Specify the own network.
0x01 Specify another network of multidrop destination.
ActStationNumber (LONG)
ActUnitNumber (LONG)
Specify the module number of the computer link module or the station number when the target is the Q series-compatible intelligent special function module. However, specify "00x0" when setting the QnA series own station (module loaded to the own station CPU).
Invalid when the target is not the computer link communication or Q series-compatible intelligent special function module.
For multidrop link, specify the module number of the target computer link module.
ActConnectUnitNumber (LONG)
Specify the module number of the computer link module, QE71 or Q series-compatible E71.
For multidrop link, specify the module number of the requesting computer link module. For multidrop link via CPU COM communication, however, the module number of the requesting station is not needed (specify "00x0").
Specify "0x00" for other than multidrop link.
For the QE71 and Q series-compatible E71, specify the relay target station number (fixed to
"0x00" for access within the own network).
For access to another network via MELSECNET/10, specify the station number set in the parameter of the connected Ethernet module.
ActIONumber (LONG)
Specify the module I/O number.
For multidrop link or intelligent special function module access, specify the actual I/O number (first I/O number 16) of the target computer link module or intelligent special function module (specify the I/O number of the relayed or requesting station for multidrop link).
Specify "0x3FF" when making access to another station via the own station CPU or network.
