Show Posts
1
Technical support / Re:FMD-88-10 PLC
« on: December 06, 2013, 03:53:08 AM »
RemoteFS is ONLY for communicating with TLServer to perform special functions such as writing a file to the PC or sending out an email on its behalf. It is not for PLC to PLC communications.
>> Yes, we used RemoteFS to writing a file (e.g Input/Output triggered) and send back to PC. TLServer is always turn on.
What is the Room B user using to receive the message from PLC in Room A? Is it text messages, emails or is it another PLC?
>> text file (.txt) and less than 1KB.
In your first post said that you have 32 FMD88-10 PLCs connected to the network. May I know are these PLC talking to each other or all of them try to talk to another PLC?
>> 32x FMD88-10 are standalone with one static IP and One workstation act as a Monitoring Signal from 32nos of PLC.
Please explain a bit more clearly of your setup in order for us to understand what is the issue you face.
>> 32 x PLC + one workstation connected to network switch, hence all devices are in same network.
>> for example, sometime user mentioned when they press a input button and didn't received any .txt from plc to notify them via workstation.
>> when encounter this problem, we did a ping test to ensure the network connectivity. unfortunately, there is many drop packet from PC ping to PLC.
>> 2nd, user just do a power cycle for the PLC , and do a same ping test again. the drop packet is gone.
>> after few days/weeks, same problem occurred again.
Are you able to use i-TRiLOGI to perform online monitoring on these PLCs?
>> YES
How is the connection quality? Do you often face communication errors when you perform online monitoring? If so then it is likely your networking equipment has some issues.
>> we have other devices connected to this network switch , but the ping result is healthy also.
>> Yes, we used RemoteFS to writing a file (e.g Input/Output triggered) and send back to PC. TLServer is always turn on.
What is the Room B user using to receive the message from PLC in Room A? Is it text messages, emails or is it another PLC?
>> text file (.txt) and less than 1KB.
In your first post said that you have 32 FMD88-10 PLCs connected to the network. May I know are these PLC talking to each other or all of them try to talk to another PLC?
>> 32x FMD88-10 are standalone with one static IP and One workstation act as a Monitoring Signal from 32nos of PLC.
Please explain a bit more clearly of your setup in order for us to understand what is the issue you face.
>> 32 x PLC + one workstation connected to network switch, hence all devices are in same network.
>> for example, sometime user mentioned when they press a input button and didn't received any .txt from plc to notify them via workstation.
>> when encounter this problem, we did a ping test to ensure the network connectivity. unfortunately, there is many drop packet from PC ping to PLC.
>> 2nd, user just do a power cycle for the PLC , and do a same ping test again. the drop packet is gone.
>> after few days/weeks, same problem occurred again.
Are you able to use i-TRiLOGI to perform online monitoring on these PLCs?
>> YES
How is the connection quality? Do you often face communication errors when you perform online monitoring? If so then it is likely your networking equipment has some issues.
>> we have other devices connected to this network switch , but the ping result is healthy also.
