adccommunitymod (AutomationDirect) asked a question.
Netedit 3
Created Date: June 06,2008
Created By: a agnone
**** 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.****
Okay brains. Using Netedit3. I have two networks,one is 191.9.2.x (wired),the other is wireless 191.9.7.x. When I run Netedit3 on the wired network I see the ECOM cards, but not on the wireless. With DirectSoft I can connect on the wireless and hard wired. Okay, so what is happening? I was told the two programs work differently.
Created Date: June 06,2008
Created by: chris.zeman
There is latency on wireless networks. I have a few PLCs connected via wireless, and finding them with NetEdit can be hit or miss. I don't believe there are any setting in NetEdit that will give the ECOMs more time to respond. You might just want to hit Scan Network a bunch of times until you see them.
Hopefully somebody else will have a smarter solution. http://forum1.automationdirect.com/board/smile.gif
Chris
Created Date: June 09,2008
Created by: a agnone
Thanks Chris, Maybe I should post on HostEng.com. I believe they wrote the program. Since I did not see any tech support answer, I believe there is no solution at this time. But I will try what you suggested.
Created Date: June 09,2008
Created by: GKiser
a agnone, chris is right. The absence of the list on the wireless network is probably due to the delay.
NetEdit sends out a broadcast and waits 600 ms for devices to respond. If the devices take longer than this to respond they will be missing from the list. After the responses are gathered, NetEdit makes a list and then polls each device in the list to get detailed data, but waits only 250ms for response from each device. If the device takes longer than this to respond some of its data may be missing. This is not a problem on a normal wired network, but can be a problem on a wireless network where responses can inadvertently be long and inconsistent. Also, since a broadcast is used, if the devices are on the other side of a network, these network devices by default will usually block broadcast packets. However, this does not necessarily mean that you cannot ping the devices (TCP/IP protocol) and/or use DirectSOFT to link to them (e.g. by manually entering the IP address).
In the next release of NetEdit, we plan on allowing the user to set the "wait " time of NetEdit.
Greg Kiser
Host Engineering, Inc.
support@hosteng.com
Created Date: June 09,2008
Created by: a agnone
However, this does not necessarily mean that you cannot ping the devices (TCP/IP protocol) and/or use DirectSOFT to link to them (e.g. by manually entering the IP address).
Yes we can ping and use DirectSoft on the wireless. Can not wait for the new NetEdit.
I tried the numerous scans but did not work.
Created Date: June 09,2008
Created by: sii
Can you not also change settings simply by typing the IP in your browser's address bar?
Created Date: June 11,2008
Created by: GKiser
Yep, you sure can. http://forum1.automationdirect.com/board/smile.gif
Greg Kiser
Host Engineering, Inc.
support@hosteng.com
Created Date: June 12,2008
Created by: a agnone
sii becareful bringing up the ecom card's page and changing setting. I did that a entered in a wrong number. I could not connect to the ecom, had to call the plant and have them hook up to the ecom and change the numbers.
Created Date: June 06,2008
Created by: a agnone
Okay brains. Using Netedit3. I have two networks,one is 191.9.2.x (wired),the other is wireless 191.9.7.x. When I run Netedit3 on the wired network I see the ECOM cards, but not on the wireless. With DirectSoft I can connect on the wireless and hard wired. Okay, so what is happening? I was told the two programs work differently.