VHDL-AMS Black Belt

I like martial arts films, from the old black and white movies dubbed in English or even subtitled, to the modern blockbusters with their almost endless array of special effects. I admit that I can’t really tell the different martial art styles apart, but frankly I don’t need to. Being able to distinguish styles wouldn’t add to my enjoyment of the films. What I do enjoy is watching a skilled expert (even minus the special effects) practice his art — it’s easy to appreciate the skills of a martial arts black belt master. I think the same can be said for engineering design – if you enjoy technology at all, it’s usually a treat to watch a well-versed engineer with basic communication skills (I know you’re smiling here) talk about systems engineering. As luck would have it, I’ve enjoyed two such opportunities in the last couple of weeks while teaching users about SystemVision and VHDL-AMS.

The more I work with the VHDL-AMS modeling language, the more I’m impressed with its capabilities. It truly is a multi-purpose modeling language well suited for describing complex mechatronic system behavior across a broad range of engineering disciplines and at multiple levels of functional abstraction. One of my responsibilities on the SystemVision team is teaching an occasional user training course. Training class instruction gets me out of my office for a few days and gives me a valuable opportunity to visit face-to-face with users to learn about what they do, and hopefully help them understand how using VHDL-AMS and SystemVision can help them improve their system designs.

When I teach a modeling or simulation training course, I am usually the sole instructor. But during the most recent two classes during the two weeks I mentioned above, an engineer from the SystemVision group tagged along to help out. I taught our standard SystemVision and VHDL-AMS courses while he added some great technical content with demonstrations tailored to the user’s applications. Gave students the chance to see practical applications for the things they were learning. My co-instructor is a long-time simulation model developer with more than 2 decades of experience, and he’s been using the VHDL-AMS language pretty much since it became a standard. Along with being a skilled modeler, he has a truly impressive collection of models and system examples covering a broad range of applications. In fact, his fingerprints are on many of the models now available in the SystemVision VHDL-AMS model library.

The majority of students in our two training classes work mostly in board level design and use at least one flavor of SPICE to simulate their designs. But when it comes to testing their board in the end system, often their only option is to build a prototype; their understanding and experience with modeling and simulation typically stop at board level. Many students were pleasantly surprised when my co-instructor turned on his laptop and started talking about modeling and simulation beyond the printed circuit board. He regularly puts both the SystemVision environment and the VHDL-AMS modeling language through their paces, much to the delight of users and fellow workers alike. By the end of both training classes, the students were noticeably impressed with the potential of both the language and the simulator – the benefits of watching a true master at work.

But it doesn’t take a black belt in VHDL-AMS to use the language and reap its benefits in system design. Armed with a basic understanding of the language, users can do some pretty impressive things with VHDL-AMS. An understanding of design technology mixed with a basic foundation in VHDL-AMS can go a long way in systems modeling. If you’re at all interested in modeling and simulation beyond SPICE, and you really should be if your board level design is part of a larger system, you owe it to yourself to investigate the capabilities of the VHDL-AMS modeling language and give it a try. No black belt required.

If you need a simulator that supports VHDL-AMS, you can download a demonstration version of SystemVision here.

Post Author

Posted October 19th, 2010, by

Post Tags

, , ,

Post Comments

No Comments

About Mike Jensen's Blog

Views, insights, and commentary on mechatronic system design and analysis. Mike Jensen's Blog

Comments

Add Your Comment

Archives

October 2014
  • Reliability vs Robustness
  • June 2014
  • Wow Factor
  • May 2014
  • SystemVision 5.10.3
  • March 2014
  • IESF 2014: Military & Aerospace
  • Engineering Oops!
  • Big Engineering
  • January 2014
  • SystemVision Model Wizard
  • December 2013
  • SystemVision 5.10.2
  • Modeling: An Engineer’s Dilemma
  • October 2013
  • What is Your Legacy?
  • September 2013
  • Automotive IESF 2013
  • July 2013
  • Simple Design Solutions
  • June 2013
  • SystemVision 5.10
  • May 2013
  • Engineering Muscle Memory
  • EDA vs. Windows 8
  • March 2013
  • VHDL-AMS Stress Modeling – Part 3
  • January 2013
  • VHDL-AMS Stress Modeling – Part 2
  • VHDL-AMS Stress Modeling – Part 1
  • December 2012
  • Practice! Practice!
  • November 2012
  • Sharing Tool Expertise
  • October 2012
  • Preserving Expertise
  • Virtual Prototyping — Really?
  • Innovations in Motion Control Design
  • September 2012
  • Game Changers
  • Do We Overdesign?
  • August 2012
  • Tsunami Remnants
  • July 2012
  • A New Look at Device Modeling
  • SystemVision 5.9
  • June 2012
  • Veyron Physics
  • May 2012
  • Rooster Tail Engineering
  • April 2012
  • Automotive IESF 2012
  • Teaching and Learning CAN Bus
  • March 2012
  • Analog Modeling – Part 6
  • Analog Modeling – Part 5
  • Analog Modeling – Part 4
  • February 2012
  • Analog Modeling – Part 3
  • Analog Modeling – Part 2
  • January 2012
  • Analog Modeling – Part 1
  • Connecting Tools and Processes
  • December 2011
  • Turning-Off and Tuning-In
  • Use vs. Experience
  • Analyzing the Big Picture
  • November 2011
  • Simulating for Reliability
  • October 2011
  • SystemVision 5.8
  • VHDL-AMS Model Portability — Fact or Fiction?
  • September 2011
  • IESF 2011 Moves to Frankfurt
  • Simulation Troubleshooting
  • August 2011
  • Qualities of VHDL-AMS Quantities
  • Military & Aerospace IESF 2011
  • Touring Johnson Space Center
  • July 2011
  • Engineering versus Science
  • June 2011
  • System Reengineering
  • May 2011
  • Integrating Hardware and Software Design
  • Engine Remote Start
  • Integrated System Design
  • Simulation Experiments (Part 3)
  • April 2011
  • Automotive IESF 2011
  • Pushbutton Cars
  • System Simulation with FEA-Base Motor Models
  • March 2011
  • Simulation Experiments (Part 2)
  • Simulation Experiments (Part 1)
  • Japan: Patience and Grace Amid Disaster
  • Top Gear = Driving Fun
  • February 2011
  • Buoyancy
  • Ideas in Motion
  • January 2011
  • The Mechanical Half of Mechatronics
  • Detroit Auto Show
  • Signal-flow vs Conserved System Modeling
  • SystemVision 5.7…Ready, Set, Go!
  • December 2010
  • SystemVision and Windows 7
  • Friction Vacation
  • Simulation Beyond Volts and Amps (Part 4)
  • November 2010
  • Simulation Beyond Volts and Amps (Part 3)
  • Simulation Beyond Volts and Amps (Part 2)
  • Simulation Beyond Volts and Amps (Part 1)
  • October 2010
  • SAE Convergence Recap (and an Unexpected Surprise)
  • VHDL-AMS Black Belt
  • Converging on SAE Convergence
  • System Design vs System Repair
  • September 2010
  • What’s the “AMS” in VHDL-AMS?
  • How Sensitive is Your System?
  • Do You Trust Your Simulator?
  • August 2010
  • What’s in a SPICE Model?
  • Cycling + Gravity = Pain
  • NI Week: Fun for Engineers
  • June 2010
  • Are You a Flexible Thinker?
  • VHDL-AMS and Switch Hysteresis
  • May 2010
  • VHDL-AMS Revisited
  • Segway to U3-X
  • Atomic Glue
  • March 2010
  • IESF Recap
  • February 2010
  • IESF is Coming…
  • System Level HDL-topia
  • January 2010
  • Mastering Design Abstraction
  • The Joy of Disassembly