Some changes are easy to implement. Some are hard and carry a risk of side effects. Let's look into some:
1. Change LO step from 100 to 50 Hz -- very easy to implement 2. Band stacking, e.g., pressing V_M+nr for the same band toggles the stacks, a menu defines the number of stacks -- easy once one figures how to implement it 2. Make 2nd RX band independent - medium IMHO 3. Allow 2nd RX use ANT2 when TX uses ANT1 and 2nd RX connected to AUX -- easy but potentially dangerous if timing not right 4. Narrow manual notch (200=> 50 Hz) and faster automatic notch -- easy but a question whether to add menus 5. NTCH and NR under AGC loop - hard if not impossible with low power DSP; possibly with side effects in the first release There is a question to whom the changes are addressed. Ignacy Julian, G4ILO wrote: > > > > Nick G3RWF wrote: >> >> Elecraft are brilliant in responding to customers' wishes/needs so I >> wonder if I am alone in wanting a little time to let current developments >> and firmware upgrades show their worth? I have just taken my soldering to >> my two K3s to install upgrades (and then upgraded the firmware). However >> I looked at the latest beta firmware and feel I am slightly on a >> treadmill. I am very happy to wait say every six months and then pick up >> any Elecraft firmware changes. I know I am free to do this but I have the >> feeling that some requests for change are very individualistic and may >> well not reflect the views of the majority of K3 users. Time for >> reflection isn't always wasted. It might even allow me to have an up to >> date handbook for a while. >> > > If you are asking for a pause in the release of new firmware updates then > I don't think that will find much favor with those who are still waiting > for various features to be implemented. Nobody is required to install > updates, and I personally don't unless the list of changes includes > something I'm particularly interested in. > > It's in the nature of a forum like this that people will throw in their > pet suggestions. I don't think anyone who does so expects their idea to > get implemented straight away. > > Where I am inclined to agree with you is that the incorporation of > features appears to occur in a haphzard fashion. Someone's idea may get > acted on straight away whereas other things - even features documented in > the manual since day 1 such as the ability to calibrate the 1ppm TCXO for > extra stability - still remain on the to-do list. > > I think your concerns might be allayed if Elecraft were to do what a > couple of developer types who I have had discussions with privately have > suggested, namely publish a roadmap for firmware development. Then we > could all see when the K3 is actually going to be "finished", when our > long-awaited feature is likely to be implemented, and people would have to > justify why their pet idea should come higher up the list than something > else. > -- View this message in context: http://n2.nabble.com/K3---pace-of-development-tp2244953p2245468.html Sent from the Elecraft mailing list archive at Nabble.com. _______________________________________________ Elecraft mailing list Post to: Elecraft@mailman.qth.net You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com
