Hello everybody,
we had a strange incident in our field try:The osal_start_timer() did not cause an event to be called. (ZStack1.4.2-1.1.0)
This function has been worked all the time in the last three months every 60min, but over the weekend the timer did not expire or whatever and an event did not get called. We haven't programmed another time-out and so the Coordinator stuck in a situation where it was waiting for the event in order to continue "as usual".
Is it safer to call osal_start_timerEx() as it has been changed in ZStack 1.4.3?
The regarding code extract:
in sapi.c:
osal_start_timer( MY_REPORT_EVT, 4000 );
In SimpleCollector.c:
/******************************************************************************
* @fn zb_HandleOsalEvent
*
* @brief The zb_HandleOsalEvent function is called by the operating
* system when a task event is set
*
* @param event - Bitmask containing the events that have been set
*
* @return none
*/
void zb_HandleOsalEvent( uint16 event )
{
// TIMEOUT FOR REPORTS
if (event & MY_REPORT_EVT )
{