Items you may want to include in your webinar for the future. As part of the subject of software includes not just the ADE/IDE and drivers. It also includes some considerations that need to be considered when evaluating basic approaches to a software defined test (what hardware is being tested, what kind of signals/measurements are needed, what kind of timing is needed, what modularity is needed, what sequencing ordering requirements are needed, etc.)
Also it would be useful to discuss the trade offs between flexibility and critical timing requirements and how that plays into the high level "approach" to creating Software Driven Tests.
Are they robots or androids? We're not exactly sure. Each talking, gesturing Geminoid looks exactly like a real individual, starting with their creator, professor Hiroshi Ishiguro of Osaka University in Japan.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.