Fixed in 0.12.42Gampy wrote: Attempting to open a read only file causes crash.
- Added parameters "FileAccess.Read, FileShare.ReadWrite"
Fixed in 0.12.42Gampy wrote: Attempting to open a read only file causes crash.
"Search in the diagnostic segment for 01 01 01 ff 00 06"ironduke wrote:Hey Joukoy, I don't want to sidetrack this topic too much, but..
How hard would it be to write some code that did this to assist in creating an XDF..
take any E38 bin
Search in the OS segment for 00 00 00 10 00 11 and read all the data including the 00 10 00 11 til it gets to 94 21 ff .. this data is made into a list of words(2 bytes)
Search in the diagnostic segment for 01 01 01 ff 00 06 and read the data including the 06 til you get to your first ff.. this data is made into a list of bytes
Each list should be the same size, add the 2 together and it makes up the DTC's AND the switch to make them A,B,C, or not reported and MIL on/off..
First in the list is all the P codes..
the codes that start with a 5 are C codes, carry a 1 for the code 5207 is c1207
the ones that start with a C are U codes, DON't carry a 1.. code c109 us U0109
00 MIL and reporting off
01 type A/no mil
02 type B/no mil
03 type C/no mil
04 not reported/no mil
05 type A/mil
06 type B/mil
07 type c/mil
I've created some XDF's by hand for OS's I have, but it would probably help everyone else if this could be automated a bit.. Lot of digging coming up with this, had some bins that had codes turned off, then kept on trying with my bench ecu setting codes then turning them off, etc..
What your saying is what I've come up with as well..kur4o wrote:ironduke,
That looks like a good piece of information. Can you provide some examples with samples how the thing works, and how it can be used by the program.
As far as I understand the dtcs available are hardcoded in the OS and there is some -and- table that is at the diag segment.
Is there any way to make a list of the OS by the DTC numbers that are used.