Meter data duplicated?

  • 1
  • Question
  • Updated 3 weeks ago
For some time I've wanted to put some software damping on the S-meter to stop it bouncing around quite so wildly, so that took me into code I've not looked at for a while to check timings.

I was perplexed to discover that my API library was sending three identical S-meter events to my application within 1ms of one another and assumed I had a bug. In fact, it appears that the radio is sending multiple copies of meter data per packet.

In the following screen-scrape of a Wireshark UDP packet capture, the S-meter is meter 0x0015:



The three sets of S-meter data are highlighted. Further inspection shows that other meters are sent multiple times as well. As the meter data are always identical in a given packet I've fixed the issue by only processing the first occurrence of each meter per packet.

Is it a bug, a feature or by design?

73, John, G3WGV
Photo of John G3WGV

John G3WGV

  • 169 Posts
  • 33 Reply Likes

Posted 3 weeks ago

  • 1
Photo of Doug - K3TZR

Doug - K3TZR

  • 72 Posts
  • 5 Reply Likes
John,

I've added some code to my API Tester to check for meter duplication in a single Vita meter packet. The code keeps track of which meters are contained in a single Vita meter packet and how many times it has seen that meter in the packet. It produces a printout whenever the count for a meter is greater than one.

Here's a portion of what got printed:

meter = 5, count = 2

meter = 1, count = 2

meter = 14, count = 2

meter = 17, count = 2

meter = 19, count = 2

meter = 2, count = 2

meter = 18, count = 2

meter = 1, count = 2

meter = 11, count = 2

meter = 12, count = 2

meter = 10, count = 2

meter = 13, count = 2

meter = 14, count = 2

meter = 5, count = 2

meter = 6, count = 2

meter = 7, count = 2

meter = 3, count = 2

meter = 1, count = 2

meter = 8, count = 2

meter = 17, count = 3

meter = 19, count = 3

meter = 22, count = 3

meter = 18, count = 3

meter = 2, count = 3

meter = 4, count = 3

meter = 9, count = 3

meter = 21, count = 3

meter = 23, count = 3

meter = 24, count = 3

meter = 1, count = 3

meter = 5, count = 3

meter = 1, count = 3

meter = 14, count = 3

meter = 17, count = 3

meter = 19, count = 3

meter = 2, count = 3

meter = 18, count = 3

meter = 1, count = 3

meter = 11, count = 2

meter = 12, count = 3

meter = 10, count = 3

meter = 13, count = 3

meter = 14, count = 3

It seems to happen constantly. As you asked, Is this by design or is it a bug?
Photo of John G3WGV

John G3WGV

  • 169 Posts
  • 33 Reply Likes
Hi Doug,

Yes, that tallies with what I am seeing on my V2.1.33 system. I'm surprised I'd not noticed it before and I wonder if it might have been introduced with V2?
Photo of Doug - K3TZR

Doug - K3TZR

  • 72 Posts
  • 5 Reply Likes
My system is also 2.1.33. I'm not sure about previous versions.
Photo of John G3WGV

John G3WGV

  • 169 Posts
  • 33 Reply Likes
I'm sure Eric will be along in a bit to give us the inside track.
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 659 Posts
  • 199 Reply Likes
Looks like a bug to me.  I wouldn't expect the same meter to show up in the same meter packet more than once.  I've captured this as #6250 for tracking.  We will let you know what we find.
Photo of John G3WGV

John G3WGV

  • 169 Posts
  • 33 Reply Likes
Thanks Eric.