The MELSECA driver should support the addressing of a specific CPU.

The MELSECA driver should support the addressing of a specific CPU.

Summary

In the driver configuration dialog of the MELSECA driver it should be possible to address a specific CPU.    

Description

In the driver configuration dialog of the MELSECA driver it should be possible to address a specific CPU.    

Solution

This issue has been addressed by adding a combo box inside the TCP/IP tab of the driver configuration dialog of the MELSECA driver which allows the selection of the CPU types default, CPU1, CPU2, CPU3, CPU4.

Issue Number: 35561
Fixed on Date: 3.12.2015
Versions: 7.20 0 BUILD 24884

    • Related Articles

    • Checklist: Driver(s) cannot establish a reliable communication

      Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

    • PHOENIX32 Driver should support variable addressing via symbolic address

      Summary PHOENIX32 Driver should Support variable addressing via symbolic address in addition to addressing via variable name. DescriptionPHOENIX32 Driver should Support variable addressing via symbolic address in addition to addressing via variable ...

    • Driver configuration cannot be opened and also no new driver can be created.

      If a Service Engine is started as a windows service also zenDrvOpsManager is running as a service. Thus zenDrvOpsManager cannot open a user interface for driver configuration and the Engineering Studio seems frozen. Running a Service Engine as a ...

    • MELSECA: enhancements to meet market needs

      The already existing driver object types Link Relay, Latch Relay and Internal Relay M now support the 16-bit data types INT, UINT and WORD. In addition, these new data types use batch-read and batch-write for the BOOL-based address range to read or ...

    • Checklist: Communication to TwinCat via BeckhoffNG driver

      Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. TwinCAT ADS communication library ...