I am running v0.8.00 with a Corgi board running FluidNC v4.0.2. The device operates properly using the FluidNC webUI.
A problem I am seeing is that the Y-axis jogs in the negative direction when pressing Y+ or Y-. X and Z work properly.
Just FYI for FluidNC users: I can home all axes individually on the move tab. When I press the home all button on the jog tab I get a homing error saying the limit switch could not be found within range and none of the axes move. I thought that this was just a Millmage problem, but when I tried it in the FluidNC webUI, I get the same error.
You are right for sure. Looked right at that and it did not register.
In the Console window…
$H Homes everything, Zaxis first. $HXYZ should do the same.
$HZ Homes only Z.
$HX and $HY, ditto.
Test all of these combinations using the Console window. Let us know if they all act as predicted. This will help us know if the problem is in the controller, or the output generated for your controller.
check all limit switches on board , try manually activating each limit switch and see if it lights up or turns of on the board, hold for about 2-3 seconds per limit switch , do Z 1st, i had similar at one stage and it was faulty limit switch, wasn’t registering that it had been activated
sounds like cable on board wrong way , remove y cable and turn around , this normally sorts it as its sending wrong signal to stepper it happened to me when i plugged steeper’s into board flipping cable solved the problem
in the FluidNC axis setup check max travel and most likely you have the seek setting in the homing cycle set to small, causing seek errors (time out) try 1.1 or something greater than 1
I believe that I may have found the root of the problem. In FluidTerm I did a $H and got better failure information. It reported that homing could not be performed because there are axes without homing switches. I only use X, Y, Z, and A axes but when I reset the controller in FluidTerm, it reports values for B and C. My config has them commented out. I even created a test config where they were deleted completely yet the booting process still reports values for them. The Corgi board has 6 motor drive ports so it seems FluidNC knows that somehow and wants to use them. I searched the wiki and cannot find how to set the axis number.
OK, the config file was definitely the issue. I edited my config to delete axes B and C and saved with a new name. Then in FluidTerm I did the normal ctrl-U with the new name and then ctrl-R to reset the controller. B and C still showed values at start up. I then realized that despite the upload, if you use a file name other than config that you have to tell FluidNC. I opened the webUI and changed it there to the new name. I then restarted the controller and voilà , B and C were gone. I could then do a home all. It still wants a homing pin for axis A which I don’t have and won’t have until Millmage supports the A axis. I will just comment the A axis out for now.