All,
I have another problem with my setup. I believe this new problem was due again to Chilipeppr leading to a crash (physical) and now I have a physical drive problem. Initially when loaded, chillipeppr would not connect (json issue i thought, so I did multiple reboots (software and hardware).
Long story short, my R7 plunged deeper than it should have on the dry run (no spindle speed) before I could E-stop it. After this problem I noticed chilipeppr was not showing the standard gcode in the left bar, and the interface was overlapping (not showing the entire screen). I did multiple computer re-sets, powered down the Tiny-G, reloaded the g-code and known good gcode. Nothing fixed this issue.
Disgruntled with the garbage Chillipeppr was displaying, I figured I’d just run the code and see if it was displaying incorrectly. When I tried to travel the axis, I noticed Y (right) moved correctly, but Y (Left) was stationary. X traveled reverse from what it was supposed to and had been. When I moved the Z, the Y (Left) would move correctly, but not both L/R sides. It also “sounded” like the motors were moving faster than before. I’m not sure if the crash ruined the Tiny-G.
I haven’t done any troubleshooting as I was about to grab a hammer and start smashing anything connected to Chilipeppr.
Suggestions? I’m leaning HEAVILY towards Mach4 and Smoothstepper due to nearly every problem I’ve had with this machine was chillipeppr driven. This was being run on a Windows 7 laptop that had been dependably running code previously. I hadn’t touched the R7 in about 4 months prior to this and had a successful run previously.
Corey