¿ªÔÆÌåÓý

Re: Should we adopt the KD8CEC firmware?


 

Arv

I have to say this is the best post on this subject in quite some time.
It certainly seems that the original firmware could use some
improvement/updating. Does it need all the additional features in Ians
code? I don't know, maybe Ashhar and Ian can work that out and strike a
happy medium.

Art N4EZZ <n4ezz@...>
GnuPG key ID 0x6712DD0E
=============================
there's no logic behind anything that happens here

On 05/16/2018 09:57 AM, Arv Evans wrote:
Interesting that this single subject has generated more comments than any
other topic.
Some comments are on-topic (*Should we adopt the KD8CEC firmware?*) while
others
seem to have drifted off into discussions of coding styles, coding
strategy, and which
functions should be supported in the factory software load. All points
have some validity
as suggestions for personalization of your own uBITX, and will probably be
considered
when Farhan writes and installs firmware for future BITX designs.

My own opinion (for whatever that is worth...?), is that the factory
software needs to insure
that the rig is fully operational, and that enough functionality is
included to make the
transceiver useful to those who are not interested in writing or modifying
code. Beyond that
it is up to the owner if she or he wants to make changes to hardware or
software. How those
changes are organized, designed, and installed is then up to each
individual owner. That
is a personal issue, and not a global one.

If you are going to modify existing firmware or are going to write your own
firmware, then
what is in the factory code is not an issue because you are going to
replace it anyway.
This sort of denigrates these person's comments regarding what the factory
firmware
should or should not include.

Has this topic evolved in enough different directions that we need new and
more specific
topics started for each issue (BITX coding methods, BITX firmware
functions, BITX code
writing for beginners, BITX firmware testing and quality control, BITX
alternative processor
systems, BITX CAT control, etc., etc.)?

Arv K7HKL
_._

Join [email protected] to automatically receive all group messages.