I dont have access to download this files its restricted for me. But thanks for your suggestion sir. If I found correct calibration files. I can  edit xml strings like you. I have all menus active and i used every day but still want 3 tabs. It looks cool.

 

Kind regards.

On 11/11/2023 at 8:13 PM, E-Ing-X20XEV said:

For your experiment in getting 3rd tab for eco/performance icon, you could try IPC 2013 software package, but I don't have access to these files.

Plus you need IPC configuration xml file for this IPC Type, like you asked before.

VIN: W0LGM5EL1D1002972

Have a look here (not a perfect fit, but close):

 

Hello dear Toby, 

 

I try this calibrations eco tab was appeared. But ipc needles stopped working. Do you have any suggestions for me.

Can i take only os calibrations from 2013 rest of stay 2012. Is it possible?

Hi,

as programming was done successful without any errors,

you have to do a sps setup&configuration via type4 app and matching xml file for the new software.

My suggestion why your ipc needles stopped working is due to eeprom mismatch. configuration&setup will write DID's in the correct places in EEPROM.

2013 OS with 2012 Cals will not work due to different cal file sizes and versions.

1 hour ago, E-Ing-X20XEV said:

Hi,

as programming was done successful without any errors,

you have to do a sps setup&configuration via type4 app and matching xml file for the new software.

My suggestion why your ipc needles stopped working is due to eeprom mismatch. configuration&setup will write DID's in the correct places in EEPROM.

2013 OS with 2012 Cals will not work due to different cal file sizes and versions.

An error occured during programming. But calibrations loaded with my old eeprom configs. Is there any easy way to solve this problem. Reset eeprom to default conditions can be ok. Because i dont have any acess to sps. I have only globaltis v32 offline database. I try 3 times Rolling back to old working calibrations. Finally old calibrations loaded without any error. Unbricking was really hard. Thanks for your kind help. 

 

Aaron

On 11/11/2023 at 6:43 PM, aaronprg said:

I dont have access to download this files its restricted for me. But thanks for your suggestion sir. If I found correct calibration files. I can  edit xml strings like you. I have all menus active and i used every day but still want 3 tabs. It looks cool.

 

Kind regards.

So I guess you know how to edit the xml file for your IPC.

You modify your IPC xml file, start setup&config in GTIS v32, go to sps folder, then t4app and replace xml file with your modified file.

The differences between 2012 xml and 2013 xml code is in the length of the DID's and there is one more DID added:

DID02 length changed from 31 bytes to 32 bytes, add 01 at the end of your DID02 and correct length information to 32.

DID03 length changed from 6 bytes to 9 bytes, add 0F0000 at the end of your DID03 and correct length information to 9.

DIDA1 is added completely add this and in the writesection also.

DIDA2 length changed from 4 bytes to 6 bytes, add 0000 at the end of your DIDA2 and correct length information to 6.

DIDA3 length changed from 7 bytes to 8 bytes, add 01 at the end of your DIDA3 and correct length information to 8.

DIDA4, DIDA5 and DIDA6 no changes.

 

I will try to explain:

    <DidItem>
      <ID>DID0002</ID>
      <DidNo>0002</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_02</Name>
      <Description>This DID enables or disables individual display warnings.</Description>
      <DidLength>32</DidLength>
      <DefaultValue>EFFFFFEFDFFFFC7FFF5E3FFFFF7F6AE7CEFFFFFE7F7FBF3F5DBFFEF1F7E97F01</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>
    <DidItem>
      <ID>DID0003</ID>
      <DidNo>0003</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_03</Name>
      <Description>This DID enables or disables 'Extended Set' warnings</Description>
      <DidLength>9</DidLength>
      <DefaultValue>040000FEFF7D0B0000</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>

    <DidItem>
      <ID>DID00a1</ID>
      <DidNo>00A1</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_A1</Name>
      <Description>This DID is used for enabling and disabling menues on the display. It shall be write protected via security access.</Description>
      <DidLength>12</DidLength>
      <DefaultValue>1F11D3ECF7A3740000000000</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>
    <DidItem>
      <ID>DID00a2</ID>
      <DidNo>00A2</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_A2</Name>
      <Description>This DID is used for masking DTCs/FTBs in the ECU. A bit set to zero means that the DTC/FTB is disabled.                    Note:                    If DTC is triggered and then masked in this DID the DTC status byte will not be changed.                    The service $04 should be sent to the IPC after an update of this DID.</Description>
      <DidLength>6</DidLength>
      <DefaultValue>5FFEFCBE1F1F</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>
    <DidItem>
      <ID>DID00a3</ID>
      <DidNo>00A3</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_A3</Name>
      <Description>This DID is used for enabling and disabling menues on the display. It shall be write protected via security access.</Description>
      <DidLength>8</DidLength>
      <DefaultValue>B7FDF31C1C000486</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>
 

  <WriteSection>
    <WriteItem IDREF="DID0002" DelayForMS="0" />
    <WriteItem IDREF="DID0003" DelayForMS="0" />
    <WriteItem IDREF="DID00a1" DelayForMS="0" />
    <WriteItem IDREF="DID00a2" DelayForMS="0" />
    <WriteItem IDREF="DID00a3" DelayForMS="0" />
    <WriteItem IDREF="DID00a4" DelayForMS="0" />
    <WriteItem IDREF="DID00a5" DelayForMS="0" />
    <WriteItem IDREF="DID00a6" DelayForMS="0" />
    <WriteItem IDREF="DID00a8" DelayForMS="0" />
    <WriteItem IDREF="DID0090" DelayForMS="0" />
    <WriteItem IDREF="DID00a7" DelayForMS="0" />
    <WriteItem IDREF="DID009c" DelayForMS="0" />
    <WriteItem IDREF="DID009d" DelayForMS="0" />
    <WriteItem IDREF="DID00a0" DelayForMS="0" DidWriteScope="Service only" />
  </WriteSection>

 

You know the way back to restore your IPC, happy playing... and have fun...

 

1 hour ago, E-Ing-X20XEV said:

So I guess you know how to edit the xml file for your IPC.

You modify your IPC xml file, start setup&config in GTIS v32, go to sps folder, then t4app and replace xml file with your modified file.

The differences between 2012 xml and 2013 xml code is in the length of the DID's and there is one more DID added:

DID02 length changed from 31 bytes to 32 bytes, add 01 at the end of your DID02 and correct length information to 32.

DID03 length changed from 6 bytes to 9 bytes, add 0F0000 at the end of your DID03 and correct length information to 9.

DIDA1 is added completely add this and in the writesection also.

DIDA2 length changed from 4 bytes to 6 bytes, add 0000 at the end of your DIDA2 and correct length information to 6.

DIDA3 length changed from 7 bytes to 8 bytes, add 01 at the end of your DIDA3 and correct length information to 8.

DIDA4, DIDA5 and DIDA6 no changes.

 

I will try to explain:

    <DidItem>
      <ID>DID0002</ID>
      <DidNo>0002</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_02</Name>
      <Description>This DID enables or disables individual display warnings.</Description>
      <DidLength>32</DidLength>
      <DefaultValue>EFFFFFEFDFFFFC7FFF5E3FFFFF7F6AE7CEFFFFFE7F7FBF3F5DBFFEF1F7E97F01</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>
    <DidItem>
      <ID>DID0003</ID>
      <DidNo>0003</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_03</Name>
      <Description>This DID enables or disables 'Extended Set' warnings</Description>
      <DidLength>9</DidLength>
      <DefaultValue>040000FEFF7D0B0000</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>

    <DidItem>
      <ID>DID00a1</ID>
      <DidNo>00A1</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_A1</Name>
      <Description>This DID is used for enabling and disabling menues on the display. It shall be write protected via security access.</Description>
      <DidLength>12</DidLength>
      <DefaultValue>1F11D3ECF7A3740000000000</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>
    <DidItem>
      <ID>DID00a2</ID>
      <DidNo>00A2</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_A2</Name>
      <Description>This DID is used for masking DTCs/FTBs in the ECU. A bit set to zero means that the DTC/FTB is disabled.                    Note:                    If DTC is triggered and then masked in this DID the DTC status byte will not be changed.                    The service $04 should be sent to the IPC after an update of this DID.</Description>
      <DidLength>6</DidLength>
      <DefaultValue>5FFEFCBE1F1F</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>
    <DidItem>
      <ID>DID00a3</ID>
      <DidNo>00A3</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_A3</Name>
      <Description>This DID is used for enabling and disabling menues on the display. It shall be write protected via security access.</Description>
      <DidLength>8</DidLength>
      <DefaultValue>B7FDF31C1C000486</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>
 

  <WriteSection>
    <WriteItem IDREF="DID0002" DelayForMS="0" />
    <WriteItem IDREF="DID0003" DelayForMS="0" />
    <WriteItem IDREF="DID00a1" DelayForMS="0" />
    <WriteItem IDREF="DID00a2" DelayForMS="0" />
    <WriteItem IDREF="DID00a3" DelayForMS="0" />
    <WriteItem IDREF="DID00a4" DelayForMS="0" />
    <WriteItem IDREF="DID00a5" DelayForMS="0" />
    <WriteItem IDREF="DID00a6" DelayForMS="0" />
    <WriteItem IDREF="DID00a8" DelayForMS="0" />
    <WriteItem IDREF="DID0090" DelayForMS="0" />
    <WriteItem IDREF="DID00a7" DelayForMS="0" />
    <WriteItem IDREF="DID009c" DelayForMS="0" />
    <WriteItem IDREF="DID009d" DelayForMS="0" />
    <WriteItem IDREF="DID00a0" DelayForMS="0" DidWriteScope="Service only" />
  </WriteSection>

 

You know the way back to restore your IPC, happy playing... and have fun...

 

Thanks for detailed explanation dear sir. I will try my best to figure it out. Your kind support is priceless. 

Best regards. 

 

Aaron 

On 9/25/2024 at 10:22 AM, E-Ing-X20XEV said:

Hi,

as programming was done successful without any errors,

you have to do a sps setup&configuration via type4 app and matching xml file for the new software.

My suggestion why your ipc needles stopped working is due to eeprom mismatch. configuration&setup will write DID's in the correct places in EEPROM.

2013 OS with 2012 Cals will not work due to different cal file sizes and versions.

Hello, 

I edit xml files like your suggestions. But I couldn't install. It gives security check error.

- Configuration update failed: 
- XML Configuration Compatibility ID inconsistent with ECU  
- XEC Writing Of Data Unsuccessful
I try to edit several xml editors but no hope. Original 2012 calibrations and 2012 xml is loaded without problems.

When i install 2013 calibrations and edited xml is not working.

Now car has 2012 calibrations and xml

 

Ooops,

I forgot one thing.

Change the ConfigurationCompatibilityIdentifier from 0007 to 0008.

 

    <ConfigurationCompatibilityIdentifier>0008</ConfigurationCompatibilityIdentifier>

 

Hi! Insignia 2012 (W0LGT8GM5C1045901), can I use calibration or xml file from Astra J 2013 or 2014 to have separate parking sensors and display rear parking sensors?
Now:
W0LGT8GM5C1045901_Insignia 2012_IPC.zip

I want a display:

of course - NO.

How to make a segmented parking sensor? Perhaps calibrations from Insignia 2013 IPC will help? I wouldn't want to damage my IPC.
My IPC has older calibrations, but I think the hardware is the same.

 

On 10/21/2023 at 8:08 PM, Lyubomir Krastanov said:

your files, I cannot get Indicator calibrations... sorry, have to buy UDD IPC to get it and at the moment I'm bit short on funds

 

p16 astra j.rar 405.6 kB · 26 downloads

@Lyubomir Krastanov @E-Ing-X20XEV

Is it possible to get an XML file?

Hey,

I got several XML files for XML-Configuration 0008.

I am not allowed to download, but I want to share the files I have.

For the Astra J files there should be the 39001185.xml file to be used, but I don't have that particular one.

These files are for Chevy Cruze, Chevy Malibu and Chevy Impala.

Specially Chevy Cruze software is the same as Astra J.

 

22997929 - Malibu 2013 UDC.xml 23454622 - Impala 2014 UDC.xml 94558208 - Cruze 2014 UDC.xml

28 minutes ago, E-Ing-X20XEV said:

привіт

Я отримав кілька XML-файлів для XML-конфігурації 0008.

Мені заборонено завантажувати, але я хочу поділитися своїми файлами.

Для файлів Astra J має бути використаний файл 39001185.xml, але в мене його немає.

Ці файли для Chevy Cruze, Chevy Malibu та Chevy Impala.

Особливо програмне забезпечення Chevy Cruze таке ж, як і Astra J.

 

22997929 - Malibu 2013 UDC.xml 96,37 кБ · 0 завантажень 23454622 - Impala 2014 UDC.xml 77,49 Кб · 0 завантажень 94558208 - Cruze 2014 UDC.xml 128,25 кБ · 0 завантажень

Do you have separate parking sensors? I'm looking for an opportunity to make separate parking sensors for Insignia 2012-2013.

I don't know what it refers to, calibrations or xml configuration.

 

I only have the rear parking sensors, so I have no park distance information in DIC at all.

I tried all UD5 and UD7 related DIDs changes and got no luck, my hope was to get the rear distance information alone.

Changing the park assist ECU from RPA to FRPA coding ends up in error message regarding service park assist (because no front sensors connected), but shows the front and rear information before throwing the error message and disabled park assist system.

I guess the newer DIC picture is in the newer calibrations.
You are on a good way to ask Lyubomir for the software.

21 hours ago, E-Ing-X20XEV said:

I only have the rear parking sensors, so I have no park distance information in DIC at all.

I tried all UD5 and UD7 related DIDs changes and got no luck, my hope was to get the rear distance information alone.

Changing the park assist ECU from RPA to FRPA coding ends up in error message regarding service park assist (because no front sensors connected), but shows the front and rear information before throwing the error message and disabled park assist system.

I guess the newer DIC picture is in the newer calibrations.
You are on a good way to ask Lyubomir for the software.

Hi! I tried to use your graphical calibration, but my parking sensors are still displayed in the old way. I think it is somewhere in the xml file.

I used Insignia 2013 IPC , Insignia 2013 IPC XML and calibration of the Astra J from this topic.

CALIBRATION  MODID  LENGTH  FMT  DESCRIPTION 
----------------------------------------------------------------------------
13321936        00   0003733  BIN  Utility File (Insignia 2013)
22936187       01   0508448  BIN  Description of Cal (Insignia 2013)
22778457       02   0001536  BIN  Description of Cal (Insignia 2013)
22778467       03   0000768  BIN  Description of Cal (Insignia 2013)
22778472       04   0000256  BIN  Description of Cal (Insignia 2013)
22974142        05   0000512  BIN  Description of Cal (Insignia 2013)
22778499       06   0000256  BIN  Description of Cal (Insignia 2013)
22778504       07   0000256  BIN  Description of Cal (Insignia 2013)
22778506       08   0000256  BIN  Description of Cal (Insignia 2013)
13422795        09   0122864  BIN  Description of Cal (Astra J 2014)
13422797        10   0614384  BIN  Description of Cal (Astra J 2014)
13422796        11   0565232  BIN  Description of Cal (Astra J 2014)

 

OK out there,

 

I did a little bit of research and testing on an Astra J with front and rear park assist.

I was able to enable the old style and disable the new style and vice versa.

The magic is done in DID 02 Byte 16 Bit 3

FRONT_PARK_ASSIST_ENABLE must be disabled (otherwise the IPC will show the old style).

And in DID 03 Byte 6 Bit 2

FRONT_AND_REAR_PARK_ASSIST_ENABLE has to be enabled to make the IPC to show the new style (If not, the IPC will show no information).

 

Example for old style:

DID 02: ADFF1FEFDFFFFC7FEFD63FFFFF7E6BFF8DFFDFFE7F7FF7FF5FA776F83FB87F01

DID 03: 9F3F0FFEFF7F0B0000

 

Example for new style:

DID 02: ADFF1FEFDFFFFC7FEFD63FFFFF7E6BFF85FFDFFE7F7FF7FF5FA776F83FB87F01

DID 03: 9F3F0FFEFF7F0F0000

 

Good luck and tell the results...

 

@E-Ing-X20XEV Thank you, now I have a new style of parking sensors.

Is it now posible to get Bars if only UD7 ist equipt? Rear only

18 hours ago, marcel_hack_guy said:

Is it now posible to get Bars if only UD7 ist equipt? Rear only

I am in the same situation like you.
Sorry to tell you that this is not possible with DPS programming or Type 4 app without having UD5 retrofitted.

I saw some pictures of exactly the bars with only UD7, but that was done with an extra device named Happyblue or Happylightshow the supplier was cantronix.

Greetings

Toby

Okay sadly the same Story seems to be on UHS ipc. No Bars even visual Parkpilot is on. And the device Simulates UD5?

The device reads CAN information and displays it on a own customizable screen in IPC.

The information is available on CAN bus, I have the warnings enabled in RVC screen in NAVI600.

Additionally you can read the measured distances from each sensor with GDS2 on UPA ECU.

Can anyone Tell what is the differnt between UD7 and UDP?

UD7 only rear parking sensors,

UDP front, side and rear sensors with blind spot detection plus parking assistance instructions in IPC.