RequiredVersion in API

  • 1
  • Problem
  • Updated 2 years ago
In FlexRequiredVersion.cs, looks like Jenkins is using an old version number?

private static ulong required_version = FlexVersion.Parse("");

This results in UpdateConnectedState() setting ConnectedState to "Update" when Status = Available.

ConnectedState     : Update
Connected          : False
WanServerConnected : False
Status             : Available

Not a big deal for me, just came across it and thought I should report it.


Photo of Robbie - KI4TTZ

Robbie - KI4TTZ

  • 484 Posts
  • 78 Reply Likes

Posted 2 years ago

  • 1
Photo of Mark - W3II

Mark - W3II

  • 260 Posts
  • 55 Reply Likes

Robbie I had the same question. For an app using the FlexAPI as is the short answer is Radio.ConnectedState should be ignored and you should use Radio.Status. The reason for this is ConnectedState compares the radio version to a single value and if it does not match ConnectedState is set to update. So this means if your app only works with a specific version like SmartSDR then you have to update the version value to the version you require then rebuild the API DLL. If your app is coded to work with any version then just ignore the ConnectedState. You could also update the value and change the ConnectedState logic to look for same or newer versions.

I hope this helps.

73, Mark AA3RK

Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 952 Posts
  • 359 Reply Likes
Correct.  We don't update this file in version control as it is constantly changing internally and would result in a mess.  You're welcome to change that value to the latest version if that helps with your application.
Photo of Stan - VA7NF

Stan - VA7NF

  • 488 Posts
  • 120 Reply Likes
Does not the API inspect the version number presented and respond in that version's protocol?  Supported levels may be withdrawn after say 1 year or a major release.
This permits 3rd party users time to upgrade and avoid update urgency on each release that may or may not disable 3rd party execution.