Input parameter FU32 Serial interface
FU33 1 = switch on RTS for RS485 0 = normal RS232 operation
Return parameter FU32 0 = ready
1 = fault
Note
– FEC Compact supports RS485 as from firmware S2.04.
– FEC Standard supports RS485 as from firmware S1.10.
Driver version 1.40 or later is required. SETRTS must be accessed when the interface has been opened.
– HC0x supports RS485 as from firmware S2.03. Driver ver-sion 1.40 or later is required. SETRTS must be accessed when the interface has been opened.
– FST IPC driver SERIALDR version 1.10 or later is required for HC1X and HC2X. SETRTS must be accessed before the interface is opened.
1.11 TCP/IP (driver TCPIP...)
With the TCP/IP driver your PLC/IPC is able to communicate via the Ethernet interface with other PCs or PLC/IPCs by means of the UDP or TCP protocol of the TCP/IP protocol series.
Each TCP/IP participant (host) requires an IP address and IP net mask. The FST TCP/IP driver offers 3 possibilities for carrying out these settings:
– in the driver configuration – by means of module access
– dynamically via the BOOTP/DHCP protocol.
Many local networks use DHCP servers which automatically assign an address to new devices. The FST TCP/IP driver supports such DHCP servers.
Please note
If the IP address is set to 0.0.0.0 (by driver configuration or module access), the BOOTP protocol will automatically be activated. When an IP address is set, the BOOTP protocol is switched off.
If the DHCP server is used, programming for communication between the controllers will take somewhat longer. A specific target IP address is required each time data is sent/received.
The controllers must first exchange these IP addresses with each other.
If the IP address of the controller is assigned by the DHCP server, the address must be read out in the program and then written by broadcast to all connected controllers in a previ-ously agreed flag word. For the communication the target address can then be read from this flag word.
The FST TCP/IP driver supports the following protocol/ser-vices for communication and for tests:
Protocol Port Name Description
ICMP – – Used for PING
UDP 7 echo Returns each character received
UDP 9 discard Discard all data received
UDP 13 daytime Returns date and time as character chain
UDP 19 charge Returns character chain
UDP 37 time Returns time as 32-bit number
UDP 991 CI Command interpreter
UDP 992 CI_EXT Extended command interpreter
UDP 993 CI_BIN Binary exchange of data
UDP 995 EasyIP Data exchange protocol
TCP 7 echo Returns each character received
TCP 9 discard Discard all data received
TCP 13 daytime Returns date and time as character chain
TCP 19 charge Sends characters at regular short intervals
TCP 991 CI Command interpreter (via telnet)
The TCP command interpreter at port 991 can be accessed by a program such as TELNET.
Start TELNET with the parameters, IP number and 991 (i.e. TELNET 10.10.10.1 991). Now it is possible to send com-mands and replies as with the normal RS232 command inter-preter.
Please note
Please note that only one connection at a time is possible.
The connection will be interrupted automatically if no message is sent within 60 seconds.
The command interpreter can also be accessed as follows:
Send a UPD datagram with the CI command (without CR/LF) to the FST controller, port 991. The result will be returned.
The result of DR0 is e.g. =1234. Operation of the extended CI on port 992 is similar, with a small extension. The original command will be returned followed by a zero character and the result, e.g.:
DR0<Zero character>=1234.
The use of the TCP (Telnet) is more suitable for users, while the use of the UDP is intended more for programs for acces-sing FST operands.
Caution
The command Y! must not be entered. This command will stop all programs and drivers. As the TCP/IP is implem-ented as a driver, this will also be stopped.
Please note
The LE commands cannot be accessed via Telnet.
Selecting and parametrizing drivers
If you wish to use TCP/IP in an FST IPC project, you must enter and parametrize the relevant TCP/IP driver in the driver configuration. The drivers of the individual target systems have different names, see the following table:
Driver name Target system
TCPIPCPX – CPX terminal with CPX-FEC TCPIPFEC – FEC Compact (FC34, FC44)
TCPIPFC2 – FEC Standard (FC440, FC560, FC640, FC660) TCPIPDRV – PS1-HC1x with PS1-CP10/CP11/CP14
– PS1-HC1x with PS1-CP12 (8-bit mode) – PS1-HC2x with PS1-CP10/CP11/CP14 – PS1-HC2x with PS1-CP12 (8-bit mode)
TCPIPHC0 – PS1-HC02
TCPIP_15 – PS1-HC1x with PS1-CP15 – PS1-HC2x with PS1-CP15
TCPIPXXX – PS1-HC1x with 2 PS1-CP10/CP11/CP14 – PS1-HC2x with 2 PS1-CP10/CP11/CP14
1.11.1 Configuration of the TCP/IP driver
The following settings are required for the configuration of a TCP/IP driver, depending on the handware used:
Driver settings Description
Target disc drive IPC drive on which the TCP/IP driver can be found or onto which it must be loaded.
IP address The IP address consists of 4 bytes, i.e. 4 numbers between 0 and 255.
The addresses 0.0.0.0 and 255.255.255.255 are not permitted. In a closed-loop local network, consisting only of your controllers and programming PC, you can select the address freely. If your network is connected to your company network, you must usually ask your data processing department for the permitted IP addresses.
Leave the address 0.0.0.0, if it has been assigned with module IP_IP, or dynamically by the BOOTP/DHCP protocol.
IP network mask The mask limits the use of the addresses. A bit of the network mask corresponds to each individual bit of an IP address. If the bit of the network mask is 1, then the bit of the IP addresses between two communicating partners must be identical.
Leave the address 255.255.255.0 if it has been assigned with module IP_MASK, or dynamically by the BOOTP/DHCP protocol.
IP address of the gateway If your controller network is to be connected to another network with the aid of a gateway, the address of this gateway must be entered here.
Leave the address 0.0.0.0, if you are not using a gateway.