Simulink Design Verifier (SLDV)/Auto Generate MIL Test Cases

Поділитися
Вставка
  • Опубліковано 31 гру 2024

КОМЕНТАРІ •

  • @jivanwagh9766
    @jivanwagh9766 4 місяці тому

    Really great explanation ❤

  • @archanachavan845
    @archanachavan845 3 роки тому +2

    One more video please on MIL. Thank you sir for sharing real time industrial experience..

  • @shindems3213
    @shindems3213 9 місяців тому +1

    Thank you so much for such a great explanation

  • @venu94
    @venu94 Рік тому

    Awesome explanation sir evergreen

  • @ankitdwivedi8567
    @ankitdwivedi8567 2 роки тому

    Very well explained sir please make more such videos on sil, pil hil

  • @sagarjundare9646
    @sagarjundare9646 2 роки тому

    Hello sir thank you for video. It is very useful.

  • @rutujamorey7230
    @rutujamorey7230 2 роки тому +2

    Sir please make a video on MAAB,MISRA,ISO2626 guidelines for the same model

  • @CreativeIndu
    @CreativeIndu 4 місяці тому

    Can we change total number of test steps and difference as per sample time while generating test through design verifier?

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

    The inputs were Boolean .. so the generated test cases were having 0 and 1 as values for key, knob, etc.. what if the data type isn’t Boolean.. then what values will it generate for inputs in test cases???
    Plz REPLY!!

  • @skpower3136
    @skpower3136 2 роки тому +1

    Please make a video on sil testing

  • @amitpotdar7646
    @amitpotdar7646 2 роки тому

    What exactly does it check in 'Check subsystem compatibility'

  • @ARUN_HENCHINAMANE
    @ARUN_HENCHINAMANE 2 роки тому +1

    You should have introduced different error instead of changing datatype. As this error can be detected simply by simulating the model. Nevertheless the SLDV feature is well explained using a simple functionality... 👍👍

  • @Mytime.295
    @Mytime.295 3 роки тому +1

    Sir can u tell diffrence between atomic subsystem nd non atomic?

    • @vaibhavbandal4820
      @vaibhavbandal4820 2 роки тому

      Nonvirtual(atomic) subsystem - Control when the contents of the subsystem are evaluated as a single unit (atomic execution). Create conditionally executed subsystems that run only when an event occurs on a triggering, function-call, action, or enabling input.
      Virtual(non atomic) subsystem - Subsystem is neither conditionally nor atomically executed. Virtual subsystems do not have checksums.

  • @venu94
    @venu94 Рік тому

    Sir can u make a video on carmaker tool also