|
After updating to 4.81 power out set to 100 watts was actually about 75 watts. I reverted back to 4.67 and all is well 100=100. Anyone else observe this?
73, John N1JM |
|
Please report any issues that you may find in Beta MCU to: <[hidden email]> Regards, Howard K6IA ______________________________________________________________ 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 |
|
And PLEASE report all anomalies here also. As owners and perspective
owners, we all need to know as much about our equipment investment as possible. The sharing of experiences and knowledge is the only means to accomplish this. Without sharing, we are in the dark. Thanks, Bill W2BLC K-Line(??) ______________________________________________________________ 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 |
|
On 2/8/2014 12:05 PM, Bill W2BLC wrote: > And PLEASE report all anomalies here also. But *not* _Beta_ firmware. Beta reports should to to Elecraft Support and/or the respective project manager - there is no reason to stir up issues with the entire user base concerning firmware that may not even be ready for release. 73, ... Joe, W4TV On 2/8/2014 12:05 PM, Bill W2BLC wrote: > And PLEASE report all anomalies here also. As owners and perspective > owners, we all need to know as much about our equipment investment as > possible. The sharing of experiences and knowledge is the only means to > accomplish this. Without sharing, we are in the dark. > > Thanks, > > Bill W2BLC K-Line(??) > > ______________________________________________________________ > 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 > 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 |
|
Unless you are either using the beta or thinking about trying the beta. All remarks are welcome!! Might be reason to wait for the next beta/production???
73 Elliott WA6TLA On Feb 8, 2014, at 3:18 PM, Joe Subich, W4TV <[hidden email]> wrote: > > On 2/8/2014 12:05 PM, Bill W2BLC wrote: > > And PLEASE report all anomalies here also. > > But *not* _Beta_ firmware. Beta reports should to to Elecraft Support > and/or the respective project manager - there is no reason to stir up > issues with the entire user base concerning firmware that may not even > be ready for release. > > 73, > > ... Joe, W4TV > > > On 2/8/2014 12:05 PM, Bill W2BLC wrote: >> And PLEASE report all anomalies here also. As owners and perspective >> owners, we all need to know as much about our equipment investment as >> possible. The sharing of experiences and knowledge is the only means to >> accomplish this. Without sharing, we are in the dark. >> >> Thanks, >> >> Bill W2BLC K-Line(??) >> >> ______________________________________________________________ >> 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 >> > ______________________________________________________________ > 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 ______________________________________________________________ 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 |
|
In reply to this post by Bill-3
Bill,
If you confine that to firmware that has been advanced to production status, I *might* agree. Keep in mind that the firmware is provided at no cost, so I cannot agree with your phrase "equipment investment". The hardware is the equipment investment, and at Elecraft the firmware is updated from time to time to add new functions that have been requested by users as well as bug fixes that have been identified - that addition to the equipment functionality is provided at no cost (therefore no 'investment' on the part of the users. Beta releases are intended to allow those who are willing to be early testers of new firmware to participate in evaluating that new level. If there are no significant problems, that level may be advanced to production, but if there are problems discovered, that firmware level will never 'see the light of day' other than the beta version. It sounds like you want all beta version anomalies to be aired publicly - I disagree, they would be properly aired among those who volunteered to engage in the beta test, but are not relevant to the entire user community, most of whom will be running the production firmware level. 73, Don W3FPR On 2/8/2014 12:05 PM, Bill W2BLC wrote: > And PLEASE report all anomalies here also. As owners and perspective > owners, we all need to know as much about our equipment investment as > possible. The sharing of experiences and knowledge is the only means > to accomplish this. Without sharing, we are in the dark. > ______________________________________________________________ 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 |
|
I've conducted many beta test cycles over the past couple of decades. I
have software in beta now. Part of my beta test agreement states that "Beta software is broken. Your job is to help find the problems so they can be fixed before production." More than a few times I've withdrawn functions and features because they didn't prove to be useful, sometimes spectacularly so. It's pretty common for a beta test agreement to include a non-disclosure clause. Particularly now, with the internet, bugs can develop a life of their own, even if they're never present in released software. I don't know what Elecraft does, but software released for beta testing is reasonably subject to the terms and conditions that Elecraft chooses -- and as widely or narrowly as they wish. Bugs found in testing have practically no bearing on ones' investment -- except perhaps as a distraction. I'd argue that a wide-open beta actually reduces the value of your investment. 73 -- Lynn On 2/8/2014 3:57 PM, Don Wilhelm wrote: > Beta releases are intended to allow those who are willing to be early > testers of new firmware to participate in evaluating that new level. > If there are no significant problems, that level may be advanced to > production, but if there are problems discovered, that firmware level > will never 'see the light of day' other than the beta version. ______________________________________________________________ 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 |
|
In reply to this post by Elliott Lawrence-3
One should fully understand what Beta Testing means if they're thinking
about running Beta software. It means that you may run into problems -- if you do a thorough job of testing, you most definitely will find them. If you aren't comfortable with that, then you really should not run beta software, period. If the software is known bug-free, it does not need beta testing. From what I've seen, Elecraft's beta software is very high quality. Beta testing can be quite rewarding -- testers should take pride in the quality of the released software, since they most definitely helped. 73 -- Lynn On 2/8/2014 3:35 PM, Elliott Lawrence wrote: > Unless you are either using the beta or thinking about trying the beta. All remarks are welcome!! Might be reason to wait for the next beta/production??? > 73 > Elliott WA6TLA ______________________________________________________________ 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 |
|
In reply to this post by Don Wilhelm-4
I'll let Don's comments re: "Equipment Investment" stand, I can't
improve on them. I believe Don is right when it comes to beta releases. Having been on the receiving end of "user issues" with beta releases, we finally limited them to a small, fairly tight group who would hash out an anomaly and the conditions under which it could be produced [or not produced] before they came to us. From them, we got actionable information. From the general user population, we got "data" that was more related to their state of mind coming to work that morning than anything relating to reality for them with the product. There's a huge difference between "data" and "information." My K3, KAT500, KPA500, and P3 work, I'm happy with them and they are NOT even at current production FW releases. I do look carefully at the Release Notes to decide if I care about the changes. Eventually, something will come along that I DO care about, and I'll get all the past changes too. 73, Fred K6DGW - Northern California Contest Club - CU in the 2014 Cal QSO Party 4-5 Oct 2014 - www.cqp.org On 2/8/2014 3:57 PM, Don Wilhelm wrote: > It sounds like you want all beta version anomalies to be aired publicly > - I disagree, they would be properly aired among those who volunteered > to engage in the beta test, but are not relevant to the entire user > community, most of whom will be running the production firmware level. ______________________________________________________________ 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 |
|
In reply to this post by John_N1JM
I think there two levels of software we should consider.
1- FIELD TEST - Software available to selected "field testers" which should be discussed among testers and Elecraft techs. This includes revs that are supplied to a more expansive group via direct email to Eric or Wayne. 2 - BETA... Software announced on list to all and available from Elecraft BETA folder on web site for download. As this is avail to all, comments should be public. ...bill nr4c Sent from my Verizon Wireless 4G LTE DROID "Lynn W. Taylor, WB6UUT" <[hidden email]> wrote: >I've conducted many beta test cycles over the past couple of decades. I >have software in beta now. > >Part of my beta test agreement states that "Beta software is broken. >Your job is to help find the problems so they can be fixed before >production." > >More than a few times I've withdrawn functions and features because they >didn't prove to be useful, sometimes spectacularly so. > >It's pretty common for a beta test agreement to include a non-disclosure >clause. > >Particularly now, with the internet, bugs can develop a life of their >own, even if they're never present in released software. > >I don't know what Elecraft does, but software released for beta testing >is reasonably subject to the terms and conditions that Elecraft chooses >-- and as widely or narrowly as they wish. > >Bugs found in testing have practically no bearing on ones' investment -- >except perhaps as a distraction. I'd argue that a wide-open beta >actually reduces the value of your investment. > >73 -- Lynn > >On 2/8/2014 3:57 PM, Don Wilhelm wrote: >> Beta releases are intended to allow those who are willing to be early >> testers of new firmware to participate in evaluating that new level. >> If there are no significant problems, that level may be advanced to >> production, but if there are problems discovered, that firmware level >> will never 'see the light of day' other than the beta version. > >______________________________________________________________ >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 > 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 |
|
It's fine just the way it is and has worked well for many years.
Let's not complicate things or make a round wheel into a square one. My opinion only. 73, Kent K9ZTV On 2/8/2014 8:59 PM, bill conkling wrote: > I think there two levels of software we should consider. > 1- FIELD TEST - Software available to selected "field testers" which should be discussed among testers and Elecraft techs. This includes revs that are supplied to a more expansive group via direct email to Eric or Wayne. > > 2 - BETA... Software announced on list to all and available from Elecraft BETA folder on web site for download. As this is avail to all, comments should be public. > > ...bill nr4c > > Sent from my Verizon Wireless 4G LTE DROID > > "Lynn W. Taylor, WB6UUT" <[hidden email]> wrote: > ______________________________________________________________ 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 |
|
Administrator
|
Folks, let's end the thread for now.
Howard from our support team, the original poster on this thread, was just asking that beta release issues also be reported to [hidden email]. Its always Ok to post beta issues here too if needed. 73, Eric List moderator etc. elecraft.com _..._ > On Feb 8, 2014, at 11:50 PM, KENT TRIMBLE <[hidden email]> wrote: > > It's fine just the way it is and has worked well for many years. > > Let's not complicate things or make a round wheel into a square one. > > My opinion only. > > 73, > > Kent K9ZTV > > >> On 2/8/2014 8:59 PM, bill conkling wrote: >> I think there two levels of software we should consider. >> 1- FIELD TEST - Software available to selected "field testers" which should be discussed among testers and Elecraft techs. This includes revs that are supplied to a more expansive group via direct email to Eric or Wayne. >> >> 2 - BETA... Software announced on list to all and available from Elecraft BETA folder on web site for download. As this is avail to all, comments should be public. >> >> ...bill nr4c >> >> Sent from my Verizon Wireless 4G LTE DROID >> >> "Lynn W. Taylor, WB6UUT" <[hidden email]> wrote: > > ______________________________________________________________ > 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 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 |
| Free forum by Nabble | Edit this page |
