How E3.SaberFrameway Can Help You Avoid System Failures in Your Electrical Designs
Last week I talked to you about why Zuken integrated Synopsys’ Saber Simulator with our electrical CAD software E³.series. This week I want to share with you more of the practicalities of using E³.SaberFrameway in your design environment.
E³.SaberFrameway provides functional and also quality checks for your electrical designs
On a basic level this add-on module, that interfaces between Synopsys’s Saber software and Zuken’s E³.series electrical design environment, means that you can carry out functional checks on your wiring and fluid designs and optimize your existing circuits. But there is also a group of people who use this for scatter analysis. With high volume and mass produced products there is a certain degree of scatter in quality and later on in the behaviour of a product. To avoid system failures it is important to carry-out worst-case simulation.
So we ask, what needs to be done to make sure the product still works in a worst case scenario?
No number of prototypes can test all the situations, that is just impossible even if cost where not an object. So this needs to be calculated mathematically – and E³.SaberFrameway allows you to do this.
More than combined electrical modelling and simulation
The focus of this solution is on electrical engineering, but it’s worth me quickly adding that there are also models available for hydraulics, pneumatics, and even optics and thermodynamics within Saber.
How do you actually do the modelling?
Using the E³.series schematic that is how.
So rather than having to re-create the schematic from scratch in Saber copying your design work from E3.series, you can simply use E³.SaberFrameway and import the design straight into Saber. No more manual errors and it saves lots of time. The Saber model is then built on the basis of this schematic.
For many companies you have the electrical engineers who design the electrical schematics and then specialist simulation engineers who prepare and perform the simulations – the nice thing about E³.SaberFrameway is that it brings these two groups of individuals together and allows them to work in a more seamless way.
So it sounds simple, and it is now…but it wasn’t so easy to get to this point. We had to understand how both users work, understand the physics and then map the software.
The process from E³.series schematic to Saber – differences between single and multi user
It starts with the schematic as I’ve already said, but then the process varies depending on the kind of design environment in place. Is just one person in the company working with E³.series or are there multiple users working on the same project simultaneously? If many people are working at once, they will have an E³. Multi user set up, which by default means that the simulation engineer can (with just a slight time delay) access the original design data and start building the model straight away. If it’s a single user arrangement the simulation engineer will need to wait until the schematic it ready or at least at a stage where the data can be modelled.
Over to Saber…
At this point the simulation engineer studies the schematic and selects the components to be simulated simply by clicking on them.
This is where the simulation starts (as long as the library knows the PIN mapping – if it doesn’t you need to do this first).
Physical simulation outputs are then generated. This includes all physical effects, and for everything (electrical, hydraulic and pneumatic) this is all done at the same time so that you can see the overall behaviour of the circuit design and then modify if necessary.
What’s even better is that when you come back to do more simulation E³.series has already stored all the simulation relevant data so you don’t need to enter that again next time around.
For more information about E³.SaberFrameway click here.