|
| |
"With Protocol" or "Without Protocol" |
QUESTIOIN
I am developing a system using Q Series but cannot communicate at all. Ethernet parameters seem to be fine.
RESPONSE
If the network parameter/open setting of GX Developer is set to "Without Protocol," DAServer cannot access to it. Set it to "With Protocol." |
| |
TCP/IP communication problem |
QUESTIOIN
After some TCP/IP communication, I could no longer connect to the PLC unless I reset it.
RESPONSE
This error occurs frequently when a cable is unexpectedly disconnected. TCP connection remains on the PLC. Change the protocol to UDP/IP, implement the heartbeat function, or set the existence confirmation parameter of the PLC appropriately. With A Series, this may occur when the ladder program for port open/close is inappropriate. |
| |
DHCP system |
QUESTIOIN
Does it support DHCP?
RESPONSE
It automatically recognizes the DHCP syste when only one adapter is used and the local IP address is set to "0.0.0.0." |
| |
The port number "5000" of MELSEC-Q/QnA series |
QUESTIOIN
Can I use port 5000 of MELSEC-Q Series without configuring the network parameters?
RESPONSE
Port 5000 is provided as a default "automatic open UDP port." There is no need to configure the network parameters. |
| |
Multiple LAN adaptors |
QUESTIOIN
Can I use multiple LAN adapters?
RESPONSE
If you allocate static IP addresses, you may enter the IP address for each adapter to recognize them. |
| |
Port number format in GX Developer |
QUESTIOIN
Cannot communicate though PING responds normally
RESPONSE
IP address is configured correctly, but the PLC has not set the port to wait open. Please take not that port number of DAServer is in a decimal value, but the PLC (GX Developer) sets it in hexadecimal. |
| |
Error on accessing "word access to a bit device (M100.H16, etc.)" |
QUESTIOIN
Attempting a word access to a bit device (M100.H16, etc.) results in an error.
RESPONSE
For a successful word access (ASCII, HEX, etc.) to a bit device (M/B/X, etc.), the start device number must be a multiple of 16. For example, you can access "M32.H3," but accessing "M30.A10" will cause an error. |
| |
DAServer's configuration file |
QUESTIOIN
I would like to back up DAServer. Where is the configuration file?
RESPONSE
Back up "MelsecEthernet.AAcfg," which is under the Install directory. |
| |
Tag name diagnostics |
QUESTIOIN
I got a wrong device number error. How can you tell which tag is causing the error?
RESPONSE
You can check the list of added tags from SMC's diagnostics screen. Check the tags that are in red. |
| |
MELSEC-A series Ethernet connection |
QUESTIOIN
Accessing "W1000" with A Series Ethernet Unit AJ71E71N results in an error.
RESPONSE
A Series Ethernet Unit can only access the device range of AnACPU. It cannot access beyond B/W1000 and D6144. |
| |
Accessing the internal device of the station on MELSECNET |
QUESTIOIN
Can I access the internal device of other stations on MELSECNET via the stations connected to the Ethernet?
RESPONSE
Since transient transmission is supported, you can access any station on MELSECNET simply by specifying the station number. However, since transient transmission interrupts the regular cyclic transmission of MELSECNET, response will be slower. Refer to MELSECNET Reference Manual for more details. |
| |
Run as Windows service program |
QUESTIOIN
Can I run DAServer as a Windows service program?
RESPONSE
You can configure the service startup from DAServer manager in SMC. With a service program, the program is already running even before you log in. |
| |
MELSEC Multiple CPU System |
QUESTIOIN
Does it support MELSEC multiple CPU system?
RESPONSE
When you use multiple Q Series CPUs, you can use the Ethernet unit to access any of them. |
| |
System Tag |
QUESTIOIN
How can I tell from the client if DAServer is communicating correctly?
RESPONSE
System Tag "$SYS$Status" is set to "1" during the communication and "0" when the communication stops. You can monitor this tag to see if a communication error has occurred. |
| |
Import / Export |
QUESTIOIN
Can I import/export tags?
RESPONSE
You can import/export tags from the "Device Item" tab on the PLC Configuration screen of SMC's DAService manager. |
| |
Server Accessing Name |
QUESTIOIN
When you access from InTouch by DDE, what will the application name be?
RESPONSE
Specify "MelsecEthernet" as the application name. ProgID to connect by OPC will be "Takebishi.MelsecEthernet.1." |
| |
Inprocess / Outprocess |
QUESTIOIN
I get an error when I connect from multiple OPC clients.
RESPONSE
DAServer runs as InPorcServer by default when CoCreateInstance is called. When you connect from multiple clients, it must be executed as OutPorcServer. Configure service startup or activate DAServer before you connect the clients. You can avoid this error by specifying CLSCTX_LOCAL_SERVER as the third argument. If you specify CLSCTX_ALL, DAServer will run as InPorcServer, so you can only connect from one client. In this case, you cannot activate DAServer from SMC ahead of time. |
|
Top Page
Datasheet
FAQ
Manual/Demo
