User guide

15
VTB USER GUIDE
4.4 Target Hardware Configuration
An application must always refer to the target hardware. That allows VTB to preconfigure for the selected hardware so
it can use the relative function-call, use the appropriate memory addresses, signal the specific errors, use the correct
debug, etc.
Normally it is set before starting the application but we can change it ever after to adapt the same application at
another hardware.
Target Hardware
This Combo allows to choose the code of target hardware. To facilitate the programming, in the list, beyond the single
products, are also some preconfigured combinations such as:
NGM13/LPC20 – NG35/LPC40 etc.
They refer to a combination of a NGM13 or NG35 CPU coupled with a Promax serial terminal LPC20, LPC40.
Saving memory reserved area
This option selects the amount of internal memory reserved (called IMS) to the application data saving (ex. Parameters,
recipes, etc.). This memory is organized in blocks of 256 bytes therefore it must select the number of blocks to reserve
for each recipes and the max number of recipes. For example if the memory needed for one recipe is 300 byte, we must
set 2 blocks (512 byte). Normally the IMS memory is removed from the flash memory reserved to the application, keep
in mind that when you set this option. This option isn't valid for the hardware in which the CODE FLASH isn't shared
with the data saving memory (ex. NGM13).
Create framework component
VTB can create a DLL Component Model to integrate in a Framework .NET application.
That allows a direct control of the Hardware resource from external Host such as PC equipped with operative system like
Windows XP, Vista, 7, CE or other supporting Framework (see Framework Component chapter ).
If create framework component is checked the component type must be choose (Windows Xp or Windows CE) and also
the DLL component name. A component framework file will be create in the same directory of VTB project.