Apart from the major new features 'CCFC' and 'Web Contents', KULI 10 also offers a list of usability enhancements. These include a 64 bit version of the calculation kernel of KULI, default values for input COM objects and more.
64 bit version of KULI
Starting with KULI 10 two different versions of the calculation kernel of KULI will be installed during setup, one for 32 bit, one for 64 bit. Both kernels will deliver exactly the same simulation results, but they run in different modes. The big benefit is that software (e.g. Matlab/Simulink® or Microsoft Excel®) based on 64 bit can now be connected over COM with KULI.
In Excel you just need to select the desired version in the Visual Basic Editor in the menu “Tools->References”, in Matlab you need to specify the correct version when setting up the activeX control manually. If you use Simulink, you can simply browse for the appropriate version using the new Simulink KULI toolbox.This provides a graphical way to integrate KULI in your Simulink model without having to write a line of code. Detailed instructions on how to choose the appropriate version are also provided in the new KULI online manual. And the good news is: You don’t have to worry about 32 or 64 bit when creating your KULI models. Both versions use exactly the same KULI files.
Deleting multiple components
A small but long awaited feature that makes life easier: When you select multiple items either in the table in the “General data” tab or graphically in the window “Circuits / Air Path” you can delete them with a single confirmation. So KULI does not ask for each individual component any more, just for the complete selection.
Default values for COM objects
COM objects and the COM interface in general are among the most popular features in KULI. We have enhanced this feature in KULI 10 by introducing default values for COM objects. So for any input COM object there is now the option to include a default value.
Figure 1: Default values for COM objects
This default value will be used in the simulation if the COM object is not set from outside (i.e. from an external application like Microsoft Excel®). In this case the COM object works pretty much like a constant. As soon as the COM object is set via the COM interface, the default value is overridden by the new value. The big advantage is that you can now use the same KULI model to be run either from KULI GUI itself or from an external application. There is no more need to replace COM objects with constants when switching from externally controlled models to models that are controlled from KULI itself. This is also extremely useful when you want to test your models from within KULI that you want to use later on using the COM interface.