Ok so where do I even begin…
On initial install and set up, Easel connected as it should have after going through the machine set up. During the first test run of a simple 1.5" x 12" rectangle outline, the program was WAY off by roughly a factor of 2 for both x and y (resulting in what was going to be an over 3" x 24" rectangle ready to crash into my clamps).
After I paused the program in mid-run to diagnose, the X-Controller disconnected from my laptop and would not reconnect even after going through the manual port assignments etc. I went back and updated the CDM drivers which in turn, while restarting my computer, resulted in a BSOD failure during shut down. And I know what you are thinking; No, BSOD’s are not common to my laptop and no I have not installed any other hardware or software at all recently which would falsely make me accuse the X-Controller to be the culprit. Likewise, after the first disconnect, my USB ports refused to work for other external hardware (mice and printers) when I got frustrated and tried working on other projects,
After a 3 more subsequent BSOD’s and hours upon hours of computer diagnostics, firmware updates, USB power management modifications, etc etc etc just to fully make sure my laptop was in full working order - everything was back to normal and I could restart without BSOD… After plugging the X-Carve in, booting up Easel, and running that first test program again however, it disconnected and screwed my computer up back to the original state of hell.
I finally managed to reboot, connect to Easel, and run / tweak the 1.5 x 12 rectangle multiple times and found that if I decrease the size by roughly .5, it runs as it should meaning my X and Y motors are travelling by twice the distance they should in Easel (which is a separate problem to fix in my list)… but (big surprise ) the X-C disconnected while I was playing with the settings in Easel and here I am.
One thing I know for sure… Though the drivers state they updated correctly, “X-Controller” is not listed in my device manager as the troubleshooting states it should, it simply lists it as a generic “USB Serial Port (COM4)” which leads me to believe there is a computer to controller communication error.
Suggestions? I see a lot of topics with similar issues/solutions running the Arduino, but what about the X-Controller solutions? As an engineer, I like to think I have at least an educated state of mind dealing with technical problems of this nature but I’m on day 2 with nothing but failure especially when this thing is now BSOD’ing my laptop of which I have a lot of important work on.