SGII Rev. 4.02 Upgrade

I am sending my SGII with firmware revision 4.02 in for an upgrade to their latest rev level. I have had two issues and have been told by LinearLogic tech support that they have resolved.

I was lost driving to work without the SGII to monitor The two issues that I have had are: 1) XGauge corruption when modifying an existing XGauge.
2) Scan for Pending Codes results in endless counting of codes.

Cristina with tech support told me the workaround for the Scan issue was to change all four of the gauges to the standard gauge VLT. This does work and will stop the endless counting of codes. So those that have this issue here is your workaround.

I re-created a HV DC ground fault before sending my unit in. According to the Repair Manual and DTC code document this should have triggered a P0AA6-XXX code. Even with the Scan feature appearing to work properly I still did not get a code to read, only No Pending Codes even though the yellow ! inside a triangle alarm light and a message Check Hybrid System. I could reset the Alarm light. This leaves me in doubt that the SGII will read all of the Prius specific DTC's, even when upgraded. I will test again when my upgraded unit returns.

Can someone that has been able to read DTC's with their SGII's list the codes that they have been able to read and when they have not been able to read codes? Also if there is a Prius tech reading this, am I correct that the Prius should be triggering a DTC when the yellow alarm light and Check Hybrid System message for a ground fault alarm is triggered?

 

I have to say that I am impressed with LinearLogic's turn-around time. I received a USPS notification early this afternoon that my SGII had been delivered. A few hours later I received another USPS notification of a tracking number for shipment back to me.

Now that is what I call customer service

 

My wife took the SGII to a Mail Room close to the house on Monday and shipped USPS Priority Flat Rate. The upgraded unit arrived in the mail today, Friday. Impressive.

The new revision is 4.12. I am already re-programming my XGauges and ready to see how this unit performs.

 

I re-programmed all of my XGauges and made modifications to some after the initial programming and am glad to report that I had no corruption of the data after the modifications. So this issue does appear to be fixed.

When I checked the Scan feature there was no more continuous counting of codes like the earlier version. So this also appears to be fixed.

I created another ground fault on the HV DC battery and generated another Check Hybrid System alarm. When I scanned for codes I received another No Pending Codes but again was able to reset the alarm. So either the ground fault alarm does not trigger a DTC or the SGII is still not able to read the code. I would really like to know for sure rather than have to wait until I do have a true DTC triggered and find out the SGII is not able to read it

 

Vincent,

Yes, please PM me the code as I am definitely interested. For some reason I was under the impression that SGII could read Prius specific codes.

Also, do you have a complete listing of the Gen III XGauges that you have deciphered? I know Adrian updated his spreadsheet with a lot of your findings but he has not updated again since late 2011.

Thanks,

Dwight

 

Vincent,

I received your conversation via email but PC gave me an error and said conversation could not be found. I saw a thread by cwerdna about the conversation not working today and you also replied to this thread. I noticed later that Danny he says that he now has this fixed.

Can I get you to try to resend the conversation? The email version did not have the parameters in a table format for easy reading.

Thanks,

Dwight

 

I tried Vincent's code for reading the number of HV codes present to check it out, even though I do not have any pending codes at this time. The code for <2 codes returned a zero which indicates that it is responding correctly.

I need to find the time to generate another HV battery ground fault and see if the SGII will read the correct DTC. I will have to try to find time one night this week since we start our annual outage at work this weekend !

 

Thanks for the link to your spreadsheet. The first chance I get I will test some of the c parameters against some known ones that work for the Gen III to see if they work for both.

 

I finally found some time this afternoon to generate another HV battery ground fault. This time Vincent's #hv Xgauge returned a 1 for the number of codes. I looked at his hv1 XGauge for the first code and received a 2726. When I converted the 2726 from Decimal to Hex I got the AA6 code that I was looking for. This is the correct P0AA6 DTC for a HV Battery ground fault.

Vincent - have you developed the XGauges for the sub codes yet ? I would be more than happy to test them for you. I would love to know which of the DTC sub codes this will point to and see if it is really useful in troubleshooting for future problems.

Thanks to Vincent, once again, for his continued development and sharing of the Prius ECU XGauge mapping with the PC community. I now know that I will be able to read any future DTC's that I may encounter.

 

Vincent,

When I looked at the difference between #hv and hv1 the only difference I saw was the RXD change from 2008 to 2810. I knew your Notes indicated Hex and I was surprised that it was not AA6 but when I converted dec to hex and it came up AA6 I knew the DTC was correct.

After you pointed to the RXF now I see the difference of 010702EA0453 and 010712EA0453 !

I will be looking forward to the sub codes

Thanks,

Dwight

 

Vincent,

I was looking at some of your XGauges for the C and noticed that with the four HV Battery temps (TBi, TB1, TB2, and TB3) that you are using a different MTH parameter for converting to degree F than before. The new MTH is 11FEFFFFFDBC.

Is this because the ECU data in the C is different than the Liftback? Have you come up with a new formula for converting degree C to degree F? Or are you requesting the data in a different format than before?

Dwight

 

Just curious, would you mind sharing the formulas that you used to come up with this new format?

 

Thanks Vincent

The Windows calculator that I use to convert from Decimal to Hex treats FFFFh as -1 instead of 65535.

Why is the FFFF treated as 65535 and not -1, yet FDBC is treated as -580? (Reading a XGauge Coding document I may have answered my own question. It appears that the Add/Subtract data is the only signed value of the three. Is this the correct answer?)

Also, you are correct that the SGII drops the decimal point once the temp gets above 99.9.