DolphinAPI

This page contains the summariy of relevant known issues for DolphinAPI sorted by software version.

- For new software projects we highly recommend to always use the latest release version.
- If you still need to work with older DolphinAPI version, make sure to read the tables below to see the known issues.
- You can find the history of changes in the What's new? file .

DolphinAPI 2.3.1.0

ID Version Affected Title Description Solution Work- around Fixed Version

DolphinAPI 2.2.5.0

ID Version Affected Title Description Solution Work- around Fixed Version
5231 2.2.5.0 Radio settings with same parameters besides revision In this release there are radio settings files with similar parameters, where only the revision is different. fixed, workaround Please take the radio settings with higher number. 5231 2.3.0.0

DolphinAPI 2.2.3.0

ID Version Affected Title Description Solution Work- around Fixed Version
5168 2.2.3.0 and older Wrong reset reason after watchdog reset when fly wheel interrupt occured too. When fly wheel timer is running and the application becomes an unexpected watchdog reset before entering sleep mode the reset reason is fly wheel reset not watchdog. not yet
5211 2.2.3.0 and older WDT reset with watchdog smaller than 150ms If the WDT counter is set to small values (<150) then the WDT reset happens even if CLR_WDT is called periodically. fixed, workaround use watchdog periode bigger as 150ms OR don't call CLR_WDT sooner than 30ms 2.2.5.0

DolphinAPI 2.2.1.0

ID Version Affected Title Description Solution Work- around Fixed Version
4955 2.2.1.0, 2.1.0.0, 2.0.0.0 Wrong remote management function number The function number in reman_sendMessage is not transmitted correctly. The upper nibble of the second byte gets lost. E.g. Fn = 0x0123 becomes Fn = 0x0103. fixed none 2.2.3.0
4926 2.2.1.0, 2.1.0.0, 2.0.0.0 Smart Acknowledge Reclaim improovement needed When performing a Smart Acknowledge Reclaim process, the first or second try may fail. There are several reasons (ghost telegrams and noise on the receiving interface, reclaim pause duration). Many improvements were performed and confirmed that with next API the reclaim rate is significantly better. fixed none 2.2.3.0

DolphinAPI 2.0.0.0, 2.1.0.0

ID Version Affected Title Description Solution Work- around Fixed Version
3852 2.1.0.0, 2.0.0.0 Reading WXIDIO and WXODIO is not working correctly When WXIDO and WXODIO are configured as input reading the pins will return incorrect values. fixed 3852 2.2.1.0
4111 2.1.0.0, 2.0.0.0 radio stops receiving telegrams if analog-to-digital converter is used In applications where the analog-to-digital converter is used and receiving radio telegrams is required it can happen that the radio receiving gets stuck. fixed 4111 2.2.1.0
4170 2.1.0.0, 2.0.0.0 Radio buffer optimization Currently there is no radio buffer dedicated to transmitting telegrams. Which can lead to a situation where ist not possible to send a radio telegram with radio_SendTelegram() without prior handling to received telegrams (radio_getTelegram()). fixed 4170 2.2.1.0
4220 2.1.0.0, 2.0.0.0 radio_getTelegram() does not deliver STATUS information about the strongest subtelegram The API scheduler compresses redundant received sub telegrams (within the rx maturity time) into one buffer. The signal strength information u8Dbm is updated with every received sub telegram, in that way that the strongest dBm value is stored.

There is an error where the STATUS field is taken from the first received sub telegram instead of the strongest subtelegram.
fixed none 2.2.1.0
4247 2.1.0.0, 2.0.0.0 internal XTAL stable flag not working correctly The internal XTAL stable signal is not working correctly. Under certain conditions its possible that the XTAL stable signal is falsely indicating a stable clock signal. Therefore the pwr_selectXTAL() or pwr_selectXTALStby() function will switch from the internal RCOSC clock to the XTAL clock too early. This can cause unexpected behavior. In some rare cases this may lead to FLASH corruptions.

Its strongly recommended to update to latest API!
fixed none 2.2.1.0
4275 2.1.0.0, 2.0.0.0 Unnecessary ADT encapsulation with DestinationID=0xFFFFFFFF When the DestinationID is 0xFFFFFFFF (Broadcast) then the radio_sendTelegram functions tries to encapsulate the telegram to ADT.

In case 0xFFFFFFF no ADT encapsulation is needed, because all telegrams without DestinationID are explicitly broadcasts.
fixed none 2.2.1.0
4385 2.1.0.0, 2.0.0.0 radio_enableRx() does fail in case of ongoing radio transmission The radio_enableRx(TRUE) function does not enable the receiver in case of ongoing radio transmission. fixed none 2.2.1.0
4393 2.1.0.0, 2.0.0.0 generic interrupt (Timer1, GPIO_ADIO0_3, GPIO_ADIO4_7, GPIO_WXIDIO_O_I) stops working The generic interrupt stops working in case more than one interrupt source is active and two events occur simulatanious. In this case it's possible that only one interrupt flag is cleared and therefore the other flag remains set and no further interrupts are triggered. fixed none 2.2.1.0
4425 2.1.0.0, 2.0.0.0 It is not possible to write with mem_writeFlash to the LOG area The mem_writeFlash does incorrectly checks the border of allowed addresses therefore it is not possible to write to the LOG area of FLASH (Address: 0x7E00). fixed none 2.2.1.0
4516 2.1.0.0, 2.0.0.0 Incorrect PWM signal when changing from higher duty cycle to lower duty cycle PWM is high in one period when changing from higher duty cycle to lower duty cycle. fixed none 2.2.1.0
4565 2.1.0.0, 2.0.0.0 filter_init() clears all filters when changing the IDX_FILTER_OPERATOR parameter Calling filter_init() clears all filters even though only one parameter needs to be changed:

filter_init(filter_param, IDX_FILTER_OPERATOR); - this command should only set the operator, but instead it also clears all the added filters
fixed none 2.2.1.0
4594 2.1.0.0, 2.0.0.0 Unwanted glitch on GPIO2 during initialization Io_init() pin initialisation causes a glitch on WXIDIO and WXODIO. fixed none 2.2.1.0
4669 2.1.0.0, 2.0.0.0 Smart Acknowledge Learn Reclaim checks mailbox index In the message Smart Acknowledge Learn Reclaim, the mailbox index is not used. But the controller checks the Mail Box index in Learn Reclaim telegram (which he should not do) and if a value other then 0x00 is specified as Mail Box the reclaim fails. fixed 4669 2.2.1.0