probably it was showing properly the lock in but not sending the right pulses... the way its wired it sends 1 pulse for each 10 pulses but is not a 1/10 of the frequency only its 1/10th of the duty cycle also...
basicaly if your frequency without dividing is 10khz the cycle time is 0.0001s so duty cycle is 50us.... i'm saying that when dividing this way you still send the same pulse but you wait ten pulses to send it again...probably it doubles the pulse width.. maybe not... if divide by 100 same pulse but one each 100 pulses..
I could be wrong...
I don't know what are the wave forms getting out of yours boards since i don't have a copy of them here... I'm pointing out that is different from stans diagrams and the original card configuration... from mine and from theory too... haha
i could try to make this wrong circuit to check... later i do it..
as i'm saying... to verify if its locking in...
you got to look at the pin 14 and pin 3 at the oscilloscope and they must be lock in... at my circuit the led turns off as it lose lock... way to see the lock in is to select the trigger only of one of the channels of the oscilloscope, such that if there is lock condition both waves still locked.. if you change the frequency going into pin 14 it should be able to follow it locked... when it looses lock the channel with no trigger will disappear or start to walk on the line in respect to the other... and led will turn off...
simple as that
As I'm looking at the datasheet, it seems to me that it doesn't really change the timing as much as pin 12 is used for the trigger pin when you have 4017's in series. Pin 12 from what I read is still the same timing as the other pins such as 11, but basically is the 10 count where 11 is the 9 count.
I have been somewhat concerned about the duty cycle however. It didn't seem to tune right. Additionally, I have another PWM circuit by ZeroFossilFuel when seems to provide much better current draw at the same frequencies.
TS