For years I couldn’t use Motion because it always got the “cannot connect” error and even though Will and/or support tried to help, it was not to be. Then my refurb PC died and I got an openbox new HP at Bestbuy and when I installed Motion it worked. I never used it for production but it did talk to my machine at least.
As the last stage of the HDX upgrade the instructions say I need to update the firmware(?) using Motion. The installed version connected but since there was a newer version of Motion available I went ahead and “upgraded” it before proceeding. Of course the new install broke Create and I am back to “cannot connect” status. Rebooted. Same.
Windows 10 on a 1 year old HP desktop. This is a Sparkfun/Shapeoko machine upgraded to XL and then upgraded to new GRBL 1.1f using the Carbide upgrade program. My beloved UGS attaches just fine and I can jog around normally (even with Z axis although I am going to have to reverse direction).
Questions are:
-
Do I really need to do anything? I am afraid to do a $H(ome) given the warnings.
-
Is there a way to do the necessary HDZ updates via other means (command line, other software)? Is it just some $ commands?
-
Is there a way to fix Motion (although this is a low priority for me)