User Manual

GAMMA instabus
Release: 12/2015
Application Program Bus Interface Modules M130, M131, M132 and M135
Runtime Environment for KNX-Processors 184/11 and 184/21
Siemens AG pages 17 Technical Manual
Building Technologies
Control Products and Systems
P. O. Box 10 09 53, © Siemens AG 2015 page 17
D-93009 Regensburg Subject to change without further notice.
6 Release Notes for new firmware revisions
6.1 Introduction
New firmware revisions will improve the stability of the operating system. All applications that
are developed with older firmware revisions can still be used with new firmware revisions
without recompiling or any modifications.
6.2 Firmware revision 2.00
6.2.1 Timer
In firmware revisions below 2.00 it is possible that the function 'GetSystemTime' returns once
a system ticks value that is about 106ms in the past. An immediate second call of this
function will return the correct value. With firmware revision 2.00 the function
'GetSystemTime' always returns the correct value.
Application programs for firmware revisions below 2.00 should write the following statement
in the first line of 'AppInit()' to prevent the described behavior above:
CR001 = 0xFFFF;
6.2.2 TPUART-Communication
It is rarely possible that the communication between the microcontroller with firmware
revisions below 2.00 and the TPUART will stall in transmit way (microcontroller to TPUART).
A failsafe function resets the communication and the system works again correctly.
In firmware revision 2.00 the communication between the microcontroller and the TPUART
was improved to avoid this possibility of this stall of transmit communication.
6.2.3 FT12-Communication
All changes of the "M13x_FT12_Patch" and "M13x_FT12_Patch_v2" (necessary for firmware
revisions below 2.00) are included in firmware revision 2.00. That means with firmware
revision 2.00 the "M13x_FT12_Patch" and "M13x_FT12_Patch_v2" are no more necessary.
Applications with one of these patches will still work correctly in firmware revision 2.00.
6.3 Firmware revision 2.01
6.3.1 Internal timing
In firmware revisions below 2.01 there was a very small probability for a timing problem
(order 10
-5
). In this case a single telegram could be lost.
If the lost telegram contains the byte 0x0B or 0x8B a restart of the controller could be
possible.
In firmware revision 2.01 this issue was fixed.