SUBARU_5EAT_DENSO_26DE2OB0 2000 26DE2OB0 26DE2OB0 - - Subaru 5EAT transmission (Denso SH705x) 5AT_3.272_LEGAS_EJDM2008.bin 5EAT SH705x subarutcudenso 1024kb UPSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. P0720 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0705 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0741 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0753 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0758 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1706 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0748 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0743 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0731 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0732 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0733 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0734 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1707 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0715 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0801 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0768 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0763 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0736 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0719 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0713 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0712 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1762 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1760 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1718 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0773 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0735 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1710 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0771 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0766 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0756 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0751 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1844 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1843 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1842 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1841 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1840 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0958 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0957 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0101 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. Unidentified 10x10 table, header at 0x0C530C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0C5328. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0C5344. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5360. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C537C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5398. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C53B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C53D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C53EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5408. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5424. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5440. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C545C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5478. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5494. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5504. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5520. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C553C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5558. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5574. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5590. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C55AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C55C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C55E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5600. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C561C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5638. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5654. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5670. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C568C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5830. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C584C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5868. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5884. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C58A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C58D8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C58F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5910. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C592C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C5964. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C5980. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C599C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C59F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C5A0C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C6C00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C6C1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C6C38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x9 table, header at 0x0C6C54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7538. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7554. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7570. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C758C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C75A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C75C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C75E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C75FC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7618. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7634. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7650. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C766C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7688. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C76A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7714. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7730. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C77D8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C77F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C7810. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C78B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A08. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A24. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A40. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A5C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A78. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7AB0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7ACC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7AE8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7B04. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B20. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B3C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B58. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B74. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B90. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7BAC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7BC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7BE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7C00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0C7C54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0C7C70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7CFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7D18. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7D34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7D50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0C7D6C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0C7D88. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7DC0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7DDC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7DF8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E68. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E84. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EA0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EBC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7ED8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EF4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7F10. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7F2C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7F64. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7FD4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7FF0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C800C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8028. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8044. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8060. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C807C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8098. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C80B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C80EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C815C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C8178. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C8194. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C81CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C81E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C8424. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C8440. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C845C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0C84B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0C84CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C84E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8504. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8520. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C853C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8558. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C8590. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C85AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C85C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C85E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C8600. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. SUBARU_5EAT_DENSO_25D12WB1 2000 25D12WB1 25D12WB1 - - Subaru 5EAT transmission (Denso SH705x) 5AT_3.583_LEGASE_JDM2008.bin 5EAT SH705x subarutcudenso 1024kb UPSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. P0720 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0705 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0741 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0753 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0758 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1706 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0748 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0743 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0731 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0732 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0733 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0734 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1707 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0715 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0801 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0768 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0763 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0736 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0719 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0713 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0712 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1762 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1760 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1718 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0773 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0735 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1710 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0771 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0766 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0756 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0751 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1844 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1843 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1842 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1841 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1840 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0958 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0957 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0101 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. Unidentified 10x10 table, header at 0x0C52F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0C5310. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0C532C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5348. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5364. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5380. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C539C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C53B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C53D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C53F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C540C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5428. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5444. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5460. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C547C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C54EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5508. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5524. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5540. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C555C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5578. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5594. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C55B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C55CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C55E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5604. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5620. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C563C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5658. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5674. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5818. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5834. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5850. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C586C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5888. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C58C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C58DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C58F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5914. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C594C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C5968. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C5984. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C59D8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C59F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C6BE8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C6C04. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C6C20. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x9 table, header at 0x0C6C3C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7520. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C753C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7558. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7574. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7590. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C75AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C75C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C75E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7600. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C761C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7638. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7654. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7670. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C768C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76FC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7718. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C77C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C77DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C77F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C78A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C79F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A0C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A28. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A44. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A60. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7A98. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7AB4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7AD0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7AEC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B08. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B24. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B40. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B5C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B78. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B94. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7BB0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7BCC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7BE8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0C7C3C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0C7C58. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7CE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7D00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7D1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7D38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0C7D54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0C7D70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7DA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7DC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7DE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E6C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E88. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EA4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EC0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EDC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EF8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7F14. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7F4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7FBC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7FD8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7FF4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8010. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C802C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8048. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8064. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8080. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C809C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C80D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C8144. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C8160. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C817C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C81B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C81D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C840C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C8428. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C8444. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0C8498. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0C84B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C84D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C84EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8508. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8524. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8540. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C8578. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C8594. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C85B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C85CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C85E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. SUBARU_5EAT_DENSO_08FB2WA0 2000 08FB2WA0 08FB2WA0 - - Subaru 5EAT transmission (Denso SH705x) 8EFB206000_08FB2WA0_14_tribeca_usdm.bin 5EAT SH705x subarutcudenso 1024kb UPSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. P0720 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0705 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0741 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0753 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0758 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1706 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0748 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0743 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0731 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0732 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0733 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0734 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1707 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0715 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0801 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0768 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0763 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0736 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0719 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0713 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0712 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1762 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1760 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1718 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0773 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0735 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1710 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0771 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0766 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0756 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0751 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1844 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1843 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1842 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1841 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1840 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0958 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0957 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. Unidentified 8x8 table, header at 0x0E5280. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E529C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E52B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E52D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E52F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E8D40. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E8D5C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E8D78. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D94. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DB0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DCC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DE8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E04. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E20. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E3C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E58. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E74. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E90. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8EAC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8EC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F8C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E9018. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E9034. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E9050. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E906C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E9088. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E90A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E90C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9264. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9280. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E929C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E930C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9328. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9344. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9360. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E9398. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E93B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E93D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E9424. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E9440. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E945C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9478. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9494. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E94B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E94CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E94E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E9520. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E953C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E9558. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E95AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E95C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E95E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9600. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E961C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9638. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9654. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9670. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E968C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E96A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E96C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E96E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E96FC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E9718. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9734. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9750. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E976C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9788. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E97A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E97C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E97DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E97F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E9814. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9830. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E984C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E9868. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9884. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E98A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB40C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB428. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB444. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB460. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB47C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB498. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB4B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB4D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB4EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB508. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB5B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB5CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB5E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB690. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB7E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB7FC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB818. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB834. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB914. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB930. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB94C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB968. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB984. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB9A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0EB9F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0EBA10. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EBA2C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EBA48. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EBA64. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA9C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBAB8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBAD4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBAF0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBB0C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBB28. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBB60. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBB7C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBBEC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC08. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC24. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC40. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC5C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC78. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC94. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCB0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCE8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD04. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD20. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD3C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD58. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD74. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD90. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBDAC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBDC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBE00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE8C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBEC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBEE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBF88. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBFA4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBFDC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBFF8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC030. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC04C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC068. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC2B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC2CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC2E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC320. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC33C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC358. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC390. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC3AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC3C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC3E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC41C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC438. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC454. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC470. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC48C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC818. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC82C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC840. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC868. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC87C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC890. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC8A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC8B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC8CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC8E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. SUBARU_5EAT_DENSO_EZAE2WB1 2000 EZAE2WB1 EZAE2WB1 - - Subaru 5EAT transmission (Denso SH705x) B1AE207100_EZAE2WB1_2010_LGT_EDM.bin 5EAT SH705x subarutcudenso 1024kb UPSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. P0720 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0705 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0741 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0753 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0758 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1706 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0748 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0743 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0731 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0732 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0733 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0734 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1707 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0715 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0801 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0768 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0763 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0736 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0719 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0713 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0712 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1762 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1760 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1718 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0773 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0735 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1710 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0771 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0766 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0756 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0751 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1844 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1843 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1842 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1841 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1840 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0958 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0957 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. Unidentified 8x8 table, header at 0x0E5208. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E5224. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E5240. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E525C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E5278. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E8CC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E8CE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E8D00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D8C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E18. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8EC0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8EDC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8EF8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F14. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F30. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F68. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F84. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FA0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FBC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FD8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FF4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E9010. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E902C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E9048. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E91EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9208. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9224. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9240. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E925C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9294. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E9320. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E933C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E9358. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E93AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E93C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E93E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9400. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E941C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9438. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9454. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9470. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E94A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E94C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E94E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9534. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9550. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E956C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9588. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E95A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E95C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E95DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E95F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9614. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9630. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E964C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9668. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9684. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E96A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E96BC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E96D8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E96F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9710. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E972C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E9748. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9764. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9780. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E979C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E97B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E97D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E97F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E980C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9828. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB394. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB3B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB3CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB3E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB404. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB420. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB43C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB458. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB474. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB490. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB538. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB554. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB570. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB618. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB768. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB784. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB7A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB7BC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB848. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB864. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB880. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB89C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB90C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB928. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0EB97C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0EB998. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EB9B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EB9D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EB9EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA24. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA40. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA5C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA78. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBA94. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBAB0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBAE8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBB04. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBB74. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBB90. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBBAC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBBC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBBE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC8C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD18. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD88. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBDDC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBDF8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE14. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE68. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBF10. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBF2C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBF64. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBF80. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBFB8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBFD4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBFF0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC238. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC254. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC270. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC2A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC2C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC2E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC318. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC334. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC350. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC36C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC414. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC73C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC750. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC764. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC778. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC7F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC804. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC818. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC82C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC840. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC854. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC868. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. SUBARU_5EAT_DENSO_PDDE2WA0 2000 PDDE2WA0 PDDE2WA0 - - Subaru 5EAT transmission (Denso SH705x) Forester_SH9_STI_3.283_JDM2010.bin 5EAT SH705x subarutcudenso 1024kb UPSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. P0720 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0705 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0741 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0753 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0758 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1706 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0748 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0743 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0731 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0732 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0733 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0734 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1707 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0715 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0801 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0768 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0763 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0736 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0719 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0713 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0712 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1762 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1760 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1718 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0773 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0735 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1710 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0771 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0766 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0756 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0751 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1844 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1843 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1842 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1841 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1840 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0958 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0957 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. Unidentified 8x8 table, header at 0x0E5208. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E5224. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E5240. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E525C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E5278. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E8CC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E8CE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E8D00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D8C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E18. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8EC0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8EDC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8EF8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F14. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F30. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F68. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F84. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FA0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FBC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FD8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FF4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E9010. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E902C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E9048. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E91EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9208. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9224. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9240. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E925C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9294. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E9320. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E933C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E9358. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E93AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E93C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E93E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9400. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E941C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9438. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9454. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9470. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E94A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E94C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E94E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9534. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9550. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E956C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9588. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E95A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E95C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E95DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E95F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9614. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9630. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E964C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9668. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9684. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E96A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E96BC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E96D8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E96F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9710. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E972C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E9748. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9764. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9780. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E979C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E97B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E97D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E97F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E980C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9828. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB394. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB3B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB3CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB3E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB404. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB420. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB43C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB458. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB474. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB490. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB538. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB554. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB570. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB618. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB768. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB784. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB7A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB7BC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB848. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB864. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB880. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB89C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB90C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB928. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0EB97C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0EB998. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EB9B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EB9D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EB9EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA24. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA40. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA5C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA78. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBA94. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBAB0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBAE8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBB04. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBB74. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBB90. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBBAC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBBC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBBE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC8C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD18. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD88. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBDDC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBDF8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE14. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE68. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBF10. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBF2C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBF64. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBF80. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBFB8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBFD4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBFF0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC238. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC254. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC270. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC2A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC2C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC2E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC318. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC334. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC350. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC36C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC414. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC73C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC750. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC764. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC778. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC7F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC804. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC818. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC82C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC840. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC854. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC868. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. SUBARU_5EAT_DENSO_WQDE2WB1 2000 WQDE2WB1 WQDE2WB1 - - Subaru 5EAT transmission (Denso SH705x) Impreza_STI_3.583_JDM2011.bin 5EAT SH705x subarutcudenso 1024kb UPSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. P0720 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0705 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0741 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0753 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0758 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1706 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0748 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0743 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0731 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0732 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0733 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0734 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1707 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0715 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0801 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0768 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0763 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0736 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0719 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0713 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0712 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1762 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1760 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1718 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0773 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0735 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1710 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0771 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0766 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0756 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0751 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1844 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1843 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1842 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1841 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1840 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0958 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0957 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. Unidentified 8x8 table, header at 0x0E5208. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E5224. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E5240. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E525C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 8x8 table, header at 0x0E5278. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E8CC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E8CE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E8D00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8D8C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8DFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E18. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E8E50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8EC0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8EDC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8EF8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F14. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F30. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F68. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8F84. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FA0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FBC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FD8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E8FF4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E9010. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E902C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E9048. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E91EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9208. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9224. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9240. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E925C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E9294. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E92E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E9320. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E933C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E9358. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E93AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E93C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E93E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9400. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E941C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9438. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9454. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E9470. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E94A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E94C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E94E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9534. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9550. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E956C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9588. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E95A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E95C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x6 table, header at 0x0E95DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E95F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9614. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9630. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E964C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9668. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x5 table, header at 0x0E9684. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E96A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E96BC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E96D8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E96F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9710. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E972C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E9748. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9764. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9780. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E979C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E97B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E97D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x10 table, header at 0x0E97F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E980C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E9828. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB394. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB3B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB3CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB3E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EB404. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB420. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB43C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB458. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB474. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EB490. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB538. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB554. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB570. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0EB618. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB768. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB784. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB7A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0EB7BC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB848. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB864. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB880. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB89C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB8F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB90C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0EB928. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0EB97C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0EB998. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EB9B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EB9D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0EB9EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA24. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA40. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA5C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0EBA78. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBA94. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBAB0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBAE8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBB04. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBB74. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBB90. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBBAC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBBC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBBE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBC8C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBCFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD18. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBD88. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBDDC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBDF8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE14. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0EBE68. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBF10. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0EBF2C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBF64. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0EBF80. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBFB8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBFD4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EBFF0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC238. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC254. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0EC270. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC2A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC2C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0EC2E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC318. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC334. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC350. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0EC36C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC3F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0EC414. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC73C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC750. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC764. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC778. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0EC7C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC7F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC804. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC818. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC82C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC840. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC854. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0EC868. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. SUBARU_5EAT_DENSO_25D1AWS1 2000 25D1AWS1 25D1AWS1 - - Subaru 5EAT transmission (Denso SH705x) SH7058S-3171121010_STI.bin 5EAT SH705x subarutcudenso 1024kb UPSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. P0720 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0705 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0741 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0753 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0758 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1706 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0748 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0743 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0731 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0732 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0733 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0734 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1707 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0715 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0801 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0768 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0763 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0736 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0719 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0713 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0712 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1762 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1760 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1718 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0773 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0735 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1710 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0771 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0766 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0756 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0751 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1844 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1843 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1842 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1841 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1840 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0958 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0957 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0101 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. Unidentified 10x10 table, header at 0x0C52F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0C5310. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0C532C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5348. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5364. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5380. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C539C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C53B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C53D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C53F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C540C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5428. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5444. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5460. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C547C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C54EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5508. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5524. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5540. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C555C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5578. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5594. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C55B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C55CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C55E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5604. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5620. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C563C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5658. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5674. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5818. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5834. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5850. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C586C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5888. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C58C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C58DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C58F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5914. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C594C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C5968. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C5984. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C59D8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C59F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C6BE8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C6C04. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C6C20. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x9 table, header at 0x0C6C3C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7520. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C753C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7558. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7574. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7590. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C75AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C75C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C75E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7600. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C761C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7638. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7654. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7670. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C768C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C76FC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7718. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C77C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C77DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C77F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C78A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C79F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A0C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A28. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A44. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7A60. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7A98. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7AB4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7AD0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7AEC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B08. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B24. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B40. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B5C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B78. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7B94. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7BB0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7BCC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7BE8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0C7C3C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0C7C58. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7CE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7D00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7D1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7D38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0C7D54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0C7D70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7DA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7DC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7DE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E6C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7E88. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EA4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EC0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EDC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7EF8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7F14. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7F4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7FBC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7FD8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7FF4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8010. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C802C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8048. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8064. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C8080. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C809C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C80D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C8144. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C8160. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C817C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C81B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C81D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C840C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C8428. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C8444. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0C8498. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0C84B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C84D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C84EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8508. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8524. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8540. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C8578. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C8594. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C85B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C85CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C85E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. SUBARU_5EAT_DENSO_YSD12WB0 2000 YSD12WB0 YSD12WB0 - - Subaru 5EAT transmission (Denso SH705x) SH7058S_TG5_3.083.bin 5EAT SH705x subarutcudenso 1024kb UPSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. P0720 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0705 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0741 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0753 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0758 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1706 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0748 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0743 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0731 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0732 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0733 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0734 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1707 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0715 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0801 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0768 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0763 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0736 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0719 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0713 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0712 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1762 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1760 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1718 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0773 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0735 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1710 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0771 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0766 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0756 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0751 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1844 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1843 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1842 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1841 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1840 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0958 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0957 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0101 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. Unidentified 10x10 table, header at 0x0DFD38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0DFD54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0DFD70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFD8C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFDA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFDC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFDE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFDFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFE18. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFE34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFE50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFE6C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFE88. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFEA4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0DFEC0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0DFF30. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0DFF4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0DFF68. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0DFF84. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0DFFA0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0DFFBC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0DFFD8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0DFFF4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E0010. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E002C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E0048. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E0064. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E0080. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E009C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E00B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E025C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E0278. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E0294. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E02B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E02CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E0304. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E0320. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E033C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0E0358. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E0390. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E03AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E03C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E041C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E0438. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E0454. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E0470. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E048C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E04A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E04C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E04E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E0518. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E0534. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E0550. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E05A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E05C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E05DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E05F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0E0614. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E0630. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 6x5 table, header at 0x0E064C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0E1158. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0E1174. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0E1190. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0E11AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x9 table, header at 0x0E11C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E207C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E2098. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E20B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E20D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E20EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2108. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2124. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2140. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E215C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2178. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0E2220. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0E223C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0E2258. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0E2300. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0E2450. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0E246C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0E2488. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0E24A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E2530. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E254C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E2568. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E2584. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E25A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E25BC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E25D8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E25F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0E2610. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0E2664. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0E2680. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0E269C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0E26B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x20 table, header at 0x0E26D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E270C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E2728. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E2744. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0E2760. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0E277C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0E2798. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E27D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E27EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E285C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2878. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2894. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E28B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E28CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E28E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2904. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2920. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2958. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E29AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E29C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E29E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2A00. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2A1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2A38. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2A54. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2A70. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2AA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0E2AFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0E2B18. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0E2B34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0E2B6C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0E2B88. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2C30. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0E2C4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0E2C84. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0E2CA0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E2CD8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E2CF4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E2D10. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0E2F3C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0E2F58. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0E2F74. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0E2FAC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0E2FC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0E2FE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0E301C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0E3038. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0E3054. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0E3070. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0E30A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0E30C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0E30E0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0E30FC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0E3118. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E3380. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E3394. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E33A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E33BC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E33E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E33F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0E340C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E3434. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E3448. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E345C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E3470. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E3484. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E3498. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0E34AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. SUBARU_5EAT_DENSO_02EB2WB0 2000 02EB2WB0 02EB2WB0 - - Subaru 5EAT transmission (Denso SH705x) Tribeca_3.583_EDM_2009.bin 5EAT SH705x subarutcudenso 1024kb UPSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 1 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 2 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 3 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 4 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 5 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. UPSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. DOWNSHIFT SCHEDULE 6 of 6. Road speed at which each shift happens, against accelerator angle. Each row is one shift: 1-2, 2-3, 3-4, 4-5 in that order, top to bottom A row reading 255 throughout is unused in this calibration. ABOVE ROUGHLY 35% PEDAL THIS TABLE STOPS DECIDING. Every row flattens into the same tail, ending at a speed the car cannot reach - 224 km/h on upshift schedules, 205 on downshift. That entry means "do not shift on road speed", and above it the shift is governed by an engine speed limit instead. Full-throttle shifts in a logged car occur at 6278 to 7300 turbine rpm against a 6944 rpm maximum: they are redline shifts. So changing the high-pedal end of these curves will NOT move a full-throttle shift point. Only the part-throttle region does anything. Below that, the threshold here is necessary but not sufficient. A logged car sat 25 to 45 km/h above every 4-5 threshold it has, in the right gear at steady speed, and held fourth for four seconds before shifting - so something inhibits the change beyond this comparison. Raising a value will delay a shift; lowering one does not guarantee it happens sooner. Confirmed against a log from WQDE2WB1, the calibration these tables were read from. See FINDINGS.md sections 36 and 37. P0720 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0705 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0741 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0753 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0758 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1706 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0748 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0743 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0731 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0732 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0733 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0734 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1707 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0715 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0801 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0768 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0763 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0736 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0724 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0719 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0713 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0712 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1762 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1760 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1718 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0773 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0735 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1710 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0771 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0766 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0761 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0756 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0751 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1844 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1843 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1842 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1841 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P1840 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0958 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0957 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0817 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. P0101 - enable or disable this diagnostic trouble code. DISABLED writes zero to this code's slot, which makes it identical to the slots the factory already leaves empty. The fault bit still sets internally, but no code number is attached to it, so nothing is reported. Know what that does and does not do. It suppresses the CODE, not the FAULT - whatever limp-home, pressure or shift behaviour the TCU applies when that bit sets will still happen. You have only stopped it telling you why. Which condition sets this code is not established for this controller family. Unidentified 10x10 table, header at 0x0C4FC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0C4FE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x11 table, header at 0x0C4FFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5018. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5034. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5050. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C506C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5088. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C50A4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C50C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C50DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C50F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5114. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C5130. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C514C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C51BC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C51D8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C51F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5210. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C522C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5248. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5264. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5280. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C529C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C52B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C52D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C52F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C530C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5328. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x8 table, header at 0x0C5344. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C54E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5504. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5520. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C553C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5558. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C5590. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C55AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C55C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x20 table, header at 0x0C55E4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C561C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C5638. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C5654. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C56A8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C56C4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C68B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C68D4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 17x8 table, header at 0x0C68F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x9 table, header at 0x0C690C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C71F0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C720C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7228. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7244. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7260. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C727C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7298. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C72B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C72D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C72EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7308. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7324. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7340. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C735C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7378. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7394. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C73B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C73CC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C73E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C7490. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C74AC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C74C8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x7 table, header at 0x0C7570. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C76C0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C76DC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C76F8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7714. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 9x5 table, header at 0x0C7730. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7768. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7784. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C77A0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C77BC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C77D8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C77F4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7810. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C782C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7848. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7864. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C7880. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C789C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x11 table, header at 0x0C78B8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0C790C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x20 table, header at 0x0C7928. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C79B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C79D0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C79EC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x4 table, header at 0x0C7A08. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0C7A24. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 5x5 table, header at 0x0C7A40. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7A78. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7A94. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 10x5 table, header at 0x0C7AB0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7B04. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7B20. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7B3C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7B58. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7B74. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7B90. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7BAC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7BC8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7BE4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7C1C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7C8C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7CA8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7CC4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7CE0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7CFC. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7D18. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7D34. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7D50. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7D6C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x5 table, header at 0x0C7DA4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C7E14. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C7E30. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C7E4C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C7E84. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x2 table, header at 0x0C7EA0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C807C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C8098. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 16x22 table, header at 0x0C80B4. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0C8108. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 15x11 table, header at 0x0C8124. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8140. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C815C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8178. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C8194. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 11x10 table, header at 0x0C81B0. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C81E8. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C8204. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C8220. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C823C. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea. Unidentified 7x14 table, header at 0x0C8258. The structure is certain - the header is self-consistent and the axes are real float arrays - but the physical quantity is NOT established, so no units are claimed and the values are shown raw. Changing it without knowing what it does is a bad idea.