search

afarran / swm2m_vms_tests

Feature tests for VMS agent
0 stars 2 forks source link

GpsBlockedState property is change after incorrect debounce time (later than expected) #29

Open ArturMalyszewicz opened 9 years ago

ArturMalyszewicz commented 9 years ago

GpsBlockedStartDebounceTime (PIN 35) is the debounce time when GpsBlocked state becomes true before registering the event. When gps blocked event is triggered (fix is older than MaxFixTimeout) GpsBlockedState is not changed after GpsBlockedStartDebounceTime but some 50 seconds later.

Steps to reproduce:

  1. Set MaxFixTimeout (PIN 12 in position service) to 60 seconds (that is minimum value for this property)
  2. Set GpsBlockedStartDebounceTime (PIN 35 in VMS service) to 1 second
  3. Simulate good GPS signal quality (fixType = 3) and check GpsBlockedState (PIN 37) - that is supposed to be false.
  4. Simulate GPS signal loss (fixType = 1) and wait for time MaxFixTimeout.
  5. Check GpsBlockedState property - it does not change after GpsBlockedStartDebounceTime (1 second) but after ca 40 seconds.

Expected behaviour is that the state changes according to GpsBlockedStartDebounceTime.

ArturMalyszewicz commented 9 years ago

This is an documentation issue - there is no information that GPS check periodically every 1 minute. GpsBlockedStartDebounceTime and GpsBlockedStartDebounceTime is obeyed correctly.

ArturMalyszewicz commented 9 years ago

In documentation for version 1.4.1 GPS check interval is not mentioned. Is this no longer applicable?