Just a courtesy update. I've sent my box back to Sherline and they have been checking it out on EMC2. They found one "bad" cable, but it was Y and not Z or A which are my issue. Just to recap my issue and what testing I did:
The issue: When jogging Zed down, it will work 100% fine. When CHANGING from down to jog up (not rapid jog btw) it fails to change direction until you try it a few times. Eventually it will change to going up, and then every jog up from that point (until I ever jog down again) is 100% fine. So my whole issue is just changing from down to up in the Zed direction. This failure happens not just with jogging by the way. It fails during a full run of a cut too, causing my Zed to be actually lower than mach3 thinks based on DRO's. DANGEROUS/VERY BAD!!!
The testing I've tried:
- Swap out the Zed cable of the CNC driver box to the A cable. I of course changed the pin out settings also in mach3 so A parallel port pins now controlled Zed. Both A and Zed fail the same way. That rules out the parallel port signal for Zed alone being bad. A and Zed could both be bad but seems unlikely.
- Tried swaping Zed and X. The failure described above follows the Zed cable output of the CNC driver Box. So that rules out the motor being bad.
- Verified my settings in motor tuning (that I got from the mach3 FTP site with xml setups for different machines) was the same for X,Y, and Zed
- Oddly if you let the CNC box sit off for a while, the issue goes away until it's allowed to warm up for 15-20 minutes.
Sherline has tested my box, but I've not yet been able to ensure they were really testing for the right failure. I'm still in talks now live rather than email to try to make a break through. They don't have a computer tech yet, or at least one that I've been able to talk to. Which is very interesting because of one more piece of information I haven't mentioned yet.
See the photo below. When looking at the circuit board inside the box for cold solder joints or anything bad, I noticed a strange thing. X and Y have PIC16F627 chips with a white dot on them. Zed and A have the same chip (in a socket btw) that has NO WHITE DOT!. The person I talked to so far at sherline didn't know why, but did confirm that the chips are programmed with different firmware! So the mystery is why would two of the linear axis' be using one firmware, and one other linear axis (along with the rotational A axis) have different firmware? And does this firmware mean I need different motor tuning settings for Zed compared with X and Y? Recall that Zed works mostly. Just has issues with changing direction. So is there a strange timing issue with just the Zed and A firmware?
Does anyone know of a good test with a logic analyzer to do on the direction change signal versus the square wave pulse train for stepping? What is the critical separation in time between those two different signals? I have a logic analyzer so I could monitor the parallel port. But I'm more thinking I need to monitor whats coming out of the CNC box.
Justin