TNF API Changes

  • 2
  • Idea
  • Updated 4 months ago
  • Implemented
  • (Edited)
In the next release after v2.0.17 we will be making modifications to TNF subscriptions. TNFs will no longer be subscribed to by default and in order to receive updates related to TNFs you will need to explicitly subscribe to them using the command 'sub tnf all'

If you're using FlexLib you can also set the property IsTNFSubscribed to true in order to subscribe.
Photo of Greg Folker

Greg Folker

  • 3 Posts
  • 0 Reply Likes

Posted 1 year ago

  • 2
Photo of John G3WGV

John G3WGV

  • 189 Posts
  • 36 Reply Likes
Thanks for the heads-up Greg. Will the API version number be updated? Alternatively, does it cause any problem with the current version to issue the sub tnf message?
Photo of Greg Folker

Greg Folker

  • 3 Posts
  • 0 Reply Likes
The API version will be updated when this change goes live. 

It doesn't hurt to issue the command right now in the current version of the API but it will return with an error because it won't know what the command is. 
Photo of John G3WGV

John G3WGV

  • 189 Posts
  • 36 Reply Likes
Thanks Greg. That's the best of all options. My controller doesn't really know about TNF yet but I was thinking about changing that, so I'll bear these changes in mind. I already use the version number to determine the behaviour of some sections of my code. Do you yet know the new version number? 1.3.0.1 perhaps for a small change like this?

Is there a public document anywhere that details the changes through the various versions?
(Edited)
Photo of Greg Folker

Greg Folker

  • 3 Posts
  • 0 Reply Likes
For a minor change like this the version number would most likely reflect a small change, such as 1.3.0.1. At the moment we do not know an exact number but it will be greater than 1.3.0.0, much of that depends on how many other large/smaller changes we try to fit into the same release.

As far as documentation goes for this change we will be updating the Wiki in the near future to reflect the new sub commands for TNFs which can be found here http://wiki.flexradio.com/index.php?title=TCP/IP_sub

-Greg
Photo of Jim Shaffer (KE5AL)

Jim Shaffer (KE5AL)

  • 37 Posts
  • 0 Reply Likes

In v2.0.19 I set IsTNFSubscribed to true, and got notified of TNFs when I connected to the radio.  If I'd marked the TNF as permanent, I got notified of the TNFs marked as permanent across a reboot of the radio.  However, with version 2.3.9, this is no longer happening.  I get notified of the TNFs that exist if I don't power off the radio, but once powered off, all TNFs, including those marked as permanent, are lost.
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 3032 Posts
  • 669 Reply Likes
That should not be happening, I have mine set as band markers and they never move or go missing. You seem to have a persistance problem in the radio. I recomend a factory reset that resets the persistance data base. Then up load your profiles back in.
Photo of Jim Shaffer (KE5AL)

Jim Shaffer (KE5AL)

  • 37 Posts
  • 0 Reply Likes

I did a factory reset, then without importing anything, I created a TNF, but it still didn't persist across a reboot of the radio.
Photo of Jim  KJ7S

Jim KJ7S

  • 138 Posts
  • 23 Reply Likes
If you create a TNF, yuou will have to right click and 'Remember' it, then it will persist through a restart and you will then have to delete it when you are ready to get rid of it as it will remain 'on' whenever it is within the passband.