Which is the correct required firmware version?

  • 1
  • Question
  • Updated 4 years ago
  • Answered
  • (Edited)
This is a question targeted ideally to Eric, or Steve if you need a break from setting up.
I found something peculiar.
I updated my radio via SSDR for Windows. All appears good. Yet,
FirmwareRequiredVersion.cs specifies 1.3.15.742, which is actually lower than the comment on that line specifying 1.3.21.1858 and during Discovery the version returning is 1.4.11.60. This causes the software to mark the radio as needing an upgrade under setVersion in Radio.cs

By way of clarification. In the Windows Radios Listbox my radio appears with a status of "Available" In tracing through the code with the 1.4.11 source, it is in a "Update" status.

Is the shipped FirmwareRequiredVersion.cs not the current one? Shouldn't the Required firmware version in FirmwareRequiredVersion.cs be 1.4.11?

Am I missing something?

Thanks,
Walt
Photo of Walt - KZ1F

Walt - KZ1F

  • 3040 Posts
  • 643 Reply Likes

Posted 4 years ago

  • 1
Photo of Walt - KZ1F

Walt - KZ1F

  • 3040 Posts
  • 643 Reply Likes
apparently editing a thread doesn't repost it.
Photo of Burt Fisher

Burt Fisher

  • 1105 Posts
  • 383 Reply Likes
I really know little about Walt. I assume he is much smarter than I. What I know about "bump" is what I saw on for sale forums when people want their item to go ahead of others. So is this not the case here?

He did threaten me saying he was giving me a warning, I responded what was his, "or else." If I am wrong about "bump" I owe an apology. I am not saying HE is classless, I am referring to "bump". Does his question trump others?
Photo of Walt - KZ1F

Walt - KZ1F

  • 3040 Posts
  • 643 Reply Likes
I am trying VERY hard not to stoop to your level. You were never 'threatened'. I will defer to the management of FlexRadioSystems to deal with you. In my opinion, I have never seen a post, bar the 'get a license then we'll discuss 6000 series (which I agreed with) that added any value. You snipe at people, you are consistently rude and now you've made this personal. As far as I am concerned you should be barred from this board.
!) it is NOT your place to pass judgement on other's questions.
2) it is NOT your place to pass judgement on what one does when their question when, due to the sheer volume of obsequious posts falls to the bottom of a second or third page. The one I just bumped has lingered unreplied to for a week. This is NOT cutting in front of others
3) it is NOT your place to make snide personal attacks in someone else's question, comment or problem.
4) if you can't add value just don't respond.
5) As far as I am concerned, you don't exist.
6) It is my sincerest hope that as far as you are concerned I don't exist. Therefore I should NEVER expect to see some personal attack or other snide-assed remark from you in ANY of my threads. There is no question I ever anticipate having where you are capable of providing an answer.

Again, this is not the first time the 'quality' of your ruminations has or will come to the attention of Flex management.
Photo of Burt Fisher

Burt Fisher

  • 1105 Posts
  • 383 Reply Likes

Thank you for your response.

What personal attack? I called your "bump" classless, NOT you and you repeated, "bump" numerous times.  I have yet to see anyone else HERE do that.

As far as I can see you are a great contributor, far far more than I.  Wasn't it you who said yesterday you had given me two warnings and this was my last chance? Or am I getting senile? You despise personal attacks, so what is the above? If you think I owe you an apology I will render it, just inform me specifically how I offended you.

If Flex wants to ban me so be it, but I know of no rule I violated. Whether they follow your advice or not does not affect my view that the company is one of the top customer service companies ever. Maybe appeasing you is good for business?

Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3593 Posts
  • 1446 Reply Likes
@Burt

You just earned another 10 points toward the 2015 Curmudgeon of the Year Award at Dayton 2016.  You are still running far behind my contest partner in crime and perennial winner of the award Dennis N6KI.  But who knows, Dennis now wants to try a Maestro and a Flex SO2R box for CQWWDX so perhaps he is leaving you an opening to sneak past him to the podium...
Photo of Burt Fisher

Burt Fisher

  • 1105 Posts
  • 383 Reply Likes
I will try to bump my comments down a notch. I do much better with 9 year olds, they accept my admonitions when they try to cut the line. 
Photo of Abed - AB5ED

Abed - AB5ED, Employee

  • 23 Posts
  • 4 Reply Likes
The required firmware version is updated by our automated build process. Since this number constantly changes on a daily basis internally, and because this number is only useful for software updates that we send out, we don't keep this file updated.
Photo of Walt - KZ1F

Walt - KZ1F

  • 3040 Posts
  • 643 Reply Likes
Ah, Thank you Abed.
The version I have from the 1.4.11 software bundle still has 1.3.15
In Radio:setVersion:292:
if (_version != _req_version)
{
    _updateRequired = true;
}
_req_version is FirmwareRequiredVersion.RequiredVersion

setVersion is called in Radio:654 in the full, not default, ctor as the radio version is passed in from the VitaDiscoveryPacket.

The above check is not done in the setter only if it is a development build.
What the VitaDisoveryPacket passes in is 0x1040b000...
This, then, is how I am seeing the issue.
Is my interpretation of what Radio.cs is doing in error?

Thanks!
Walt - kz1f
Photo of Abed - AB5ED

Abed - AB5ED, Employee

  • 23 Posts
  • 4 Reply Likes
Walt, you are correct. We should really be updating the version to match whenever we release a new version of FlexLib. The FlexLib.dll is compiled with the correct matched version, which is probably why others don't have an issue. We'll update the source and make it available. Thanks!
Photo of Walt - KZ1F

Walt - KZ1F

  • 3040 Posts
  • 643 Reply Likes
this is weird, my last update didn't register as one...as it still shows the last activity being from Abed.

I'll update my FirmwareRequiredVersion but I still don't understand how the c# version doesn't fail the same way. Those code references are in your code.
(Edited)
Photo of Walt - KZ1F

Walt - KZ1F

  • 3040 Posts
  • 643 Reply Likes
Tim, this can be marked as answered
thanks,
Walt
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 9152 Posts
  • 3478 Reply Likes
Done

This conversation is no longer open for comments or replies.