Ticket Created
over 4 years ago

WERETECH-9909

Unsupported constellation option (CONSTELLATION_GLONASS)

I use the latest Garmin SDK 3.2.3 on a Windows 10 computer and get following error when using Position.CONSTELLATION_GLONASS:

Error: Unhandled Exception

Exception: Unsupported constellation option

Following sequence leads to the error:

if (Sensor has :enableSensorType) {
  // Enable GPS with continuous location updates using GPS, GLONASS and GALILEO
  Position.enableLocationEvents({
    :acquisitionType => Position.LOCATION_CONTINUOUS,
    :constellations => [ Position.CONSTELLATION_GPS, Position.CONSTELLATION_GLONASS, Position.CONSTELLATION_GALILEO ]
  },
  method(:onGpsSensorInfoUpdate)
);

Without using GLONASS as shown in following sequence it works fine:

if (Sensor has :enableSensorType) {
  // Enable GPS with continuous location updates using GPS, GLONASS and GALILEO
  Position.enableLocationEvents({
    :acquisitionType => Position.LOCATION_CONTINUOUS,
    :constellations => [ Position.CONSTELLATION_GPS, Position.CONSTELLATION_GALILEO ]
  },
  method(:onGpsSensorInfoUpdate)
);

Robs_1976
Parents
  • over 4 years ago in reply to jim_m_58

    's assumption here is correct--this API just enables the combinations made available by the system, but I can understand why you'd try using all three constellations. We don't explain what constitutes an "invalid combination of constellation values."

    I'm going to see if there's any clarification we can make in our docs.

Comment
  • over 4 years ago in reply to jim_m_58

    's assumption here is correct--this API just enables the combinations made available by the system, but I can understand why you'd try using all three constellations. We don't explain what constitutes an "invalid combination of constellation values."

    I'm going to see if there's any clarification we can make in our docs.

Children
  • over 4 years ago in reply to Brandon.ConnectIQ

    The problem is that the combinations that are allowed can vary across devices. It could potentially vary across firmware versions on the same device, but this isn't very likely.

    We could clarify by listing the known valid combinations, but I don't see any way to generate the list dynamically, which means that the list would have to be manually maintained.