Thanks for more input:
<Mike>
I did use a Crossover cable. As I said, the XP setup has been working fine. The only initial problems I had when setting up the machine several months ago, was my encoders were not showing a full 5v. at initial start-up. I found the problem after much searching. My dspmc controller, I/O boards, + 24v ps, and 5v ps, are in a rack mount chassis. All the machine cabling to the controller chassis, is DB9 connectors and shielded cable at the rear of the chassis. The office XP computer would connect immediately to the Ethernet when I was testing the controller chassis in my office. When it was in the Mill, and all the cables connected, the Ethernet icon showed “no cable connection.” By trial and error, I eventually tested the voltage on the encoder inputs, and discovered that at start-up, the voltage was only 3.2 volts at the encoder terminal. If I disconnected all the encoder plugs, the Ethernet would connect immediately. If I then re-connected the encoders while the Ethernet icon was showing good, I could then start Mach3, and the machine would work OK. Once the machine was shut off, and then restarted, the “Ethernet cable not connected” problem returned. My fix was to run separate +5v/GND wires to each encoder board (the J2, J3) connection to a second Molex 5v/GND connector in the chassis to the 5v. power supply. Previously, the source of the 5v signal originated at the 7535 board 5v. logic terminals, but this is not sufficient at startup, as I discovered.
---
<Peter 81>
I looked on the Newegg site for PCI Ethernet boards, and read the reviews. The majority of reviewers had changed the motherboard Ethernet connection to a PCI board Ethernet connection to solve problems.
I did a re-install of XP on the computer since my first post. I also used “Driver Dectective” to update all the drivers it could find, which included the Ethernet connection. However, before I did the XP install, I used “Wipe Drive” to totally erase the HD, and then did a full XP install. The HD is brand new, as is the computer. The same computer is now working fine, and the Ethernet connection is immediate. The Mach3 program and dspmc works smooth as silk.
It would appear now, the physical Ethernet port could not be cause of the problem I was having. Before re-installing XP, and getting
everything working again, the port was definitely suspect.
When doing the Win7 install, I did not use “Driver Dectective” for getting the latest drivers. That is now, the major suspect to Win7 not working properly with the Ethernet connection.
Thanks very much, Mike and Peter. It is great to have feedback on these kind of endeavors. Sometimes, working alone on a problem, we overlook the simple answer. Other input really helps.
Regards for now,
John M