|
|
|
|
| CHAPTER2 Ethernet Unit | |
|
|
|
|
|
|
|
|
|
|
|
|
| |
No. | Symptom |
| Probable causes | Checkpoints | Action |
|
|
|
|
|
|
|
|
|
| 7) | Wrong IP | • Check the settings after referring to “2- | • Redo the IP address, subnet mask and |
|
|
|
| address, subnet | gateway settings correctly. Then turn |
| |
|
|
| mask or gateway | 3 Setting the subnet mask” p. 12, and | on the controller power again. |
|
|
|
| settings on |
|
| |
|
|
| controller. |
|
|
|
|
|
|
|
|
|
|
|
| 8) | Ethernet unit is | • Try substituting the Ethernet unit. | • If operation returns to normal, then the |
|
|
|
| defective |
| Ethernet unit is probably defective, so |
|
|
|
|
|
| replace the Ethernet unit. |
|
|
|
|
|
|
|
|
2 | Cannot make | 1) | Wrong IP | • Check that the IP address of the | • Enter the correct IP address. |
|
| TELNET |
| address used | controller you are attempting to |
|
|
| connection or |
| during Telnet | connect with is correct. |
|
|
| cannot |
| connection |
|
|
|
| terminate the | 2) | Wrong Port No. | • Check that the port No. of the | • Enter the correct IP address. |
|
| TELNET |
| used during | controller you are attempting to |
|
|
| connection |
| TELNET | connect with is correct. |
|
|
| right away. |
| connection. |
|
|
|
| (ping reply is | 3) | The controller is | • When connected, the message “telnet is | • Await termination of current TELNET |
|
| normal). |
| already logged in | already used!” appears. | connection. |
|
|
|
| with another |
|
|
|
|
|
| TELNET |
|
|
|
|
|
| terminal. |
|
|
|
|
| 4) | Alarm issued to | • Alarm message appears when | • Troubleshoot according to the type of |
|
|
|
| controller. | connected. | alarm. |
|
|
|
|
| • Connect the TPB and check for an |
|
|
|
|
|
| alarm. |
|
|
|
|
|
| • Status led is lit up in red. |
|
|
|
|
|
|
|
| |
|
| 5) IP address is the | • Check if the IP address and MAC | • If the IP address and MAC address do |
| |
|
|
| same as another | address have a correct match by using | not match each other, then the IP |
|
|
|
| network device. | the “arp” command incorporated in the | address is wrong, so try redoing the |
|
|
|
|
| OS. | settings. |
|
|
|
|
| • Check all devices on the network to | • If found to be the same as another |
|
|
|
|
| find if the same IP address is being | device, change the setting. |
|
|
|
|
| used. |
|
|
|
| 6) | Network traffic | • Check if the traffic load is appropriate. | • Change the network structure to get a |
|
|
|
| (communication |
| smaller traffic load. |
|
|
|
| data load) is too |
|
|
|
|
|
| heavy. |
|
|
|
|
|
|
|
|
|
|
3 | An OK does | 1) | Ethernet unit is | • See | • Enable the Ethernet unit and turn on |
|
| not come |
| not enabled and | (p. 9) and check if the Ethernet Unit is | the power to the controller again. |
|
| back after |
| not identified | enabled. |
|
|
| login, or no |
| (recognized) by |
|
|
|
| replay comes |
| controller. |
|
|
|
| back even | 2) | I/O custom | • Check the I/O signal (Check on the | • Always use a pulse input for the |
|
| after issuing a |
| command input | sequencer monitor, etc.) | custom command input. |
|
| command. |
| signal is set ON. | • Communication error is issued when |
|
|
| (Some unit |
|
| TPB is connected to controller. |
|
|
| control |
|
|
|
|
|
| 3) | Commands such | • Reply comes back after axis movement | • When issuing TELNET commands, do |
| |
| commands |
| as origin return, | or writing data. | not run commands from the I/O or RS- |
|
| are useable |
| axis movement |
| 232C. |
|
| such as |
| commands, or |
|
|
|
| LOGOUT or |
| data write |
|
|
|
| BYE.) |
| commands are |
|
|
|
|
|
| being run from |
|
|
|
|
|
| I/O or RS/232C. |
|
|
|
|
|
|
|
|
|
|
33