Post Go back to editing

AD2S1210 Equation 5 (LOS angular latency) missing square root?

Category: Datasheet/Specs
Product Number: AD2S1210

I'm reading the AD2S1210 datasheet Rev. B, Loss of Signal Detection section, pages 16–17. And I have a question regarding Eqation (5).

Equation (5) states:

- Angular Latency = 2 × Arccos(LOS Threshold / Max Amplitude)

My assumption is this is derived from the monitor signal in Equation (4), which, if one signal is lost and θ = ϕ, simplifies to:

- Monitor = A1 × sin²(θ)

LOS triggers when this hits the LOS threshold:

- A1 × sin²(θ) = LOS Threshold -> θ = Arcsin(sqrt(LOS Threshold / A1)) -> Angular Error = Arccos(sqrt(LOS Threshold / A1))

And doubling that for worst-case latency.

This would mean that a square root is missing in Equation (5). Could you confirm if this is the case or if the angular latency in equation (5) is as intended?


Regards,
David

Parents
  • Thanks  , but isn't that the no-fault case? My understanding is that Equation (5) applies when one channel is lost.

    Thanks,  . I think you're onto something, although I can't see where the arctan term comes from when I try to derive it myself.

    Let's assume the cosine channel fails and remains at zero, while the sine channel continues operating normally. In that case, the cosine channel is always below the threshold, whereas the sine channel only falls below the threshold at arcsin(Threshold/Amplitude).

    If LOS detection is triggered only when both channels are simultaneously below the threshold, then the resulting blind-zone width becomes:

    2 × arccos(LOS Threshold / Amplitude)

    This derivation seems to support Equation (5) being correct, although for a different reason than I originally assumed. My initial assumption was that LOS was based on the monitor signal, whereas this result follows from individual SIN/COS threshold comparisons combined with an AND condition. However, with this approach and no faults (both cosine and sine channels nominal), LOS would repeatedly be triggered at e.g.: 45, 135, degrees if the LOS threshold would be set lower than A x sin(45) = A x 1/sqrt(2), which seems odd.

    To rephrase my question: Is LOS detected by comparing the monitor signal's values against the threshold, or by comparing the SIN and COS channels individually using an AND condition? Could you confirm which method is actually implemented?



    Regards,
    David

Reply
  • Thanks  , but isn't that the no-fault case? My understanding is that Equation (5) applies when one channel is lost.

    Thanks,  . I think you're onto something, although I can't see where the arctan term comes from when I try to derive it myself.

    Let's assume the cosine channel fails and remains at zero, while the sine channel continues operating normally. In that case, the cosine channel is always below the threshold, whereas the sine channel only falls below the threshold at arcsin(Threshold/Amplitude).

    If LOS detection is triggered only when both channels are simultaneously below the threshold, then the resulting blind-zone width becomes:

    2 × arccos(LOS Threshold / Amplitude)

    This derivation seems to support Equation (5) being correct, although for a different reason than I originally assumed. My initial assumption was that LOS was based on the monitor signal, whereas this result follows from individual SIN/COS threshold comparisons combined with an AND condition. However, with this approach and no faults (both cosine and sine channels nominal), LOS would repeatedly be triggered at e.g.: 45, 135, degrees if the LOS threshold would be set lower than A x sin(45) = A x 1/sqrt(2), which seems odd.

    To rephrase my question: Is LOS detected by comparing the monitor signal's values against the threshold, or by comparing the SIN and COS channels individually using an AND condition? Could you confirm which method is actually implemented?



    Regards,
    David

Children
No Data

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.