Robin Bornoff's blog

Views and insights into the concepts behind electronics cooling with a specific focus on the application of FloTHERM to the thermal simulation of electronic systems. Investigations into the application of FloVENT to HVAC simulation. Plus the odd foray into CFD, non-linear dynamic systems and cider making.

8 September, 2014

Develop 3D is a UK based Magazine and Website focussing on the technologies involved in product design. The latest copy had a fascinating article on Dell’s Precision Workstation labs. This blog is being written on a Precision M4500 which I’ve lugged around countless airports and dumped, wearily, on numerous hotel beds. The fact that it works as well now as when I first got it a few years ago is testament to Dell’s design processes and technologies.

The article, , looks into Signal Integrity and Thermal design. Both are key aspects in achieving competitive product performance. From a thermal perspective the overall power dissipation is related to the frequency at which the PC will operate (well, the dynamic portion of the power dissipation is). Increased power leads to increased temperatures. If the temperatures get too high things start to break, the supplier gets a bad reputation, warranty costs spiral, other very bad things ensue. This catastrophe can be diverted by throttling down the power before the temperatures get too high. Downside is that performance is limited. Having a cooling architecture that is sufficiently effective at removing the heat quickly can therefore have a marked and direct effect on the competitive nature of the product (read $$).

As the article quotes, “[We do] simulation way early on, looking at how thermals are going to work, almost in turn figuring out how the whole box is going plug in together and work together before we even build the first one.” An excellent example of doing design at the right time. A mature design process is one where simulation is used at a conceptual, pre ‘concept commit’ stage to determine at a high level what the major design constraints will be. Interesting that at this stage in the design, before the green light has been given and lots and lots of engineers and detailed engineering tools are deployed, there is very little detailed design data. From a simulation perspective this is actually quite liberating. Good engineering judgement can be applied to drive the simulation tool, in the context of little or no IDF or STEP, to answer questions such as “how many vents will we need?”, “one micro blower or two?”, “heatpipes?” etc.

Generic Laptop SectionFloTHERM was adopted early on for telecomms, networking and computing applications and is especially well suited to conceptual design. It’s simple CAD type interface, building block approach to 3D model construction, instant grid calculation and fast+robust CFD solution technology really comes into their own. Here’s some output from an application example we install with FloTHERM. A corner section of a generic laptop with a double inlet/outlet blower, convection cooling a couple of ducted heatsinks that are supplied the heat via a couple of heatpipes connected to a PLCC package.

The animated air flow behaviour enables appreciation of how the design is working, is all the cold air ingested that could be? Is any hot air recirculated back inside?

Generic Laptop Section Top

Generic Laptop Section Below

If you’d like to find out more about FloTHERM this introduction to FloTHERM webinar gives a good overall impression as to what it can do, worth checking out.

One final thought, if you are ‘lucky’ enough to have highly detailed EDA and MCAD design data to hand when using FloTHERM maybe you should ask yourself if it’s a bit late in the day simulating the design for the first time.

8th August 2014, Ross-on-Wye


4 September, 2014

A release so good it has 11 best top 10 features, very Spinal Tap. I thought I’d wrap up this series with a list of more minor, but imo, very useful features and finish off with some words on cultural idioms.

FloTHERM V10.0 and V10.1 together satisfy about 60 software enhancement requests as voted for on the Mentor IDEAS site for Mechanical Analysis Products, a strategy we’ve been committing to for a number of years now. It’s not always the big headline grabbing features that the most interesting though. Here are some of my personal less well known favourites:

  • Indication of whether a loaded model has results or not. Done via a coloured icon in the bottom status bar in the Project Manager. ResultsYesNo No more having to load a model and open the Profiles window to see whether there is any residual history.


  • NomObjectsHow many objects are selected? Now given directly, again in the Project Manager bottom status bar. If no objects are selected this changes to the total number of objects in a model. I benefit from this often in my use of FloTHERM, though to tell you the truth I’m not exactly sure why!


  • AlignI like the simplicity of shape moving and editing in Microsoft products. Needs no training. One thing that is missing from Office (but now not form FloTHERM!) is a double align on both centers, in one operation. Now a one button operation in V10.


  •  Having a RecentProjectslist of recently used files/documents for quick access to recent data is quite standard nowadays. FloTHERM’s had this for a while. However it only worked if the selected project was in the current project solution directory. This has now been rectified. Loading a previous project will automtically force change of the solution directory and load the project.


  • AbortSolver So many times I’ve started a solve only to suddenly realise that I’d forgotten to make some required tweak or modification to the model. The solver stops slowly as it finishes its current iteration then writes out all the solution data to disk. Sure, we could have added an ‘Are you sure?’ dialog each time the GO button was pressed. We’d be lynched though. Instead we’ve added an ‘Abort Solver Action’ feature that will terminate the solver executable immediately, no results written but you can get back and make the change asap. Hands up who remembers ‘kill -9′ on Unix?

Well, that’s it for V10. Development for V11 is well underway. FloTHERM ploughs ahead!

4th September 2014, Ross-on-Wye

p.s. O yes, idioms. Not sure where the phrase ‘odds and sods’ comes from, it’s in common use in the the UK though. ‘Odds and ends’ is the more common variant I suppose. There are a number of phrases that are perfectly acceptable to use in the UK but would raise eyebrows elsewhere, normally in the US. Yep, in the UK it’s perfectly acceptable to go out of the pub and ask someone if you could ‘bum a fag’. Also, a private school in the UK is referred to as a public school (well, it’s open to any member of the public to pay to send their children to!). This and other US/UK travel word tips can be found here.


4 September, 2014

Arguably the most important (and often least well characterised) parameter controlling the temperature of electronic products is their power dissipation. Usually dissipated on the active layer of a die, this heat power seeps through the die, package, PCB, air, chassis all the way to the ambient in which the product sits. The less heat power the better, the lower the temperature rises that occur. The last thing the cooling requirements need is even more power being added to the product but that’s exactly what happens on any sun apparent face. Sun bathing was fashionable in the 70s, it never was for electronics**.

Our own star provides us with a maximum of about 1400 W/m2 of incident solar energy, most of the power coming in the visible spectrum range. This can have a marked effect on the resulting surface temperature of an outdoor pole mounted repeater or base station cabinet. Accurate accommodation of such a power input to a FloTHERM electronics cooling simulation model is often critical.

Solar loading defined and modelled in FloTHERM. The +ve SolarVis field indicates where there are no shadows

Solar loading defined and modelled in FloTHERM. The +ve SolarVis field indicates where there are no shadows. The banded effect of the resulting surface temperature is evident.

SolarSpeedUpFloTHERM’s had the ability to specify the solar effects for a number of releases. The (annual) date and time of the simulation is specified together with the location and compass orientation of the model, FloTHERM does the rest, works out the sun apparent solid faces, the incident angles and imposes the correct resultant power on those faces.

This ‘pre-processing’ calculation used to take some time, days in some cases. It doesn’t any more. Speed improvements comparing V10 to V9 of up to x80 faster are now achieved though a rewrite and added parallel support for multiple processors. Yet another example of our strategy to reinforce the core functions in our software.

4th September 2014, Ross-on-Wye

**Photovoltaics aside of course

, ,

4 September, 2014

FloVENT, FloTHERM’s sister product aimed at 3D CFD simulation of the built environment, has for many years been able to simulate the thermal behaviour of a data center. After all a data center is a built environment, albeit more for servers and the like than humans. We’ve not changed this capability of FloVENT but we have copied the relevant data centric features over to FloTHERM, extending the positioning to cover electronics thermal management from the chip to the room.

FloTHERM 10 splashscreen

The electronics thermal supply chain is linked together with the desire on one side, and the obligation on the other, of assuring thermal compliance in the customer’s application. Thermal performance of the equipment in the data center is a function of density, layout, cooling architecture and operation. Now I don’t know exactly what % of all PCBs designed and manufactured end up in a data center, likely not that many. However I assume that nearly all of the bytes communicated in this IoT age are routed through such rooms.

CRAC operationPushing bytes around the net needs energy. Bytes don’t have much kinetic energy themselves, which is why that energy ends up being dissipated as heat. Leave that heat lying around unattended and things will get too hot and stop working. Ever wondered what a world full of teenagers lamenting the loss of Facebook, Twitter and SnapChat might sound like? Ouch.

FloTHERM’s Rack and Cooler SmartParts allow for the quick and easy definition of these common data center items. That coupled, with FloTHERM’s renowned ease of use and rapid simulation performance, enables the thermal performance of a given data center configuration to be rapidly determined. Check out this video for a look at the typical output from such a simulation.

4th September 2014, Ross-onWye

, , ,

29 August, 2014

Electronics thermal simulation historically focussed on steady state conditions, worse case scenarios where for example a power dissipation is assumed at a maximum and unchanging. Not a direct reflection of reality but the conservative (over)temperature simulation results enabled design margins to be implicitly factored in. Over the years, as margins reduced and the need for ever more accurate simulations increased, the proportion of transient simulations that FloTHERM conducted has increased dramatically. From a FloTHERM development perspective we’ve kept on top of this trend. An overhaul of our transient definition capabilities in V9.1 has now been followed by substantial changes in our transient modelling capabilities in V10.

Beyond standard transient considerations such as the thermal response of a system to fan failure condition, or a cold start power on, thermostatic control is an approach that can be used to both limit operational temperatures and lower power usage. Various user posted feature requests on the Mentor ‘IDEAS for Mechanical‘ site alluded to this, all of which have now been satisfied by a couple of new V10 features.

Transient TerminationThe ability to stop a transient solution, automatically, is now available via a new ‘Monitor point transient termination criteria’ option. One or more monitor points can be nominated, with individual stopping criteria temperatures. During the transient simulation, as soon as one condition is met, the simulation automatically stops. This allows inspection of the model at that time/temperature, results exported or manual modifications made to the model and solved onwards.

The real doozy though is an extension we have made to the transient attribute. The transient attribute is a curve that relates a multiplier value with time. This attribute can then be attached to a power dissipation value, a temperature etc. to vary those boundary conditions (BCs) in time. In V10 we have added the option to also include a multiplier vs. (monitor point) temperature curve as well. In this way a BC can be varied in time AND/OR as a function of temperature.

Themostatic ControlVery powerful, especially when considering the application to die level models where it would allow for a transient variation of the switching power portion and a temperature dependence of the leakage power portion of the power dissipation together.

AndTheresMoreAnd there’s more… FanThermostaticDeratingThermostatic controlled fans are very common, especially in consumer/laptop type products. Ever hear your laptops’ fan come on when the CPU gets too hot running all your FloTHERM simulations? In V10 you can now attach a transient attribute to a fan to affect its RPM derating factor during the transient simulation, either as a function of time or monitor point (hub mounted or remote) temperature.

AndTheresMoreAnd there’s more… In addition to a single curve relating the BC with temperature, a Hysteresis option can be checked to allow two curves to be defined, one controlling the BC when the temperature is increasing, the other to control the BC when the temperature is decreasing.


Accommodation of such hysteresis allows for better tuned thermostatic control methodologies to be investigated and determined in FloTHERM. If you want to leanr more about such control, here’s an interesting piece from Panasonic comparing and contrasting PID and Hysteresis control approaches.

As you can hopefully see, the FloTHERM development team are big fans of transient simulation technologies :)

29th August 2014, Ross-on-Wye

p.s. let’s hear it for Jimmy Cricket!

, , , , ,

18 July, 2014

I’m sure in the (far) future, product design and manufacture will just involve a big box that you can ask to make things for you. “A leg driven transport device with communication, health monitoring and illumination functions that will last me the week. Please Mr. Box” (or ‘Bob the making box’ as I’d call mine). Out it would pop. Think Star Trek Next Generation Replicator, extrapolated. In the mean time product design is far more manual, time consuming and let’s face it, FUN! Time however is money and no matter how much fun it is, it has to be profitable. Waiting around for your FloTHERM thermal simulation to complete is both not fun and time consuming. Maybe not as much now though…

The CFD solver is the core, the nucleus of a CFD software. Everything upstream of it’s deployment is intended to serve it (boundary conditions, geometry, mesh etc.) and nothing downstream can happen (results inspection) until it’s done its business. Just like a watched kettle, the CFD solver can appear to take a long time to finish. More maybe due to the feeling of helplessness, that all you can do is watch those residuals come down.

I’ve been working in the application and product management side of CFD for all my professional career. I know enough about the maths to be dangerous, not enough to be useful. For FloTHERM V10 we have substantially reworked the CFD solver, especially its parallel performance. Using nothing more than words I’ll attempt to g**k porn a description of what we’ve done…

The main aim of this project was to improve the parallel scalability of the CFD solver. Experience is that for a shared memory approach care has to be taken to achieve +ve scaling above 4 cores. Key to this is focussing on load balancing between the cores. To that end we:

  • Modified our data structures to distribute the computational work across the cores more uniformly.
  • Modified our linear solvers to take advantage of the better load-balancing including introduction of a new more scalable preconditioner
  • Memory management is modified to take advantage of the NUMA-architecture (Non-Uniform Memory Access) of modern processors
  • Enhanced memory layout of our data structures to optimize the memory accesses for the modern cache-based processors

There are many ways to present the performance of parallel CFD solvers. I’ve seen enough graphs showing maximum linear scaling (use N cores results in an N times speed up) to start questioning their integrity long ago. We decided to focus on the improvements a FloTHERM user would expect to see when moving from V9 to V10.The following graph shows how many times faster V10 is compared to V9, for a range of different models, on 1, 2, 4 and 8 cores.

v9 vs v10

Being the real world, we found that the relative performance improvement is case specific, the improvement does get better the more cores you use but (surprisingly) the performance is not effected by mesh topology (i.e. the number and layout of localized grid spaces). Some of the changes we made for scalability also had a dramatic effect running even on a single core!

We did tests on up to 8 cores on all models, some we tested up to 32 cores, continued +ve scaling was observed.

Being twice as fast, having to wait half the time, is nothing to be sniffed at. 10 times faster is quite remarkable. Less time to read SF and speculate about the future, more time to get back to the real work of designing good (thermally compliant) product.

18th July 2014, Ross-on-Wye


30 June, 2014

If there’s one word that describes electronics products it’s ‘complexity’. Actually, scratch that, that’s too generic a term. How about ‘cluttered’? IC packages are constructed from a number of different parts, soldered onto a PCB that is constructed from a series of layers and secured into some kind of chassis. ‘Packaging’ at various levels, physically interconnecting functionality with itself and to the outside world. From an electronics thermal simulation perspective such an application is not complex in terms of advanced physics and convoluted curved geometries but it does entail specific challenges for those involved in assuring thermal compliance.

Detailed package _explodedThere are only about a 3 orders of magnitude difference in the thermal conductivities of the materials that go to make up an electronic product. ‘Only’ when compared to a 12 orders of magnitude difference in electrical resistivities. Electrical current therefore remains flowing in very well defined parts of the product, isolated from both a physical, design tool and design process perspective.  Heat on the other hand spreads all over the place, like a bad smell. It cares not for the classic divisions in the product development process, turns its nose up at electrical engineering as it gushes out from the IC, sneers at the PCB designer as it spreads through the board and shows nothing but disdain to mechanical engineering as it get whisked away by the air on its way out. Enter the thermal engineer, brave knight, thermocouple and FloTHERM in hand. Tasked with taming the dragon that is heat, chasing it through these scales and disciplines.

GenericSmartPhone1As such, a typical FloTHERM model will contain parts (with associated physical and behavioural parameters) such as: die, die attach, lead frame, die pad, substrate, boned wires, encapsulant, lid, solder ball, signal layer, power plane, ground plane, dielectric layers, pads, electrical vias, thermal vias, connectors, capacitors, LEDs, RF cans, EM shields, potting compound, thermal interface greases/pads/tape, heatsinks, fan-sinks, fans, blowers, heat pipes, thermo-electric coolers, batteries, cables, vents, fan trays, enclosures, chassis, nut and bolts. To name but a few.

When making predictions about operating temperatures using FloTHERM, the thermal engineer must be sure that their model of the proposed product is accurate to the extent where the resulting accuracy of the simulation will be useful. This involves inspecting the model in various ways, often, throughout the model building and results inspection process. Sure, graphical and node tree views of the model are standard. In FloTHERM V10 we have added an additional view of the model and the data that used to define it.

Integrated Summary ColumnsIntegrated summary columns can be invoked to show a tabular type view of the model, linked to the node tree view. Columns will show, per part, what attribute is attached (name tool tipped on mouse over), size, power, cumulative power for assemblies and whether any face of that object is de-keypointed due to use of minimum cell size grid constraint.

The summary columns can be shown/hidden using the “i” key shortcut. By providing a quick view of the model input, without having to navigate to the tabs that are used to enter or set that data, the user can make the frequent inspections necessary to assure that the model has all the required settings so that they can get back to doing battle with the heat and not waste unnecessary time sharpening their software sword.

30th June 2014, Hampton Court.


10 June, 2014

Flo. As far as prefixes go, I don’t know of another company that uses one so consistently for product branding, well apart from Apple. ‘Flo’ comes from ‘Flow’ and was part of the naming of Flomerics (Flow-Numerics), the company that first developed FloTHERM (flow-thermal) and FloVENT (flow-ventilation). FloMOTION was a favourite branding (animated post-processing module). Other completely unrelated Flos include Flo Rida, Flo Jo and Auntie Flo. We still use this prefix (though try to steer clear of too much conFlosion) and when it came to naming a new automation scripting technology we developed for FloTHERM V10, the name was obvious; FloSCRIPT.

Scripting allows for instructions to be stored/recorded/replayed that would otherwise have to have been done manually in the GUI. As such, scripting can do no more than would be possible manually. What it can do though is to automate such tasks. Automation saves time and can be used to impose quality and consistency on the simulation process.

FloSCRIPT_fragmentEach FloTHERM session is logged to a FloSCRIPT file, the last 5 session scripts are retained (in the \flosuite_v10\flotherm\WinXP\bin\LogFiles directory). FloSCRIPT is XML based, with each operation performed in the new Project Manager / Drawing Board window being logged.

An obvious application for this technology is when it comes to communicating with customer support. Gone are the days where a user would have to remember and recount the steps they went through when helping a support engineer replicate the steps leading to the issue being reported. Now it’s simply a case of sending the FloSCRIPT file whereupon the support engineer can replay it (using [Project/Run FloSCRIPT...]) to repeat the steps directly.

Although FloTHERM has a wealth of functions and features, often these operate at a lower level than the input might be defined at. Sure, it’s possible to define a transient variation of power dissipation as a function of time, using inputs such as start time, end time, power multiplier, attachments of such transient attributes to those objects that should vary their power dissipation in time (e.g. via RefDes of all actives). However this is somewhat removed and cumbersome when compared to how the input might be considered by the user, e.g. ‘the device should be in idle mode for 20 seconds, receiving data for 70 seconds then play video for 120 seconds’ where a table of power dissipations reflects these differing modes of operation. FloSCRIPT can be bought to bear on this, enabling the input to be phrased intuitively, and for the FloSCRIPT to do the low level implementation of this input.

A FloSCRIPT generating spreadsheet example is installed to \flosuite_v10\flotherm\examples\FloSCRIPT. It enables capture of the simulation intent directly. A lookup table indicates the various power dissipation levels, per RefDes, for each mode of operation of the model. The transient power profile itself is captured via a Duration vs. Mode table. The ‘Create FloSCRIPT file’ button then runs Visual Basic scripting to convert the input into a series of commands that can be applied to a loaded model, again via  [Project/Run FloSCRIPT...].


Running the FloSCRIPT on a loaded model will, in one click:

  • set the model to transient
  • define the overall transient solution time
  • define appropriate time patches with efficient time step distributions
  • create transient attributes that specify the power dissipation vs. time
  • attach the transient attributes to the relevant thermal attributes (using RefDes as the keying)

If you have to demonstrate the thermal compliance of your model in a number of differing customer environments then such an automation may save you a massive amount of time.

FloSCRIPT together with FloXML provide a wealth of other automation opportunities. Byron Blackmore gave an excellent overview of both automation technologies in this webinar, well worth checking out.

If I had an independent report to prove it I’d say that, unlike any other comparable CAE tools, it’s the inherent simplicity and subsequent robustness of FloTHERM’s underlying technology that enables FloTHERM to be automated to this extent and that, although other tools purport to have similar technologies, attempting to automate them is compromised due the amount of manual intervention required when the automation fails.  I don’t though, so I won’t.

10th June 2014, Ross-on-Wye.


4 June, 2014

FloTHERM’s strength has always its been its robustness, founded on a simplicity of technology that we’ve tried not to compromise over its 25 year life. This is no truer than in its 3D CAD drawing interface. More Lego than Sculpting in its capabilities, it’s always been quick and easy to mock up a conceptual cooling architecture for a proposed design. FloTHERM V10 provides a step change in usability when it comes to such 3D sketching.

FloTHERM’s CAD drawing interface is not a fully fledged 3D MCAD type environment. Geometry isn’t based on sketches extruded into features and such like. (For that fully MCAD enabled FloTHERM experience we’ve developed FloTHERM XT). FloTHERM has a set of primitive shapes out of which geometry is created, either manually using click/drag or automatically created by converting existing MCAD geometry into these primitives using the FloMCAD Bridge window. Such an approach isn’t new. Lego has been around since 1932 and if anything it’s popularity is greater now than ever before. Maybe due to the very low barrier to adoption, it’s simple, and fun!


The display of the geometry in FloTHERM’s Drawing Board has to date been rendered in wireframe only. In recent years as the size and complexity of FloTHERM models has exploded due to 64 bit support and the lifting of the lid on the old 32 bit 2GB (3GB with a trick) addressable memory limit. Trying to manipulate geometry in wireframe only is notoriously difficult. So in V10 we added the option to render geometry as solid.

Wireframe Solid

Objects can be translated, resized, rotated in either view, including a new cursor change on mouse over a grab handle. Speaking of views, to the 4 view /1 view option we’ve added a couple of 2 viewport modes (horizontal and vertical) as well as the ability to resize each view port:


All the the existing view manipulation short cuts have been retained; f(irst angle projection), t(hird angle projection), r(efit) etc. as well as an extremely useful new shortcut v(iew selected) where the view will be zoomed into the currently selected object(s). [Menu entry equivalents exist for all shortcuts of course]

KeyboardSnapAlign2D shape manipulation in Microsoft Office products has always been intuitive. In the 3D FloTHERM CAD environment we’ve replicated some of that simplicity. The existing ‘snap to object’ snap mode, where an object will snap to another one on a move or resize as soon as object being moved gets to within a few pixels of another object, has been given a keyboard equivalent. Pressing the Alt key together with a keyboard arrow key will move an object in that coordinate direction, snapping to the next object edge in that direction. Going one step beyond Microsoft, in addition to the standard left, right, up etc. align options we’ve also added an ‘Align to Center’ option that’s proving to be repeatedly useful!

Lego_PC“It’s not called modelling for nothing”. You can use Lego to build models of a range of different things, from buildings to spaceships to dinosaurs to computers :)

4th June 2014, Ross-on-Wye


3 June, 2014

Temperature has always been, and will continue to be, a good enough leading indicator of product reliability. As a parameter it is easy to specify a maximum rating value and relatively easy to measure. However it is not temperature itself that directly causes product failure, more often than not it is some kind of mechanical fracture or deformation that itself is fuelled by thermo-mechanical effects. Differences in temperature and differences in material properties cause objects to bend, deform and possibly break. When applied to electrical circuits any break in that circuit is catastrophic in that, to put it simply, the product stops working.

Einstein famously once said that “Everything should be made as simple as possible, but not simpler”. Industrial processes tend naturally to gravitate towards this as well. Simplicity is more robust and cheaper. Humans also, whilst not inherently lazy, are programmed not to expend energy unnecessarily. It is no surprise that temperature has proved such a useful metric to gauge electronic product reliability, why go any further? Looking at thermo-mechanical behaviour will provide a more explicit understanding of the actual physics of failure. Solder joint fracture is by far the most common method of failure and whilst bulk temperature prediction may indicate probability of failure, detailed stress/strain prediction will indicate exactly where and under what conditions that failure will occur.

FLOFEA_ExportWe have not incorporated a thermo-mechanical simulation capability in FloTHERM V10, instead we have enabled FloTHERM 3D temperature predictions to be exported for subsequent import into existing FEA tools. This export capability is straightforward and requires no additional license. Simply select an assembly in a solved project, RMB pop-up and Export Assembly to ‘FLOFEA’. A file will be written that contains temperature values for all solid cells that reside in the selected assembly, together with information about cell size and location.

An FEA geometry and mesh is likely to differ from that used for thermal simulation. Thermal behaviour allows for certain simplifying approaches to be adopted for thermal simulation that are invalid for a mechanical simulation. Solder ball modelling being a case in point. From a thermal perspective so long as the thermal resistance of the ball, in the direction of heat flow, is preserved, the ball can be represented as a far more mesh efficient cuboidal shape. Not appropriate for mechanical simulation, especially considering it’s the stress levels in the solder ball that is the key output to be simulated and those values are geometry dependent.

FSIMApper_InterpolationThe  FLOFEA file has been written so as to be importable into a 3rd party interpolation tool, namely MpCCI FSIMapper from Fraunhofer SCAI. MpCCI is a well established and highly regarded set of tools to enable CAE interfacing. An existing FEA mesh is imported into FSIMapper, as is the FLOFEA file, whereupon an intelligent interpolation is performed, mapping the FloTHERM temperatures onto the FEA mesh, the interpolation algorithms accommodating for differences in the geometry definition between the two model types. The FEA mesh and interpolated temperatures is then written out and can be set as thermal load boundary conditions in Ansys Mechanical or Abaqus.

For more information either contact Fraunhofer SCAI directly or contact your local FloTHERM account manager.

3rd June 2014, Ross-onWye

, , , , ,