FC9Y-B1278 FC5A SERIES User’s Manual Web Server CPU Module
SAFETY PRECAUTIONS • Read this user’s manual to make sure of correct operation before starting installation, wiring, operation, maintenance, and inspection of the Web server CPU module. • All Web server CPU modules are manufactured under IDEC’s rigorous quality control system, but users must add a backup or failsafe provision to the control system when using the Web server CPU module in applications where heavy damage or personal injury may be caused in case the Web server CPU module should fail.
Revision History Date March, 2011 Manual No. B-1278(0) June, 2011 B-1278(1) January, 2013 B-1278(2) PREFACE-2 Description First print • Error code 8 is added in the error code table for EMAIL instruction. • Notes for devices of EMAIL and PING instructions are updated. • Descriptions for pass-through over Modbus RTU is added in chapter 7. • Wrong descriptions are revised.
About This Manual This user’s manual primarily describes entire functions, installation, and programming of the Web server CPU modules. Also included are powerful communications of the Web server CPU module and troubleshooting procedures. Chapter 1: General Information General information about features, brief description on special functions, and various system setup configurations for communication for the Web server CPU module.
RELATED MANUALS The following manuals related to the FC5A series MicroSmart are available. Refer to them in conjunction with this manual. Type No.
TABLE OF CONTENTS Revision History ............................................................................................................................... Preface-2 About This Manual .......................................................................................................................... Preface-3 CHAPTER 1: General Information About the Web Server CPU Module .......................................................................................................... 1-1 Features....
TABLE OF CONTENTS Maximum Quantity of Applicable Expansion Modules ............................................................................3-15 Allowable Total Internal Current Draw ........................................................................................3-15 Internal Current Draw by Expansion Modules .............................................................................3-15 Terminal Connection ........................................................................................
TABLE OF CONTENTS CHAPTER 6: Remote Host List Applications ............................................................................................................................................... 6-1 Description of Functions............................................................................................................................ 6-1 Programming WindLDR .............................................................................................................................
TABLE OF CONTENTS CHAPTER 12: Web Server Web Server Overview...............................................................................................................................12-1 Folder Structure .......................................................................................................................................12-1 Programming WindLDR............................................................................................................................
1: GENERAL INFORMATION Introduction This chapter describes general information about the powerful capabilities of the FC5A series Web server CPU modules and the system setups to use the Web server CPU module in various ways of communication. About the Web Server CPU Module The FC5A series MICROSmart PentraTM Web server CPU module is a slim-type micro programmable logic controller that has built-in Ethernet and USB ports.
1: GENERAL INFORMATION Features Logic Engine® The Web server CPU module features the Logic Engine® to achieve fast execution of instructions — 0.056 μs for a basic instruction (LOD) and 0.167 μs for an advanced instruction (MOV). This improves real-time performance for executing the user program. Basic Functions The Web server CPU module is fully equipped with functions as a programmable logic controller to achieve the best system.
1: GENERAL INFORMATION HMI Module An optional HMI module can be installed on the HMI base module mounted next to the Web server CPU module. The HMI module makes it possible to manipulate the RAM data in the CPU module without using WindLDR. Communication Adapter and Module The Web server CPU module can be used with an optional RS232C or RS485 communication module to add communication port 2.
1: GENERAL INFORMATION System Setup Example To use the Web server CPU module, the network environment must be arranged. Setup examples and important notes are shown below.
1: GENERAL INFORMATION Operation Examples Operation examples for the various functions of the Web server CPU module are described.
1: GENERAL INFORMATION Send E-mail DĂŝů ƐĞƌǀĞƌ DĂŝů ƐĞŶƚ ĨƌŽŵ W> DĂŝů ƌĞĐĞŝǀĞĚ DĂŝů ƐĞŶƚ ƚŽ ĞdžƚĞƌŶĂů W EĞƚǁŽƌŬ DĂŝů ƐĞŶƚ ƚŽ ŵĂŝů ƐĞƌǀĞƌ DĂŝů ƌĞĐĞŝǀĞĚ WŽƌƚĂďůĞ ƚĞƌŵŝŶĂů tĞď ^ĞƌǀĞƌ Wh DŽĚƵůĞ džƚĞƌŶĂů W E-mails can be sent from the Web server CPU module. Data register values can be embedded in the e-mail message body. The Web server CPU module can send e-mails periodically or when any event occurs.
2: MODULE SPECIFICATIONS Introduction This chapter describes part names and specifications of Web server CPU modules. Variety of modules such as I/O modules and analog I/O modules are available in Web server CPU modules. For details about each module, see FC5A User’s Manual Basic Volume. CPU Modules (Slim Type Web Server) Slim type Web server CPU modules are available in 12-I/O type and have 8 input and 4 output terminals.
2: MODULE SPECIFICATIONS )JOHFE -JE &YQBOTJPO $POOFDUPS 4FBM 64# 1PSU $PWFS %VNNZ $BSUSJEHF (1) Power Supply Terminals Connect power supply to these terminals. Power voltage 24V DC. (2) I/O Terminal Block For connecting input and output signals. (3) Expansion Connector For connecting digital and analog I/O modules. (4) Power LED (PWR) Turns on when power is supplied to the CPU module. (5) Run LED (RUN) Turns on when the CPU module is executing the user program.
2: MODULE SPECIFICATIONS (18) Communication Connector For connecting an optional communication module or HMI base module. Remove the connector cover before connecting a module. (19) Hinged Lid Open the lid to gain access to the cartridge connectors 1 and 2, analog potentiometer, and analog voltage input connector. (20) Dummy Cartridge Remove the dummy cartridge when using an optional memory cartridge or clock cartridge. (21) USB Port Cover Open this cover to use the USB port.
2: MODULE SPECIFICATIONS General Specifications Normal Operating Conditions CPU Module Operating Temperature Storage Temperature Relative Humidity Pollution Degree Degree of Protection Corrosion Immunity Altitude Vibration Resistance Shock Resistance ESD Immunity Weight FC5A-D12K1E FC5A-D12S1E 0 to 55°C (operating ambient temperature) –25 to +70°C 10 to 95% (non-condensing, operating and storage humidity) 2 (IEC 60664-1) IP20 (IEC 60529) Atmosphere free from corrosive gases Operation: 0 to 2,000m (0 to 6,5
2: MODULE SPECIFICATIONS Function Specifications CPU Module Specifications CPU Module Program Capacity Expandable I/O Modules Input I/O Points Output User Program Storage Backup Duration Backup Data Battery RAM Backup Charging Time Battery Life Replaceability Control System Instruction Words Basic instruction Processing Time END processing Internal Relay Shift Register Timer Counter Data Register Expansion Data Register Extra Data Register Input Filter Catch Input Interrupt Input Self-diagnostic Function
2: MODULE SPECIFICATIONS Analog Voltage Input Pulse Output Communication Port Cartridge Connector Quantity: 1 point Input voltage range: 0 to 10V DC Input impedance: Approx. 100 kΩ Data range: 0 to 255 (8 bits) 3 points Maximum frequency: 100 kHz Communication connector for port 2 2 points for connecting a memory cartridge (32KB, 64KB, or 128KB) and a clock cartridge Note 1: Select program capacity of 62,400 bytes or 127,800 bytes.
2: MODULE SPECIFICATIONS Memory Cartridge (Option) Memory Type EEPROM 32 KB, 64 KB, 128 KB The maximum program capacity depends on the CPU module. When using the 32 KB memory cartridge on the slim type CPU module, the maximum program capacity is limited to 30,000 bytes. CPU module WindLDR One user program can be stored on one memory cartridge. (Note 1) When a memory cartridge is installed, the user program on the memory cartridge is executed.
2: MODULE SPECIFICATIONS DC Input Specifications (Slim Type Web Server) FC5A-D12K1E FC5A-D12S1E CPU Module Input Points and Common Lines Terminal Arrangement Rated Input Voltage Input Voltage Range Rated Input Current Input Impedance Turn ON Time Turn OFF Time Isolation Input Type External Load for I/O Interconnection Signal Determination Method Effect of Improper Input Connection Cable Length Connector on Mother Board Connector Insertion/Removal Durability 8 points in 1 common line See CPU Module Termina
2: MODULE SPECIFICATIONS Transistor Sink and Source Output Specifications (Slim Type Web Server) FC5A-D12K1E FC5A-D12S1E CPU Module FC5A-D12K1E: Sink output FC5A-D12S1E: Source output 4 points in 1 common line See CPU Module Terminal Arrangement on page 2-10. 24V DC 20.4 to 28.8V DC 0.3A per output point 1A per common line 1V maximum (voltage between COM and output terminals when output is on) 1A maximum 0.1 mA maximum 39V±1V 8W L/R = 10 ms (28.
2: MODULE SPECIFICATIONS CPU Module Terminal Arrangement and I/O Wiring Diagrams (Slim Type Web Server) FC5A-D12K1E (12-I/O Transistor Sink High-speed Output Type CPU Module) Applicable Terminal Blocks: FC5A-PMTK16EP (supplied with the CPU module) Terminal No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Input/Output I0 I1 I2 I3 I4 I5 I6 I7 COM COM Q0 Q1 Q2 Q3 COM(-) +V 2-wire Sensor + – NPN – + 24V DC Load Fuse L L L L – + • Outputs Q0 to Q3 are transistor sink outputs.
2: MODULE SPECIFICATIONS Dimensions CPU Modules (Slim Type Web Server) FC5A-D12K1E, FC5A-D12S1E NN XIFO UIF DMBNQ JT QVMMFE PVU All dimensions in mm.
2: MODULE SPECIFICATIONS 2-12 WEB SERVER CPU MODULE USER’S MANUAL FC9Y-B1278
3: INSTALLATION AND WIRING Introduction This chapter describes the methods and precautions for installing and wiring Web server CPU modules. Before starting installation and wiring, be sure to read “Safety Precautions” in the beginning of this manual and understand precautions described under Warning and Caution. Warning • Turn off the power to the Web server CPU module before starting installation, removal, wiring, maintenance, and inspection of the Web server CPU module.
3: INSTALLATION AND WIRING Assembling Modules Caution • Assemble Web server CPU modules together before mounting the modules onto a DIN rail. Attempt to assemble modules on a DIN rail may cause damage to the modules. • Turn off the power to the Web server CPU module before assembling the modules. Failure to turn power off may cause electrical shocks. The following example demonstrates the procedure for assembling the all-in-one 24-I/O type CPU module and an I/O module together.
3: INSTALLATION AND WIRING Installing the HMI Module Caution • Turn off the power to the Web server CPU module before installing or removing the HMI module to prevent electrical shocks. • Do not touch the connector pins with hand, otherwise electrostatic discharge may damage the internal elements. The optional HMI module (FC4A-PH1) can mount on any all-in-one type CPU module, and also on the HMI base module mounted next to any slim type CPU module.
3: INSTALLATION AND WIRING Removing the HMI Module Caution • Turn off the power to the Web server CPU module before installing or removing the HMI module to prevent electrical shocks. • Do not touch the connector pins with hand, otherwise electrostatic discharge may damage the internal elements. This section describes the procedures for removing the HMI module from the optional HMI base module mounted next to any slim type CPU module. 1. Insert a thin flat screwdriver (ø3.
3: INSTALLATION AND WIRING Securing USB Extension Cable Using Cable Tie When FC5A-D12K1E/S1E is installed in a control panel, it is possible to extend the USB Mini-B port of the PLC to the panel surface using a USB extension cable (Note 1). When using the USB extension cable, it is recommended that the USB extension cable is secured to the USB port cover of the PLC using a cable tie (Note 2) so that the USB extension cable does not come loose from the USB port of the PLC.
3: INSTALLATION AND WIRING Mounting on DIN Rail Caution • Install the Web server CPU modules according to instructions described in this user’s manual. Improper installation will result in falling, failure, or malfunction of the Web server CPU module. • Mount the Web server CPU modules on a 35-mm-wide DIN rail or a panel surface. Applicable DIN rail: IDEC’s BAA1000PN10 or BAP1000PN10 (1000mm/39.4” long) 1. Fasten the DIN rail to a panel using screws firmly. 2.
3: INSTALLATION AND WIRING Removing the Direct Mounting Strip 1. Insert a flat screwdriver under the latch of the direct mounting strip to release the latch (A). (A) (B) 2. Pull out the direct mounting strip (B). Mounting Hole Layout for Direct Mounting on Panel Surface Make mounting holes of ø4.3 mm as shown below and use M4 screws (6 or 8 mm long) to mount the Web server CPU modules on the panel surface. FC5A-D12K1E, FC5A-D12S1E ¡ All dimensions in mm.
3: INSTALLATION AND WIRING Installation in Control Panel The Web server CPU modules are designed for installation in a cabinet. Do not install the Web server CPU modules outside a cabinet. The environment for using the Web server CPU module is “Pollution degree 2.” Use the Web server CPU module in environments of pollution degree 2 (according to IEC 60664-1).
3: INSTALLATION AND WIRING Removing the Terminal Blocks Caution • Turn off the power to the Web server CPU module before installing or removing the terminal blocks to prevent electrical shocks. • Use the correct procedures to remove the terminal blocks, otherwise the terminal blocks may be damaged. This section describes the procedures for removing the terminal blocks from slim type CPU modules FC5A-D16RK1, FC5AD16RS1, FC5A-D12K1E and FC5A-D12S1E. 1.
3: INSTALLATION AND WIRING Removing the Communication Connector Cover Caution • When using a thin screwdriver to pull out the communication connector cover, insert the screwdriver carefully and do not damage the electronic parts inside the CPU module. • When first pushing in the communication connector cover to break, take care not to injure your finger.
3: INSTALLATION AND WIRING Input Wiring Caution • Separate the input wiring from the output line, power line, and motor line. • Use proper wires for input wiring. All-in-one type CPU modules: UL1015 AWG22 or UL1007 AWG18 Slim type CPU and I/O modules: UL1015 AWG22 Output Wiring Caution • If output relays or transistors in the Web Server CPU or output modules should fail, outputs may remain on or off.
3: INSTALLATION AND WIRING Contact Protection Circuit for Relay and Transistor Outputs Depending on the load, a protection circuit may be needed for the relay output of the Web server CPU modules. Choose a protection circuit from A through D shown below according to the power supply and connect the protection circuit to the outside of the CPU or relay output module.
3: INSTALLATION AND WIRING Power Supply Caution • Use a power supply of the rated value. Use of a wrong power supply may cause fire hazard. • The allowable power voltage range for the slim type Web server CPU module, expansion interface module FC5A-EXM2, and expansion interface slave module FC5A-EXM1S is 20.4 to 26.4V DC. Do not use the Web server CPU module on any other voltage.
3: INSTALLATION AND WIRING Precautions for Connecting Communication Devices When connecting communication devices to the Web server CPU module, take possible external noise sources into consideration.
3: INSTALLATION AND WIRING Maximum Quantity of Applicable Expansion Modules This section describes precautions for installing the expansion RS232C communication module in connection with the internal current draw by other expansion modules. The all-in-one 24-I/O type CPU module (except 12V DC power type) can mount a maximum of three expansion RS232C communication modules. The slim type CPU module can mount a maximum of five expansion RS232C communication modules.
3: INSTALLATION AND WIRING Example: Installing five expansion RS232C communication modules to the slim type CPU module Module Type No. Quantity Internal Current Draw (5V DC) Total Internal Current Draw 5 85 mA 425 mA 7 2 — — 455 mA 30 mA FC5A-SIF2 (Earlier than V200) Maximum Applicable Expansion Modules (Slim CPU) Balance Expansion RS232C Communication Module In the above example, two more expansion modules can be added, with a maximum total current draw of 30 mA.
3: INSTALLATION AND WIRING Terminal Connection • Make sure that the operating conditions and environments are within the specification values. Caution • Be sure to connect the grounding wire to a proper ground, otherwise electrical shocks may be caused. • Do not touch live terminals, otherwise electrical shocks may be caused. • Do not touch terminals immediately after power is turned off, otherwise electrical shocks may be caused.
3: INSTALLATION AND WIRING 3-18 WEB SERVER CPU MODULE USER’S MANUAL FC9Y-B1278
4: OPERATION BASICS Introduction This chapter describes general information about setting up the basic Web server CPU module system for programming, starting and stopping Web server CPU module operation, and introduces simple operating procedures from creating a user program using WindLDR on a PC to monitoring the Web server CPU module operation. Start by setting up the maintenance environment. Then, connect a PC that has WindLDR installed and the Web server CPU module with a USB cable.
4: OPERATION BASICS PLC Selection Before programming a user program on WindLDR, select the PLC type. 1. Select Configuration from the WindLDR menu bar, then select PLC Type. The PLC Selection dialog box appears. PLC Selection Option CPU Module Type No.
4: OPERATION BASICS Communication Setup Procedure This section describes the procedure to set up communication between a PC and the PLC, using an example. WindLDR is used to configure the network settings of the Web server CPU module and monitor the status of the CPU module using an Ethernet connection. USB Connection 1. Select Online from the WindLDR menu bar, then select Set Up. The Communication Settings dialog box appears. 2. Select USB and click OK button. 3.
4: OPERATION BASICS 6. The Download dialog box appears. Click OK button. 7. After the download has been completed successfully, select Online from the WindLDR menu bar, and then click Monitor. 8. Select Online from the WindLDR menu bar, and then click Batch. 9. The Batch Monitor dialog box appears. Confirm that the IP address for confirured in step 4 is shown in D8330 to D8333 correctly. Ethernet Connection 10. Exit Monitor, then select Online from the WindLDR menu bar, and then click Set Up. 11.
4: OPERATION BASICS 12. The IP Address Settings dialog box appears. Click on the New button. 13. The Input IP Address dialog box appears. Enter the IP address configured in step 4 and click OK button. 14. Select Online from the WindLDR menu bar, and then click Monitor. The IP Address Settings dialog box appears. Click OK button. 15. Select Online from the WindLDR menu bar, and then click Status. 16. The PLC Status dialog box appears.
4: OPERATION BASICS Start/Stop Operation This section describes operations to start and stop the Web server CPU module and to use the stop and reset inputs. Caution • Make sure of safety before starting and stopping the Web server CPU module. Incorrect operation on the Web server CPU module may cause machine damage or accidents.
4: OPERATION BASICS Start/Stop Operation Using the Power Supply The Web server CPU module can be started and stopped by turning power on and off. 1. Power up the Web server CPU module to start operation. See “Introduction” on page 4-1. 2. If the Web server CPU module does not start, check that start control special internal relay M8000 is on using WindLDR. If M8000 is off, turn it on. See “Start/Stop Operation Using WindLDR” on page 4-6. 3. Turn power on and off to start and stop operation.
4: OPERATION BASICS Simple Operation This section describes how to edit a simple program using WindLDR on a PC, transfer the program from the PC to the Web server CPU module, run the program, and monitor the operation on the WindLDR screen. Connect the Web server CPU module to the PC as described in “Introduction” on page 4-1. Note: See the Basic Volume, “Chapter 7: Basic Instructions” (page 7-1) for details on instructions.
4: OPERATION BASICS Disable Tag Function The following example describes a simple procedure without using the tag function. From the WindLDR menu bar, select View, then click the check box of Device Address. Check the Device Address check box. Edit User Program Rung by Rung Start the user program with the LOD instruction by inserting a NO contact of input I0. 1. From the WindLDR menu bar, select Home > Basic > A (Normally Open). 2.
4: OPERATION BASICS 3. Enter I0 in the Tag Name field, and click OK. A NO contact of input I0 is programmed in the first column of the first ladder line. Next, program the ANDN instruction by inserting a NC contact of input I1. 4. From the WindLDR menu bar, select Home > Basic > B (Normally Closed). 5. Move the mouse pointer to the second column of the first ladder line where you want to insert a NC contact, and click the left mouse button. The Normally Closed dialog box appears. 6.
4: OPERATION BASICS Continue programming for rungs 2 and 3 by repeating similar procedures. A new rung is inserted by pressing the Enter key while the cursor is on the preceding rung. A new rung can also be inserted by selecting Home > Append > Append a Rung. When completed, the ladder program looks like below.
4: OPERATION BASICS Simulate Operation Before downloading the user program, you can simulate the operation on the WindLDR screen without connecting the Web server CPU module. From the WindLDR menu bar, select Online > Simulation. The Simulation screen appears. To change an input status, place the mouse pointer on the input and right-click the mouse. In the pop-up menu, select Set or Reset to set or reset the input. To quit simulation, from the WindLDR menu bar, select Online > Simulation.
4: OPERATION BASICS Monitor Operation Another powerful function of WindLDR is to monitor the PLC operation on the PC. The input and output statuses of the sample program can be monitored in the ladder diagram. From the WindLDR menu bar, select Online > Monitor > Monitor. When both inputs I0 and I1 are on, the ladder diagram on the monitor screen looks as follows: Rung 1: When both inputs I0 and I1 are on, output Q0 is turned off. Rung 2: When both inputs I0 and I1 are on, output Q1 is turned off.
4: OPERATION BASICS 4-14 WEB SERVER CPU MODULE USER’S MANUAL FC9Y-B1278
5: FUNCTION AREA SETTINGS This chapter describes the various functions of the Web server CPU module along with applications and procedures to use those functions. Function Area Settings This section describes the Function Area Settings. Device Settings Self Diagnostic Network Settings E-mail Settings Network Management Connection Settings Web Server Program capacity selection can be configured. Watchdog timer value can be configured.
5: FUNCTION AREA SETTINGS Program Capacity Selection This section describes the program capacity selection. Applications The program capacity selection enables you to increase the program capacity to 127,800 bytes when the default program capacity of 62,400 bytes is insufficient. Description of Functions The program capacity selection enables you to configure the program capacity for the Web server CPU module to either 62,400 bytes or 127,800 bytes.
5: FUNCTION AREA SETTINGS Watchdog Timer Setting This section describes watchdog timer setting. Applications The watchdog timer value for the Web server CPU module is 400 ms by default. When the default setting of 400 ms is too small, the watchdog timer value can be changed. Description of functions The watchdog timer value can be changed between 100 ms and 4000 ms. Note: • The watchdog timer can be reset by inserting a NOP instruction in a ladder program.
5: FUNCTION AREA SETTINGS Network Settings This section describes the network settings of the Web server CPU module. Applications The network settings are configured to utilize functions that use the Ethernet port of the Web server CPU module. Description of Functions The network settings can be configured in a similar manner to the network settings of the PC. It is also possible to configure the network settings using special data registers.
5: FUNCTION AREA SETTINGS IP and DNS settings can be configured with one of the following three methods: 1. Obtain network settings automatically from the DHCP server A DHCP server must exist on the network in which the Web server CPU module is installed. All network settings are configured automatically. The network settings are obtained from the DHCP server when the user program is downloaded to the CPU module or when the CPU module is turned on. 2.
5: FUNCTION AREA SETTINGS Special Internal Relays Device Address M8190 Description IP Address Change Flag Operation When M8190 is turned on, the values in special data registers D8304 through 8323 are applied as the network settings.
5: FUNCTION AREA SETTINGS SNTP Server This section describes the configurations for using SNTP server. Applications The Web server CPU module can obtain the current time from an SNTP server in the network. The obtained time is stored in the special data registers and can be used to adjust the clock cartridge. When the clock cartridge is not installed, calendar/clock data obtained from SNTP server can be used as a simple clock.
5: FUNCTION AREA SETTINGS Special Data Registers and Special Internal Relays Special Internal Relays Device Address M8191 Description SNTP Calendar/Clock Data Write Flag Operation When M8191 is turned on, the clock cartridge is adjusted with SNTP calendar/clock data. If M8191 is kept on, the clock cartridge is adjusted every 24 hours. Special Data Registers The calendar/clock data obtained from the SNTP server is stored in the following special data registers.
5: FUNCTION AREA SETTINGS Adjusting the time zone with a special data register (D8413) The time zone (GMT-12:00 to GMT+13:00) configured in the function area settings can be adjusted using D8413 in a multiple of 15 minutes. The time zone after the adjustment should be within GMT-12:00 to GMT+13:00. For example, when the time zone configured in the function area settings is GMT+9:00, and D8413 is 1, 15 minutes are added to the time zone, and the adjusted time zone will be GMT+09:15.
5: FUNCTION AREA SETTINGS Connection Settings This section describes the configurations for client/server connections of the Web server CPU module. Applications The Web server CPU module supports Ethernet communication functions with a maximum of 11 server connections and a maximum of three client connections. Using those connections, maintenance communication, user communication, and Modbus TCP communication can be used. Those communications can be configured in the Function Area Settings dialog box.
5: FUNCTION AREA SETTINGS Maintenance Communication Server When Enable maintenance communication server is enabled, the standard maintenance communication server can be configured. For details, see "Maintenance Communication Server " on page 7-1. Server Connection Select the communication mode for each server connection in the corresponding pull-down list box. A maximum of eight server connections can be configured.
5: FUNCTION AREA SETTINGS Maintenance Communication Server Status and Connected IP Address The connection status of the standard maintenance communication server with network client devices can be confirmed with special internal relays M8212 to M8214. When a connection with a client device is established, the corresponding special internal relay is turned on. When the connection is disconnected, the corresponding special internal relay is turned off.
5: FUNCTION AREA SETTINGS Client Connection Status and Connected IP Address The connection status of client connections with remote hosts can be confirmed with special internal relays M8215 to M8217. When a connection with a remote host is established, the corresponding special internal relay is turned on. When the connection is disconnected, the corresponding special internal relay is turned off. The IP addresses of the remote hosts can be confirmed with special data registers D8394 to D8405.
5: FUNCTION AREA SETTINGS 5-14 WEB SERVER CPU MODULE USER’S MANUAL FC9Y-B1278
6: REMOTE HOST LIST Introduction This chapter describes how to configure a list of network devices (remote hosts) in the network to which the Web server CPU module communicates. Applications When the Web server CPU module accesses and communicates with other network devices in the network, the remote host device should be specified.
6: REMOTE HOST LIST 2. Click New button or select an existing remote host and click Edit button. The Remote Host dialog box appears. IP Address: Specify the remote host with an IP address. Host Name: Specify the remote host with a host name. Port Number: Specify the port number of the remote host. Comment: The comment for the remote host can be assigned. The contents or the length of the comment has no effect on the CPU module operation. 3.
7: MAINTENANCE COMMUNICATION SERVER Introduction This chapter describes the specification and configuration procedure of the maintenance communication server functions of the Web server CPU module. Applications The Web server CPU module features the maintenance communication server functions. WindLDR can monitor the device values in the Web server CPU module and can also download or upload the user program to or from the Web server CPU module through the maintenance communication server.
7: MAINTENANCE COMMUNICATION SERVER Configurations for Pass-Through over Modbus RTU Configuring Modbus RTU Master To configure a Web server CPU module as Modbus RTU master for pass-through, enable Modbus RTU Pass-Through in one of the eight server connections (Note 1) and configure the communication port 2 as Modbus RTU master (Note 2).
7: MAINTENANCE COMMUNICATION SERVER 3. Click on Settings button. The Maintenance Communication Server dialog box appears. Local Host Port No.: The port number that the Web server CPU module opens for the maintenance communication. Number of Connections: The number of connections that the Web server CPU module accepts through the local host port number. The maximum number of connections is three. Receive Timeout (ms): The timeout can be configured between 10 and 2550 ms. The default timeout is 500 ms.
7: MAINTENANCE COMMUNICATION SERVER When you enable Pass-Through over Modbus RTU option, the server connection can be used for the pass-through over Modbus RTU. You also have to configure the communication port 2 as Modbus RTU master. The port used for the passthrough over Modbus RTU cannot be used in any other server connections.
8: ETHERNET USER COMMUNICATION Introduction This chapter describes the Ethernet user communication for the Web server CPU module. Ethernet user communication works on TCP/IP protocol. The Web server CPU module can be used as a user communication client/server. With Ethernet user communication instructions (ETXD and ERXD instructions), the Web server CPU module can exchange the data with devices on the network.
8: ETHERNET USER COMMUNICATION User Communication Client When a client connection is configured as the user communication client, the Web server CPU module communicates with the specified server device according to the settings configured in the ETXD and ERXD instructions that are programmed for the client connection. The remote host number and other communication settings can be configured in the Connection Settings tab in the Function Area Settings dialog box.
8: ETHERNET USER COMMUNICATION Programming WindLDR (User Communication Client) To use the user communication client, configure the user client communication settings in the Function Area Settings dialog box and then download the user program to the CPU module. 1. Select Configuration from the WindLDR menu bar, and then click Connection Settings. The Function Area settings dialog box appears. 2. Select the User Communication Client as the communication mode for the client connection 1.
8: ETHERNET USER COMMUNICATION 3. Edit the user program. To insert Ethernet user communication instructions to the ladder editor, select the Ethernet user communication instructions (ETXD or ERXD instructions) in the Coil Selection dialog box. The Ethernet User Communication Instruction dialog box appears. Select ETXD (Transmit over Ethernet) to transmit data or ERXD (Receive over Ethernet) to receive data as the instruction type.
8: ETHERNET USER COMMUNICATION User Communication Server When a server connection is configured as the user communication server, a client device can access and communicate with the Web server CPU module. The Web server CPU module communicates with the client device according to the settings configured in the ETXD and ERXD instructions that are programmed for the server connection.
8: ETHERNET USER COMMUNICATION Programming WindLDR (User Communication Server) To use the user communication server, configure the user communication server settings in the Function Area Settings dialog box and then download the user program to the CPU module. 1. Select Configuration from the WindLDR menu bar, and then click Connection Settings. The Function Area settings dialog box appears. 2. Select the User Communication Server as the communication mode for the server connection 1.
8: ETHERNET USER COMMUNICATION 3. Edit the user program. To insert Ethernet user communication instructions to the ladder editor, select the Ethernet user communication instructions (ETXD or ERXD instructions) in the Coil Selection dialog box. The Ethernet User Communication Instruction dialog box appears. Select ETXD (Transmit over Ethernet) to transmit data and ERXD (Receive over Ethernet) to receive data as the instruction type.
8: ETHERNET USER COMMUNICATION 8-8 WEB SERVER CPU MODULE USER’S MANUAL FC9Y-B1278
9: MODBUS TCP COMMUNICATION Introduction This chapter describes the Modbus TCP communication of the Web server CPU module. The Web server CPU module can be used as Modbus TCP client/server. The Web server CPU module can communicate with the devices supporting Modbus TCP communication on the network. Modbus TCP Communication Overview The Web server CPU module can be used as Modbus TCP client/server. Modbus TCP server and client of the Web server CPU module can be used simultaneously.
9: MODBUS TCP COMMUNICATION Modbus TCP Client Start and Stop When request execution devices are designated in the Modbus TCP Client request table, internal relays as many as the request quantity are allocated to execute Modbus TCP Client communication. The internal relays are allocated in the order of requests. For example, when internal relay M0 is designated as the request execution device, M0 is allocated to request No. 1, M1 to request No. 2, and so on.
9: MODBUS TCP COMMUNICATION Programming WindLDR (Modbus TCP Client) In order to use Modbus TCP client, configure the Modbus TCP client in the Function Area Settings dialog box and then download the user program to the CPU module. 1. From the WindLDR menu bar, select Configuration > Connection Settings. The Function Area Settings dialog box appears. 2. Select Modbus TCP Client as the communication mode for the client connection 1. The Modbus TCP Client Request Table dialog box appears. 3.
9: MODBUS TCP COMMUNICATION 4. Configure the requests of the Modbus TCP Client. A maximum of 255 requests can be entered in one request table. Specify the Modbus TCP servers with the remote host numbers. After all requests are configured, click OK button to close the dialog box. Choose to use Request Execution Devices and Error Status data registers. When using Request Execution Devices and Error Status data registers, enter the first number of the devices. 5. Download the user program to the CPU module.
9: MODBUS TCP COMMUNICATION Master Device Address When function code 01, 02, 03, or 04 is selected to read data from Modbus servers, designate the first data register or internal relay number to store the data received from the Modbus server. When function code 05, 06, 15, or 16 is selected to write data to Modbus servers, designate the first data register or internal relay number to store the data to write to the Modbus server.
9: MODBUS TCP COMMUNICATION Processing Requests The data for Modbus communication are processed between the client and servers as shown below. Bit Data at Servers (Function Codes 01, 02, 05, and 15) • Master Device Address: Internal Relay Internal Relay (M) Modbus Address Bit +0 Bit +0 Bit +1 Bit +1 Bit +2 Bit +2 Master Slave • Master Device Address: Data Register Data Register (D) Modbus Address Word +0 b15 b14 ... b2 b1 b0 Bit +0 Word +1 b15 b14 ...
9: MODBUS TCP COMMUNICATION Modbus TCP Server When the Web server CPU module is configured as the Modbus TCP server, Modbus TCP client devices can access and communicate with the Web server CPU module. When the Web server CPU module receives a valid request from a Modbus TCP client device, the data is read or written according to the request received. The communication data received from Modbus TCP clients are processed at the END processing.
9: MODBUS TCP COMMUNICATION Programming WindLDR (Modbus TCP Server) In order to use Modbus TCP server, configure the Modbus TCP server in the Function Area Settings dialog box and then download the user program to the CPU module. 1. From the WindLDR menu bar, select Configuration > Connection Settings. The Function Area Settings dialog box appears. 2. Select Modbus TCP Server as the communication mode for the server connection 1. The Modbus TCP Server dialog box appears. 3.
9: MODBUS TCP COMMUNICATION Modbus TCP Communication Format This section describes the communication format used for Modbus TCP client and server communication. Modbus TCP communication format starts with the Modbus TCP header followed by the RTU mode communication format without the idle 3.5 characters at both ends and CRC as shown below.
9: MODBUS TCP COMMUNICATION 9-10 WEB SERVER CPU MODULE USER’S MANUAL FC9Y-B1278
10: E-MAIL Introduction This chapter describes how to use the e-mail functions in the Web server CPU module. The EMAIL instruction sends an e-mail that is configured in WindLDR. EMAIL (Send E-mail) The EMAIL instruction sends an e-mail. Symbol Operation Details When the input to the EMAIL instruction is on, the EMAIL instruction sends an e-mail specified by S1.
10: E-MAIL The operation status includes the operation transition state (status code) and the error detail (error code). The status code can be obtained by masking the least 4 bits of the operation status. The error code is stored in the least 4 bits of the operation status.
10: E-MAIL Special Data Registers Confirm the error detail of EMAIL instruction When the error code stored in D2 of EMAIL instruction is 7, the response from sending e-mail server can be confirmed with special data register D8457. The error code that the sending e-mail servers return could vary with each sending e-mail server. For details about the error code, contact the administrator of the sending e-mail server.
10: E-MAIL SMTP Authentication (login) Depending on each sending e-mail server and network environment, SMTP authentication may be required. The Web server CPU module supports the login method of the SMTP authentication and can utilize sending e-mail servers that require the SMTP authentication with the login method. Contact the administrator of the sending e-mail server to confirm if the e-mail server requires the SMTP authentication.
10: E-MAIL E-mail Address Book Settings in E-mail Address Book The e-mail addresses and e-mail address groups can be configured in E-mail Address Book dialog box. E-mail addresses can be grouped into an e-mail address group. The e-mail address group can be used to specify a group of e-mail addresses in each e-mail. Programming WindLDR 1. Double-click on the E-mail Address Book in the Project Window. The E-mail Address Book dialog box appears. 2.
10: E-MAIL 3. Click New E-mail Group or select an existing e-mail address group and click Edit button. The E-mail Group dialog box appears. Group Name: Specify the name of e-mail address group to register in the E-mail Address Book dialog box. Comment: The comment for the e-mail address group can be assigned. The contents or the length of the comment has no effect on the CPU module operation. The e-mail addresses that have not been added to the e-mail address group are shown in the list box on the left.
10: E-MAIL E-mail Editor Settings in E-mail Editor The e-mails can be configured in E-mail Editor dialog box. The following three parameters should be configured for each e-mail. • E-mail recipients (To and Cc) E-mail address or e-mail group can be specified as the recipients. The maximum size of texts for To or Cc is 512 bytes. Comma (,) is inserted as a separating character between e-mail addresses. For example, the total size of an e-mail group "ccc" containing two e-mail addresses "aa@example.
10: E-MAIL Enter the subject of the e-mail in the subject field. Enter the body of the e-mail in the text box on the bottom. The e-mail body can be written in multiple lines. 2. Click on the Insert Data Register button. The Variable (Data Register) dialog box appears. The data register values can be embedded in the e-mail body when the Web server CPU module sends e-mails. DR Number: Specify the data register number.
11: PING INSTRUCTION Introduction This chapter describes how to use the PING instruction. The PING instruction sends a ping packet to the specified remote host to check if the communication can be done with the remote host on the Internet Protocol (IP) layer. PING (Ping) The PING instruction sends a ping packet to the specified remote host. Symbol Operation Details When the input to the PING instruction is on, the PING instruction sends a ping packet to the remote host specified by S1.
11: PING INSTRUCTION Notes: • When the system program version is 100, do not specify the same remote host number in multiple PING instructions. When the system program version is 100 and a data register is specified as S1, do not store the same remote host number used by the other PING instructions in the user program to the data register. • When a data register is specified as S1, do not change the data register value while PING instruction is executed.
12: WEB SERVER Introduction This chapter describes the Web server functions in the Web server CPU module. Web Server Overview The Web server enables you to access the Web server CPU module using web browser on your PC in order to monitor the status or change the device data. You can create your own web pages and download them to the Web server CPU module. The web pages can be customized for each Web server CPU module.
12: WEB SERVER Programming WindLDR 1. Select Configuration from the WindLDR menu bar, and then click Web Server. The Function Area settings dialog box appears. Web Server Settings Web server port: Specify the port number for the Web server of the Web server CPU module. The default port number is 80. User name: Specify the user name used for authentication. The default user name is "administrator." Password: Specify the password used for authentication. The default password is "password.
12: WEB SERVER System Web Page Overview The system web page of the Web server CPU module consists of the following files. /system/index.html: The PLC status can be monitored. This is also the top page of the system web page. /system/batch_monitor.html: Batch monitor to monitor a group of data registers. /system/custom_monitor.html: Custom monitor to register and monitor a maximum of 30 data registers or internal relays. /system/device_read.
12: WEB SERVER System Web Page The Web server CPU module features the system web page which can be used to check PLC status, monitor, and update data register values and internal relay. Since the system web page is embedded in the Web server CPU module, you can easily access and utilize the system web page. PLC Status In the PLC status page, the Web server CPU module status, such as the system program version or scan time, can be confirmed.
12: WEB SERVER Batch Monitor In the batch monitor, 200 consecutive data registers can be monitored and controlled with the specified data type. 1. Enter the device number in the Device Number. 200 consecutive data registers starting with the specified data register are monitored. The valid device numbers are 0 to 7800, 8000 to 8300, and 10000 to 49800. If an invalid value is entered, the value is corrected automatically. 2. Select the monitor type to display the data registers in the desired format.
12: WEB SERVER Custom Monitor In the custom monitor, a maximum of 30 devices and corresponding data types can be specified to monitor and control. 1. Enter the device (type and number) in the Device Number. "D" (data register) or "m" (internal relay) can be specified. Specify data device number in decimal, such as D2058 or m0112. 2. Select the monitor type to display the corresponding device in the desired format.
12: WEB SERVER Programming WindLDR The procedure to configure the tree structure in the user web page is described. The user web page is managed in the User Web Page in the Project Window. Importing web pages If there are already tree structured web pages on your PC, the entire files and folders can be imported to the user web page. Right click on the User Web Page in the Project Window and select Import Folder. The Browse For Folder dialog box appears.
12: WEB SERVER 4. Right click on the User Web Page in the Project Window and select New Folder. The New Folder dialog box appears. Enter the folder name "folder" and click OK button. A new folder is created under the User Web Page. If you want to rename the folder, right click on the folder and select Rename. Enter the name and click OK to rename the folder. 5. Right click on the folder created with step 4 and select Import Files. 6. Select page2.html in the Open dialog box and click Open button. 7.
12: WEB SERVER Example: Removing web pages from the user web page In this example, steps to remove page33.html and folder44 are described. 1. Right click on page33.html and select Delete. Click OK button to confirm. 2. Right click on folder44 and select Delete. Click OK button to confirm. folder44 and all files/folders in folder44 will be deleted. Notes: • If you want to remove all user web pages, right click on the User Web Page in the Project Window and select Delete All. Click OK button to confirm.
12: WEB SERVER Monitoring Function In the user web pages, data register values can be monitored without directly using JavaScript or CGI. To enable monitoring function, check Enable data register monitoring in Web Server settings in the Function Area Settings dialog box. Note: When the ladder program is converted in WindLDR, WindLDR inserts links to the system JavaScript library files of the Web server CPU module in the head section of the imported htm or html files.
12: WEB SERVER Bit Button (Image) When data register monitoring is enabled, and the following string is included in an html page, that string is replaced with specified images and the images are switched according to the bit state read from the Web server CPU module. The system library is responsible for reading or writing data via CGI. {{Read/Write, Device Type, Device Number, Driver Number, Network Number, Data Type, Off State Image, On State Image}} Example: {{R,m,123,0,0,BIT,./BIT_IMG_OFF.jpg,.
12: WEB SERVER Bar Graph (Vertical) When data register monitoring is enabled, and the format string for vertical bar graph is included in a DIV tag in an html page, that string is replaced with a vertical bar graph and the bar graph is updated according to the data register values read from the Web server CPU module. The system library is responsible for reading data via CGI.
12: WEB SERVER Example: The following format string shows the vertical bar graph for D2040 and D2042 with data type Double.
12: WEB SERVER Bar Graph (Horizontal) When data register monitoring is enabled, and the format string for horizontal bar graph is included in a DIV tag in an html page, that string is replaced with a horizontal bar graph and the bar graph is updated according to the data register values read from the Web server CPU module. The system library is responsible for reading data via CGI.
12: WEB SERVER Example: The following format string shows the horizontal bar graph for D2040 and D2042 with data type Double.
12: WEB SERVER Trend Graph When data register monitoring is enabled, if the format string for trend graph is included in a DIV tag in an html page, that string is replaced with a trend graph and the trend graph is updated according to the data register values read from the Web server CPU module. The system library takes care of reading data via CGI. In order to show a trend graph, insert a DIV tag and assign a unique string as the id and "trend" as the data-graph attribute to the DIV tag.
12: WEB SERVER marker_col line_width marker_width Specify the color of the markers. The default color is the same with the front_col. Specify the width of the line for each series in pixel. This setting has a priority than the initial line width specified with line_width. Specify the size of markers in pixel. This setting has a priority than the initial marker color specified with marker_width.
12: WEB SERVER JavaScript Functions When data register monitoring is enabled, device data can be read or written with the following JavaScript functions included in the system library. Since data register values exchanged via CGI can be directly used in your JavaScript programs, the values can be flexibly manipulated. For details about CGI interface, see "Appendix" on page A-1. Reading Device Data var raw_data = Idec.device_read(device, address, length, driver, net_no) device: Specify the device type.
13: TROUBLESHOOTING Introduction This chapter describes the procedures to determine the cause of trouble and actions to be taken when any trouble occurs while operating the Web server CPU module. The Web server CPU module has self-diagnostic functions to prevent the spread of troubles if any trouble should occur. In case of any trouble, follow the troubleshooting procedures to determine the cause and to correct the error. Errors are checked in various stages.
13: TROUBLESHOOTING Reading Error Data When any error occurs during the Web server CPU module operation, “Error” is indicated and error details can be read using WindLDR on a computer. Monitoring WindLDR 1. From the WindLDR menu bar, select Online > Monitor > Monitor. The monitor mode is enabled. 2. From the WindLDR menu bar, select Online > Status. The PLC Status dialog box appears. When any error exists, “Error” is displayed in the error status box.
13: TROUBLESHOOTING 3. On the right of the Error Status in the PLC Status dialog box, click the Clear button. This procedure clears the error code from special data register D8005 (general error code), and the error is cleared from the PLC Status dialog box. Clear Button Error Cleared Special Data Registers for Error Information Two data registers are assigned to store information on errors.
13: TROUBLESHOOTING CPU Module Operating Status, Output, and ERR LED during Errors Error Items Power failure Watchdog timer error Data link connection error User program ROM sum check error TIM/CNT preset value sum check error User program RAM sum check error Keep data error User program syntax error User program writing error CPU module error Clock IC error Memory cartridge program transfer error (Note 3) I/O bus initialize error User program execution error Operating Status Stop Stop Stop Stop Maintaine
13: TROUBLESHOOTING When a memory cartridge is installed on the CPU module, the user program in the memory cartridge is checked. 0010h: Timer/Counter Preset Value Sum Check Error The execution data of timer/counter preset values is broken. The timer/counter preset values are initialized to the values of the user program automatically. Note that changed preset values are cleared and that the original values are restored. Clear the error code using the HMI module or WindLDR on a computer.
13: TROUBLESHOOTING User Program Execution Error This error indicates that invalid data is found during execution of a user program. When this error occurs, the ERR LED and special internal relay M8004 (user program execution error) are also turned on. The detailed information of this error can be viewed from the error code stored in special data register D8006 (user program execution error code).
13: TROUBLESHOOTING User Program Execution Error Code (D8006) 33 34 35 Error Details In the RNDM instruction, S1 is larger than S2, or S1 or S2 data exceeds 32767. NDSRC has invalid data for source device S3. In the SUM instruction, the execution result exceeds the valid range for the selected data type, or S2 data is 0.
13: TROUBLESHOOTING Troubleshooting Diagrams When one of the following problems is encountered, see the trouble shooting diagrams on the following pages. Problem Troubleshooting Diagram The PWR LED does not go on. Diagram 1 The RUN LED does not go on. Diagram 2 The ERR LED is on. Diagram 3 Input does not operate normally. Diagram 4 Output does not operate normally. Diagram 5 Communication between WindLDR on a computer and the Web server CPU module is not possible.
13: TROUBLESHOOTING Troubleshooting Diagram 1 The PWR LED does not go on. NO Is power supplied? Supply power. YES NO Is the power voltage correct? Is the PWR LED on? YES Supply the rated voltage. All-in-one type: 100-240V AC 24V DC Slim type: 24V DC NO YES NO Is the PWR LED on? Call IDEC for assistance.
13: TROUBLESHOOTING Troubleshooting Diagram 2 The RUN LED does not go on. YES Is the ERR LED on? See Troubleshooting Diagram 3, “The ERR LED is on.” NO Click the Start button in WindLDR on a computer connected to the Web server CPU module. Note: The Start button is found in the WindLDR menu bar. YES Is the RUN LED on? NO Note: To monitor M8000, from the WindLDR menu bar, select Online > Monitor > Monitor, then Online > Custom > New Custom Monitor.
13: TROUBLESHOOTING Troubleshooting Diagram 3 The ERR LED is on. Clear error codes using WindLDR. See Note below. Is the ERR LED turned off? YES NO See “General Error Codes” on page 13-3. Identify the error code and correct the error. END Note: Temporary errors can be cleared to restore normal operation by clearing error codes from WindLDR. See “Clearing Error Codes from WindLDR” on page 13-2.
13: TROUBLESHOOTING Troubleshooting Diagram 4 Input does not operate normally. Is the input LED on? YES NO Are input device addresses correct? Is the input wiring correct? NO NO YES Correct the program. Correct the input wiring. YES Is the input terminal powered correctly? NO Supply the rated voltage to the input terminal. Input voltage range All-in-one CPU, input, mixed I/O modules: Slim type CPU modules: AC input module: Are wiring and operation of external devices correct? NO 20.4 to 28.
13: TROUBLESHOOTING Troubleshooting Diagram 5 Output does not operate normally. Note: The Start button is found in the WindLDR menu bar. Is the RUN LED on? NO Click the Start button in WindLDR on a computer connected to the Web server CPU module. YES Is the output LED on? YES Make sure of correct output wiring. NO Correct the program. NO Check the output allocation numbers. Are output device addresses correct? YES Monitor the output using WindLDR.
13: TROUBLESHOOTING Troubleshooting Diagram 6 Communication between WindLDR on a computer and the Web server CPU module is not possible. Is the computer link cable connected correctly? NO Connect the cable completely. YES Is the PWR LED on? NO See Troubleshooting Diagram 1, “The PWR LED does not go on.” YES Is the Communication Settings correct? NO Correct the Communication Settings using WindLDR. See "Communication Settings" of the advanced volume (page 21-3). YES Call IDEC for assistance.
13: TROUBLESHOOTING Troubleshooting Diagram 7 Cannot stop or reset operation. Note: To monitor M8000, from the WindLDR menu bar, select Online > Monitor > Monitor, then Online > Custom > New Custom Monitor. Enter M8000 in the Device box in the Custom Monitor dialog box. Is stop or reset input designated in the WindLDR Function Area Settings? NO Monitor the start control special internal relay M8000 using WindLDR on a computer.
13: TROUBLESHOOTING Troubleshooting Diagram 8 Watchdog timer error occurs and the CPU does not run. YES Is the scan time longer than 400 ms? Change the watchdog timer value in the Function Area Settings. For details, see “Watchdog Timer Setting” on page 5-3. NO Call IDEC for assistance. Troubleshooting Diagram 9 The interrupt/catch input cannot receive short pulses. Are the input ON/OFF voltage levels correct? NO Make sure of correct input voltage.
13: TROUBLESHOOTING Troubleshooting Diagram 10 Frequency measurement does not work. Are input signals connected to correct terminals? NO Make sure that input signals are connected to correct terminals. See "Frequency Measurement" of the basic volume (page 5-30). NO Select Single-phase High-speed Counter in the Groups 1 through 4. NO Make sure that the gate input is on and the reset input is off.
13: TROUBLESHOOTING Troubleshooting Diagram 11 The calendar/clock does not operate correctly. Is the clock cartridge installed correctly? NO Install the clock cartridge correctly. See "Clock Cartridge" of the basic volume (page 2-95). YES Is the ERR LED on? YES See Troubleshooting Diagram 3, “The ERR LED is on.” NO Read the error data using WindLDR. See “Reading Error Data” on page 13-2. Is “Calendar/clock error” displayed? YES Clear the error code.
13: TROUBLESHOOTING Troubleshooting Diagram 12 Analog I/O module does not work (END refresh type). Does the status DR store status code 4 (hardware failure)? YES Supply the rated power voltage to the analog I/O module. See "Wiring Diagram" of the basic volume (page 9-19). NO Does the status DR store status code 3 (invalid parameter)? YES Make sure of correct parameters. NO After changing settings, was the CPU stopped and restarted? NO Stop and restart the CPU to configure the analog I/O settings.
13: TROUBLESHOOTING Troubleshooting Diagram 13 Data link communication is impossible. NO Is the PWR LED on? See Troubleshooting Diagram 1, “The PWR LED does not go on.” YES Check port 2 settings using WindLDR. See "Programming WindLDR" of the basic volume (page 11-8). NO Is data link selected for port 2 correctly? Select data link for port 2 correctly and download the user program again. See "Programming WindLDR" of the basic volume (page 11-8).
13: TROUBLESHOOTING Troubleshooting Diagram 14 Data is not transmitted at all in the user communication mode. Is the communication cable connected correctly? NO Make sure of correct wiring. YES Is the input to the TXD instruction on? NO Turn on the input to the TXD instruction. YES Is the PWR LED on? NO See Troubleshooting Diagram 1 “The PWR LED does not go on.” YES Call IDEC for assistance.
13: TROUBLESHOOTING Troubleshooting Diagram 15 Data is not transmitted correctly in the user communication mode. Are communication parameters set correctly using WindLDR? NO Set the communication parameters to match those of the remote terminal using WindLDR. See "Programming WindLDR" of the basic volume (page 10-5). YES Is the data register designated as transmit status used repeatedly? YES Correct the program to replace the duplicate data register with a different data register.
13: TROUBLESHOOTING Troubleshooting Diagram 16 Data is not received at all in the user communication mode. Is the communication cable connected correctly? NO Make sure of correct wiring. YES Is the input to the RXD instruction on? NO Turn on the input to the RXD instruction. YES Is the PWR LED on? NO See Troubleshooting Diagram 1 “The PWR LED does not go on.” YES Call IDEC for assistance.
13: TROUBLESHOOTING Troubleshooting Diagram 17 Data is not received correctly in the user communication mode. Are communication parameters set correctly using WindLDR? NO YES Is the data register designated as receive status used repeatedly? YES Set the communication parameters to match those of the remote terminal using WindLDR. Web server CPU module can use constants only for start and stop delimiters. See “Programming WindLDR” of the basic volume (page 10-5.
13: TROUBLESHOOTING Troubleshooting Diagram 18 Modbus master communication does not work. Are communication parameters equal at master and slave? NO YES Are error data stored in D8069 to D8099? (Note) YES Confirm the slave number (high-order byte) and error code (low-order byte). See “Communication Error Data of Each Slave” of the basic volume (page 12-4). NO NO Confirm communication settings using WindLDR. See “Programming Modbus Master Using WindLDR” of the basic volume (page 12-4).
13: TROUBLESHOOTING Troubleshooting Diagram 19 WindLDR does not communicate with PLC via USB. Is a communication error displayed when monitoring is started on WindLDR? Carry out the steps 1 and 2 below and try again. YES Step 2: Check communication settings Open the Communication Settings dialog box in WindLDR. Select USB and uncheck the Use HGxG Pass-Through check box.
13: TROUBLESHOOTING Troubleshooting Diagram 20 Modbus master communication request is slow. Select to use request execution internal relay and designate an internal relay number. Keep unnecessary internal relays turned off and turn on internal relays only when sending requests. END Troubleshooting Diagram 21 E-mail is not sent. Is the EMAIL instruction error code "7"? YES The request for sending e-mail is received by the SMTP server but the e-mail is not transferred.
13: TROUBLESHOOTING 13-28 WEB SERVER CPU MODULE USER’S MANUAL FC9Y-B1278
APPENDIX CGI (Common Gateway Interface) The device data can be read from or written to the Web server CPU module via CGI using JavaScript. This section describes the CGI formats. The CGI format described here may not operate properly if they are not used with JavaScript. Request Format (Reading Device Data) Device data can be read from the Web server CPU module with the following format using the GET method. /system/device_read.
APPENDIX Request Format (Writing Device Data) Device data can be written to the Web server CPU module with the following format using the POST method. /system/device_write.cgi?device=DEV&address=XXXX&length=XXXX&driver=XX&net_no=XX&data=XXXX The CGI parameters are as follows: /system/device_write.cgi device address length driver net_no data : : : : CGI file name Specify the device type of the target device using a character. "D" (Data Register) is supported.
APPENDIX USB Driver Installation Procedure Installing on Windows XP 1. Connect a USB cable to the USB port on the FC5A-D12X1E (with power supplied) and the PC running. 2. After the message "Found New Hardware" appears on the PC, the driver installation wizard appears. Select No, not this time and click Next. 3. Select Install the software automatically (Recommended) and click Next.
APPENDIX 4. Click Continue Anyway button. If the installation is aborted without showing the dialog box above, Block is selected in the Driver Signing Options in Driver Signing in the System Properties dialog box. If the installation is aborted, this option should be changed to Warn. After changing the option to Warn, reconnect the Web server CPU module and retry the installation procedure from the step 1. 5. Installation is now complete. Click Finish.
APPENDIX Installing on Windows Vista 1. Connect a USB cable to the USB port on the FC5A-D12X1E (with power supplied) and the PC running. 2. The dialog box below appears. Select Locate and install driver software (recommended). 3. The User Account Control dialog box appears. Click Continue button. 4. The dialog box below appears. Select Install this driver software anyway. 5. Installation is complete once the message “Your devices are ready to use” appears in the bottom right corner of the desktop.
APPENDIX A-6 WEB SERVER CPU MODULE USER’S MANUAL FC9Y-B1278
INDEX A analog potentiometer 2-5 voltage input 2-6 applicable expansion module maximum quantity 3-15 assembling modules 3-2 authentication e-mail 10-4 B bar graph 12-12, 12-14 batch monitor 12-5 bit button 12-10, 12-11 C calendar/clock SNTP 5-7 cartridge connector 2-6 CGI A-1 reading device data A-1 writing device data A-2 character set e-mail 10-4 clearing error codes 13-2 client user communication 8-2 client connection 5-10 connected IP address 5-13 status 5-13 client connections communication mode i
INDEX G general specifications 2-4 grounding 3-13 H high-speed counter 2-5 HMI module installing 3-3 removing 3-4 host name 6-1 I I/O bus initialize error 13-5 usage limits 2-8 input internal circuit 2-8 operating range 2-8 specifications CPU module 2-8 wiring 3-11 inrush current at powerup 3-13 installation and wiring 3-1 in control panel 3-8 location 3-1 installing HMI module 3-3 instruction EMAIL 10-1 ERXD 8-2 ETXD 8-2 PING 11-1 internal circuit input 2-8 output 2-9 current draw 3-15 IP address 5-6,
INDEX reset input 4-7 system status 2-6 response time 4-7 restart system status 2-6 revision history Preface-2 rung 4-9 S system setup example 1-4 system web page 12-3 language 12-2 screwdriver 3-17 server connection 7-3 maintenance communication 7-1 user communication 8-5 server Connection connected IP address 5-13 server connection status 5-13 server connections 5-10 communication mode information 5-11 server/client communications 1-5 sever connection status 5-13 simple operation 4-8 simulate operation
INDEX quit 4-13 start 4-1, 4-8 wiring 3-1 diagrams I/O 2-10 input 3-11 output 3-11 power supply 3-13 IV WEB SERVER CPU MODULE USER’S MANUAL FC9Y-B1278
NOTES WEB SERVER CPU MODULE USER ’S MANUAL FC9Y-B1278 1
NOTES 2 WEB SERVER CPU MODULE USER ’S MANUAL FC9Y-B1278
UNITED STATES JAPAN IDEC CORPORATION 1175 Elko Drive, Sunnyvale, CA 94089-2209, USA Tel: +1-408-747-0550 Toll Free: (800) 262-IDEC Fax: +1-408-744-9055 Toll Free Fax: (800) 635-6246 E-mail: opencontact@idec.com IDEC CORPORATION 7-31, Nishi-Miyahara 1-Chome, Yodogawa-ku, Osaka 532-8550, Japan Tel: +81-6-6398-2571 Fax: +81-6-6392-9731 E-mail: marketing@idec.co.
