The issue only occurs when I try to home . Again the x-axis works properly. Please let me know what you mean by NO and NC. When the switch is open the terminals should read an infinite impedance and zero when triggered and that is what I measured on all the switches including the x-axis.
NO means Normally Open and NC means Normally Closed.
For the microswitches, the NO (normally open) contact will be open circuit/infinite impedance until the switch is pressed, at which point it will be short circuit/zero impedance to the COM (common) pin. The NC (normally closed) contact is the opposite, short circuit/zero impedance to the COM (common) pin when the switch isnât pressed and then open circuit/infinite impedance once the switch is pressed.
For these systems, the correct wiring is to use the NC (normally closed) contact for the homing switches. The switch is shorted until the machine reaches the homing switch. The switch goes open-circuit, the controller sees this and stops the machine from moving. Itâs wired this way so that a fault in the cable will stop the machine moving, rather than preventing it from stopping at the home point.
Itâs important to note that these switches arenât end-stops or limit switches, theyâre homing switches. They are ignored during normal operation and only ever used for homing. If youâre only seeing issues during homing, thatâs because thatâs the only time the switches matter.
3 Likes
So at this point X should show up in the terminal. I bring this up because this can help, we know X works letâs make sure you are using $limits right. Open the terminal run $limits and watch the terminal window. Any of the 6 inputs we use will show a signal here, including the probe.
That is to be expected, the switches are only active when that axis is âhomingâ.
So to troubleshoot this step, when you just press Y+ does the axis move away from you?
If you home, while far away from the end, manually trigger the switch with your finger does that do anything to either side?
1 Like
@vicious1 Perhaps changing to using home switch or homing switch in the docs instead of limit switch or end stop as a term might help? This seems to be a pretty common form of confusion.
4 Likes
It is very confusing. After I reboot and moved the x and y axis I ran $limits and saw in the terminal all limit switches activating , x showed x , y0 and y1 showed y and z0and z1 showed z. After a reboot I ran homing on x then moved each axis independently and they worked. I then ran $limits and got no response when triggering the switshes by hand. I then rebooted and ran y homing and manually trigged the limit switch and got no response. After that I got an alarm signal and it disconnected from the network. Is it possible I ave a bas Jackpot3 controller or it was mis programmed by V1?
that was âhave a badâ not âave a basâ
I do not understand. I thought that the limit switch only worked during the homing process and the limit switch is hardware and the homing process is a software command.
The NC statement you made does not appear to be the way my x-axis works. The microswitch is in the open position and when triggered it is in the closed position and it seems to be working.
The Z Probe works that way (NO), but the X, Y & Z homing should be NC.
2 Likes
If you power down fully, give it a 2-3 minutes, then power back on does it home just fine?
How are you connecting to the jackpot, wifi - ssid fluidnc, or wifi home network, USB?
In the terminal type $SS, it will tell you at the top what is on it, for what board, and who wrote it.
I think it was a communication problem I powered down overnight then when I first booted up and let it sit for a while , my first command was to home the y axis and it worked. I still have more tests to run but I think I am zeroing in or the problem. Thanks for all your help Iâll let you know when it is fully functional.
1 Like
I manged to get the limit switches to work on the y-axis however I get an ALARM in the position where it generally says IDLE then in the upper right hand corner I the comment âHoming failed could not find limit switch within the serch limits. I have adjusted the screws where the switches hit but have no reference to know where the correct position is. Also, after the alarm triggers all other commands are locked out. Is there a way to clear the alarm so I do not have to reboot my system each time. I am operating wifi-ssid fluidicnc
Home one axis at a time to find out which axis is the issue. Easier to help with a fix when we know what axisâŚ$limits would normally tell us if all your switches are working.
The alarm is just saying a switch is not triggering.
Not sure which one you need but, Alarm and Error Codes | Wiki.js, 0X18, $X, should work
I am working just the y-axis
I donât understand how this works
When in alarm state. go to the terminal and type $X and that will clear the alarm
Thanks
1 Like
Can you take a video of what you are telling it to do and what its actually doing and post it? You will have to upload it to youtube or something like that then share a link here, you cant actually upload a video directly to the forum
If it only works sometimes, yet it is still homing then the switch is not getting triggered. When you home listen for a click, watch both sides for switch engagement. The little metal tab can get bent a little if neededâŚbut you absolutely should not need to the screw has plenty of travel, make sure you are actually hitting the screw on both sides.
I 100% agree that we could help better if we could see a video of what you are doing. Something is not right. $limits should work, and you should easily know if the switches are not triggering because it will hit the end of the belt holders and sound like it is grinding.