Results 1 to 9 of 9

Thread: OBD-II for BR-3 ActiveX (and code)

  1. #1
    Newbie
    Join Date
    Jan 2005
    Posts
    22

    OBD-II for BR-3 ActiveX (and code)

    Thought i should make a new tread as the old 'Skinnable OBD II Software' one is a little long and out dated. I stopped coding, and released partial code. I am a little short on time for the next few months. read the release 'readme' if you want to attempt to use what I have released.

    SourceForge: http://sourceforge.net/projects/br3-obd2/
    ETA: Unknown
    Status: Stopped Coding for a while.
    Code Sections:
    Find BR3: Done (Test did not go right)
    Determine Protocol: Done (Ford confirmed others untested, Read a couple posts down)
    Send OBDII Requests: Done
    Recieve OBDII Response: Done
    Proccess OBDII Data: Done
    ActiveX: Haven't Started Yet
    GUI/Skin stuff: Currently Working On
    Trouble Code Lookup Tables: Done
    Extended OBD Data Support: Will be partially supported (You must supply the PIDs, unless someone can give me a list of them)

    This project will be a working example and activex.
    If someone can provide me with a layout for a skin (gauge locations etc.) I will make it skinnable too.

    Any other suggestions or add-ons any one wants?

  2. #2
    Newbie
    Join Date
    Aug 2006
    Posts
    19
    Are you hooking up with this dude?

    Quote Originally Posted by joeyoravec View Post
    I've mentioned my offer in another thread, but it should like I should mention it again here.

    My company designs and manufactures the Mongoose ISO/CAN PassThru vehicle interface. I've offered hardware, sample code, and full support to anybody interested in developing software. All you'd have to do is create a graphical plug-in; the rest is (mostly) already available.

    So if somebody is interested in making that for FrodoPlayer, the heavy-lifting for OBD-II is already done and available. You'd just have to make a graphical frontend or any plug-in code to make it work with FrodoPlayer.

  3. #3
    Confusion Master
    Auto Apps:loading...
    Enforcer's Avatar
    Join Date
    Sep 2003
    Location
    If you go down to the woods today, You're sure of
    Posts
    14,061
    Quote Originally Posted by maxer6 View Post

    One difference, mine will most likely be a working example or an activex, as I don't know how to make skinnable apps (maybe someone else can put my activex in a skinnable form, or send me a skinnable vb project I can look at).

    Take a look at the RoadRunner source code, Guino also provides an SDK to make plugins for Road Runner, which can also run standalone with other apps.

  4. #4
    Newbie
    Join Date
    Jan 2005
    Posts
    22
    Draxx: The Mongoose interfaces currently don't support ford (my parts truck). also the reason many of the people on the other tread wanted the br-3 was because it was cheap ($38-$96) and once one person saw it the reast kinda jumped on the bandwagon. If they had it for ford and I knew about it before I sold my mustang (the car with the carpc); I probably would have gotten it instead (since it included code). so, no I'm going to stick with the br-3, and work on it by my self. (I did find a nice pdf on that site that has a tutorial on 'C', now I can learn that too, thanks).

    Enforcer: The RoadRunner looks like it might be helpful in making the skinnable part, I will look at it (I just downloaded binary and source for it) when I get to that point.

  5. #5
    Constant Bitrate joeyoravec's Avatar
    Join Date
    Oct 2005
    Location
    Livonia, MI
    Posts
    202
    Mongoose Ford comes out at the end of this month. All you had to do is ask.

  6. #6
    Newbie
    Join Date
    Jan 2005
    Posts
    22
    I need a little help from some one who's car supports one of the following OBDII protocols:
    VPW (GM)
    ISO-9141 (Asian)
    ISO-14230
    ISO-14230 Fast Init

    I need to find out how to initilize the interface for these protocols. If you have one of these please follow the following instructions and get back to me. I would prefer if you use Diagnose 3.2 but 4.0 might work.

    1) Download Portmon (http://www.sysinternals.com/Utilities/Portmon.html) this will log all serial communications with the device.
    2) Make sure 'Diagnose' is not running, untill I tell you to. Open Portmon.
    3) In Portmon under the 'Capture' -> 'Ports' place a check next to all the com ports.
    4) In Portmon under the 'Edit' open 'Filter/Highlight' and enter 'IRP_MJ_WRITE;IRP_MJ_READ' (no quotes) in the 'Include' box.
    5) In Portmon under 'Capture' place a check next to 'Capture Events'.
    6) Launch 'Diagnose'.
    7) Click 'Start' button in 'Diagnose'.
    8) Click 'Automatic Protocol' Button.
    9) After 'Diagnose' finds and loads everything DON'T do anything in 'Diagnose' (no checking sensors and stuff).
    10) Go to Portmon and wait for the window to stop scrolling (or 3 minutes which ever comes first).
    11) Uncheck 'Capture Events' under 'Capture' menu.
    12) 'File' 'Save As' and send me the file.
    13) If you are feeling very generous (and have time) rerun steps 5-12 a little differently as mentioned below.

    13*1) In Portmon 'Edit' -> 'Clear Display'
    13*2) Redo steps 5-12 selecting the protocol manualy (not step 8).

    Please include:
    The Version of Diagnose
    The Protocol that was used
    The Make/Model of car

    As I only have an old Ford F-150 I have no way of testing the other protocols besides bugging the neighbors. So if you want this to support other vehicles I will need informatio on the initilization. Thanks in advance!

  7. #7
    Newbie
    Join Date
    Jan 2005
    Posts
    22
    Quote Originally Posted by joeyoravec View Post
    Mongoose Ford comes out at the end of this month. All you had to do is ask.
    The way the the whole OBDII thing works (as I understand) looks pretty simular interface to interface, so If you want to give a code example I might be able to build support for multiple interfaces into this one activex. as for making a front end for anything, I make some of the uglyest programs in existance so I would rather stick to the code, and let someone else make the front ends. or else if someone makes an image of a front end I can put code behind it. Maybe frodo might take the activex and put it in frodoplayer (less work for him).

    The interface does sound nice though, but I really have no real need for one any more, no computer or ECU in my camaro.

  8. #8
    Low Bitrate Zharvek's Avatar
    Join Date
    Jan 2005
    Posts
    71
    I know this is an old thread, but I would like to add to it.

    I have started to work on a small project using VB6 that communicates with the BR-3 unit, and can pull data into your programs.

    I have this working on my 2004 Grand Prix GTP thus far, and would like to test later on with other vehicles.

    I will post a simple sample application soon as I can make sure it is working, just wanted to let some others know, incase they want something like this.

  9. #9
    Low Bitrate
    Join Date
    Jun 2007
    Posts
    76
    Quote Originally Posted by Zharvek View Post
    I know this is an old thread, but I would like to add to it.

    I have started to work on a small project using VB6 that communicates with the BR-3 unit, and can pull data into your programs.

    I have this working on my 2004 Grand Prix GTP thus far, and would like to test later on with other vehicles.

    I will post a simple sample application soon as I can make sure it is working, just wanted to let some others know, incase they want something like this.
    I am currently also starting a VB6 project for my ELM327 device

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
  •