Testing FreeDiag

Help
gegi
2011-08-06
2013-04-24
  • gegi

    gegi - 2011-08-06

    I've just compiled freediag under linux. But when i tested in my car I cant make it work :(

    Im using this interface:
    http://www.dealextreme.com/p/obdii-v600-usb-car-diagnostic-cable-for-vw-audi-skoda-37633

    Witch is compatible with ISO9141 protocol but nothing.

    Any ideas?? The interface works fine with vag-com

    I've tryed setting every interface

    some of my output:
    Trying ISO9141:
    diag_tty.c:562: Read/Write timeout.
    diag_tty.c:562: Read/Write timeout.
    diag_tty.c:562: Read/Write timeout.
    diag_tty.c:562: Read/Write timeout.
    diag_l0_vw.c:334: Read/Write timeout.
    diag_l0_vw.c:391: Read/Write timeout.
    ISO9141 Failed!

     
  • CSB

    CSB - 2011-08-06

    2.6 kernels manage timing differently; a patch was submitted a while ago to address this ( https://sourceforge.net/tracker/?func=detail&aid=1695875&group_id=34714&atid=412183 ). I'm currently working on applying that patch to the current code; I should be finished in a day or two. Don't expect a miracle though, dumb interfaces are extremely difficult to get working…

    Could you try running the following commands in freediag, and pasting the output:
    > debug all -1
    > diag connect

     
  • gegi

    gegi - 2011-08-07

    Her you go: :)

    scantool> debug all -1
    Debug values: L0 0xffffffff, L1 0xffffffff, L2 0xffffffff L3 0xffffffff CLI 0xffffffff

    scantool> diag connect
    diag_l2.c:346:  diag_l2_open SE9141 subinterface /dev/ttyUSB0 L1proto 1 called
    diag_l2.c:307:  diag_l2_closelink 0x2312600 called
    diag_l0_se.c:154:  link 0x2312780 closing
    diag_l0_se.c:113:  open subinterface /dev/ttyUSB0 protocol 1
    diag_tty.c:133:  Device /dev/ttyUSB0 opened, fd 3
    diag_tty.c:499:  1312737311.381413 : DTR/RTS changed
    diag_tty.c:562: Read/Write timeout.
    diag_l2.c:440:  diag_l2_startCommunications dl0d 0x2312780 L2proto 1 type 9 baud 10400 target 0x33 src 0xf1 called
    diag_l2_iso9141.c:205:  diag_l2_iso9141_startcomms conn 0x2312a20
    diag_tty.c:266:  setup: device fd 3 dt 0x2312900 speed 10400 databits 8 stopbits 1 parity 3
    diag_tty.c:562: Read/Write timeout.
    diag_l2.c:707:  diag_l2_ioctl 0x2312a20 cmd 8705
    diag_l0_se.c:298:  device link 0x2312780 info 0x23127c0 initbus type 2
    diag_tty.c:562: Read/Write timeout.
    diag_l0_se.c:209:  slowinit link 0x2312780 address 0x33
    diag_tty.c:266:  setup: device fd 3 dt 0x2312900 speed 5 databits 8 stopbits 1 parity 3
    diag_tty.c:266:  setup: device fd 3 dt 0x2312900 speed 10400 databits 8 stopbits 1 parity 3
    diag_tty.c:562: Read/Write timeout.
    diag_l0_se.c:278:  slowinit link 0x2312780 read timeout
    diag_l0_se.c:279: Read/Write timeout.
    diag_tty.c:266:  setup: device fd 3 dt 0x2312900 speed 10400 databits 8 stopbits 1 parity 3
    diag_l0_se.c:331:  initbus device link 0x2312780 returning -8
    diag_l2_iso9141.c:241:  diag_l2_iso9141_startcomms returns -8
    diag_l2.c:528:  protocol startcomms returned -8
    diag_l2.c:560:  diag_l2_StartComms returns (nil)
    diag_l2.c:413:  diag_l2_close 0x2312780 called
    scantool.c:928: Initbus type not supported by H/W.

    Connection to ECU failed
    Please check :-
    Adapter is connected to PC
    Cable is connected to Vehicle
    Vehicle is switched on

     
  • CSB

    CSB - 2011-08-07

    Hi,
    could you try again with the newest code in CVS ? I committed a lot of changes yesterday. Also, please also try the DUMB interface, I'm merging VAGTOOL + SE9141 as a single interface since they are almost identical.

     
  • gegi

    gegi - 2011-08-09

    SE9141 interface:
    scantool> debug all -1
    Debug values: L0 0xffffffff, L1 0xffffffff, L2 0xffffffff L3 0xffffffff CLI 0xffffffff
    scantool> diag connect
    diag_l2.c:346:  diag_l2_open SE9141 subinterface /dev/ttyUSB0 L1proto 1 called
    diag_l2.c:307:  diag_l2_closelink 0xa8a600 called
    diag_l0_se.c:154:  link 0xa8a760 closing
    diag_l0_se.c:113:  open subinterface /dev/ttyUSB0 protocol 1
    diag_tty.c:136:  Device /dev/ttyUSB0 opened, fd 3
    diag_tty.c:502:  1312895670.686192 : DTR/RTS changed
    diag_tty.c:613:  Entered diag_tty_read with count=1024, timeout=150ms
    diag_tty.c:665:  timed out: 300ms
    diag_l2.c:440:  diag_l2_startCommunications dl0d 0xa8a760 L2proto 1 type 9 baud 10400 target 0x33 src 0xf1 called
    diag_l2_iso9141.c:205:  diag_l2_iso9141_startcomms conn 0xa8a8e0
    diag_tty.c:269:  setup: device fd 3 dt 0xa8a7a0 speed 10400 databits 8 stopbits 1 parity 3
    diag_tty.c:613:  Entered diag_tty_read with count=1024, timeout=150ms
    diag_tty.c:665:  timed out: 300ms
    diag_l2.c:708:  diag_l2_ioctl 0xa8a8e0 cmd 8705
    diag_l0_se.c:298:  device link 0xa8a760 info 0xa8a8c0 initbus type 2
    diag_tty.c:613:  Entered diag_tty_read with count=1024, timeout=150ms
    diag_tty.c:665:  timed out: 300ms
    diag_l0_se.c:209:  slowinit link 0xa8a760 address 0x33
    diag_tty.c:269:  setup: device fd 3 dt 0xa8a7a0 speed 5 databits 8 stopbits 1 parity 3
    diag_tty.c:613:  Entered diag_tty_read with count=1, timeout=2750ms
    diag_tty.c:269:  setup: device fd 3 dt 0xa8a7a0 speed 10400 databits 8 stopbits 1 parity 3
    diag_tty.c:613:  Entered diag_tty_read with count=1, timeout=750ms
    diag_tty.c:665:  timed out: 1500ms
    diag_l0_se.c:278:  slowinit link 0xa8a760 read timeout
    diag_l0_se.c:279: Read/Write timeout.
    diag_tty.c:269:  setup: device fd 3 dt 0xa8a7a0 speed 10400 databits 8 stopbits 1 parity 3
    diag_l0_se.c:331:  initbus device link 0xa8a760 returning -8
    diag_l2_iso9141.c:244: Read/Write timeout.
    diag_l2.c:536: Read/Write timeout.
    diag_l2.c:413:  diag_l2_close 0xa8a760 called
    scantool.c:930: Initbus type not supported by H/W.

    Connection to ECU failed
    Please check :-
    Adapter is connected to PC
    Cable is connected to Vehicle
    Vehicle is switched on

    DUMB interface:
    scantool> debug all -1
    Debug values: L0 0xffffffff, L1 0xffffffff, L2 0xffffffff L3 0xffffffff CLI 0xffffffff
    scantool> diag connect
    diag_l0_sim.c:206:   0 responses freed from queue.
    diag_l2.c:282:  diag_l2_init called
    diag_l2.c:346:  diag_l2_open DUMB subinterface /dev/ttyUSB0 L1proto 1 called
    diag_l0_dumb.c:95:  open subinterface /dev/ttyUSB0 protocol 1
    diag_tty.c:136:  Device /dev/ttyUSB0 opened, fd 3
    diag_tty.c:502:  1312895795.549146 : DTR/RTS changed
    diag_tty.c:613:  Entered diag_tty_read with count=1024, timeout=150ms
    diag_tty.c:665:  timed out: 300ms
    diag_l2.c:440:  diag_l2_startCommunications dl0d 0x121e760 L2proto 1 type 9 baud 10400 target 0x33 src 0xf1 called
    diag_l2_iso9141.c:205:  diag_l2_iso9141_startcomms conn 0x121e8e0
    diag_tty.c:269:  setup: device fd 3 dt 0x121e7a0 speed 10400 databits 8 stopbits 1 parity 3
    diag_tty.c:613:  Entered diag_tty_read with count=1024, timeout=150ms
    diag_tty.c:665:  timed out: 300ms
    diag_l2.c:708:  diag_l2_ioctl 0x121e8e0 cmd 8705
    diag_l0_dumb.c:359:  device link 0x121e760 info 0x121e740 initbus type 2
    diag_tty.c:613:  Entered diag_tty_read with count=1024, timeout=150ms
    diag_tty.c:665:  timed out: 300ms
    diag_l0_dumb.c:260:  slowinit link 0x121e760 address 0x33
    diag_tty.c:269:  setup: device fd 3 dt 0x121e7a0 speed 5 databits 8 stopbits 1 parity 3
    diag_tty.c:613:  Entered diag_tty_read with count=1, timeout=2400ms
    diag_l0_dumb.c:314:  slowinit 5bps address echo 0x1
    diag_tty.c:269:  setup: device fd 3 dt 0x121e7a0 speed 10400 databits 8 stopbits 1 parity 3
    diag_tty.c:613:  Entered diag_tty_read with count=1, timeout=400ms
    diag_tty.c:665:  timed out: 800ms
    diag_l0_dumb.c:334:  slowinit link 0x121e760 read timeout
    diag_l0_dumb.c:335: Read/Write timeout.
    diag_tty.c:269:  setup: device fd 3 dt 0x121e7a0 speed 10400 databits 8 stopbits 1 parity 3
    diag_l0_dumb.c:390:  initbus device link 0x121e760 returning -8
    diag_l2_iso9141.c:244: Read/Write timeout.
    diag_l2.c:536: Read/Write timeout.
    diag_l2.c:413:  diag_l2_close 0x121e760 called
    scantool.c:930: Read/Write timeout.

    Connection to ECU failed
    Please check :-
    Adapter is connected to PC
    Cable is connected to Vehicle
    Vehicle is switched on

     
  • CSB

    CSB - 2011-08-09

    Unfortunately not much I can do… getting a dumb interface to work under linux and through a USB-serial adapter isn't going to be easy. That is, unless you have a way to monitor the actual data with an oscilloscope, logic analyzer, or even a soundcard analyzer. If you don't want to get that involved, you can try later with another version of the source code; I'm still changing / fixing a few things in the near future.

     
  • gegi

    gegi - 2011-08-10

    Ok thanks, Im going for a "smart" interface instead. I might do the logic interface project later if i can find the time for it :)

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks