I have the jackpot board purchased from V1E flashed with the MPCNC firmware. I have the web interface up and working. The jog wheel X, Y, and Z all work. When I hit home (for any axis) the head moves maybe 10mm positive on that axis then throws an alarm. I’d expect it to move negative on the axis.
The end stop switches all work - bless the design decision to have those green LEDs on the board. What would make it home backwards though??? Seems like a firmware thing, but this is the factory flash. I compared it to github and it seems current. I have no idea where to look.
This is the behaviour that I would expect if the limit switches were either not plugged in, or are wired incorrectly.
The firmware says:
“Move towards the stops until they are triggered.”
Of course they already are. So you get zero motion.
Then the firmware says “Back off 10mm, then try again, but slower.” To get a more accurate measure.
The problem is that the stops are again, already triggered. It doesn’t like that because it knows it just backed off, so it throws an alarm because something ain’t right. It would probably accept a shorter range, but it would need to at least not be triggered before moving back towards the stops.
What’s that alarm look like in the web UI?
Do you have to be in the console to see it or is there anything that appears on the GUI to indicate this issue?
How about this: on the jackpot board, the end stop light should be off until it touches the end point. Like when the Z probe closes, the light goes on. Correct?
This system previously had an SKR pro 1.2 board, but I broke the USB port (long story) so I decided to upgrade to the Jackpot. On the SKR, hitting home on the touch screen would make the axis move negative immediately until the end stop closed. I guess that’s why I’m so confused here.
I wonder… I suspect that the switches are wired wrong.
Have the switches pressed, then try to home. See if the homing movement stops when the switches are released.
The firmware will expect normally closed switches, that is switches that conduct normally, but break the circuit when pressed. If you wired them the other way (conduct when pressed) you will not get correct behaviour.
The switches that V1 sells (and others I have seen) have 3 terminals. C, NO, NC. The 2 outside terminals should be wired to signal and ground. The middle terminal should not be connected.
(I don’t yet have a Jackpot.) IIRC, the LED should be off normally, then come on when the switch is pressed.
Been a while since I looked at FluidNC, so I don’t know, but GRBL-ESP32 does this if I try to home anything on my laser. (My laser has no end stops, so I never do this…)
Look at the console in the tablet tab. you should see what errors are coming out there.
this does sound like a limit switch issue. How are your endstops wired?
The x and y I can understand wiring it normally open vs closed. But for the z probe? I’m not sure how you would connect the probe from the store. Not like I can leave it “normally closed” clipped onto the bit while it is spinning.
That’s where I’m unclear. Do I hook the 2 pin probe to Probe or to Z? I’ve tried both, and it seems the same. Right now on the board, the 4 lights for the X and Y stops are lit. The Z one is NOT until I touch the contacts together. That seems backwards, and I’m thinking if I reverse it like I did with X/Y, homing for Z will work as well.
Probe goes to probe.
Z stop should be wired same as X and Y.
Jackpot LEDs should be on when NOT tirggered and off when they are triggered. @vicious1 - the Jackpot docs don’t read well at least for some-
Maybe instead “Will have the LED ON when not triggered, and LED OFF when triggered”
Check your config.yaml. The z axis should have cycle: 0. You don’t want the z axis to home.
z:
steps_per_mm: 200.000
max_rate_mm_per_min: 1200.000
acceleration_mm_per_sec2: 80.000
max_travel_mm: 100.000
soft_limits: false
homing:
cycle: 0
Instead you want to use:
M0 (MSG Attach probe)
G38.2 Z-80 F200 P0.5 (probe down set thickness )
G1 Z10 F900
M0 (MSG Remove probe)
M62 P1 (If used start spindle pin27 )
Probe is the Z minimum… aka clip to the spindle bit and the other contact is the sheet metal. What is the Z stop? Z maximum?? I didn’t think that was a thing?
Primo firmware, so far as I know, should not “home” Z. Don’t use the “home all” button.
Probing Z should have the touch plate set up.
The Primo does not normally use the Z stop switch. Older V1 Marlin used to home down to the touchplate, because the touchplate was connected to the Z_Min stop, but that wasn’t really intended.
LR firmware homes Z upwards, so maybe that behaviour is mimiced by the FluidNC firmware for the Primo.
Of course, you could add a Z stop at Z max. Wired the same way, connected to the Z stop, it should work.
I have seen several Z Max stops on Thingiverse/Printables. I don’t use one, my “home all” pretends that there is no Z axis to home.
What would make it home backwards though??? Seems like a firmware thing, but this is the factory flash. I compared it to github and it seems current. I have no idea where to look.
