How many bytes will you need to handle between re-synch's ?
I still dont get how it works - sorry, but under all cir***stances you
need to make an *****ment on the error you could get based on a worst
case scenario. Then you should calculate wether the clock in your system
will be able to cope with that timing. If it can then go ahead.
Otherwise think of another ap****ach.
I guess this is of no help either.
Hope you will get better advice from others.
Good hunting.
Klaus
la_panza skrev:
> Klaus (DK) ha scritto:
>
>> I dont exactly understand what you mean by that.
>> If data were ****fted in eternity you are right - the error will
>> eventually get too high. BUT there MUST be some sort of
>> re-synchronisation in an asynchronous world as this is. Usually you
>
> You are right, there is in fact a starting point, but it's at the
> begining g of the frame, there is a "start of frame" sequence you can
> rely on to trigger your timebase.
>
> after the start of frame sequence, characters are sliced into 4
> groups of two bits each, LSB first,... each bit couple is expressed by
> positioning a 9.44 usec pulse on one of four possible "phases", the bit
> couple lasts 9.44 usec X 4, a pulse on the first quarter means 00, a
> pulse on the second quarter means 01 and so on..
> .
> Apart from the start of frame sequence, all this has no more start
> bits, stop bits nor any redundancy or synchronization pattern ,
> characters are 8 bit each transmitted on 4 couples of 2 bits, the frame
> may be made of many bytes. during which the error may propagate, though
> I confess I never made a percentage evaluation of this error...
>
>> BR
>
> Adolfo
>
|
