Announcement

Collapse
No announcement yet.

Custom OBD-II Monitoring Screenshots

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Custom OBD-II Monitoring Screenshots

    I recently made some updates to my OBD-II driver for LabVIEW. My driver supports PassThru (J2534-1) vehicle interfaces for all OBD protocols including CAN, J1850, ISO9141, and ISO14230.

    I write a sample program that monitors accelerator pedal position and graphs RPM. Notice how my crappy truck nearly stalled after going WOT:



    It's pretty easy to program LabVIEW. You drag-and-drop icons that represent the various functions. For my 2001 Ranger I select J1850PWM, then connect the icons to read different paramters from the vehicle. Here's the "source code" for the example above:



    I've posted this LabVIEW PassThru (J2534) OBD-II driver free on my company's website. You would also need the LabVIEW software which is pretty expensive, but you might be able to buy a student copy much cheaper if you're at a university?

    I've also written a 0-60 and quarter-mile program. I'm going to write some more CarPC examples, and I'll post screenshots to keep you guys updated.

  • #2
    I have an older version of measurement studio which is basically labview controls for VB/C++ (If you didn't already know that). I had suggested using it since the final app can be redistributed freely (no royalty or runtime required)

    Nice to see a fellow Labview user!
    Status: 40%
    Car: 2006 Scion tC (Buying)
    CPU: AOpen Pandora/1.5 Cel M/1GB DDR2/Ipod Vid
    Screen: Lilliput 7"
    Power: Carnetix 1900
    GPS: Deluo GPS
    Software: nLiteXP, RR, IG, PhoCo
    XM: XM Direct
    http://www.chrispuckett.com/mp3car/

    Comment


    • #3
      We have Labview at work, but my Labview programming skills are next to zero However, from what I have seen, I would agree on Labview being an ideal programming environment for quickly building touchscreen friendly OBD-2 applications.
      CarPC status: HW all done, SW needs tweaked.
      Hardware: VIA MII-12K, 512MB, 60GB 2.5", CW-8123 DVD-CDRW, 7" Lilli ts, Opus 90W, BU-353 GPS, 802.11b PCI, USB bluetooth dongle, AverMedia AverTV Cardbus Plus, Morex Cubid 3677
      Software: RR, MM/FD

      Comment


      • #4
        Originally posted by joeyoravec
        My driver supports PassThru (J2534-1) vehicle interfaces for all OBD protocols including CAN, J1850, ISO9141, and ISO14230.
        Great job! Does your driver support my ELM323 (ISO) based serial interface?

        This may well be the little boost I need to get started on learning Labview!
        CarPC status: HW all done, SW needs tweaked.
        Hardware: VIA MII-12K, 512MB, 60GB 2.5", CW-8123 DVD-CDRW, 7" Lilli ts, Opus 90W, BU-353 GPS, 802.11b PCI, USB bluetooth dongle, AverMedia AverTV Cardbus Plus, Morex Cubid 3677
        Software: RR, MM/FD

        Comment


        • #5
          Its the reason i am learning it.

          Comment


          • #6
            If you happen to be in the Detroit area, I'll be giving a presentation on automotive networks and my LabVIEW driver at the next Detroit LabVIEW users group meeting. The date isn't nailed down yet, but should be around May 2006.

            Hopefully the cops aren't around so we can do some datalogging (ie. burnouts) in the parking lot.

            Comment

            Working...
            X