Hi
I have been working on modifying the hex code for the ibbu07 raid battery to be able to replace defective battery with new instead of buying a new Lsi pack at the price of 230$ here in Norway.
Here I have replaced U4 with new hexcode, U4 is a regular 24lc01B.
New Samsung ICP103450S battery fitted removed from a new Dell Perc6 battery module.
Here I have replaced hex code and the battery with 2000mAh , as you can see design capacity is 1800mAh which is 10% derated. Orginal battery I'm sure you now is 1215mAh if your module is fitted with Sony US503759 a8h but full capacity is 1350mAh also 10% derated.
I also changed date of manufacture just for fun, clock 22.40.53 is not stored in eeprom but copied from the computer when smbus was accessed.
Manufacturer and serialnumber is as orginal, completed discharge cycles I resetted to have a fresh start.
This if the modified code I used for the 1800mAh setup above except for 0x3F that I changed to 64 and seals the eeprom.
At first I did keep 0x3F at 24 but doing that Lsi has a built in code in msm or fw that replaces alot of alterations as you can see. It only happens when battery is fully charged at 100% and 4100mV.
Here Megaraid storage manager or raid card fw replaced some of my alternations.
When Lsi fw or msm noticed an unseal eeprom log also comes up with a few errors, later this weekend the log is not showing any errors with the new code.
For those of you that is using a Lsi ibbu07 I hope you can check something for me. As you can see from picture above I have finished a battery relearn and battery is charging but stops at 49% and battery status is 'Optimal'
Not sure if it is a problem with my hex code or normal feature of this software but can you check your software and report back at what capacity your battery charging stops ? pictures showing both properties and advanced properties just as picture above is more then welcome -serial number and manufacturer I don't need to see so feel free to paint over.
Data I need is voltage, design and full capacity, remaining capacity and charge %.
After fitting this battery I now regret using this big capacity - charging takes many many hours but I'm sure data retention time is awesome.
Also yesterday I made a new post in the want to buy thread, I'm looking for a Lsi ibbu08 pack with swollen/defective battery to see ibbu08 code and see what charge controller it uses.
If you have one let me know - link
I have been working on modifying the hex code for the ibbu07 raid battery to be able to replace defective battery with new instead of buying a new Lsi pack at the price of 230$ here in Norway.
Here I have replaced U4 with new hexcode, U4 is a regular 24lc01B.
New Samsung ICP103450S battery fitted removed from a new Dell Perc6 battery module.
Here I have replaced hex code and the battery with 2000mAh , as you can see design capacity is 1800mAh which is 10% derated. Orginal battery I'm sure you now is 1215mAh if your module is fitted with Sony US503759 a8h but full capacity is 1350mAh also 10% derated.
I also changed date of manufacture just for fun, clock 22.40.53 is not stored in eeprom but copied from the computer when smbus was accessed.
Manufacturer and serialnumber is as orginal, completed discharge cycles I resetted to have a fresh start.
This if the modified code I used for the 1800mAh setup above except for 0x3F that I changed to 64 and seals the eeprom.
At first I did keep 0x3F at 24 but doing that Lsi has a built in code in msm or fw that replaces alot of alterations as you can see. It only happens when battery is fully charged at 100% and 4100mV.
Here Megaraid storage manager or raid card fw replaced some of my alternations.
Code:
ID = 148
SEQUENCE NUMBER = 343
TIME = 16-01-2016 23:45:31
LOCALIZED MESSAGE = Controller ID: 0 Battery is discharging
ID = 113
SEQUENCE NUMBER = 342
TIME = 16-01-2016 23:44:31
LOCALIZED MESSAGE = Controller ID: 0 Unexpected sense: PD = -:-:0Power on, reset, or bus device reset occurred, CDB = 0x8f 0x00 0x00 0x00 0x00 0x01 0x45 0x31 0x10 0x00 0x00 0x00 0x10 0x00 0x00 0x00 , Sense = 0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x29 0x00 0x00 0x00 0x00 0x00
ID = 113
SEQUENCE NUMBER = 341
TIME = 16-01-2016 23:44:31
LOCALIZED MESSAGE = Controller ID: 0 Unexpected sense: PD = -:-:1Power on, reset, or bus device reset occurred, CDB = 0x8f 0x00 0x00 0x00 0x00 0x01 0x42 0x92 0x40 0x00 0x00 0x00 0x10 0x00 0x00 0x00 , Sense = 0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x29 0x00 0x00 0x00 0x00 0x00
ID = 113
SEQUENCE NUMBER = 340
TIME = 16-01-2016 23:44:30
LOCALIZED MESSAGE = Controller ID: 0 Unexpected sense: PD = -:-:0Power on, reset, or bus device reset occurred, CDB = 0x8f 0x00 0x00 0x00 0x00 0x01 0x45 0x30 0x30 0x00 0x00 0x00 0x10 0x00 0x00 0x00 , Sense = 0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x29 0x00 0x00 0x00 0x00 0x00
ID = 113
SEQUENCE NUMBER = 339
TIME = 16-01-2016 23:44:30
LOCALIZED MESSAGE = Controller ID: 0 Unexpected sense: PD = -:-:1Power on, reset, or bus device reset occurred, CDB = 0x8f 0x00 0x00 0x00 0x00 0x01 0x42 0x91 0x20 0x00 0x00 0x00 0x10 0x00 0x00 0x00 , Sense = 0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x29 0x00 0x00 0x00 0x00 0x00
ID = 268
SEQUENCE NUMBER = 338
TIME = 16-01-2016 23:44:30
LOCALIZED MESSAGE = Controller ID: 0 PD Reset: PD = -:-:1, Critical = 3, Path = 0x4433221102000000
ID = 268
SEQUENCE NUMBER = 337
TIME = 16-01-2016 23:44:30
LOCALIZED MESSAGE = Controller ID: 0 PD Reset: PD = -:-:0, Critical = 3, Path = 0x4433221103000000
ID = 151
SEQUENCE NUMBER = 336
TIME = 16-01-2016 23:44:30
LOCALIZED MESSAGE = Controller ID: 0 Battery relearn started
ID = 267
SEQUENCE NUMBER = 335
TIME = 16-01-2016 23:44:28
LOCALIZED MESSAGE = Controller ID: 0 Command timeout on PD: PD = -:-:1No addtional sense information, CDB = 0x8f 0x00 0x00 0x00 0x00 0x01 0x42 0x91 0x10 0x00 0x00 0x00 0x10 0x00 0x00 0x00 , Sense = , Path = 0x4433221102000000
ID = 267
SEQUENCE NUMBER = 334
TIME = 16-01-2016 23:44:28
LOCALIZED MESSAGE = Controller ID: 0 Command timeout on PD: PD = -:-:0No addtional sense information, CDB = 0x8f 0x00 0x00 0x00 0x00 0x01 0x45 0x30 0x20 0x00 0x00 0x00 0x10 0x00 0x00 0x00 , Sense = , Path = 0x4433221103000000
ID = 242
SEQUENCE NUMBER = 333
TIME = 16-01-2016 23:44:16
LOCALIZED MESSAGE = Controller ID: 0 Battery charge complete
For those of you that is using a Lsi ibbu07 I hope you can check something for me. As you can see from picture above I have finished a battery relearn and battery is charging but stops at 49% and battery status is 'Optimal'
Not sure if it is a problem with my hex code or normal feature of this software but can you check your software and report back at what capacity your battery charging stops ? pictures showing both properties and advanced properties just as picture above is more then welcome -serial number and manufacturer I don't need to see so feel free to paint over.
Data I need is voltage, design and full capacity, remaining capacity and charge %.
After fitting this battery I now regret using this big capacity - charging takes many many hours but I'm sure data retention time is awesome.
Also yesterday I made a new post in the want to buy thread, I'm looking for a Lsi ibbu08 pack with swollen/defective battery to see ibbu08 code and see what charge controller it uses.
If you have one let me know - link
Last edited: