adccommunitymod (AutomationDirect) asked a question.
KepDirect can't see DL450
Created Date: February 11,2008
Created By: Kristjan H
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
I am having KepDirect OPC server talk with a H4-ECOM on a crossover cable (direct link between PC and PLC) and the communication is bad. I developed the project talking with a D2-ECOM through a router and had no problems. I use IP# 192.168.2.5 for the PLC in both cases. Do I need a different kind of IP# for direct links? NetEdit (launched from KepDirect) can find the ECOM, but only in IPX. Anyone see what silly detail I am missing? PS. Does the H4-ECOM not respond to pings?
Created Date: February 12,2008
Created by: GKiser
You do not need a different kind of IP address for direct links. If NetEdit can't see the ECOM on TCP/IP, this is usually caused by having>1 NIC on your PC. You might try, therefore, to reprioritize your NICs bringing the NIC you are using to the top of the list.
Yes, the H4-ECOM will respond to pings.
Created Date: February 14,2008
Created by: stimpsonjcat
or just disable all other NICs and other network adapters (1394 etc) long enough to figure it out.
If you can ping it, you ought to be able to make the link work.
Created Date: February 11,2008
Created by: Kristjan H
I am having KepDirect OPC server talk with a H4-ECOM on a crossover cable (direct link between PC and PLC) and the communication is bad. I developed the project talking with a D2-ECOM through a router and had no problems. I use IP# 192.168.2.5 for the PLC in both cases. Do I need a different kind of IP# for direct links? NetEdit (launched from KepDirect) can find the ECOM, but only in IPX. Anyone see what silly detail I am missing?
PS. Does the H4-ECOM not respond to pings?