Page 5 of 40 FirstFirst 12345678910111213141530 ... LastLast
Results 101 to 125 of 985

Thread: Diagnostic program with realtime graph view

  1. #101
    Join Date
    Nov 2012
    Location
    minsk
    Posts
    3
    My Cars
    1997 bmw 523
    Thank you for your work. But the new version will not be displayed schedules all cylinders (gasoline engines) in the other did not check. And on the previous version everything was fine.

  2. #102
    Join Date
    Aug 2010
    Location
    Pittsburgh, PA
    Posts
    608
    My Cars
    E36 M3 / 2.0T WRX
    I have an MS41.2 ECU. I don't think that's in the list of ECUs. I can't seem to connect using Testo; can't read values and as a result, can't run the trace. I think the cable on Com 1 is fine since it works with Smooth's program. Any ideas?

    I've never tried to get EDIABAS working and use the factory tools. The cable I'm using is a simple VAG-COM cable. Should I be able to run the trace function with it? I don't know what port Testo looks for etc.

    I also have a KWP2000+ cable and a BMW Scanner 1.4 cable if you think I should try it with that.
    Last edited by mrf; 11-29-2012 at 11:47 PM.

  3. #103
    Join Date
    Nov 2007
    Location
    Finland, Europe
    Posts
    530
    My Cars
    E61 520d LCI
    Quote Originally Posted by dov70 View Post
    Thank you for your work. But the new version will not be displayed schedules all cylinders (gasoline engines) in the other did not check. And on the previous version everything was fine.
    Hi!

    Can you take a screen capture JPG ? I am not not sure what you mean.

    Quote Originally Posted by mrf View Post
    I have an MS41.2 ECU. I don't think that's in the list of ECUs. I can't seem to connect using Testo; can't read values and as a result, can't run the trace. I think the cable on Com 1 is fine since it works with Smooth's program. Any ideas?

    I've never tried to get EDIABAS working and use the factory tools. The cable I'm using is a simple VAG-COM cable. Should I be able to run the trace function with it? I don't know what port Testo looks for etc.
    mrf, thanks for testing. Well, you have to install INPA / EDIABAS first as my program relies on that. Do you have it installed and working ? I'm not 100% sure if plain VAG-COM cable will work. I myself use ADS cable.

    When you read fault codes from your ECU with INPA you should see the variant it uses. For example for MS41 there are many PRG files (variants). I believe it should be found from the list of Testo too but the name may still say it is 41.0.

    This would be one of the areas that would need enhancement - automatic variant finding. To be honest I don't know the procedure how INPA finds the correct variant.
    Last edited by pheno; 11-30-2012 at 04:31 PM. Reason: Automerged Doublepost
    E61 520d LCI

    Check out TestO - free datalogger for BMW. Includes support for: AEM, PLX, 14point7, Innovate (through SDK)

  4. #104
    Join Date
    Nov 2012
    Location
    minsk
    Posts
    3
    My Cars
    1997 bmw 523
    Hi! Unfortunately I can not yet connect to the machine. remember msv70
    Motor roughness
    status_motorlaufunruhe
    to display graphics on all cylinders at the same time

  5. #105
    Join Date
    Nov 2007
    Location
    Finland, Europe
    Posts
    530
    My Cars
    E61 520d LCI
    Quote Originally Posted by dov70 View Post
    Hi! Unfortunately I can not yet connect to the machine. remember msv70
    Motor roughness
    status_motorlaufunruhe
    to display graphics on all cylinders at the same time
    Thank you for reporting !

    I just fixed the bug .. it was a tough one. I just hate to have bugs in my software.
    E61 520d LCI

    Check out TestO - free datalogger for BMW. Includes support for: AEM, PLX, 14point7, Innovate (through SDK)

  6. #106
    Join Date
    Aug 2010
    Location
    Pittsburgh, PA
    Posts
    608
    My Cars
    E36 M3 / 2.0T WRX
    OK, I'll try again once I get INPA etc. working.

  7. #107
    Join Date
    Nov 2007
    Location
    Finland, Europe
    Posts
    530
    My Cars
    E61 520d LCI
    Hmm... I've received only a few trace files. Does this mean You guys are not interested in faster logging ?

    It is impossible for me to implement faster logging based on directly reading/writing from serial port without trace files from You. It is not going to happen without Your help. Every trace file is important. I really mean it.

    Well, do you have any other feature requests ?
    E61 520d LCI

    Check out TestO - free datalogger for BMW. Includes support for: AEM, PLX, 14point7, Innovate (through SDK)

  8. #108
    Join Date
    Aug 2010
    Location
    Pittsburgh, PA
    Posts
    608
    My Cars
    E36 M3 / 2.0T WRX

    Exclamation Attention - All INPA/DIS users - R&D request - Datalogging

    A user on this site, pheno, is working on trying to support high speed datalogging for BMW ECUs. For him to do that, he needs trace files for various ECUs by requesting the ECU for various parameters and dumping it to a log file which he can use to poll the ECU natively using serial commands. This will enable him to write code to log those parameters bypassing EDIABAS which is significantly faster.

    He needs people who have a working EDIABAS install tested with INPA/DIS to run his program and run the Debug->Trace command as noted in this post.

    Please, if you can, run his program and attach the trace output to your post in this thread.

    Thanks for your support.

  9. #109
    Join Date
    Nov 2012
    Location
    minsk
    Posts
    3
    My Cars
    1997 bmw 523
    Hi! I can not figure out where to attach the file. Tell email address.
    Sorry for the Google transliteration.

  10. #110
    Join Date
    Nov 2007
    Location
    Finland, Europe
    Posts
    530
    My Cars
    E61 520d LCI
    Quote Originally Posted by dov70 View Post
    Hi! I can not figure out where to attach the file. Tell email address.
    Sorry for the Google transliteration.
    Thank you.

    email is: phenotesto@gmail.com
    E61 520d LCI

    Check out TestO - free datalogger for BMW. Includes support for: AEM, PLX, 14point7, Innovate (through SDK)

  11. #111
    Join Date
    Aug 2010
    Location
    Pittsburgh, PA
    Posts
    608
    My Cars
    E36 M3 / 2.0T WRX
    Ugh... The mods moved the request thread I started to this one... Great. The whole point of that thread was to get people who have a working INPA/DIS to run the trace command. And there are a lot of people who can do that but don't necessarily check this main thread for updates etc.

    Anyway, I still need to get INPA/DIS working before I can run the trace command on my MS41.2.

  12. #112
    Join Date
    Jun 2009
    Location
    Wichita,KS/FortCollins,CO
    Posts
    21,274
    My Cars
    (4x7)+8=36
    This is where it belongs.
    95 840Ci, Calypso Red/Silver, 83k - 99 740i, Black/Black, 185k, Alpina Mods - 01 740i, Titanium/Silver, 40k, Sport Pkg
    Complete Turnkey Diagnostic/Programming systems available...PM for details.

    http://www.8Coupe.com - Please register, spot, and help the project.

  13. #113
    Join Date
    Aug 2010
    Location
    Pittsburgh, PA
    Posts
    608
    My Cars
    E36 M3 / 2.0T WRX
    pheno, what cable do you have that allows you to use your program? Is your car ADS or OBD compatible?

  14. #114
    Join Date
    Nov 2007
    Location
    Finland, Europe
    Posts
    530
    My Cars
    E61 520d LCI
    Quote Originally Posted by mrf View Post
    pheno, what cable do you have that allows you to use your program? Is your car ADS or OBD compatible?
    I have ADS and also simple K-Line interface. Both work with my ECU.
    E61 520d LCI

    Check out TestO - free datalogger for BMW. Includes support for: AEM, PLX, 14point7, Innovate (through SDK)

  15. #115
    Join Date
    Aug 2010
    Location
    Pittsburgh, PA
    Posts
    608
    My Cars
    E36 M3 / 2.0T WRX
    Which ADS interface? Which K-Line interface? Got a link(s)?

  16. #116
    Join Date
    Nov 2007
    Location
    Finland, Europe
    Posts
    530
    My Cars
    E61 520d LCI
    Quote Originally Posted by mrf View Post
    Which ADS interface? Which K-Line interface? Got a link(s)?
    I'm using rv8flyboy's ADS interface:

    http://forums.bimmerforums.com/forum....php?t=1435617

    It has a switch that allows also OBD mode

    K-Line interface is made by myself and I couldn't find the schema anymore. Uses max232 and some transistors and is very simple.

    I would suggest getting the ADS interface. BMW OBD2 interface will work too as your car is newer than mine. It does not cost as much as ADS.
    I'll try to get a link for you.
    E61 520d LCI

    Check out TestO - free datalogger for BMW. Includes support for: AEM, PLX, 14point7, Innovate (through SDK)

  17. #117
    Join Date
    Nov 2007
    Location
    Finland, Europe
    Posts
    530
    My Cars
    E61 520d LCI
    I've got some trace files from finnish guys. MS42, MS43 and MS41 and DME338 (M60B40). Thanks guys!

    I just have to find some time to find out actual values from hex data. Help is appreciated too. Tool32 has window (tabellen-info) which has info on factors. For MS42 they do not seem to exist but looking at MS43 gives good hint.

    To convert from hex to actual value it seems hex byte is first converted to decimal and then multiplied with some factor and then added or substracted with another value. Could try to do some automatic "script" to find out these numbers.
    E61 520d LCI

    Check out TestO - free datalogger for BMW. Includes support for: AEM, PLX, 14point7, Innovate (through SDK)

  18. #118
    Join Date
    Aug 2010
    Location
    Pittsburgh, PA
    Posts
    608
    My Cars
    E36 M3 / 2.0T WRX
    Quote Originally Posted by pheno View Post
    I've got some trace files from finnish guys. MS42, MS43 and MS41 and DME338 (M60B40). Thanks guys!

    I just have to find some time to find out actual values from hex data. Help is appreciated too. Tool32 has window (tabellen-info) which has info on factors. For MS42 they do not seem to exist but looking at MS43 gives good hint.

    To convert from hex to actual value it seems hex byte is first converted to decimal and then multiplied with some factor and then added or substracted with another value. Could try to do some automatic "script" to find out these numbers.
    Awesome! Any chance you can post them here?

    I have some documents that might help in figuring out the conversion factor if we can figure out what hex belongs to what type of data (MAF, RPM, Load, etc.)
    Last edited by mrf; 03-06-2013 at 03:03 PM.

  19. #119
    Join Date
    Nov 2007
    Location
    Finland, Europe
    Posts
    530
    My Cars
    E61 520d LCI
    Quote Originally Posted by mrf View Post
    Awesome! Any chance you can post them here?

    I have some documents that might help in figuring out the conversion factor if we can figure out what hex belongs to what type of data (MAF, RPM, Load, etc.)
    I'd be happy to take a look what you've got. Send me an email maybe ? phenotesto@gmail.com

    I was planning to create a website for this and put all the trace files there. But now that you asked...

    Attached is actually a .ZIP file (rename traces.txt to traces.zip) that holds generated trace files for MS41, MS42 and MS43 as an example. Took me a while to figure out how to code the "trace function" Really nothing magical though. You can see from the files what data is sent and what is received. And the correct values determined by EDIABAS API.

    For MS43 all the info about conversion factors can be found from tool32. This is good news as such. So basically in one request (12 05 0B 03) we get almost 30 values. For MS41 and MS42 there's no such table inside .prg file. But it looks like in the response received in MS41 and MS42 the values are following the order of MS43. I already solved majority of those but apparently lost the document

    My intention is to integrate this serial port based communication into the current Test-o application.

    For diesel owners, at least DDE 4.0 and higher you can find a table in tool32 in the .prg file. So you can choose from the list (BETRIEBSWTAB) what values you want to receive. For example in DDE 5.0 there are almost 200 different values.
    Depending on the DDE the job is called MW_SELECT_LESEN or MW_SELECT_LESEN2. You can already use this feature in Test-o. Just put the arguments separated by space (from right click-> job arguments). Arguments are either plain text or address (0x1234) for example

    If someone is interested to test this feature I could bring the tables into the application so it is easy to choose the values. It would mean we could get like 20 values in one response. But as I do not have a diesel car this is impossible to test by me.

    Here's example screen for DDE 4.0

    Attached Files Attached Files
    Last edited by pheno; 03-07-2013 at 04:44 AM.
    E61 520d LCI

    Check out TestO - free datalogger for BMW. Includes support for: AEM, PLX, 14point7, Innovate (through SDK)

  20. #120
    Join Date
    Aug 2010
    Location
    Pittsburgh, PA
    Posts
    608
    My Cars
    E36 M3 / 2.0T WRX
    pheno, that is fantastic! btw, sent you that email.

    Those trace files really have everything there. Amazing that BMW documented this stuff so well. Now I just need to spend some time with http://translate.google.com/#de/en/

    Also, wish I had a DDE 4.0 or higher ECU! That's some good stuff right there.

    Can you help me understand the trace file? For example the job for 'engine speed' how do parse that into human readable format?
    Code:
    '12.01.2013 20:38:57 <jobstart>'STATUS_MOTORDREHZAHL','_STD     [      1437] SENDECUTEL
    _STD     [      1437]  INPUT: 12 05 0B 03 
    _STD     [      1437]   I -> D: 14 06 00 FF FF 00 
    _STD     [      1437]   D -> I: 01 03 00 
    _STD     [      1437]   I -> D: 13 04 00 01 
    _STD     [      1437]   D -> I: 01 04 00 00 
    _STD     [      1437]   I -> D: 06 07 00 12 05 0B 03 
    _STD     [      1516]   D -> I: 01 20 00 12 1D A0 00 00 00 24 00 00 D3 E0 4F 00 00 24 5C 98 
    _STD                            7C 00 7E 80 00 80 00 06 06 00 00 15 
    _STD     [      1516]   I -> D: 13 04 00 01 
    _STD     [      1516]   D -> I: 01 04 00 00 
    _STD     [      1516]  ERROR: NO ERROR
    _STD     [      1516]  OUTPUT: 12 1D A0 00 00 00 24 00 00 D3 E0 4F 00 00 24 5C 98 7C 00 7E 
    _STD                           80 00 80 00 06 06 00 00 15 '
    12.01.2013 20:38:57 'JOB_STATUS','OKAY','text'
    12.01.2013 20:38:57 'STAT_MOTORDREHZAHL_WERT','0.000000E+000','real'
    12.01.2013 20:38:57 'STATUS_MOTORDREHZAHL_EINH','1/min','text'
    12.01.2013 20:38:57 'STATUS_MOTORDREHZAHL_WERT','0.000000E+000','real'
    12.01.2013 20:38:57 <jobend>
    I understand that we send the ECU "12 05 0B 03" through our laptop's serial port but then how do we parse what we get back? What is "I -> D" and vice versa?

    Does the EDIABAS API document explain all of this? Anyway you can send or post that document to me?

    Also, implementing these serial functions into Testo would be absolutely fantastic.

  21. #121
    Join Date
    May 2005
    Location
    Melb,Australia
    Posts
    579
    My Cars
    3.0 Euro M3, 328is track
    I have an Euro E36 M3 3.0, s50b30, and am happy to get any data u need, i've been using testo alot and am eager for updates

    As you know, INPA does not work with the ecu in the euro m3, so we have no easy way of retrieving the fault codes(without tool32 thatis)

    would love a button that would display all logged faultcodes similar to how tool32 does it and inpa would do it.

    BLAKE AuST
    Last edited by BLAKE AuST; 03-08-2013 at 02:27 AM.

  22. #122
    Join Date
    Nov 2007
    Location
    Finland, Europe
    Posts
    530
    My Cars
    E61 520d LCI
    Quote Originally Posted by BLAKE AuST View Post
    I have an Euro E36 M3 3.0, s50b30, and am happy to get any data u need, i've been using testo alot and am eager for updates

    As you know, INPA does not work with the ecu in the euro m3, so we have no easy way of retrieving the fault codes(without tool32 thatis)

    would love a button that would display all logged faultcodes similar to how tool32 does it and inpa would do it.

    BLAKE AuST
    Happy to hear the program has been useful for you!

    So are you using DM33S501.PRG (DME 3.3 S50 fuer M3 mit EWS) ?

    As for the fault codes. I need to make a few modifications for the current implementation of trace function in order to get info about how to read fault codes for your ecu. Then I'll ask you to take a trace from the debug menu.

    Then I need to analyze the trace and based on that info try to make fault code reading function. So it is very much possible I'll let you know
    E61 520d LCI

    Check out TestO - free datalogger for BMW. Includes support for: AEM, PLX, 14point7, Innovate (through SDK)

  23. #123
    Join Date
    Aug 2010
    Location
    Pittsburgh, PA
    Posts
    608
    My Cars
    E36 M3 / 2.0T WRX
    http://pastie.org/6275149
    Is this a list of jobs the MSS54 ECU can run? Lots of interesting stuff in there.

  24. #124
    Join Date
    Nov 2007
    Location
    Finland, Europe
    Posts
    530
    My Cars
    E61 520d LCI
    It would be nice to get traces for MS41 ECU: MS410DS0, MS410DS2, MS410DS3 then all MS41 variants would be supported. Not sure about mrf's MS41.2 though

    Also more traces from S52, S54 like E39 M5 and E46 M3and also M62 engines would be nice. It takes only about a few minutes and won't do any harm to your car.
    I've already solved most important from MS43, MS42 and MS41 (DS1 variant) and some variant of M62 (ME7.2)

    - - - Updated - - -

    Quote Originally Posted by mrf View Post
    pheno, that is fantastic! btw, sent you that email.

    Those trace files really have everything there. Amazing that BMW documented this stuff so well. Now I just need to spend some time with http://translate.google.com/#de/en/

    Also, wish I had a DDE 4.0 or higher ECU! That's some good stuff right there.

    Can you help me understand the trace file? [/code]
    Look at the OUTPUT line: 12 means ecu index in the K-bus, 1D is message length, A0 means "OK". from byte 3 starts data.

    Between <jobstart> and <jobend> is issued one job from EDIABAS. The trace file generation is done by me. EDIABAS does not have this kind of trace file generation.

    We will get one decoded value from EDIABAS (which means in EDIABAS terms 'job result', for example STATUS_MOTORDREHZAHL_WERT) at the end. And we also get the output that contains (somewhere) this value. As I said before value is decoded by taking a byte and multiplying it with value a then summed by value b. You just have to find out what are the values a and b. EDIABAS and .prg files do not tell you all of the details.
    Last edited by pheno; 03-26-2013 at 05:56 PM.
    E61 520d LCI

    Check out TestO - free datalogger for BMW. Includes support for: AEM, PLX, 14point7, Innovate (through SDK)

  25. #125
    Join Date
    May 2010
    Location
    Sydney,NSW,Australia
    Posts
    17
    My Cars
    316 Compact
    Ediabas has full trace capability, simply edit the ini file, it is quite well done and very useful, I would expect it to assist in what you are doing

Page 5 of 40 FirstFirst 12345678910111213141530 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •