There are 16 messages in this thread.
You are currently looking at messages 0 to 10.
I bread boarded my PLL yesterday. I was able to get it to lock just fine on a multivibrator running at 33Hz. I was able to solve the jitter problem by using a very large value for C1 (1000u). However, when I attached my cameras to the loop, (one running at 22.2fps and the other running at 25fps) the loop would lock at a frequency slightly above the camera speed ~39Hz. The camera has a contact that closes ~5ms every frame advance. I tried using the contact to pull to ground, and to pull to rail. I got the same result either way. Any suggestions? Thanks, Chris Maness
On Feb 28, 7:25=A0am, Chris <christopher.man...@gmail.com> wrote: > I bread boarded my PLL yesterday. =A0I was able to get it to lock just > fine on a multivibrator =A0running at 33Hz. =A0I was able to solve the > jitter problem by using a very large value for C1 (1000u). =A0However, > when I attached my cameras to the loop, (one running at 22.2fps and > the other running at 25fps) the loop would lock at a frequency > slightly above the camera speed ~39Hz. =A0The camera has a contact that > closes ~5ms every frame advance. =A0I tried using the contact to pull to > ground, and to pull to rail. =A0I got the same result either way. =A0Any > suggestions? > > Thanks, > Chris Maness Which phase detector are you using? An XOR can lock to ratios of numbers of the input signal like 2/3 A tristate phase frequency comparator is bothered by contact bounce.
Chris wrote: > I bread boarded my PLL yesterday. I was able to get it to lock just > fine on a multivibrator running at 33Hz. I was able to solve the > jitter problem by using a very large value for C1 (1000u). However, > when I attached my cameras to the loop, (one running at 22.2fps and > the other running at 25fps) the loop would lock at a frequency > slightly above the camera speed ~39Hz. The camera has a contact that > closes ~5ms every frame advance. I tried using the contact to pull to > ground, and to pull to rail. I got the same result either way. Any > suggestions? > > Thanks, > Chris Maness Two camera's in line with different fps ? how do you expect it to lock properly?
On Feb 28, 7:39=A0am, MooseFET <kensm...@rahul.net> wrote: > On Feb 28, 7:25=A0am, Chris <christopher.man...@gmail.com> wrote: > > > I bread boarded my PLL yesterday. =A0I was able to get it to lock just > > fine on a multivibrator =A0running at 33Hz. =A0I was able to solve the > > jitter problem by using a very large value for C1 (1000u). =A0However, > > when I attached my cameras to the loop, (one running at 22.2fps and > > the other running at 25fps) the loop would lock at a frequency > > slightly above the camera speed ~39Hz. =A0The camera has a contact that > > closes ~5ms every frame advance. =A0I tried using the contact to pull t= o > > ground, and to pull to rail. =A0I got the same result either way. =A0An= y > > suggestions? > > > Thanks, > > Chris Maness > > Which phase detector are you using? > > An XOR can lock to ratios of numbers of the input signal like 2/3 > > A tristate phase frequency comparator is bothered by contact bounce. I am using Comparator II for edge detection. Yes, there might be some bounce. How can I clean up the signal? Also, with the 33Hz multivibe there is a extremely low frequency FM'ing ~1/2Hz. Should I try a smaller C2 in combination with a bigger R3? Correction: the 1000u is C2. Thanks, Chris Maness
On Feb 28, 7:57=A0am, Jamie <jamie_ka1lpa_not_valid_after_ka1l...@charter.net> wrote: > Chris wrote: > > I bread boarded my PLL yesterday. =A0I was able to get it to lock just > > fine on a multivibrator =A0running at 33Hz. =A0I was able to solve the > > jitter problem by using a very large value for C1 (1000u). =A0However, > > when I attached my cameras to the loop, (one running at 22.2fps and > > the other running at 25fps) the loop would lock at a frequency > > slightly above the camera speed ~39Hz. =A0The camera has a contact that > > closes ~5ms every frame advance. =A0I tried using the contact to pull t= o > > ground, and to pull to rail. =A0I got the same result either way. =A0An= y > > suggestions? > > > Thanks, > > Chris Maness > > =A0 Two camera's in line with different fps ? > =A0 =A0how do you expect it to lock properly? No, I have two cameras that I would use at different times. Not in series. I am designing the circuit because most small gauge film cameras run "wild" and I am designing the tape to slave off of the "wild" cameras at the expense of some pitch shifting. The design will ultimately convert the ~24Hz pulses to ~60Hz pulses with a proportional error. When the film is scanned in to a frame accurate file @ exactly 24fps, the tape (perforated tape with a film base) can be played back at exactly 24fps from a crystal reference. The end product is lip sync sound. Thanks, Chris Maness
On Sun, 28 Feb 2010 07:25:56 -0800 (PST), Chris <c...@gmail.com> wrote: >I bread boarded my PLL yesterday. I was able to get it to lock just >fine on a multivibrator running at 33Hz. I was able to solve the >jitter problem by using a very large value for C1 (1000u). However, >when I attached my cameras to the loop, (one running at 22.2fps and >the other running at 25fps) the loop would lock at a frequency >slightly above the camera speed ~39Hz. The camera has a contact that >closes ~5ms every frame advance. I tried using the contact to pull to >ground, and to pull to rail. I got the same result either way. Any >suggestions? > >Thanks, >Chris Maness Contact bounce? John
On Feb 28, 8:23=A0am, Chris <christopher.man...@gmail.com> wrote: > On Feb 28, 7:39=A0am, MooseFET <kensm...@rahul.net> wrote: > > > > > On Feb 28, 7:25=A0am, Chris <christopher.man...@gmail.com> wrote: > > > > I bread boarded my PLL yesterday. =A0I was able to get it to lock jus= t > > > fine on a multivibrator =A0running at 33Hz. =A0I was able to solve th= e > > > jitter problem by using a very large value for C1 (1000u). =A0However= , > > > when I attached my cameras to the loop, (one running at 22.2fps and > > > the other running at 25fps) the loop would lock at a frequency > > > slightly above the camera speed ~39Hz. =A0The camera has a contact th= at > > > closes ~5ms every frame advance. =A0I tried using the contact to pull= to > > > ground, and to pull to rail. =A0I got the same result either way. =A0= Any > > > suggestions? > > > > Thanks, > > > Chris Maness > > > Which phase detector are you using? > > > An XOR can lock to ratios of numbers of the input signal like 2/3 > > > A tristate phase frequency comparator is bothered by contact bounce. > > I am using Comparator II for edge detection. =A0Yes, there might be some > bounce. =A0How can I clean up the signal? =A0Also, with the 33Hz multivib= e > there is a extremely low frequency FM'ing ~1/2Hz. =A0Should I try a > smaller C2 in combination with a bigger R3? > > Correction: the 1000u is C2. > Since you know the rough frequency you have options: (1) A one shot that has a time a little over 1/2 the cycle time can be made so that is only accepts the switch closures that are about far enough apart. (2) A few stages of HC14s connected one to the next by a low pass RC filter will add delay but will also take the bounces off. (3) Your VCO can be running at a multiple of the input and you can use logic from the divide down counter to only allow edges at the right time through. Basically this would mean to use a flip flop that is cleared just before the time the edge is expected and gets clocked by the edge to go high. > Thanks, > Chris Maness
On Feb 28, 1:56=A0pm, MooseFET <kensm...@rahul.net> wrote: > On Feb 28, 8:23=A0am, Chris <christopher.man...@gmail.com> wrote: > > > > > On Feb 28, 7:39=A0am, MooseFET <kensm...@rahul.net> wrote: > > > > On Feb 28, 7:25=A0am, Chris <christopher.man...@gmail.com> wrote: > > > > > I bread boarded my PLL yesterday. =A0I was able to get it to lock j= ust > > > > fine on a multivibrator =A0running at 33Hz. =A0I was able to solve = the > > > > jitter problem by using a very large value for C1 (1000u). =A0Howev= er, > > > > when I attached my cameras to the loop, (one running at 22.2fps and > > > > the other running at 25fps) the loop would lock at a frequency > > > > slightly above the camera speed ~39Hz. =A0The camera has a contact = that > > > > closes ~5ms every frame advance. =A0I tried using the contact to pu= ll to > > > > ground, and to pull to rail. =A0I got the same result either way. = =A0Any > > > > suggestions? > > > > > Thanks, > > > > Chris Maness > > > > Which phase detector are you using? > > > > An XOR can lock to ratios of numbers of the input signal like 2/3 > > > > A tristate phase frequency comparator is bothered by contact bounce. > > > I am using Comparator II for edge detection. =A0Yes, there might be som= e > > bounce. =A0How can I clean up the signal? =A0Also, with the 33Hz multiv= ibe > > there is a extremely low frequency FM'ing ~1/2Hz. =A0Should I try a > > smaller C2 in combination with a bigger R3? > > > Correction: the 1000u is C2. > > Since you know the rough frequency you have options: > > (1) > A one shot that has a time a little over 1/2 the cycle time can be > made so > that is only accepts the switch closures that are about far enough > apart. > > (2) > A few stages of HC14s connected one to the next by a low pass RC > filter > will add delay but will also take the bounces off. > > (3) > Your VCO can be running at a multiple of the input and you can use > logic from the divide down counter to only allow edges at the right > time > through. =A0Basically this would mean to use a flip flop that is cleared > just before the time the edge is expected and gets clocked by the edge > to go high. > > > Thanks, > > Chris Maness I was thinking about #1 just using a NE555 for a one shot @ 1/2 a cycle. Also, the NE555 (1.5 cycle one shot) could be used with an AND gate to shut the output off when there is no signal from the camera. Starting to feel like all of this would be better done in software. Thanks, Chris Maness
On Feb 28, 10:25=A0am, Chris <christopher.man...@gmail.com> wrote: > I bread boarded my PLL yesterday. =A0I was able to get it to lock just > fine on a multivibrator =A0running at 33Hz. =A0I was able to solve the > jitter problem by using a very large value for C1 (1000u). =A0However, > when I attached my cameras to the loop, (one running at 22.2fps and > the other running at 25fps) the loop would lock at a frequency > slightly above the camera speed ~39Hz. =A0The camera has a contact that > closes ~5ms every frame advance. =A0I tried using the contact to pull to > ground, and to pull to rail. =A0I got the same result either way. =A0Any > suggestions? > > Thanks, > Chris Maness low pass filter the ref signal coming from the camera contacts, there may be bounce and the PLL is correctly locking to the "higher frequency" as it sees those extra edges. Mark
On Feb 28, 6:46=A0pm, Mark <makol...@yahoo.com> wrote: > On Feb 28, 10:25=A0am, Chris <christopher.man...@gmail.com> wrote: > > > I bread boarded my PLL yesterday. =A0I was able to get it to lock just > > fine on a multivibrator =A0running at 33Hz. =A0I was able to solve the > > jitter problem by using a very large value for C1 (1000u). =A0However, > > when I attached my cameras to the loop, (one running at 22.2fps and > > the other running at 25fps) the loop would lock at a frequency > > slightly above the camera speed ~39Hz. =A0The camera has a contact that > > closes ~5ms every frame advance. =A0I tried using the contact to pull t= o > > ground, and to pull to rail. =A0I got the same result either way. =A0An= y > > suggestions? > > > Thanks, > > Chris Maness > > low pass filter the ref signal coming from the camera contacts, there > may be bounce and the PLL is correctly locking to the "higher > frequency" as it sees those extra edges. > > Mark That sounds like a good Idea. What would be a good cutoff frequency? Chris