I don't have as many pictures as I'd like to share, but our furnace went out this weekend so any time I spent in the shop was not focused on taking a million pictures. The bedrooms got into the low 50's and the basement into the mid 40's (it is low 20's outside). Not terrible, but much less than ideal.
I re-imaged the computer back to a bare Win 10 machine. From there I installed Mach 4 and configured it for use with the Ethernet smoothstepper. I am very impressed with the menus in Mach 4. They seem to be laid out intuitively rather than the haphazard placement of settings in Mach 3. I did identify a few potential wiring errors on the I/O during some initial testing that I need to dig deeper into, however as it stands right now, each drive correctly receives the control input pins, as well as an enable signal. Each drive also sends back a fault signal and the encoder index output. This output gives actual speed feedback to mach for the spindle (pretty cool) as well as enables home to switch then to encoder marker which is more accurate than the switch alone. All the limit/home switches work properly, the ESTOP is working, and the pendant MPG is reading into Mach (although it seems to count by 4's?). I know that my "operator station" input (start, hold, and stop buttons) seems to only have the start button operational at the moment, and the pendant resolution selector switch seems to have the X10 and X100 inputs stuck on. I have not tested any of the outputs including the electronic gearing relays, the relay outputs for the 120V outlets on the side of the panel, or the power drawbar solenoid outputs. The panel internal outputs such as the drive enable and fault reset pins work perfectly.
I loaded Putty, a free terminal emulator, onto the computer as well as my laptop, and after an hour of fiddling with it, got the two PCs talking to each other over RS485. From there I connected the computer to the drives, but when I tried to connect, Ultraware (Allen Bradley utility for servo drive configuration) would just freeze up. It took me a little while to realize that every drive had its network node address set to node 0. When Ultraware tried to talk to the X axis drive, they would all answer at the same time. I had to power each one on, one at a time, to set them to different node addresses. Now whenever I open Ultraware it automatically connects to each drive that is powered on. This is hugely helpful for troubleshooting since every piece of data from the drives is exposed for monitoring and adjustment. Since I got the network working I have not had a single issue with it. If I can figure out Mach 4 LUA then I feel very confident that the networking of the drives will be very reliable.
I tested some jogging with Mach 4 and found it to be a bit unresponsive to keyboard inputs compared to Mach 3. There was a barely noticeable delay when starting and stopping a jog compared to the key press. It probably doesn't matter, but coming from industry it makes me a little uncomfortable when you can "feel" the software between you and the machine. My other, much more major, issue with Mach 4 is that it hangs after 3-5 minutes of running code. This is the demo version right now,
but it is not the timeout (I have seen the timeout message and know what it looks like). The machine will be running and BANG, all the servos stop dead but remain enabled. The software ESTOP does not shut them down (thankfully I also have a hardware ESTOP to kill drive power). The Mach 4 greys out and the cursor is the blue Win 10 waiting circle. This happens repeatably both running Artsoft sample GCode as well as a program I used to machine the spindle housing. The program never recovers and has to be closed with task manager. The Smoothstepper remains waiting for Mach signals and won't reconnect when Mach opens leading to me having to power cycle the machine.
At first I thought that this was due to an underpowered computer. The VersaView 5400 computer that is on the machine runs on a 4 core Intel Atom E3845 chipset @ 1.90GHz. It has 4.0Gb of memory and runs Win 10. This is very much on the bottom edge of the system performance requirements for Mach 4 (especially the memory), but there are posts in MachSupport about people not having issues running mach on much less powerful computers without issues. During loading of Mach 4 the CPU is between 70-80%, at idle it is 30-40%, when loading a Gcode program 70-80% and while running the machine it holds quite steady at the mid 60's%. The memory utilization never got above 2.0Gb (50%). This all seems like the computer was doing just fine, but I was convinced that this computer just didn't have the guts to run Mach 4.
To test the situation, I installed the same version of Mach 4 and ESS utilities onto my laptop (Intel i7 6700HQ 3.5GHz, 32Gb of memory, Win 10). I copied the configuration file from the CNC computer to my laptop and connected to the smoothstepper without issues. I ran the same test files and sure enough, Mach 4 crashed about 5 minutes into the code same as the other computer. I tried this several more times and had the same results. I then tried running the machine from Mach 3 on my laptop and it finished the 2 hour and 20 minute program with no issue whatsoever.
I am posting some questions about this on the Mach support forum, but if anyone here has experience with Mach 4 I'd appreciate any input. My next test will be to install Mach 3 on the VersaView computer and try running the machine that way. I know that the programs are very different, but if the computer fails to work with Mach 3 then I would believe it to be underpowered.
Here are some Mach 4 screenshots. Not super interesting, but hey, it's all I have.
Pink wanted to know why I was in the shop rather than in bed with the electric blanket!
Zoey needed to investigate as well.