ETCS Bites Back - 49 (Balises are vital)

Поділитися
Вставка
  • Опубліковано 20 січ 2025

КОМЕНТАРІ • 4

  • @salvatorepuglisi5459
    @salvatorepuglisi5459 3 місяці тому

    I started studying subset 026 for work (I conduct onboard system tests for an Italian company) and I don't know how to thank you for the clarity of your exposition, your willingness to convey the concepts, and the effectiveness with which you manage to engage those who follow you.
    Thank you so much.

    • @johnalexander995
      @johnalexander995  3 місяці тому +1

      @@salvatorepuglisi5459 glad you found it useful. It often takes a long time to understand but once you do then it makes sense (normally)

  • @Atte5820
    @Atte5820 2 місяці тому

    9:15: If balise 2 is a duplicate of balise 1 & balise 1 is a duplicate of balise 0 => Balise 2 can't be the reference location balise if balise 0 & 1 are faulty?

    • @johnalexander995
      @johnalexander995  2 місяці тому

      You can only have duplicates in pairs - balise A needs to say it is duplicated by balise B (the next balise) and balise B needs to say it is a duplicate of balise A. I think that if you tried to mark balise C as a duplicate of balise B without marking B that C would duplicate it then you would get a consistency error and there is only one M_DUP in the header.
      So, if you make 0 and 1 a duplicate pair then as long as one is working then the reference location can be defined, albeit at potentially two different places (so you need to adjust Q_LOCACC). If both 0 and 1 fail then the balise group is incomplete and an error will be generated.