[miretni]

Thank you shawnsheridan for providing the newest software.
I'm no longer provide the ESYS and psdzdata.

cables are almost out of stock, i will no longer corporate with the cable manufacture. but i still have a few cable left, if you are interest and live in Toronto,
i would like to give it away for a cup of coffee and make some friends

Thanks again shawnsheridan, if anyone need the software you can @ shawnsheridan in this thread, i guess shawnsheridan will happy to help you. For the forum being neat, then u dont need to open another discussion for the software

[miretni]

yes, updated

[shawnsheridan]

Originally Posted by miretni

...
I will also share the newest psdzdata,
as the BMW services department update their database, i will update my psdzdata also.

anyway, the link to esys 3.25.3 and psdzdata 52.1: https://onedrive.live.com/?cid=EB5B2...9488585%212000

and down below is the 52.3 update files for 52.1
just simply cover the original files.

You cannot just copy jetstream update files (e.g. 52.1, 52.2, 52.3, 52.4, etc.) into existing full PSdZData folder (e.g. 52.0). You will have conflicts, and it won't work.

[miretni]

Originally Posted by shawnsheridan

You cannot just copy jetstream update files (e.g. 52.1, 52.2, 52.3, 52.4, etc.) into existing full PSdZData folder (e.g. 52.0). You will have conflicts, and it won't work.

well, this happens before in version 48.x update,
i covered those files and i still able to used. Eventually, 52.3 is not necessary for most cars, 52.1 is good enough by now. I have 52.3 on my laptop and its working well. but i trust u, due to the safety reason, i will tag 52.3 as [not necessary].

[949]

so this cable will allow me to code any bmw? or just certain ones?

[HFW003]

The cables are only $20 through one stop electronics!

[miretni]

Originally Posted by 949

so this cable will allow me to code any bmw? or just certain ones?

this is for F-chassis

[miretni]

Originally Posted by HFW003

The cables are only $20 through one stop electronics!

in my opinion, it looks like hand-made and yes, they are cheaper.
but this one, u pay for the quality

[EclipseDS]

And what's wrong with a hand-made? Unless you bought a specialized robotic machine to do all the soldering, cutting, and assembling for you, your claim is just that - a claim.

Full disclosure: I sell cables on eBay and sold almost a hundred now. Not one single complaint so far.

Talking about materials, did you use metal film resistors? 1% or 2% variant? 26 or 24 AWG? Solid or stranded copper? Lead-free solder?

Having said all that, craftsmanship is the most important. Soldering skills, testing...etc. those makes up quality, IMHO.

And E-Sys 3.25? Those in the know don't use it and recommend against using it for a reason. I don't get why some people insist on it.

[EclipseDS]

My real point is that you don't make others look bad just so you can sell your own stuff. Let your work speak for you. Claiming that eBay cables are bad and yours is the absolute bomb don't sit well with me.

[shawnsheridan]

Originally Posted by miretni

well, this happens before in version 48.x update,
i covered those files and i still able to used. Eventually, 52.3 is not necessary for most cars, 52.1 is good enough by now. I have 52.3 on my laptop and its working well. but i trust u, due to the safety reason, i will tag 52.3 as [not necessary].

Technically it depends on the specifics of each update. If it contains only the mapping, security, cafd, or swe updates, these can be copied into existing psdzdata. However, if it contains extLibs, kiswb, or mainseries updates, as is usually the case, then the corresponding older files must be deleted and replaced. They can not coexist without conflicts.

[shawnsheridan]

Originally Posted by EclipseDS

...
And E-Sys 3.25? Those in the know don't use it and recommend against using it for a reason. I don't get why some people insist on it.

This is very true. 3.25.2 was broke, and 3.25.3 works but has bugs, and until they are fixed, 3.24.3 is a wiser choice.

[miretni]

Originally Posted by EclipseDS

And what's wrong with a hand-made? Unless you bought a specialized robotic machine to do all the soldering, cutting, and assembling for you, your claim is just that - a claim.

Full disclosure: I sell cables on eBay and sold almost a hundred now. Not one single complaint so far.

Talking about materials, did you use metal film resistors? 1% or 2% variant? 26 or 24 AWG? Solid or stranded copper? Lead-free solder?

Having said all that, craftsmanship is the most important. Soldering skills, testing...etc. those makes up quality, IMHO.

And E-Sys 3.25? Those in the know don't use it and recommend against using it for a reason. I don't get why some people insist on it.

As i said, these cable are from my friend, i m selling these samples for him.
I dont know the exactly specs of those cables, and i didnt mean "hand-made must be bad quality", but the truth is i saw it..ehh, i dont mean hand-made is bad, no offenses, just telling people that story...u know.
I used to learned electronic, i know that if u can handle each details, it will be awesome, and I know some hand-made has better quality, but i just give buyer one more choice

[miretni]

Originally Posted by shawnsheridan

Technically it depends on the specifics of each update. If it contains only the mapping, security, cafd, or swe updates, these can be copied into existing psdzdata. However, if it contains extLibs, kiswb, or mainseries updates, as is usually the case, then the corresponding older files must be deleted and replaced. They can not coexist without conflicts.

You are right, boss!

[sbc55]

Originally Posted by shawnsheridan

This is very true. 3.25.2 was broke, and 3.25.3 works but has bugs, and until they are fixed, 3.24.3 is a wiser choice.

Do you mind tell me what is the bug for 3.25.3?? I have been using this to flash my ecus for f10 and recently just flashed my NBT to 52.3 successfully..

Just want to know what is the bug so that I may choose 3.24.3 next time.

[shawnsheridan]

I tested 3.25.3 back in December, almost 1/2 year ago, when it first came out, and there were issues with it, so I went back to 3.24.3.

I don't recall specifically. but I remember that functionally it seemed to work, but the UI was displaying bizarre things, particularly in the ToolTips, which was enough for me to know it came out of the oven too early.

In addition, the security was completely changed in 3.25.3, including not just the "patch" needed, but also the .EST Token itself, so anyone switching would need a completely new Token solution.

Since 3.25.3 adds zero functionality though, there is no reason nor benefit to use it. If you are not having any issues with it, stick with it, or you can drop down to previous version. Whatever works for you.

[mistercyril]

Hello,
This is my first try at this so it may sound like a stupid question but please bare with me, as I am really interested in understanding how to do this...

I have a 328iA sport (F30) from august 2012. The dealer last programmed it in may 2014 during a recall.

I have ESYS 3.25.3, PSdzData 52.1 and of course the cable.

How do I know if this is the proper PSdzData ?

My understanding is that the PSdzData contains all the latest configuration files for eligible BMWs. Is that correct?

I would appreciate any insight on this because i'm a bit overwhelmed by all the information out there.

Thanks,
C

[shawnsheridan]

The PSdZData version being used is >= to the last version of ISTA/P used to program the car. If you use the latest PSdZData, then you don't have to worry about it. Otherwise, you will need to read I-Step current from VCM, cross-reference it to the ISTA/P version, and determine if your PSdZData version is >= to it.

http://f30.bimmerpost.com/forums/sho...postcount=1403

[mistercyril]

Hello Shawn,
Thanks for the prompt reply.

Apparently the version of PSdkData I downloaded from the links provided above is broken... I get "The structure of the archive is damaged" when I try de decompress the rar files.

I'm decompressing with a mac, could that be the reason? Or do you think I should look for it elsewhere?

Best,
C.

[shawnsheridan]

Originally Posted by mistercyril

Hello Shawn,
Thanks for the prompt reply.

Apparently the version of PSdkData I downloaded from the links provided above is broken... I get "The structure of the archive is damaged" when I try de decompress the rar files.

I'm decompressing with a mac, could that be the reason? Or do you think I should look for it elsewhere?

Best,
C.

I really can't speak to this version, as I have no idea about its origin or its compression. On MAC though, you should use UnRarX, open only Part1.rar, and hit extract. If you get errors, your download is corrupt, and you will need to redownload it.

[mistercyril]

Sorry about my latest post but I hadn't realized I only needed to decompress the first .rar file...

Now i'm kind of stuck here because the install instruction manuals i'm finding on-line don't seem to look like what's going on with the version of e-Sys (3.25.3) offered above.

I've installed e-SYS and the root directory for the application is here :
C:\EC-Apps\ESG\E-SYS

Where do I put the PSdzData file?
How do I apply the patch?
Where do I add the provided token?

I'm asking this because the file structure doesn't look the same as previous versions of e-SYS, and because i'm really just trying to wrap my head around this...

Hope you can point me in the right direction.

Thanks,
C.

[shawnsheridan]

You need better Installation and Setup Instructions.

PM sent.

As for your token solution, you can put the .EST file anywhere. You just need to go under E-Sys Options and set the .EST Path to point to wherever you located it.

But, token solution is more than just the .EST Token file. You should have 2 patched .jar files that you need to replace E-Sys' native .jar files with.