I didn't mean to make things even more confusing, sorry here's why I am confused...
I've quoted your post word-for-word...
Quote:
When I first opened V8 software got a message
The V8 software does not give you messages about checksum errors when the software is "first opened". (At least I don't think it does. If it really does, then I need to investigate that).
So my confusion for that statment: Was it really a checksum error? Was it some other error unrelated to a checksum? Is the software showing a checksum error for some other reason (i.e. a checksum fault in the V8 software executable itself)? I was just trying to clarify the answers to those questions.
Quote:
stating that controller section had a checksum error with one of the controllers
I don't know what a controller section is. I simply wanted to clarify that you meant to say "segment" or "controller segment".
I also got confused by your term with one of the controllers (again you probably mean with one of the segments). But the way you worded it got me thinking of the list of controllers (i.e. list of tune files) that appear on the front screen of EFILive as soon as you start the V8 software. Maybe the software is somehow reporting an error that one of the controllers (i.e. tune files) in that list is somehow faulty, I thought maybe it could be showing a summary of segment checkusm faults for each file and popping up a warning that one of the controllers (i.e. the tune files) in that list has a bad checksum. I don't think the software does that but I can't be entirely sure, just asking for clarification.
Quote:
and did I want to check for new checksum
You should never ever get asked by the V8 software to check for new checksum. Yes, a red X is displayed next to each segment that has an incorrect checksum but the software will never ask you to correct them. You must right click on one or more segments and select "Force Checksum to be Correct". So if the software really did ask you to correct the checksums I need to know that because that is not how it should work.
Quote:
Already sent trace files (5838-UHCB-8296 --- 81c9f9d7), doesn't PCM stand for Power Control Module? So PCM = controller, isn't a controller a PCM? Semantics. Is there an "E" segment? Maybe an "E" as in E67 controller (PCM)? ;-)
You said this in the previous post
Quote:
I have an older tune file with the correct checksum which I posted within the body of the OP.
There is no file attached to the body of the OP, which I assume means Original Post. I was just asking for you to send me that file. Or maybe your statement meant that you have a file that used to have a bad checksum but that you've now corrected it. And that you posted that fact/information (not the actual file) in the original post. Its not clear to me which of those two meanings is correct. I assumed you meant that you had attached the file to the original post, my assumption may have been wrong.
And this:
Quote:
(5838-UHCB-8296 --- 81c9f9d7)
Is that meant to be a link to the help desk ticket that you have logged? If so, that is not a valid link. If you have logged a help desk ticket can you please send a proper link to your ticket so I can look up your ticket.
I have no idea why you're discussing the differences between ECM and PCM. Did I say something that confused those two terms in my original post? Maybe the confusion has to do with you using the term "controller" when I think you meant to use the term "segment".
Quote:
Tell me how to revert back to original and I will gladly send to you. Don't ask me to reread the file again unless you offer a faster way of doing that without errors. :-)
You can't revert a checksum that has been corrected back to its incorrect state.
If you really want this solved, then the only way would be to re-read the controller and send me the *.ctz tune file (that has the bad checksum segments in it) and matching *.htx trace file.
I too wish there was a faster way to read it, but at 41,600bps it is slower than most dial up Internet connections were back in the 90's :)
I understand you're frustrated with something not working properly in the software. But I really am confused about what you've posted. I don't want to rush off trying to fix something if I've misunderstood the problem that you're describing. I've done that before, I've assumed I knew what the problem was only to find out days later and much wasted time later that I was wrong. The more you can help me, the sooner I can get the correct fix done.
Regards
Paul