Testing Homing Switches

[mickv]

Derek,

Tried my first homing switch test tonight by hand per your "show verbose output" Youtube video. Got the PnY and PnX reponse, but no Z. After checking all my connections at the switch and shield, still nothing. I swaped the Z switch with the X switch - the X worked, Z didn't, so it appears the switch is OK. Swaped connections between the Z and X at the CNC shield and X worked, Z didn't, so that would tell me the wires are OK. Seems like my connection for the Z+ terminal at the CNC shield isn't responding. Does this sound right? 

Also, if this is not the right place for me to be asking these newbie questions, let me know please.

thanks again
Mick

[Bruce]

I guess a final test would be to simply short the Z+ pins at the shield. If that doesn't work make sure the shield is plugged into the Uno good, no pins misaligned or bent. Can you move any of the motors with the jog buttons?

[stever]

Hi Mick,
I just recently finished my carve king and had the same issue. Derek said to move the z homing switch down to the pins labeled SpEn. It showed up in ugs for me after that.

-Steve

[mickv]

Yes, I am able to move all the motors with the jog buttons.

Steve: I will take a look at repositioning the Z switch on the board as you mention.

Thanks much!!
Mick

[Derek the Admin]

I'm going to have to look into this as this isn't our default build. We're investigating this morning to see if one of our computers got the wrong file for flashing.

[mickv]

Steve (and Derek): I switched the Z to the SpEn terminal on the shield as suggested and that did the trick in acknowledging the Z switch. THANK YOU!

Mick

[m2]

I just had the same thing happen to me with the Z switch. Switched to the spnen port and recognized the Z switch right away. Was able to home my switches after doing this. Not sure if this is correct but it works.

[razman]

Same thing is happening for me. If we find out anything let me know. In the meantime homing seems to be working for me at the SpnEn pins.

[Derek the Admin]

Thanks for letting me know. I'm investigating to see what in the world is happening. Even verified all of our hex files again. I'm seeing it this all tracks back to a common date and if so, it would mean that someone flashed the laser hex file instead of the "normal" hex file. Nothing else would be affected other than that switch location being moved if that's the case.