zenon Process Gateway ICCP sends zenon and not ICCP name variables
Summary
zenon Process Gateway ICCP sends zenon and not ICCP name variables
Description
zenon Process Gateway ICCP sends zenon and not ICCP name variables
Solution
Now uses configured ICCP name on communication level.
Information
A possible workarround was to use the ICCP Name as the zenon name for the variables.
Issue Number: 31017
Fixed on Date: 13.12.2013
Versions: 7.10 0 BUILD 9356
Related Articles
zenon Changesets Excel
Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in CSV format ...
zenon Changesets CSV
Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in as Excel ...
Checklist: Process Gateway cannot establish a reliable communication
Time estimate: 45 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] ...
Checklist: Process Gateway cannot start
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. Checklist usage: #. [Quick hints] ...
While type mismatches zenon Process Gateway ICCP-TASE.2 as client on data set reception is corrupting value of not mismatched variables
Summary zenon Process Gateway ICCP TASE.2 is mismatching received values - all (or some) of zenon variables linked in ICCP-client. It transfers to the Runtime values of another received data points or random. It happens only when by one (or more) ...