|
| |
Not possible to communicate with PLC |
QUESTIOIN
The response timeout error is displayed in WWLOGGER, and it is not possible to connect it with PLC.
RESPONSE
Please confirm whether to communicate with the sequencer at the TCP/IP level of OS by using the PING command. There is incompleteness in the network environment or the sequence program when it is not possible to communicate. |
| |
Not possible to connect it with two or more PLCs |
QUESTIOIN
The response error occurs if it connects it with two or more PLCs.
RESPONSE
It is necessary to change the port number respectively when connecting it with two or more PLCs with TCP/IP fullpassive. For instance, please set three port numbers (PLC 1:1025, PLC 2:1026, and PLC 3:1027, etc.) when connecting it with three PLCs. It sets and it is unnecessary for TCP unpassive (Host's port is set to "0"). |
| |
Is there a method of checking the communication of each topic |
QUESTIOIN
Can you see the communication of each topic when communicating with two or more PLCs?
RESPONSE
If system tag "STATUS" and "ERROR" are used, the state of the communication and the error code can be confirmed.
(Ex : "AJ71QE71|PLC1!STATUS")
(Ex : "AJ71QE71|PLC1!ERROR")
(Ex : "AJ71QE71|PLC2!STATUS")
(Ex : "AJ71QE71|PLC2!ERROR")
.
.
.
(Ex : "AJ71QE71|PLC9!STATUS")
(Ex : "AJ71QE71|PLC9!ERROR") |
| |
The initialization error occurs if the InTouch viewer is reactivated |
QUESTIOIN
The initialization error occurs if the InTouch viewer is reactivated
RESPONSE
When TCP/IP is used, the connection is closed every time the viewer of InTouch is ended once. Therefore, there is a possibility that reconnecting is not processed on the sequence program side when "Initialization error" is generated when the viewer is reactivated. Please refer to the sample program of the attachment.
Moreover, it might take time in the TCP/IP environment of WindowsNT so that OS may open the port number when the port is closed once. Please set the host port number of I/O Server to 0 to evade this.
|
| |
Please teach the method of setting NetDDE |
QUESTIOIN
Does the I/O Server support NetDDE?
RESPONSE
I/O Server supports it. The setting of "DDE sharing" is needed to use NetDDE according to the following procedures.
(Because NetDDE can be used by default in latest OS such as Windows XP, it sets and it is unnecessary.)
1. "Run" is selected from the start menu, and "DDEShare.exe" is started.
2. Please select "DDE Share" from "Shares" menu, and push "Add a share" button.
3. Please set it to communicate DDE from the outside as follows.
It is possible to prepare it for the access from the outside by this.
Finally, please start the service of NetDDE on the machine with the execution process of the I/O Server. Afterwards, please access computer name + "AJ71QE71" from the client as an application name. For instance, it is possible to access it by "\\ServerMachine\AJ71QE71".
 |
| |
The exception error occurs when manual operations are linked with VB |
QUESTIOIN
The exception error occurs if DDE Manula Link is done though DDE Automation Link can be done with the system of Microsoft Visual Basic that uses NetDDE.
RESPONSE
When the check on "NetDDE being used" of the Server Setting screen is turning on, DDE Manual Link cannot be used. Please turn off this check box.
 |
| |
Response=38 Error=31 |
QUESTIOIN
The response error occurs, and it is not possible to communicate with the PLC.
RESPONSE
This error occurs when "Data code setting (SW2)" of the dip switch on the PLC side is turning on (ASCII). Please turn off dip switch 2 and use it. |
| |
Response=81 Error=57 |
QUESTIOIN
Response error (Response=81 Error=57) occurs unusually.
RESPONSE
This error occurs when the device out of range is continuously accessed. Please confirm the range of the device that can be used with CPU or unit used.
For instance, the useful range of input device "X" is X0-X1ff for A2USCPU.
access X1f7...
access X1f8...
access X1f9...
access X201...
In this case, because I/O Server does the batch reading to X1f0-X20f, it becomes out of device range, and error code 57 is returned. |
| |
Response=81 Error=58 / Response=82 Error=58 |
QUESTIOIN
Response Error(Response=81 Error=58) is occured.
RESPONSE
This error occurs when the device outside the range is accessed. Please confirm the range of the device that can be used with CPU or unit used.
For instance, the useful range of input device "X" is X0-X1ff for A2USCPU.
access X0...OK
access X100...OK
access X201...NG
Error 58 occurs when X201 is accessed. |
| |
Response=83 Error=55 |
QUESTIOIN
Response Error is occured if it poke to PLC.
RESPONSE
This error occurs when write-protecting on PLC side. Please confirm H/W setting * of the Etherent unit used.
* Dip switch 7 is turning ON for AJ71E71
* Dip switch 3 is turning ON for A1J71E71 |
| |
Send Error (CODE=10054) |
QUESTIOIN
It comes to be able to communicate after a while though the communication is broken off by the error such as following sometimes occurring.
RESPONSE
This error occurs when the connection is cut from the PLC side. For instance, when reset and the power supply of the sequencer are dropped while communicating, it is generated. |
| |
Wait=4,GOT=0,Winsock=10035 |
QUESTIOIN
When UDP/IP is communicated, PING command passes to PLC. However, it is not possible to connect it. I/O Server displays "Winsock=10035".
RESPONSE
This error occurs when IP address or port number set with I/O Server is different from the setting of the PLC side it. Please confirm PLC program. |
| |
Connect Error (ret=10061) |
QUESTIOIN
PING command passes to PLC. However, it is not possible to connect it. I/O Server displays "Connect Error(Port=*** ret=10061)".
RESPONSE
Because the connection remains on the PLC side, it is not possible to connect it from I/O Server. Please correct it to the OPEN waiting state (state of LISN) the port in the PLC program when you use TCP/IP of the MELSEC-A series. Moreover, if the existence confirmation function is not set though it is MELSEC-Q/QnA series, it is likely to become this phenomenon. Please set appropriate TCP/IP referring to the manual of PLC. |
| |
Method of releasing service start setting |
QUESTIOIN
When I/O Server was assumed the service of Windows NT and the start setting was done, it did not stand up.
RESPONSE
When the service setting is done in the environment in which InTouch7.x or more is not installed, and the storage place of the execution file is moved after service is set, it doesn't stand up because the service start of I/O Server uses the function of InTouch7.x.
The service setting is compelling released in this situation, and the method for operation as a usual application is as follows. It is possible to release it only by turning off "Service" setting by the menu of I/O Server usually.
1. Open "Service" of the control panel.
2. Please set it to "Invalidity" pushing "Startup" button with "AJ71QE71_IOServer" selected.
3. Run Registry Editor(REGEDIT.EXE)
4. Delete the entry "NTService" in "\HKEY_LOCAL_MACHINE\SOFTWARE\Wonderware\AJ71QE71_IOServer"
5. It operates as a usual application of I/O Server from the start menu. |
|
Top Page
Introduction
FAQ
Manual/Demo
