DoIP with Vector CANoe (1/6): A Typical Communication Sequence

Поделиться
HTML-код
  • Опубликовано: 7 фев 2025

Комментарии • 8

  • @venkataparuchuri9951
    @venkataparuchuri9951 4 года назад

    Thank you for giving clear details on DoIP

  • @abdallahrashed1947
    @abdallahrashed1947 5 лет назад +1

    Thank you, very helpful, looking for the next

  • @shadabmohid5801
    @shadabmohid5801 4 года назад +1

    That was quite informative, thank you :)

  • @AyoubIsmail-q2b
    @AyoubIsmail-q2b 6 месяцев назад

    Thanks for these valuable informations, in case we have two DoIP gateways, the first one is connected to test equipment and the second one is behind the first gateway, how the identification works ? does one vehicle identification request is enough to make Gateway 1 and 2 both respond (gateway 1 forward request to gateway 2) or we must process one request for each gateway (means we need two Vehicle identification request)? thanks in advance

  • @karthiks2873
    @karthiks2873 2 года назад

    Can you please brief on the activation line part?. I'm not sure on why it is required

  • @rapidsplash9339
    @rapidsplash9339 5 лет назад

    With thanks for sharing this very good video.

  • @sudhan123
    @sudhan123 Год назад

    With Doip version 2019 this sequence is correct?

    • @vectorinformatik
      @vectorinformatik  Год назад

      Yes, this sequence is still correct. The DoIP standard ISO 13400-2:2019 has essentially only introduced a new protocol version 3 for the header, a new routing activation response code (0x07) and encrypted communication via TLS. The extensions are described in part 5 of this video series ("Encrypted communication over TLS").