Hyperlynx DRC Workshop
Tuesday the 4th or 25th of November 2014
The HyperLynx DRC Workshop is developed to show you all the capabilities of this powerful tool. It is the completion of a series of articles: Design errors, included?, written by Laury Watervoort.
By attending the workshop you will receive a 30-days evaluation license of HyperLynx DRC software. With the gained knowledge you can start an evaluation of the tool by yourself.
During the day we will highlight the capabilities of detecting EMI, SI and PI problems with the included standard rules. A basic knowledge of the User-Interface, Rule-Setup and Rule-Execution is given.
The HyperLynx DRC tool offers the possibility to program your own rules and also offers a complete debug environment for that purpose. During this workshop we will teach the usage of the debug environment, and give a short introduction to the Data model so you get a quick start for writing your own rules
Hands-on lab exercises will reinforce lecture and discussion topics under the guidance of our instructor. This workshop is offered on Windows platform.
An additional date is set for this workshop: Tuesday the 25th of November 2014.
You will learn
- Basic application knowledge•
- Graphical user interface
- Process Flow (startup)
- Run DRC rules
- Reviewing the design
- Understand functionality of pre-implemented rules
- Basics of the Debugging environment
Throughout this workshop, extensive hands-on lab exercises provide you with practical experience using HyperLynx DRC software. Hands-on lab topics include:
- Setting up rules
- Executing rules.
- Using the Debug environment
|Location||InnoFour Twentepoort Oost 61-02, Almelo|
|When||Tuesday the 4th or the 25th of November 2014|
|Time||09.00 - 16.00 hr|
There is no registrations fee, however a ‘no-show’ fee of € 75,00 will be charged if you don’t show up at the workshop.
HALT can be an important step in best practice reliability activities but its use is extremely limited without root-cause analysis. In HALT, failures are frequently treated in either a "fix and move on" or "ignore as not relevant" fashion. As a result, organizations experience significant losses from unreliable equipment and processes as they repeatedly correct rather than prevent problems. This is a reactive rather than a proactive method of solving, managing an eliminating undesirable events.Webinar: The Reliability of Wearable Electronics
What are the requirements of a typical wearable electronics device? They must be non-restrictive, portable, always be accessible, easily controllable, and have both localized communication and possibly wireless communications capabilities. The soldier systems must be much more robust and be able to withstand rain, sand and dust, thermal shock, solar radiation (UV exposure), icing, high and low temperatures, fungus growth, water immersion, mechanical shock and electromagnetic (EMC) compatibility. As such, these systems are costly and have long development cycles.