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

• Related Articles

• 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 ...

• 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] ...

• CTI driver has high CPU load in combination with slower communication processor/ PLC

  Summary The CTI driver has a unusual high CPU load when it communicates to specific (older versions, slower,TI 5x5 Plcs) The CPU load is arround 40-60%. Description The CTI driver has a unusual high CPU load when it communicates to specific (older ...

• MELSECA driver: Blockwrite does not work

  Summary With enabeled Blockwrite the MELSECA driver fails to write variable values even writing a single variable does not work Description With enabeled Blockwrite the MELSECA driver fails to write variable values even writing a single variable does ...

• MELSECA driver: String variables show the value of the 1st (offset) string variable if displayed on the same screen

  Summary MELSECA driver: If string variables with consecutive addressing (offsets) are displayed on the same screen they all show the value of the 1st addressed (offset variable). On different screens the variables display the correct and respective ...