EZEthernet FAQ0001
04-Sep-2002
Q: Is it possible to connect EZ Ethernet/EtherPLUS cards to PC NIC?
A: PC would have to act like an ECOM for this to work. Host has not created a driver to do this yet, but is making plans for one.

EZEthernet FAQ0002
05-Sep-2002
Q: Does the EZ Ethernet/EtherPLUS card support TCP/IP or IPX?
A: Both.

EZEthernet FAQ0003
13-Sep-2002
Q: Can EZ Ethernet/EtherPLUS be used on an EZ-S6C-K panel?
A: No, only on the -F panels.

EZEthernet FAQ0004
21-Oct-2002
Q: In EZ Touch v2.2 software crashes if a project is reloaded.
A: There is a bug in the EZ Touch software when Ethernet protocol is picked, that if the Panel-to-Node Config Name is 16 characters or greater, this could cause a crash. The EZETHER.DLL has been repaired. Repaired DLL file version is v1.01 and can be downloaded on Host's website.

EZEthernet FAQ0005 (similar to DirectSOFT FAQ0013; DSData FAQ0045; ECOM FAQ0024)
08-Feb-2008
Q: Using NetEdit the EZ Ethernet/EtherPLUS is visible, but when using EZTouch software's Select Panel, it does not show up in the list.
A: NetEdit reports everything that responds to the broadcast (looking for modules), but the Select Panel button in EZTouch software filters out everything on the network that is not an EZ Ethernet/EtherPLUS adapter. It also uses IPX protocol whereas NetEdit can use both. Therefore, check the following:

• Make sure IPX protocol is loaded for the NIC you are using.
• If your PC has 2 (or more) NICs (Network Interface Cards), then make sure that you try one of these:
       (*) Reprioritize your NICs:
            If you have WinXP:
                 (1)  Start -->  Control Panel.
                 (2)  Double-click on the "Network Connections" icon.
                 (3)  On the menu at the top, select Advanced --> Advanced Settings...
                 (4)  On the "Adapters and Bindings" tab, in the top window, select the connection you are using.
                 (5)  Use the green arrows at the right to move this connection to the top of the list.
                 (6)  Press <OK> and close Network Connections window.
                 (7)  You may have to reboot your PC.
            If you have WinVista:
                 (1)  Start -->  Control Panel.
                 (2)  Double-click on the "Network & Sharing Center" icon.
                 (3)  At the left of this window, click on "Manage network connections"
                 (4)  Press the <ALT> key to make a menu appear at the top of this window.
                 (5)  On the menu at the top, select Advanced --> Advanced Settings...
                 (6)  On the "Adapters and Bindings" tab, in the top window, select the connection you are using.
                 (7)  Use the green arrows at the right to move this connection to the top of the list.
                 (8)  Press <OK> and close Network Connections window.
                 (9)  You may have to reboot your PC.
       (*) Uninstall or disable one NIC.
       (*) Make sure that the NICs don't have common protocols enabled (i.e. IPX and TCP/IP). In other words, you might enable IPX on one NIC and TCP/IP on the other NIC, but not on both simultaneously (see EZEthernet FAQ0027 for installing protocols).

EZEthernet FAQ0006
17-Mar-2011
Q: Getting various errors with EZ Ethernet/EtherPLUS adapter (e.g. no longer visible or disappears from the network).
A: Several temporary errors can be remedied by powering down the EZ Touch panel, removing the EZ Ethernet/EtherPLUS adapter (leaving it out for a few moments), then reinstalling and powering up. For more specific help, refer to the following specific errors and their solutions or work-arounds:

• (1) EZ-Ethernet/EtherPLUS disappears from the network with no indication of any error.
  This can happen on rare occasions and is a known issue with the EZ-Ethernet/EtherPLUS and EZTouch panel interface. Some things that can help:
  - Switch to using the serial port exclusively and uninstall the EZ-Ethernet.
  - Update to the latest firmware (EZ-Ethernet v1.3.4, EZ-EtherPLUS v2.0.13) as these are the last revisions to address this problem.
  - If you are using the serial port to poll the PLC and the EZ-Ethernet to just make program changes, slow the serial poll rate down.
  - If you are using the EZ-Ethernet to poll the PLC then make sure you do not have more than 8 EZ-Ethernet cards polling the same PLC.
  - Make sure your EZTouch screens contain consecutive V-memory locations. If they are not consecutive, more telegrams must be formed.
  - Make sure your EZTouch screens have as little data as possible.
   
• (2) "0x0008 Protocol error"
  EZTouch software help file says "0x0008 Protocol Error - The driver has received a serial communications protocol error from the PLC. The driver is unable to communicate with the PLC when this error occurs." However this just means one of the following:
  
  - The PLC is in the RUN mode (instead of TERM)
  - The PLC has a password.
   
• (3) "Write tag retry count exceeded" or "Read tag retry count exceeded"
  These errors mean the EZ Ethernet/EtherPLUS card is not getting responses to write/read requests in a timely fashion. Check the following and correct:
  
  - Does the EZ Touch project have more than one screen? (If it does, there was a bug in EZ Ethernet v1.0.0e. Newer firmware than this one can be downloaded from our website.
  - Is the network bad or network situation bad?
  - Is the PLC scan time excessively large? (Try putting PLC in STOP mode; reduces scan time to 0).
  - Does the EZ Touch have an excessive number of tags on a single screen? (Especially if they are noncontiguous locations?)
  - Is the network hardware OK? (Replace hub? Switch?)
  - Try increasing the Timeout for the node in EZ Touch software.
  - Consider using multiple ECOMs for different EZ Ethernet/EtherPLUS cards.
  - If using multiple ECOMs, consider using isolated networks.
  - Use a hub instead of a switch, or vise versa.
   
• (4) "Adapter write queue overflow"
  This error means that the EZ Touch panel is writing write requests into the EZ Ethernet/EtherPLUS's queue faster than the EZ Ethernet/EtherPLUS is able to empty them out via write requests to the ECOM. This can especially happen if the situation is busy (see above suggestions for "Write tag retry count exceeded") and if there are writes from the EZ Touch for recipes. The write queue is only 25 requests in size and a recipe can be up to 20 requests. The EZ Ethernet/EtherPLUS has to guarantee that these recipe writes get to the PLC, so if they cannot, then the requests are reentered into the write queue to try again. So if things are busy, then this error can happen. Thus, again, try the above things.
   
• (5) "Download failed with error 0x8006"
  This error means that the PC could see the EZ Ethernet/EtherPLUS adapter (i.e. a link was established), but the transfer of data to the EZ Ethernet/EtherPLUS adapter timed out. This means the EZ Ethernet/EtherPLUS adapter is too busy to process the download. Check:
  
  - If the panel is actively scanning PLCs, try the download with the panel isolated from these PLCs.
  - The panel itself could be the problem; look for messages displayed there.
   
• (6) "T02_3 Invalid address"
  This occurs when you are trying to create objects in EZ Touch. This was due to a bug in our EZETHERNET.DLL file specific to Win2K SP4 PCs. To fix, you have two choices:
  
  - Change operating systems on your PC (hardest!)
  - Update the EZETHERNET.DLL file by downloading the latest updates for your EZ Ethernet/EtherPLUS card on our website (easy!)
   
• (7) "Ethernet adapter card not responding" or "Driver can't access adapter Shared RAM"
  This indicates there is not enough time for the EZ Ethernet/EtherPLUS card to respond to the panel it is plugged into. The first thing to make sure of is that the EZ Ethernet card has at least v1.3.2 firmware and the ECOMs have at least v1.0.211 firmware. But otherwise, this error generally means:
  
  - The EZ Ethernet/EtherPLUS card is getting swamped with comms from the PLC(s) it is connected to. In this case you probably only need to adjust the Timeout values (and/or Retries) for the comms.
  - The EZ Ethernet/EtherPLUS card is getting swamped by broadcasts on the network. In this case you either have to isolate the adapter from these broadcasts on the network, or make sure that you have EZ Ethernet v1.3.4 or EZ EtherPLUS v2.0.10.
  - The EZ Ethernet/EtherPLUS card has "lost its mind" in which case you will have to power cycle to get it back. Sometimes you may even have to unplug the EZ Ethernet/EtherPLUS card from the panel!
   
• (8) "Error reading EZ-Ethernet Adapter device definition"
  This indicates that EZTouch software could not ascertain the device definition from the adapter. It must complete this step before the download may proceed. Check:
  
  - Make sure the address ID of the EZ Ethernet/EtherPLUS adapter is unique (no duplicate IDs on the same network).
  - Remove the EZ Ethernet/EtherPLUS adapter from the panel and reinstall.
  - Isolate the PC-to-EZ Ethernet/EtherPLUS network and reboot the switch(es) involved.
   
• (9) "Adapter could not lock Shared RAM"
  This error is caused by the EZ Ethernet/EtherPLUS needing access to the EZ Touch panel's Shared RAM, but being locked out 3 times in a row. Sometimes this is seen on power up of a system that has a single EZ Touch panel talking to multiple PLCs (e.g. 7 or more).
  
  - The EZ Touch panel should eventually recover on its own from this error.
  - If if does not recover, you may have to reduce the number of PLCs it is talking to; or isolate the network (if it is not already isolated).

EZEthernet FAQ0007 (see also NetEdit FAQ0004; EBC FAQ0078; ECOM FAQ0025; EDRV FAQ0011; ERM FAQ0052)
27-Jan-2010
Q: Can retries and timeout values for NetEdit be adjusted to allow it to find Host Ethernet devices on much slower networks?
A: No, but we will probably include this ability in future releases of NetEdit (greater than v3.7). Currently 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 his list. After the responses are gathered, NetEdit makes a list and then polls each device in the list one at a time to get detailed data, but waits only 250 ms 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 or across the Internet where responses can inadvertently be long and inconsistent. Also, since a broadcast is used, any device between NetEdit and the Host Ethernet modules that block broadcasts can prevent NetEdit from seeing anything.

EZEthernet FAQ0008 (see also ECOM FAQ0042; DirectSOFT FAQ0048; DL Plus FAQ0009; DNLoader FAQ0010; DSData FAQ0005; HA-TADP FAQ0002; Lookout Direct FAQ0014; NetEdit FAQ0005; SDK FAQ0020)
31-Jan-2008
Q: Why doesn't the ECOM use subnet mask or gateway address like the ECOM100?
A: Since the ECOM doesn't do "master"-type communications, it doesn't use the subnet mask or gateway address. Whatever talks to the ECOM will be using IPX or UDP/IP, and the ECOM simply swaps the destination and source addresses in the telegram and responds in this way, not "caring" about the subnet or gateway. However, the ECOM100 acts more like a conventional TCP/IP device. The ECOM100 has the capability to be a master and has a full-blown TCP stack inside. Thus, if it is to transmit to an IP address not on its subnet, it will, of course, transmit to its configured gateway address instead.

EZEthernet FAQ0009
11-Feb-2003
Q: How many PLCs can I connect to one EZ Ethernet/EtherPLUS adapter card?
A: Six (6) is considered the limit. Anything over six is considered a "crap shoot." It might work, or it might give you trouble.

EZEthernet FAQ0010 (see also CTRIO FAQ0045; DirectSOFT FAQ0132; DL Plus FAQ0010; DNLoader FAQ0011; DS Data FAQ0102; EBC FAQ0083; ECOM FAQ0084; EDRV FAQ0084; ERM FAQ0058; General FAQ0004; HA-TADP FAQ0008; Lookout Direct FAQ0015; NetEdit FAQ0037; PBC FAQ0014; PSCM FAQ0003; SDK FAQ0022; SERIO FAQ0004; WinPLC FAQ0038)
31-Dec-2009
Q: What is the export classification of your products (e.g. ECCN)
A: None of our products have an ECCN. Automation Direct sells our products and they export EAR99 NLR (No License Required). ECCN is Export Controlled Classification Number and none of our products are controlled.

EZEthernet FAQ0011 (see also EBC FAQ0015; HA-TADP FAQ0001; EDRIVE FAQ0001; ECOM FAQ0008; ERM FAQ0009; WinPLC FAQ0004)
07-Feb-2003
Q: Can the MAC address be changed?
A: The MAC address is burned into the ROM of the device and is set just before it leaves the factory. There is no logical way for any protocol to change this address. Host Engineering’s range for Ethernet MAC addresses is 00.E0.62.xx.xx.xx.

However, there was a bug with the old Ether32.EXE program that could change the MAC Address! If you use Ether32.EXE to update the booter using TCP/IP protocol (i.e. use the "/pi" option on the command line), then the MAC Address could be changed by accident!

• If MAC Address gets changed by accident in the above fashion, then you will have to ship the module(s) to Host Engineering for repair.
• When updating the booter/firmware of the EBC, EDRV, ECOM or ERM always use NetEdit instead of the outdated Ether32.EXE.

EZEthernet FAQ0012
09-Jan-2003
Q: How can I configure the EZ Ethernet/EtherPLUS over the Internet?
A: Follow instructions:

1. The EZ Ethernet/EtherPLUS adapter must have a registered Internet (TCP/IP) address.
2. Ping your EZ Ethernet/EtherPLUS adapter using a Command Prompt: (e.g. type:      ping <your EZ Ethernet/EtherPLUS's TCP/IP Address>    and press <ENTER>).
3. Note the average turnaround time.
4. Select Panel in EZ Touch:

• In Step 1 Window select Ethernet under Ethernet/COM Port.
• Press <Select Panel> button.

• In the Edit EZ Touch Panel Configuration Window select:
• Configuration Mode - Connected to Network
• Protocol - TCP/IP
• Address Mode - IP Address <your EZ Ethernet/EtherPLUS's TCP/IP Address>
• Advanced Settings - Timeout (observed turnaround time x 2 + 1000)

Now you should be able to configure the EZ Touch Panel from the Internet.

EZEthernet FAQ0013 (see also ECOM FAQ0099; EBC FAQ0085; EDRV FAQ0028)
19-May-2010
Q: Do Host Ethernet devices use full- or half-duplex communications?
A: Half-duplex, allowing alternating transmission in 2 directions, but not in both directions simultaneously.

EZEthernet FAQ0014 (see also ERM FAQ0014; EBC FAQ0023; ECOM FAQ0019; EDRIVE FAQ0005)
26-Mar-2003
Q: For my Ethernet network that would exceed 100 meters, is a standard hub considered a repeater so as to increase the permissible length?
A: Yes. The maximum distance per 10BaseT cable segment is 100 meters. Repeaters (e.g. hubs, bridges, etc.) extend the distance. Each cable segment attached to a repeater can be 100 meters. Thus, two repeaters can gain you a total of 300 meters distance.

EZEthernet FAQ0015
11-Sep-2003
Q: Can I update my EZ Ethernet card to an EZ EtherPLUS?
A: No. The EZ-EthernetPLUS is a completely different hardware platform.

EZEthernet FAQ0016 (deleted)

EZEthernet FAQ0017 (see also ECOM 0028; EBC FAQ0033, ERM FAQ0020, EDRV FAQ0007, DirectSOFT FAQ0181; DS Data FAQ0088; SDK FAQ0012; NetEdit FAQ0013)
20-Nov-2003
Q: What Ethernet protocols are used by your products?
A: Refer to chart below:

(1)  Not an industry standard. However, protocol is available for 3rd-party development upon request.
(2)  Not really a distinct protocol. This setting is used to intelligently pick K-sequence or DirectNet as needed by the hardware/software.
(3)  Used when doing ECOM-to-ECOM via RX/WX instructions with RX/WX Node Map configured in sending ECOM.
(4)  Used when doing ECOM-to-PC (Report-by-Exception) via RX/WX instructions (Address 90 only) with ECOM's dipswitch 7 set ON.
(5)  Used when doing ECOM-to-ECOM via RX/WX instructions without RX/WX Node Map configured in sending ECOM.
(6)  RX/WX Node Map must be configured in ECOM.
(7)  ERM can talk to one slave with UDP/IP and another with IPX simultaneously.
(8)  Planned for Dec2004-Feb2005.
(9)  Requires K-sequence protocol spec (request from Automation Direct)
(10)  Uses K-sequence to perform "Test CPU Access!" function.
(11)  Uses this protocol to perform "Show Base Contents..." function.
(12)  The older HA-EDRV2 cannot talk Modbus TCP.

EZEthernet FAQ0018 (see also CTRIO FAQ0046; EBC FAQ0047; ECOM FAQ0036; EDRV FAQ0009; ERM FAQ0030; PBC FAQ0009; PSCM FAQ0001; WinPLC FAQ0018; NetEdit FAQ0014)
07-Nov-2002
Q: What software tool do I use to upgrade/downgrade my Host Engineering hardware?
A: Refer to the following:

NOTE: All the firmware for the above products can be downloaded using NetEdit3's File --> Live Update... The firmware files are stored in c:\HAPTools\Images folder.

EZEthernet FAQ0019
25-Mar-2004
Q: Can the EZ EtherPLUS card serve as a gateway between the PLC and a Modbus TCP/IP slave device?
A: No. Although the EZ EtherPLUS card is a Modbus TCP/IP master and can therefore talk to any Modbus TCP/IP slave, it is not a control device. The EZ Touch panel does not allow automatic control (scripting, or writing data automatically) and therefore cannot write data to the Modbus TCP/IP slave device without user intervention (i.e. pressing a button on the EZ Touch panel).

EZEthernet FAQ0020
06-Dec-2002
Q: Using NetEdit the EZ Ethernet/EtherPLUS does not show up in the list.
A: NetEdit reports everything that responds to the broadcast (looking for modules). Therefore, check the following:

• Switch the protocol in NetEdit.
• Make sure IPX protocol is loaded for the NIC you are using (see EZEthernet FAQ0027 for installing protocols).
• If you have 2 NICs installed in your PC, you will have to load IPX protocol for one of them and TCP/IP for the other (see EZEthernet FAQ0027 for installing protocols).
• If all else fails try powering down the EZTouch panel; removing the EZ Ethernet/EtherPLUS card and reinstalling. This clears all memory in the panel and EZ Ethernet/EtherPLUS.

EZEthernet FAQ0021
20-Jan-2003
Q: My EZ Ethernet/EtherPLUS adapter locks up (stops responding).
A: This is more than likely caused by the adapter getting hit by broadcasts on the network. Any broadcast packet placed on the wire must be processed by the EZ Ethernet/EtherPLUS adapter; it cannot simply ignore it. Therefore if the network has broadcast packets then this increases the opportunity for a deadlock condition between the panel and the EZ Ethernet/EtherPLUS adapter to occur simply because the adapter gets so busy trying to process them that it appears to lockup. The best thing to do is to isolate the EZ Ethernet/EtherPLUS and its ECOM(s) from the broadcast traffic. An isolated network is highly recommended!!!

But this problem has been fixed in:

EZ Ethernet firmware v1.3.4
EZ EtherPLUS firmware v2.0.10

EZEthernet FAQ0022
24-Mar-2003
Q: Can multiple EZ Ethernet/EtherPLUS adapters be used on the same network as a DirectSOFT programming link to the same ECOM?
A: Yes, this will work. However EZ Ethernet/EtherPLUS performance will suffer considerably when you are online with DirectSOFT; particularly if monitoring data in DirectSOFT. Therefore if frequent used is needed for DirectSOFT is would be a much better idea to get a second ECOM and isolate the networks from each other.

EZEthernet FAQ0023
14-Mar-2003
Q: When I switch from IPX to UDP/IP protocol in the "PC to Panel Config" dialog, my panel doesn't show up in the list until I dismiss the dialog and reenter it.
A: This was a bug in the EZEther.DLL. Download at least firmware v1.3.3 from our website. (The latest .DLL is zipped up with the firmware in this file).

EZEthernet FAQ0024
11-May-2004
Q: Trying to download to the EZ Touch panel and getting, "Error opening HEIDevice."
A: The "HEIDevice" is actually the EZ Ethernet/EZ EtherPLUS card. Some things that cause this error are:

• The IPX protocol is not loaded for the NIC you are using. Therefore, load it (see EZEthernet FAQ0027 for installing protocols).
• You have 2 NICs on your PC. You will need to load IPX for the NIC with which you want to talk to the EZ Ethernet/EZ EtherPLUS card; and TCP/IP for the other NIC (see EZEthernet FAQ0027 for installing protocols).
• Make sure that your PC's IP address is on the same network as your EZ Ethernet/EZ EtherPLUS card. In other words, check your NIC's Subnet Mask setting.

EZEthernet FAQ0025 (deleted)

EZEthernet FAQ0026 (see also NetEdit FAQ0012; DS Data FAQ0087; DirectSOFT FAQ0180; EBC FAQ0052; ECOM FAQ0040; EDRV FAQ0010; ERM FAQ0034)
27-Apr-2004
Q: Getting various errors when attempting to use NetEdit to see or establish a link to a Host Ethernet device.
A: Here are know errors and their suggested solutions:

CAUTION: You may want to consult your Network Administrator before doing any of the solutions below! He/she may not want you to change your PC's setup at all!

• (1) "Error 10047" - This is an error from Microsoft Winsock. Formally it is known as "WSAEAFNOSUPPORT" and is described as, "Address family not supported by protocol family. An address incompatible with the requested protocol was used. All sockets are created with an associated address family (that is, AF_INET for Internet Protocols) and a generic protocol type (that is, SOCK_STREAM). This error is returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, for example, in sendto."
  
  Possible causes:
  (1)  IPX protocol is not installed for your NIC.
  (2)  TCP/IP protocol not installed for your NIC.
         (see EZEthernet FAQ0027 for installing protocols)
   
• (2) "Error 10051" - This is an error from Microsoft Winsock. Formally it is known as "WSAENETUNREACH" and is described as, "Network is unreachable. A socket operation was attempted to an unreachable network. This usually means the local software knows no route to reach the remote host. Very similar to Error 10065 WSAEHOSTUNREACH only this is usually related to IPX protocol."
  
  Possible causes:
  (1)  NIC is disabled.
  (2)  IPX protocol is not installed for your NIC (see EZEthernet FAQ0027 for installing protocols).
   
• (3) "Error 10061" - This is an error from Microsoft Winsock. Formally it is known as "WSAECONNREFUSED" and is described as, "Connection refused. No connection could be made because the target computer actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host---that is, one with no server application running."
  
  Possible causes:
  (1) You have a firewall software installed and enabled (e.g. ZoneAlarm).
       (a)  Uninstall it, or...
       (b)  Disable it, or...
       (c)  Poke a hole in it by making exceptions for the NetEdit3.EXE application or for TCP Port # 0x7070 (28784 decimal).
   
• (4) "Error 10065" - This is an error from Microsft Winsock. Formally it is known as "WSAEHOSTUNREACH" and is described as, "No route to host. A socket operation was attempted to an unreachable host. Very similar to Error 10051 WSAENETUNREACH only this is usually related to TCP/IP protocol."
  
  Possible causes:
  (1)  NIC is disabled.
  (2)  TCP/IP protocol is not installed for your NIC.
  (3)  Your NIC and the Host Ethernet device are on different subnets:
       (a)  Change your NIC's TCP/IP address to put it on the same subnet as the Host Ethernet device, or...
       (b)  Change your Host Ethernet device's TCP/IP address to put it on the same subnet as the NIC, or...
       (c)  Change the subnet mask in your network configuration settings.
   

• (5) "Error reading configuration values from device."
  First of all, there was a bug in versions of NetEdit previous to v3.1, that when you pressed the Query Network button this error could pop up. If this is the case then you just need to download a later copy (at least v3.1) of NetEdit from our website. If this is not the case then notoriously, this error is caused by one of the following:

  1. Is the EBC/ECOM/EDRV/ERM/EZ Ethernet  powered up properly? If not, make sure it is.
  2. Is the LINK GD (link good) light on? This indicates that the cabling is good.
  3. While using NetEdit, does the ACTIVE light blink when changing protocols from IPX to UDP/IP? This indicates that the EBC/ECOM/EDRV/ERM/EZ Ethernet  is seeing Ethernet packets.
  4. Is the IPX protocol loaded for the NIC you are using and enabled? (see EZEthernet FAQ0027 for installing protocols). There are fewer things to mess up with IPX, so it is the better protocol to use when trying to diagnose the problem.
  5. Is there just one NIC in the PC? If not, then it is possible that the packets are going out one or both NICs but being received by the “wrong” NIC as seen from NetEdit.
  6. Is there just one LAN connection loaded for the NIC? Multiple LAN connections (e.g. WAN network driver) can cause similar problems as with two NICs.
  7. Is the Network Number for the IPX protocol set to 00000000? If not, it must be, or it will not talk.
  8. Is the NIC running at 10Mpbs? (disconnect NIC cable; reboot PC; reconnect NIC cable). If it is trying to run at 100Mbps, it will not talk.
  9. Do you have "802.1p QoS packet tagging" enabled? If so, disable it (Device Manager, Network Adapter, Properties, Advanced). This adds information to the IPX and TCP/IP packets that is not understood by NetEdit.
  10. Is there firewall software loaded (e.g. ZoneAlarm)? This can interfere with the IPX and the TCP/IP protocol packets. We have to disable this software to get ours to talk properly.
  11. Is the network hardware verified? (cabling / hub / EBC/ECOM/EDRV/ERM/EZ Ethernet / NIC)?

  If none of these things fix the problem, then it is possible that the EBC/ECOM/EDRV/ERM/EZ Ethernet device is defective and you may need to send it in for repair.
   

• (6) Nothing shows up in the list, or not all devices show up in the list, or list shows incomplete data.
  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 LAN or WAN, 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 general, however, problems like this can also be caused by the things listed in bullet (5) above.
   
• (7) The "C" column indicates an asterisk (*), but there are no conflicts with addresses on the network.
  An asterisk in the "C" column means NetEdit "sees" an address conflict on the network. First, make sure that no IP addresses are the same between the devices that NetEdit sees on the network and the devices NetEdit doesn't see on the network (i.e. PCs, servers, etc.). Second, make sure none of the IDs of any of the devices in NetEdit are the same. If there are no conflicts, this could be caused by an older version of NetEdit. Therefore make sure you have at least NetEdit3 v3.6c or later.

EZEthernet FAQ0027  (see also DirectSOFT FAQ0183; DS Data FAQ0093; EBC FAQ0057; ECOM FAQ0043; EDRIVE FAQ0012; ERM FAQ0037; NetEdit FAQ0017)
27-Sep-2010
Q: How can I install IPX protocol for my NIC?
A:  You can find instructions on how to do this for your particular operating system by going to Start --> Help & Support and searching for "Install NWLink." Below are the instructions from Microsoft for doing this on a WinXP PC. The instructions are similar for other operating systems (e.g. WinNT, Win98, WinME, Win2K).

To install NWLink IPX/SPX/NetBIOS Compatible Transport Protocol
(1)  Open Network Connections:
       (a)  Click Start --> Settings --> Control Panel.
       (b)  Double-click Network Connections.
     NOTE:  You must be a member of the Administrators group to install protocols. Also, when IPX is installed it is installed for all your connections. If you don't want it installed for a certain connection, then right-click that connection, click Properties and, on either the General or Networking tab, clear the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol check box.
(2)  Right-click a local area connection, then click Properties.
(3)  On the General tab, click Install.
(4)  In the Select Network Component Type dialog box, click Protocol, and then click Add.
(5)  In the Select Network Protocol dialog box, click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, and then click OK.

IMPORTANT: The IPX/SPX protocol is not available on WinXP 64-Bit Edition, WinVista or Win7.

EZEthernet FAQ0028 (see also EBC FAQ0059; ECOM FAQ0051; EDRIVE FAQ0013; ERM FAQ0040; NetEdit FAQ0022)
22-Sep-2005
Q: I inadvertently changed the IP address of my Host Engineering Ethernet device and now NetEdit cannot find it, nor can I ping it. How can I get it "back?"
A:  It can be changed using IPX protocol:

1. If IPX protocol is not installed for your PC's NIC, then install it (see EZEthernet FAQ0027 above).
2. Select IPX protocol in NetEdit3 and edit the IP address.

EZEthernet FAQ0029 (see also EBC FAQ0061; ECOM FAQ0052; EDRIVE FAQ0015; ERM FAQ0042; HA-TADP FAQ0005; WinPLC FAQ0028)
29-Sep-2005
Q: Do any of your Ethernet devices support the next generation of Internet (IPv6)?
A:  No; nor do we have any plans to implement it at this time.

EZEthernet FAQ0030 (see also EBC FAQ0069; ECOM FAQ0055; EDRIVE FAQ0018; ERM FAQ0044; HA-TADP FAQ0006; WinPLC FAQ0032)
15-Nov-2005
Q: What types of Ethernet framing do your Ethernet products support?
A: All our Ethernet products (ECOM, ECOM100, EBC, EBC100, EDRV, ERM, EZ Ethernet, EZ EtherPLUS, HA-TADP and WinPLC) all support the following types of Ethernet framing:

• IEEE 802.2
• IEEE 802.3
• Ethernet II
• Ethernet SNAP

EZEthernet FAQ0031 (see also EBC FAQ0070; ECOM FAQ0061; EDRIVE FAQ0019; ERM FAQ0045; HA-TADP FAQ0007; WinPLC FAQ0033)
22-Feb-2005
Q: Are the Host Engineering Ethernet products compliant to AS ISO 15745?
A: No.

EZEthernet FAQ0032 (see also ECOM FAQ0114, EBC FAQ0086, EDRV FAQ0029, ERM FAQ0060, NetEdit FAQ0040)
11-Feb-2011
Q: What do the Ethernet Stats at the bottom of NetEdit specifically mean?
A:  These are stats that are reported up to the firmware from the hardware communication components. They are technically defined as:

Missed Fr - "Missed Frames" - A count of the packets missed due to overruns, unavailable buffers or a disabled receiver.
TX Coll - "Transmit Collisions" - A count of the packets which had a late collision while being received.
Lost Pkts - "Lost Packets" - A count of the packets discarded because they were too long or too short.
Bad Pkts - "Bad Packets" - A count of the packets which have bad CRCs (checksums).
Unknown - A count of the packets which contain invalid symbols, extra bits or resulted in a receiver overrun condition.
TX Errors - "Transmit Errors" - A count of the packets which could not be sent because the transmitter was unavailable for an extended period of time.