Getting a frame pulse early !

[Viewmaster]

I chuck this idea into the ring and see if it rebounds. (I'm sure it will!)
I haven't seen it mentioned before, although it probably has.

As I read it, the standard method of recovering the missing frame pulse is, as has been said, 'The missing the bus' method......... setting a multi vib to be retriggered at each line and it only finishing its cycle when the line pulse is missing at line 32, and so giving the frame pulse.

Suppose this recovered frame pulse triggers yet another multi vib whose timing was one whole frame, 80ms, but whose timing could be adjusted a few ms, or parts of a ms, either way, by a low value pot in the RC timing cct.

Using this o/p from the 80ms vib. as the new frame pulse, one would not miss the bus if the timing of the 80ms multi vib were set very slightly less.

So, one is using a previously recovered frame pulse to give one the present pulse, as it were, and its timing is adjustable plus or minus to suit. I cannot see a problem with that, but I daresay that there is.

[dominicbeesley]

Perfectly sensible way of doing it...

I started doing a flywheel sync unit for mine on a similar principle. The idea being to try and put clean syncs back on a (very)noisy signal. It is buried somewhere under fifty other half finished projects!

A 4046 and a handfull of components should do it plus a monostable to give you a frame pulse rather than a full half-frame.

D

[Viewmaster]

Hi Dominic. I think that in my suggestion, the main problem is that each mono vib has innacuracies in the timing due to RC changes with tempereature etc.

Peter Smith used a very 50us stable IC ( 4538) but using two of them
(2.6ms + 80ms) willl double timing error so the final frame pulse may not be stable enough, time wise.

Maybe, a way around this would be to just use ONE 80ms (+-) multi vib. Then when it is triggered by the last line pulse before the missing one, mask it off from any further line pulses until it is allowed to finish its cycle to give the frame pulse.
Then repeat its triggereing with the line pulse at the start of a new frame. Masking maybe done with another vib in sort of parallel, as it were. But there again, a long time 80ms vib might be subject to error where the shorter 2,6ms is not so much
..........I do wish I knew what I was talking about.

Flywheeel sync, had a brief one line mention in the handbook, but I don't recall any ccts anywhere suitable for NBTV.

[Steve Anderson]

the main problem is that each mono vib has innacuracies in the timing due to RC changes with tempereature etc..

Albert I think you're worrying about timing drift with temperature a little too much. If a a metallized Polyester film capacitor (PET) and a metal-film resistor were used for the timing components the change in pulse length is likely to be a lot less than 1% over normal room temperatures.(10-30 Celcius).

The low resistance (as a percentage) 'framing' pot would also allow adjustment for this.However this method does require a reasonably close to 400Hz line-rate.

More important is supply stability, especially when using the CD/HEF series of monostables, the supply would definitely need regulating...but more often than not they are these days. The 78xx type being perfectly adequate for this in conjunction with good supply bypassing/decoupling.

Steve A.

[Viewmaster]

the main problem is that each mono vib has innacuracies in the timing due to RC changes with tempereature etc..

Albert I think you're worrying about timing drift with temperature a little too much. If a a metallized Polyester film capacitor (PET) and a metal-film resistor were used for the timing components the change in pulse length is likely to be a lot less than 1% over normal room temperatures.(10-30 Celcius).

The low resistance (as a percentage) 'framing' pot would also allow adjustment for this.However this method does require a reasonably close to 400Hz line-rate.

Yes on thinking about some more, I now see your point about the reqirement to be close to the 400Hz rate.

But if the sync rate was not exactly 400 but stable, then a slight adjust of the fine pot might still give a reliable frame pulse, without 'missing the bus'
It would be interesting to see on the Niptrix the picture change as the pot were slightly adjusted either way. Rolling sideways I would guess.

OK also on your mention of the best R and C to use.....I was wondering about changing my existings to these anyway if problems arose with my existing cct setup.

Gee whiz, Steve, I am so happy that you and others, (so far !!) haven't grounded my idea for a 82.5 ms multi vib with +- frame timing adjustment.

[Steve Anderson]

It's a valid method of frame sync detection with the proviso that the 80-odd ms mono can be adjusted.

Some time ago I thought of the idea below. Instead of using a long-duration mono a counter is employed which when it reaches 31 fires of the delay mono which in turn fires off the frame sync mono.

The 'Missing the bus' mono triggers a further one which resets the counter to zero during line 1. This will allow for much wider variations in the line-speed and no concerns about temperature stability.

Timings are nominal.

Steve A.

[Steve Anderson]

I've noticed that 8-input AND/NAND gates are getting a bit rare these days so a suggested alternative is below...note following monostable input is changed too...

Steve A.

[Viewmaster]

Thanks for the cct, Steve.
What with your cct, Peter Smith's and my own little idea of masking a
82.5ms +- vib with another one I should certainly be able to,
'catch the bus.'

[Viewmaster]

Steve, on further looking at your cct I notice that the 4024, 31 counter is reset by the first mono timed at 3.75ms with a short pulse from the second mono (100us)
Forgive me but I cannot understand this.

Shouldn't the 4024 counter be allowed to count 31 line pulses, which is 77.5ms, before being reset?

I know I probably have this wrong but cannot see how.

[Steve Anderson]

Shouldn't the 4024 counter be allowed to count 31 line pulses, which is 77.5ms, before being reset?

There are only 31 incoming sync pulses per frame (if there were 32 the AND/NAND gates could go) The last one signifies the end of line 31, the start of 32. I hope the sketch below makes things clearer...remember 0 is a valid binary count, unlike humans who start at 1.

It is entirely possible I've made a complete cods of this...It was an idea some time back and stored in my head which has many bad sectors.

Steve A.

[Viewmaster]

It was an idea some time back and stored in my head which has many bad sectors.
Steve A.

My head is more like a floppy , but I shall try to fathom
your explanation, and sketch, Steve.
Thanks for going to all that trouble in drawing it up.

[M3DVQ]

remember 0 is a valid binary count, unlike humans who start at 1.

Pfft, most humans do

[Steve Anderson]

In the background Albert and I have 'tweaked' this counter method a bit. For the NIPTRIX it requires a continuous 400Hz line sync, this would also apply to CRT based displays too (sorry Gary).

A simple change to the AND gating and the result is shown in 'Counter Method 4' below.

To be able to separately tweak both the generated frame sync and the inserted line sync the circuit in 'Counter Method 5' provides this.

The inveterate pot-twiddler will have plenty to do during those cold winter evenings.

Steve A.

[Viewmaster]

Yes, and thanks for that Steve.

Not only does that give me plenty of leeway to get the timings right but I can now experiment to see how the picture is changed.

I have line and frame adjust , just like the old 405 line TV's.........now all I want are focus, width and height controls. ......
........and Sylvia Peters

[gary]

Y.....and Sylvia Peters