Alert #1146 Returns! {sigh}

[gregd]

Hi folks,

After a 20 mile trip back up the hill after an appointment, my OVMSv3 cheerfully proclaimed an Alert #1146 (DMC Motor Fan Problem) just as I was pulling into my driveway. {sigh}. The car charged normally, but more of the alerts were given. According to the logs (pulled after the charging was done) there were 55 of them in total! Nothing displayed in the cabin, of course, so if I didn't have the OVMS module installed I would have not known they had occurred.

Oddly, the temps on both motor and PEM were quite unremarkable, and the weather was seasonably pleasant.

So, I presume this is the infamous PEM Fan connector issue, returning. Last yearly service was this past spring, so it shouldn't be a matter of clogged pipes. Before I open a service call, is there anything else I should check for? The timing of the alerts, and the related temps, seem inconsistent with what I know about the alert. I did have the A/C on during the trip, and had turned it off shortly before the alert. Any connection there, perhaps?

Thanks,

Greg

 

[petergrub]

I take it you have the dual fan controller (DFC) setup, but we may as well try. Was the data in the log file, that followed each one of the 55 alerts, consistent?

That data is supposed to tell you more about the error like whether it was an undercurrent issue, amperage exceeded 15A, etc. The DFC setup may have changed the way the firmware logs the motor fan error data. Otherwise, your best bet is to remove the three phase cables going to the motor and pulling RHC34 and inspecting for damage, or down below at the fan(s) at RHC25.

 

[gregd]

I take it you have the dual fan controller (DFC) setup, but we may as well try. Was the data in the log file, that followed each one of the 55 alerts, consistent?

That data is supposed to tell you more about the error like whether it was an undercurrent issue, amperage exceeded 15A, etc. The DFC setup may have changed the way the firmware logs the motor fan error data. Otherwise, your best bet is to remove the three phase cables going to the motor and pulling RHC34 and inspecting for damage, or down below at the fan(s) at RHC25.

Never looked at the data... The values appear to be quite varied, but what does it mean? (I have the single motor, dual blower upgrade.)

0x00063b73: 08/13/2018 15:23:26 | 1534199006 | ERR | 03 02 17 17 3F 00 5B7204DE | 08 00 76 00 7A 04 06 02 00 BB B6 B4 24 28 6F error code 1146 6 bytes
0x00063b8c: 08/13/2018 15:25:10 | 1534199110 | ERR | 03 02 17 17 3F 00 5B720546 | 08 00 76 00 7A 04 06 02 00 DD B4 AE 24 28 EC error code 1146 6 bytes
0x00063ba5: 08/13/2018 15:25:42 | 1534199142 | ERR | 03 02 17 17 3F 00 5B720566 | 08 00 76 00 7A 04 06 02 00 7E B5 98 24 28 40 error code 1146 6 bytes
0x00063bbe: 08/13/2018 15:25:57 | 1534199157 | ERR | 03 02 17 17 3F 00 5B720575 | 08 00 76 00 7A 04 06 02 00 F2 B4 6D 24 28 E9 error code 1146 6 bytes
0x00063bd7: 08/13/2018 15:29:07 | 1534199347 | ERR | 03 02 17 17 3F 00 5B720633 | 08 00 76 00 7A 04 06 02 00 1C B5 D8 24 08 B4 error code 1146 6 bytes
0x00063bf0: 08/13/2018 15:31:36 | 1534199496 | ERR | 03 02 17 17 3F 00 5B7206C8 | 08 00 76 00 7A 04 06 02 00 1F B6 A2 24 28 31 error code 1146 6 bytes
0x00063c09: 08/13/2018 16:19:06 | 1534202346 | ERR | 03 02 17 17 3F 00 5B7211EA | 08 00 76 00 7A 04 06 02 00 FA B6 52 24 28 79 error code 1146 6 bytes
0x00063c22: 08/13/2018 16:19:14 | 1534202354 | ERR | 03 02 17 17 3F 00 5B7211F2 | 08 00 76 00 7A 04 06 02 00 79 B6 A4 24 08 C0 error code 1146 6 bytes
0x00063c3b: 08/13/2018 16:26:39 | 1534202799 | ERR | 03 02 17 17 3F 00 5B7213AF | 08 00 76 00 7A 04 06 02 00 B3 B6 44 24 08 27 error code 1146 6 bytes
0x00063c54: 08/13/2018 16:27:00 | 1534202820 | ERR | 03 02 17 17 3F 00 5B7213C4 | 08 00 76 00 7A 04 06 02 00 5D B6 A2 24 08 0A error code 1146 6 bytes
0x00063c6d: 08/13/2018 16:27:27 | 1534202847 | ERR | 03 02 17 17 3F 00 5B7213DF | 08 00 76 00 7A 04 06 02 00 0B B7 06 24 08 DC error code 1146 6 bytes
0x00063c86: 08/13/2018 16:28:36 | 1534202916 | ERR | 03 02 17 17 3F 00 5B721424 | 08 00 76 00 7A 04 06 02 00 BF B6 D8 24 28 F1 error code 1146 6 bytes
0x00063c9f: 08/13/2018 16:28:43 | 1534202923 | ERR | 03 02 17 17 3F 00 5B72142B | 08 00 76 00 7A 04 06 02 00 FA B6 8A 24 28 FD error code 1146 6 bytes
0x00063cb8: 08/13/2018 16:29:01 | 1534202941 | ERR | 03 02 17 17 3F 00 5B72143D | 08 00 76 00 7A 04 06 02 00 06 B7 D6 24 28 92 error code 1146 6 bytes
0x00063cd1: 08/13/2018 16:29:53 | 1534202993 | ERR | 03 02 17 17 3F 00 5B721471 | 08 00 76 00 7A 04 06 02 00 3F B6 F3 23 28 0A error code 1146 6 bytes
0x00063cea: 08/13/2018 16:31:23 | 1534203083 | ERR | 03 02 17 17 3F 00 5B7214CB | 08 00 76 00 7A 04 06 02 00 92 B6 67 24 28 E8 error code 1146 6 bytes
0x00063d03: 08/13/2018 16:33:06 | 1534203186 | ERR | 03 02 17 17 3F 00 5B721532 | 08 00 76 00 7A 04 06 02 00 B6 B6 B1 24 28 12 error code 1146 6 bytes
0x00063d1c: 08/13/2018 16:35:36 | 1534203336 | ERR | 03 02 17 17 3F 00 5B7215C8 | 08 00 76 00 7A 04 06 02 00 3D B7 1C 24 28 89 error code 1146 6 bytes
0x00063d35: 08/13/2018 16:35:46 | 1534203346 | ERR | 03 02 17 17 3F 00 5B7215D2 | 08 00 76 00 7A 04 06 02 00 A3 B6 38 24 28 FE error code 1146 6 bytes
0x00063d4e: 08/13/2018 16:35:59 | 1534203359 | ERR | 03 02 17 17 3F 00 5B7215DF | 08 00 76 00 7A 04 06 02 00 77 B6 1D 24 28 38 error code 1146 6 bytes
0x00063d67: 08/13/2018 16:36:05 | 1534203365 | ERR | 03 02 17 17 3F 00 5B7215E5 | 08 00 76 00 7A 04 06 02 00 87 B6 11 24 28 2E error code 1146 6 bytes
0x00063d80: 08/13/2018 16:36:35 | 1534203395 | ERR | 03 02 17 17 3F 00 5B721603 | 08 00 76 00 7A 04 06 02 00 48 B6 79 24 28 E6 error code 1146 6 bytes
0x00063d99: 08/13/2018 16:36:45 | 1534203405 | ERR | 03 02 17 17 3F 00 5B72160D | 08 00 76 00 7A 04 06 02 00 66 B6 D2 24 28 65 error code 1146 6 bytes
0x00063db2: 08/13/2018 16:38:02 | 1534203482 | ERR | 03 02 17 17 3F 00 5B72165A | 08 00 76 00 7A 04 06 02 00 04 B6 B6 24 28 96 error code 1146 6 bytes
0x00063dcb: 08/13/2018 16:38:31 | 1534203511 | ERR | 03 02 17 17 3F 00 5B721677 | 08 00 76 00 7A 04 06 02 00 32 B6 85 24 28 7C error code 1146 6 bytes
0x00063de4: 08/13/2018 16:39:50 | 1534203590 | ERR | 03 02 17 17 3F 00 5B7216C6 | 08 00 76 00 7A 04 06 02 00 F0 B6 4E 24 28 A6 error code 1146 6 bytes
0x00063dfd: 08/13/2018 16:40:53 | 1534203653 | ERR | 03 02 17 17 3F 00 5B721705 | 08 00 76 00 7A 04 06 02 00 7C B5 B2 24 28 77 error code 1146 6 bytes
0x00063e16: 08/13/2018 16:44:44 | 1534203884 | ERR | 03 02 17 17 3F 00 5B7217EC | 08 00 76 00 7A 04 06 02 00 8D B6 79 24 28 B7 error code 1146 6 bytes
0x00063e2f: 08/13/2018 16:45:29 | 1534203929 | ERR | 03 02 17 17 3F 00 5B721819 | 08 00 76 00 7A 04 06 02 00 EA B6 E6 23 28 C0 error code 1146 6 bytes
0x00063e48: 08/13/2018 16:45:53 | 1534203953 | ERR | 03 02 17 17 3F 00 5B721831 | 08 00 76 00 7A 04 06 02 00 EB B5 A3 24 28 EA error code 1146 6 bytes
0x00063e61: 08/13/2018 16:46:09 | 1534203969 | ERR | 03 02 17 17 3F 00 5B721841 | 08 00 76 00 7A 04 06 02 00 D6 B5 B3 24 28 DF error code 1146 6 bytes
0x00063e7a: 08/13/2018 17:06:03 | 1534205163 | ERR | 03 02 17 17 3F 00 5B721CEB | 08 00 76 00 7A 04 06 02 00 4A B6 D9 24 28 96 error code 1146 6 bytes
0x00063e93: 08/13/2018 17:06:27 | 1534205187 | ERR | 03 02 17 17 3F 00 5B721D03 | 08 00 76 00 7A 04 06 02 00 FE B5 D3 24 28 D0 error code 1146 6 bytes
0x00063eac: 08/13/2018 17:07:01 | 1534205221 | ERR | 03 02 17 17 3F 00 5B721D25 | 08 00 76 00 7A 04 06 02 00 DA B6 3F 24 28 65 error code 1146 6 bytes
0x00063ec5: 08/13/2018 17:07:19 | 1534205239 | ERR | 03 02 17 17 3F 00 5B721D37 | 08 00 76 00 7A 04 06 02 00 96 B6 C0 24 28 16 error code 1146 6 bytes
0x00063ede: 08/13/2018 17:07:26 | 1534205246 | ERR | 03 02 17 17 3F 00 5B721D3E | 08 00 76 00 7A 04 06 02 00 21 B6 BE 24 28 86 error code 1146 6 bytes
0x00063ef7: 08/13/2018 17:21:23 | 1534206083 | ERR | 03 02 17 17 3F 00 5B722083 | 08 00 76 00 7A 04 06 02 00 85 B6 C6 24 08 F2 error code 1146 6 bytes
0x00063f10: 08/13/2018 17:21:56 | 1534206116 | ERR | 03 02 17 17 3F 00 5B7220A4 | 08 00 76 00 7A 04 06 02 00 10 B7 E7 24 28 04 error code 1146 6 bytes
0x00063f29: 08/13/2018 17:22:08 | 1534206128 | ERR | 03 02 17 17 3F 00 5B7220B0 | 08 00 76 00 7A 04 06 02 00 21 B7 A1 24 28 2D error code 1146 6 bytes
0x00063f42: 08/13/2018 17:22:30 | 1534206150 | ERR | 03 02 17 17 3F 00 5B7220C6 | 08 00 76 00 7A 04 06 02 00 62 B6 B3 24 28 C5 error code 1146 6 bytes
0x00063f5b: 08/13/2018 17:22:36 | 1534206156 | ERR | 03 02 17 17 3F 00 5B7220CC | 08 00 76 00 7A 04 06 02 00 8F B6 BA 24 28 8B error code 1146 6 bytes
0x00063f74: 08/13/2018 17:22:48 | 1534206168 | ERR | 03 02 17 17 3F 00 5B7220D8 | 08 00 76 00 7A 04 06 02 00 41 B6 A9 24 28 DE error code 1146 6 bytes
0x00063f8d: 08/13/2018 17:22:54 | 1534206174 | ERR | 03 02 17 17 3F 00 5B7220DE | 08 00 76 00 7A 04 06 02 00 FE B6 7F 24 28 45 error code 1146 6 bytes
0x00063fa6: 08/13/2018 17:23:13 | 1534206193 | ERR | 03 02 17 17 3F 00 5B7220F1 | 08 00 76 00 7A 04 06 02 00 93 B6 D1 24 28 4B error code 1146 6 bytes
0x00063fbf: 08/13/2018 17:23:20 | 1534206200 | ERR | 03 02 17 17 3F 00 5B7220F8 | 08 00 76 00 7A 04 06 02 00 88 B6 64 24 28 BC error code 1146 6 bytes
0x00063fd8: 08/13/2018 17:23:30 | 1534206210 | ERR | 03 02 17 17 3F 00 5B722102 | 08 00 76 00 7A 04 06 02 00 F9 B6 83 24 67 E2 error code 1146 6 bytes
0x00063ff1: 08/13/2018 17:24:05 | 1534206245 | ERR | 03 02 17 17 3F 00 5B722125 | 08 00 76 00 7A 04 06 02 00 27 B6 D3 24 28 80 error code 1146 6 bytes
0x0006400a: 08/13/2018 17:41:13 | 1534207273 | ERR | 03 02 17 17 3F 00 5B722529 | 08 00 76 00 7A 04 06 02 00 9D B6 9F 24 08 56 error code 1146 6 bytes
0x00064023: 08/13/2018 17:41:28 | 1534207288 | ERR | 03 02 17 17 3F 00 5B722538 | 08 00 76 00 7A 04 06 02 00 BD B5 E6 24 08 E1 error code 1146 6 bytes
0x0006403c: 08/13/2018 17:52:31 | 1534207951 | ERR | 03 02 17 17 3F 00 5B7227CF | 08 00 76 00 7A 04 06 02 00 19 B6 AB 24 08 26 error code 1146 6 bytes
0x00064055: 08/13/2018 18:19:27 | 1534209567 | ERR | 03 02 17 17 3F 00 5B722E1F | 08 00 76 00 7A 04 06 02 00 8C B6 AD 24 08 5A error code 1146 6 bytes
0x0006406e: 08/13/2018 18:19:52 | 1534209592 | ERR | 03 02 17 17 3F 00 5B722E38 | 08 00 76 00 7A 04 06 02 00 BD B6 D8 24 08 E5 error code 1146 6 bytes
0x00064087: 08/13/2018 18:22:19 | 1534209739 | ERR | 03 02 17 17 3F 00 5B722ECB | 08 00 76 00 7A 04 06 02 00 43 B6 96 24 08 0E error code 1146 6 bytes
0x000640a0: 08/13/2018 18:22:29 | 1534209749 | ERR | 03 02 17 17 3F 00 5B722ED5 | 08 00 76 00 7A 04 06 02 00 8B B6 85 24 08 CD error code 1146 6 bytes
0x000640b9: 08/13/2018 18:22:41 | 1534209761 | ERR | 03 02 17 17 3F 00 5B722EE1 | 08 00 76 00 7A 04 06 02 00 03 B7 90 24 08 3D error code 1146 6 bytes

 

[Stefan T]

Bad fan or bad connector under the PEM

 

[petergrub]

The values appear to be quite varied, but what does it mean?

I have started working on my own parser, so I'll use my own experience to help decode the following log file record.

0x00063b73: 08/13/2018 15:23:26 | 1534199006 | ERR | 03 02 17 17 3F 00 5B7204DE | 08 00 76 00 7A 04 06 02 00 BB B6 B4 24 28 6F error code 1146 6 bytes

There are several sections in the above parsed log record as denoted by the colored sections.

• Record Number: 0x00063b73 → 408,435
• Record Datestamp: 0x5B7204DE → 1534199006 → 08/13/2018 15:23:26 (This is an example of LSB where the bytes are read in left-to-right order. The datestamp is the only byte group that is read in LSB in this record example)
• Record Type: 0x17 → Permanent Error (ERR)
• Error ID: 0x7A04 → 0x047A → 1146 (This is an example of MSB where the bytes are read in right-to-left order. Also note that bytes are groups of two characters so x7A04 doesn't become x40A7)
• Number of Data Bytes for the Error: 0x06 → 6
• Failure Type Data Bytes for the Error: 0x0200 → 0x0002 → 2 → Fan wired backwards (Might be due to the DFC setup and not the actual problem)
• Voltage Data Bytes for the Error: 0xBBB6 → 0xB6BB → 46779 → 12.06V
• Amperage Data Bytes for the Error: 0xB424 → 0x24B4 → 9396 → 4.95A

I would like to credit Scott Swazey's parser, and Tom Saxton's log file parsing documentation for paving the way to much of my own work and research.

I would say check the wiring, even though we can see all instances of the record show a consistent failure mode, and that the voltage and current are stable too.

If I correctly understand how the OVMS works, then it picked up the error notification on the PEM CAN bus and reported it to you. However, it seems the VMS chose to ignore the error notification based on the parameters set in it's firmware, and only logged the issue in the log file rather than send the error notification to the VDS on the IP CAN bus?

 

[markwj]

If I correctly understand how the OVMS works, then it picked up the error notification on the PEM CAN bus and reported it to you. However, it seems the VMS chose to ignore the error notification based on the parameters set in it's firmware, and only logged the issue in the log file rather than send the error notification to the VDS on the IP CAN bus?

The errors reported on the CAN bus are like this:

Error Notification
  B1=0x93
  B2=On, Off, Severity, etc, indication
  B3=Error code LSB
  B4=Error code MSB (error code 0xFFFF means no error)
  B5=Data LSB
  B6=Data
  B7=Data
  B8=Data MSB

N.B. Regarding B2, we've seen:
  0x01 = 00000001b = Show Alert
  0x00 = 00000000b = Cancel Alert
  0x05 = 00000101b = Show Alert
  0x04 = 00000100b = Cancel Alert
  0x15 = 00010101b = Show Message
  0x14 = 00010100b = End Message
  Suggestion is that bit0 is set when alert is raised, and zeroed when alert is cleared.

We don't see any difference on the CAN bus between normal (visible on the VDS) error codes, and debug (DMC) errors. So, OVMS will report all. The VDS, by default, will suppress the DMC debug alerts. I think this 1146 is a debug-style alert (DMC: Motor Fan Problem).

 

[gregd]

Failure Type Data Bytes for the Error: 0x0200 → 0x0002 → 2 → Fan wired backwards (Might be due to the DFC setup and not the actual problem)

Um, what? Wiring? Yeah, not the actual problem, but perhaps one of the set of contacts is at issue? They've got a pair that used to drive separate motors, now connected in parallel in the wiring harness, right? Maybe it's an indication that one of the four pins is oxidizing?

Looking at the logs for correlations... The car was plugged in and started charging at 15:30:42, which is between the 5th and 6th events. One more event, then nearly an hour for the next burst. Charging ended at 18:40:00, which is after the last one. I've driven the car since then (short trips, short charges) and no further events, but haven't stressed it much.

I think I'll not panic at this point, and see how it behaves. Maybe wait until I get new tires in a month or so, and have them take a look at the connector then. I don't believe I have been able to get at the connector through the access door in the trunk, and am not up to removing the PEM myself. Do you think there would be damage done to the contacts by waiting?

 

[petergrub]

Um, what? Wiring? Yeah, not the actual problem, but perhaps one of the set of contacts is at issue?

I don't believe I have been able to get at the connector through the access door in the trunk, and am not up to removing the PEM myself. Do you think there would be damage done to the contacts by waiting?

It's probably an oversight in the firmware when Tesla created the DFC setup and not an actual issue, though it couldn't hurt to have Tesla double check on your next visit.

If you open the access door in the trunk, remove the three phase cables to the motor, and unplug all the connectors under the PEM, then there's usually enough slack on the last cable, RHC34, to pull it towards the access opening for easy inspection of the terminals.

However, since the VDS didn't report a motor fan error and it was only occurring on the back end as a debug alert as markwj pointed out, then you probably don't need to worry. In your case, error ID 1220 DFC: Motor Fan UnderCurrent would be the one to look out for if the motor fan is experiencing an undercurrent issue.

 

[Kerios]

1146 errors suck. But as @dpeilow and I have significant experience of this, they can be rectified fairly easily. The problem as @petergrub indicates usually lies with the connector at the PEM end, long story short we know that the fans were switche from single to dual, the connection cable at the fan end was modified by the SC to allow the dual fit fans to be added. This changed the load fractionally, but enough to cause potential damage i.e. shorting at the connection to the PEM. Additionally the connector’s MTFB (mean time to failure) isn’t clearly defined but we know that Tesla have stated that it is disconnected during service and this leads to degradation of the connector pins.

Weather doesn’t appear to be a key symptom for failure, but washing your car, driving in any condition which increases the load on the dual fans e.g. dusty, wet, leaves on the line , etc can lead to 1146 error, and it is cumulative, as the shorting or arcing increases (Peter may have more data on this) then the failure escalates faster.

There are in my view several key things one can do to mitigate this, and subsequent damage to the PEM:

1. Pull the fan and check the connections, including the modified harness - I replaced the fan unit after my dual fan failed, you can incidentally get a new dual fan (needs to be 12V, IP68 (that’s the weather proof rating)) for about $180 with a 3 year warranty from a UK dealer - PM me for details if you want them. The fan can be removed and refitted in an one hour, it’s seriously easy.

2. Check the harness at both ends, so as @petergrub says remove the motor 3 phase connections (after inhibiting the vehicle), and then remove (carefully) the cables on the under side of the PEM. Check with a mirror or endoscope for damage to the pins this will manifest as burn marks, carbonisation or melting worse case. If the connector is damaged then you may need to consider either having the SC look at the connector to the CIC board, or the connector on the cable harness - the latter can be easily replaced if you are competent with soldering etc - I’d advocate replacing the weather proof taping with heat shrink.

3. Finally, not trivial and one I think for @petergrub is to consider whether the CIC board connector can be replaced with something more heavy duty, that would be more serious, but would mitigate future failure, and could be a comparatively easily replacement within PEM and for fan. This option best for those cars out of warranty.

What is clear though is that the failure of the fans will lead to more serious overheating to the PEM, if the car has an Achille’s Heal, the dual fan blower unit is it. My car has been through 4 PEMS, yes you heard that right 4 PEMS, and that I am is certain due to a failure mode commencing with the 1146 error.

My tuppence. Happy to clarify if useful.

 

[gregd]

Thanks, Kerios, all understood. I've been through this once before, a few years ago, and had both the PEM and wiring harness (or at least the pins) replaced. They gave me quite a deal, money-wise, since apparently my car was one of the early ones to diagnose what was really happening. I also got 1144's back then, and some other 11xx (I forget exactly which). Besides the connector, I also had an air leakage problem with the duct work, and an incorrectly wired wiring harness (root cause unknown). So, this car's "Achilles heel" applies to both legs and maybe an elbow or two.

What has me puzzled, though, is what petergrub's decoding of my logs indicates. The car wasn't stressing the fans - only about 5 amps at the time. The last few miles of the journey were generally downhill, and on surface streets (45mph and less). One stop light a mile from my house, then a long downhill glide to the driveway. It's downhill enough that I can coast all the way here (had to do that in a prior car when the clutch went out). I had the A/C on, but turned it off when I turned onto my street (2 short blocks from home). So the low fan current is consistent with a lower need for cooling; there is not a spike in current that would be sensed as a resistive contact. Interestingly, however, the first event happened just as my wheels went over the curb onto the driveway, which is hit at an angle (passenger wheel first). So, that kind of suggests a mechanical root cause - a little frame twisting; perhaps the connector might just be loose? I think I can get a bit of a grasp on the wiring, and may try to just push it into place a bit more, and see if that changes things. I recall another posting some year or two ago where this was the case.

Unfortunately, if I continue to want Tesla to service that part of the car, I need to work with them on any modifications or repairs. I couldn't even get them to apply some DeOxit at the annual service earlier this year, which I would think would be a maintenance fundamental for this sort of situation, no? I think my approach this coming time will be to see if I can open their eyes a bit, that their expertise on these cars is going down, while ours (the owners) is going up, and we'd both be better off making it a partnership rather than a traditional service relationship. They've got a new service manager at my SC, so crossing my fingers... You don't put fine china in the dish washer. Think that line will work?

 

[hcsharp]

I couldn't even get them to apply some DeOxit at the annual service earlier this year, which I would think would be a maintenance fundamental for this sort of situation, no?

A lot of service centers ARE applying DeOxit to the connector when performing the annual service. Surprising your's hasn't figured that out.

 

[gregd]

A lot of service centers ARE applying DeOxit to the connector when performing the annual service. Surprising your's hasn't figured that out.

Excellent to hear! Any specific references that I can pass on to them?

 

[utch]

I have started working on my own parser, so I'll use my own experience to help decode the following log file record.
…...

• Failure Type Data Bytes for the Error: 0x0200 → 0x0002 → 2 → Fan wired backwards (Might be due to the DFC setup and not the actual problem)
• Voltage Data Bytes for the Error: 0xBBB6 → 0xB6BB → 46779 → 12.06V
• Amperage Data Bytes for the Error: 0xB424 → 0x24B4 → 9396 → 4.95A

This is awesome! Is there somewhere to look up the Failure Type? How does the volt/amp get converted to the decimal values?
In my case, I get the following:

0x00028029: 07/09/2018 10:20:39 | 1531153239 | ERR | 03 02 17 17 3F 00 5B438B57 | 08 00 76 00 7A 04 06 00 00 C1 67 10 0E 01 CA error code 1146 6 bytes
0x00028042: 07/09/2018 10:22:59 | 1531153379 | ERR | 03 02 17 17 3F 00 5B438BE3 | 08 00 76 00 7A 04 06 00 00 4B 67 0C 0E 01 B8 error code 1146 6 bytes

I'm unsure how to interpret the Failure type 0x0000 nor how to figure out the volt/amp from that data.

 

[hcsharp]

Excellent to hear! Any specific references that I can pass on to them?

Watertown, MA told me they check the contacts, clean and spray them with DeOxit.

 

[PV-EV]

O[=full]328273[/ATTACH] [QUOTE="gregd, post: 2959499, member: 31354"Do you think there would be damage done to the contacts by waiting?[/QUOTE]

This is what happened when I waited. Luckily I was two miles from home and the car would go about 1/4 mile at a time before shutting down so I didn’t need a tow. The mating male 90 degree connector that is soldered to a circuit board inside the PEM was fried and had to be replaced. Larger, heavier duty connectors have a different pin spacing on the PCB so it is non trivial to upgrade. My advice to you is perform regular maintenance on this known problem.

 

[PV-EV]

Somehow I messed up the quote in my reply but I think you get the idea

 

[gregd]

Thanks, PV-EV. I've driven the car several times since the event, and no further alerts. Not likely that the connector is that badly damaged. Ambient temps are also lower, for now, so I'm not going to panic. Also not willing to "go it alone" and begin doing all my own servicing, since that's a one-way street with Tesla.

New tires are on the agenda for next month, so will have the SC take a look at it then. Henry's reference to another service center who actually do try to address the issue, at least a little, will be a help. Not every 2.x Roadster has failed, and in the back of my mind I'm still thinking that the timing of the alert and the crossing of the driveway curb can't be a coincidence. I just wish I knew what the car saw in the voltage / current / temperature readings that caused it to throw the alerts. Nothing in Peter's decoding of the log would indicate a problem (at least, not to me).

 

[jfischer]

• Voltage Data Bytes for the Error: 0xBBB6 → 0xB6BB → 46779 → 12.06V

• Amperage Data Bytes for the Error: 0xB424 → 0x24B4 → 9396 → 4.95A

Peter, How to do you convert the HEX to the amperage and voltage?. 46779 to get 12.06V? and 9396 to get 9.95 amps?



Im getting a 1144 ERROR similar to this and wanted to see what the draw pull is...

Some of my output looks like

0x00064df8: 10/04/2018 12:59:53 | 1538675993 | ERR | 03 02 17 17 3F 00 5BB65519 | 08 00 74 00 78 04 06 02 00 4A B4 BC 23 20 17 error code 1144 6 bytes
0x00064e11: 10/04/2018 12:59:58 | 1538675998 | ERR | 03 02 17 17 3F 00 5BB6551E | 08 00 74 00 78 04 06 02 00 42 B5 66 23 20 6F error code 1144 6 bytes
0x00064e2a: 10/04/2018 13:00:09 | 1538676009 | ERR | 03 02 17 17 3F 00 5BB65529 | 08 00 74 00 78 04 06 02 00 3F B4 99 24 01 53 error code 1144 6 bytes
0x00064e43: 10/04/2018 13:02:20 | 1538676140 | ERR | 03 02 17 17 3F 00 5BB655AC | 08 00 74 00 78 04 06 02 00 ED B4 DC 22 20 C2 error code 1144 6 bytes
0x00064e5c: 10/04/2018 13:03:23 | 1538676203 | ERR | 03 02 17 17 3F 00 5BB655EB | 08 00 74 00 78 04 06 02 00 EB B3 2D 23 20 34 error code 1144 6 bytes
0x00064e75: 10/04/2018 13:04:06 | 1538676246 | ERR | 03 02 17 17 3F 00 5BB65616 | 08 00 74 00 78 04 06 02 00 AA B4 11 24 08 7B error code 1144 6 bytes

Looking to know how to decode the 5BB65616 in the last line for amps and volts.

John

 

[petergrub]

Peter, How to do you convert the HEX to the amperage and voltage?. 46779 to get 12.06V? and 9396 to get 9.95 amps?

The voltage and amperage are stored as 16-bit values in either a signed or unsigned short integers.
Voltage: unsigned 16-bit integer with a base value of .35V at 0x0000 and 16.75V at 0xFFFF
Current: signed 16-bit integer with a base value of -3.15A at 0x0000 and 0A at 0x0E46 to a value of 25.10A at 0x7FFF, and a base value of -31.40A at 0x8000 and -3.15A at 0xFFFF

I don't know why the current is a little weird as it should be symmetrical, but following those constraints should get you the correct values. I really need to finish my error decoder program for you guys.

 

[slcasner]

When Scott and I were working on the first decoding of the log files years ago what we determined was that all the voltages and currents in the charging and drive records were scaled by a power of 2. That is, the encoding was a fixed-point number with a binary point somewhere in the middle of the 8- or 16-bit value. Some were signed, some were unsigned, and in a few instances there was an offset added, but most were zero-based.