Windows 7 & PLC Ethernet Connections

It could be worse, you could be using allan bradley

I was going to send you the the manufacturer's site but I see you're already there

Thanks! Yes, this is an on-going issue....

Thanks! Yes, this is an on-going issue...

JCChiefEng,

Looking at your narration of the issue, this does not seem to have anything to do with windows 7 or the "unknown network", since you said that communications are OK with a router in between, and further that the serial port works fine [with windows 7], Or did I hear you say that?

Also, I wonder what it means for the ntework to freeze; but I guess you needed to give it more time to sort it self out. This is common with Windows 7 when the system does not have ample RAM, or is running low on Hard Disk space, or, may be, some 'heavy' autostart programs run start up routines at logon.

I have not used EZAutomation PLCs and software. Instead I have used Siemens S5 and S7 PLCs, with SIMATIC Step 7 and WinCC software. In Step 7 and WinCC communications configuration, one needs to explicitly specify whether the TCP/IP connection to PLC is through a router/ gateway (by checking a box in the configuration dialogue).

I get the feeling that the commincation configuration in EZPLC Edit / EZTouch may have, by default, assumed that the TCP/IP communication is via router. Therefore, I would suggest that you review the communication settings from EZPLC Edit / EZTouch (and not from Windows 7 !!) and ensure that no option specifying communication via a router is activated; and then try again.

If problem persists, then I suggest you seek expert technical support from EZAutomation. Since, I read from the forums that "Innovative Logical Controls, LLC, uses the AVG / EZAutomation brand of PLC, exclusively." you colud be worthy of much attention from EZAutomation.

Good luck.

starmodi-

Thanks for your post. Unfortunately, it is the Windows 7 that is causing the problem. I have been working with EZAutomation ethernet for years without any problems. All works well with my XP machines. What I will agree with is the possibility that there may not be enough memory in the Win 7 machine. I will investigate that further.

The fact that Win 7 needs a router to communicate with devices with static IP addresses is a problem. I believe if I resolve that issue, all should work fine.

Any additional thoughts on the router vs. no router issue would be appreciated! Thanks.

When Windows 7 (or any OS for this matter) communicates on any Ethernet network using TCP/IP, it does not care - infact does not need to know - whether or not there is a router on the network. All that needs to happen is for your application (in this case EZPLC Edit or EZTouch) to let Windows 7 know the destination IP, which in this case is the static PLC IPv4 address. Note that, by using static IP addressing, it saves you from alot of hassles associated with having to put up a server on your network to resolve IP addresses against computer names. Dynamic IP addressing would require a server on the network to offer DHCP, DNS, ARP, RARP, etc. services . Therefore, using static IP addresses for the setup is not a problem at all.

It is a well known phenomenon that Windows 7 seems to be highly upopular at the moment, infact even so is vista (and windows 7 is not very different from Vista); to the extent that may users prefer to go back to 'good old' XP. But, trust me, you have to let Win 7 off the hook for now, because it has not done anything wrong for you as yet. (... am not the Microsoft PR incharge of WIndows 7 defence... )

I'd suggest you look at two issues:

1. When connecting a PC/Laptop directly to the PLC using Ethernet, one needs to use a special type of cable known as the cross-over, rather than the ordinary one - known as a straight-through - which is used when connecting computers and PLCs via a central hub / switch/ router. So, if your cable is running from your PC or Laptop directly to the PLC, then you need to ensure that you are using a cross-over Ethernet cable. Otherwise, if you have any hub,switch,router, etc. between your computer and the PLC, then you need to use the common straight-through Ethernet cable.
2. If physical connectivinty / wiring is OK, then you need check your communication settings in EZPLC Edit / EZTouch to ensure that there is NO default or accidental selection or ativation of the option of reaching the PLC via a gateway or router.

That's it for now.

starmodi-

You seem to be well versed in the Microsoft products, thanks.

I have been in the controls industry for "many" years working with building networks.

All of my networks function until I connect the Windows 7 laptop. I have even taken down a local network at one of my customer's sites by attempting to connect to their network wirelessly, but that's another story.

FYI-On all XP networks I connect to all PLC's through an unmanaged switch at each PLC station, so I do not need the crossover cable. Windows 7 is the only problem. The EZPLC communicates without error at all of my sites with XP or without the PC when I leave the site. Windows 7 is the only problem!

Please, if you are going to post again, give me an education on Windows 7. It is the Windows 7 issue of automatically creating a network that I need resolved. If you can, please explain how to turn off this function and allow me to create my own network connection when I want to. Thanks!

XP was good with a direct connect

Please expand this; what are you implying?

A serial port and cable is the connection method unless your PLC has the Ethernet option, you will not be able to set up this feature and use it. All com setup is completed using the serial port and cable. Your PC must communicate through a supported "COM" port on your PC (COM1, COM2, etc...)

In regard to EZTouch, the PLC and EZTouch must communicate on the same protocol. You may use Ethernet if the option is available. The PLC's must have static IP addresses and must be programmed into the EZTouch to communicate.

.

He is using cat5 connections, very simple ether networks

the security of w7 isn't compatible with the plc's & the vendors haven't caught up

not a big enough market for windows to care about very much

I now this thread is quite old, but I run into the same trouble with Windows 7. I could not find my answer through forums, but after a lot of reading found the solution. So, I'm posting for others to get help.

Problem is that laptops with Win 7 might have several other network connections other than LAN/Ethernet, wireless for instance, VMware or VirtualBox (if you installed), or even some duplicated LAN (my case), and Windows pools through what is available for configuration (although the physical connection might not be available, some new laptops seem to have several network connections because there are several chips inside fulfilling functions).

Story short: You need to disable (at least temporarily) the other network connections (Control Panel, right click). Go to your business and you should be done.

BTW, it happened to me when trying to configure the BOOTP for a Micrologix 1100. So, it is not the software or the PLC, it is the way Windows 7 handles the bootp priority for configuration.