|>>... You don't
|>> 'improve' firmware for modern electronics. It has to be written
|>> exactly one way, to perform the job at hand.
|> Wow; all that experience and you can still say that. Woof! How many
|> times have you seen the same hardware with different functions and uses?
|> All you change to get from one to another is ... wait for it ... the
|> firmware! Careful; if you say never, you're either blind & inexperienced
|> or lying.
| It was not I who "wrote" the tiny part of "Michael A. Terrell"'s post
| that you quoted. Nor did any of the others your posting software
It looks like he got the header quoting wrong. It should at the end have
stated that Michael A. Terrell (M.A.T.) wrote that. I double checked and
saw MAT's post to see that it appears he really did (though I did not trace
the posting path to be sure it wasn't forged by someone trying to make him
| There are some things that can lend themselves to "modding"
| via a modified firmware, but it is highly unlikely that "phil-news-
| nospam" has gone from clueless about battery maintenance, at
| the beginning of this thread - to being able to "improve" the basic
| charging algorithms and sophisticated monitoring routines
| imbedded in today's charge controllers. Even modding the
| firmware of a DVD drive to be region free and changing speeds
| in the media tables, requires a detailed understanding of how the
| processing is implemented, not just the spec sheet data for the
| ICs involved.
Remember, I'm the one that ASKED about battery maintenance. Only a few people
offered genuine clues. The rest, like MAT and KRW, offered nothing or wasted
time making personal attacks.
Once I do understand exactly what is involved in battery maintenance, then
I will be able to program firmware or hostware to manage it. It sure seems
to be that _this_
place is not a place to learn anything.
| This is a guy who wouldn't have the slightest idea how to set
| the options of a modern charge controller, to match a particular
| battery setup. He had no understanding of the impacts of the
| physical construction, chemistry, operational environment, or
| any other pertinent factor, and yet he now claims to be ready
| to improve on the firmware developed by the makers of the
Once I do know the battery related issues, then yes, I will be able to apply
that to fireware because I already have the programming and system hardware
knowledge to do that. It's the battery maintenance physics I'm still trying
| You will run into this kind of egotist, all the time in Internet
| postings, it is foolish to play their games, after they have
| exposed their true nature.
You have some difficulty in understanding programming, it seems. One does NOT
need to learn the science of what is to be controlled before learning to do the
programming to control it. I already have the programming skills. This, like
any other project, involves combining the ALREADY EXISTING PROGRAMMING SKILLS
with the science of the application (in this case, batteries) and then it can
be done. So I am _ready_
as soon as I know the battery science. And based on
what information is available now, it sure appears that a lot of that is going
to have to be acquired through scientific experimentation. There seems to be
very very few people here who really know the subject.
I never assumed anyone here would teach it all. What I was hoping for was a
civil discussion. But until idiots like MAT and KRW leave and stay away, it
looks like such things cannot happen.
|WARNING: Due to extreme spam, googlegroups.com is blocked. Due to ignorance |
| by the abuse department, bellsouth.net is blocked. If you post to |
Click to see the full signature.