|
As I read of updates -- and one specifically saying K3S -- is there going
to be a difference coming between what applies to K3S and the K3 itself? Thanks! -- 73 de Ted Edwards, W3TB and GØPWW and thinking about operating CW: "Do today what others won't, so you can do tomorrow what others can't." ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
Ted,
There already is a difference. K3 Utility figures out which you have and loads the matching firmware when there is a difference. It should be seamless whether you have a K3 or K3S. 73, Don W3FPR On 2/23/2017 9:51 AM, Ted Edwards W3TB wrote: > As I read of updates -- and one specifically saying K3S -- is there going > to be a difference coming between what applies to K3S and the K3 itself? > > Thanks! > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
Hi Don,
Hold on a second. Up to this point the firmware for the K3 and the K3S has been exactly the same. The firmware figures out at run time which features are available whether it being in the K3 or the K3S and behaves accordingly. Is there something changed here? That would really complicate things. AB2TC - Knut
|
|
Knut,
The functions of the K3 and K3S are the same, and will likely remain the same. The differences are in the hardware, so a 2nd MCU file has been in place for some time to allow for a change in the microcontroller used in later K3s and the K3S. I can envision this being expanded, not to change the functions, but to support minor differences in the hardware. Part of the Elecraft "magic", such things are transparent to the user. My point is that K3Utility sorts it all out, and does not have to be visible to the user, because the same steps to update firmware are used. 73, Don W3FPR On 2/24/2017 7:24 AM, ab2tc wrote: > Hi Don, > > Hold on a second. Up to this point the firmware for the K3 and the K3S has > been exactly the same. The firmware figures out at run time which features > are available whether it being in the K3 or the K3S and behaves > accordingly. Is there something changed here? That would really complicate > things. ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
|
Administrator
|
The differences between K3 and K3S firmware features are very minor, all having to do with hardware addressing. For example, the K3S has a second attenuator section. Other than this, there is no difference in functionality.
The reason there are two different .hex files in the load package is that older K3's had a different display controller. This affects so much of the code that I build it two different ways. K3 Utility detects the controller type and loads the associated image. 73, Wayne N6KR Sent from my iPad > On Feb 24, 2017, at 5:23 AM, Don Wilhelm <[hidden email]> wrote: > > Knut, > > The functions of the K3 and K3S are the same, and will likely remain the same. The differences are in the hardware, so a 2nd MCU file has been in place for some time to allow for a change in the microcontroller used in later K3s and the K3S. > I can envision this being expanded, not to change the functions, but to support minor differences in the hardware. Part of the Elecraft "magic", such things are transparent to the user. > > My point is that K3Utility sorts it all out, and does not have to be visible to the user, because the same steps to update firmware are used. > > 73, > Don W3FPR > >> On 2/24/2017 7:24 AM, ab2tc wrote: >> Hi Don, >> >> Hold on a second. Up to this point the firmware for the K3 and the K3S has >> been exactly the same. The firmware figures out at run time which features >> are available whether it being in the K3 or the K3S and behaves >> accordingly. Is there something changed here? That would really complicate >> things. > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
| Free forum by Nabble | Edit this page |
