@Ta2dResqr, since you took the time to write that message, I'll give you my point of view.
On post #9 I was replying to Majestic not to Texas Marauder.
What was said in post # 10 was spot on but the added comments totally changed how the message is perceived:
Read this:
LOL, sometimes I think I'm talking to the wall. Your "procedure" affected the CEL. You really have no idea what it did, if anything. Assuming you have a 2010 as noted in your signature, it didn't reset the BMS because your car does not have a BMS. How can you tell? Is there a sensor on the negative cable? No there isn't. But, believe whatever you want.
Now read this:
Your "procedure" affected the CEL. You really have no idea what it did, if anything. Assuming you have a 2010 as noted in your signature, it didn't reset the BMS because your car does not have a BMS. How can you tell? Is there a sensor on the negative cable? No there isn't.
Different, right?
I spend more time than I should on forums and am an Admin of one. I love helping people and have written and documented multiple repairs I've done to guide others. Electronics is not my forte.
Written communication lacks tone, facial expression and gesture and many times the same message can be perceived differently when its written. This is why, as a general rule, comments like the ones quoted should be omitted.
Now, let's look at the chain of events:
1) 10:25 am - I post about my issue.
2) 11:04 am - kryptto provides lots of info. I don't have time to read the attachments, saved for later.
3) 11:30 am - majestic asks if I reset the BSM
4) 11:41 am - I reply that I did (as I thought I did) and explain how.
5) 11:50 am - majestic replies suggesting to use forscan.
6) 12:46 pm - texas marauder replies with an initial point of view reinforcing my initial thought of the issue being a bad alternator.
7) 1:03 pm - kryptto replies reinforcing the previous post.
8) 1:27 pm - texas marauder points out that the 2010 doesn't have a BSM and provides a document on how the system operates. Again, no time to read immediately, saved for later.
9) 2:01 pm - I reply to majestic's previous message and explain why (I thought) the procedure worked, not trying to ignore what was said about the BSM.
10) 6:06 pm I receive a message accusing me of being stubborn and not listening to the advice provided.
I'll leave it at that.
I'm not asking anyone to pick sides, this is not about that. I'm just stating my point of view.
I thank kryppto, majestic and texas marauder for the help and information provided up to this point.
______________________
Since then I've been looking a the attachments. Some of it I already did but will continue checking connections.
From the Principles of Operation:
The PCM is able to adjust the charging voltage according to the battery temperature by using a signal from the Intake Air Temperature (IAT) sensor. The PCM also uses other inputs to control charging system voltage such as the Vehicle Speed Sensor (VSS) and Engine Coolant Temperature (ECT). The voltage set point is calculated by the PCM and communicated to the voltage regulator by the GENCOM circuit based on the needs of the vehicle and the conditions.
My vehicle was low on engine coolant which I now topped up with no change. Maybe that affected the ECT reading misleading the PCM?
There is also something else I don't fully understand about the Check Charging System (let's not call it BSM anymore) going off after the engine goes above 2000 rpm.
A few days ago I disconnected the battery for more than 2 hours while I was cleaning some connections and the shift tables and other things reset. Something that changed is that before that I would get the CCS (Check Charging System) alarm after a short period of driving and it would go away, and then come back, and then go away... After that day, it comes on within 10 seconds of me turning the engine on, even if its still idling, and it won't go away.
I'll go over the connections again this weekend and will re-read the info sent. Some of it I don't really understand but will try my best. Will also go through forscan again to see if I can find a way to properly reset this system.