search

afarran / swm2m_avl_tests

Feature tests of AVL agent
0 stars 0 forks source link

For setting AirBlockageTime = 0 terminal does not enter to AirCommBlocked state #47

Closed ArturMalyszewicz closed 9 years ago

ArturMalyszewicz commented 9 years ago

An Air Communication Blocked (AirCommBlocked MIN 33) event occurs when a from-mobile message has been waiting in the terminal’s transmit queue for more than AirBlockageTime (PIN 22). Documentation says that AirBlockageTime is measured in minutes and allowed values are: minimum: 0, maximum: 1440. But for setting AirBlockageTime = 0 terminal does not enter to AirCommBlocked state at all.

The question is: Does 0 mean that this feature is disabled (bug in documentation) or does 0 mean that terminal should enter AirCommBlocked immediately (bug in AVL)?

Steps to reproduce:

  1. Set AirBlockageTime = 0
  2. Set movingDebounceTime to 5 seconds
  3. Simulate speed above stationary speed threshold
  4. Simulate air communication blokage
  5. Wait until MovingStart message is generated (air communication blockage timer should start counting from now)
  6. Check if terminal enters AirCommBlocked state - it does not.
afarran commented 9 years ago

0 means disabled. This is a documentation issue