Results 1 to 4 of 4

Thread: No Spk Adv in gmh-vn68vp68.xml

  1. #1
    Lifetime Member limited cv8r's Avatar
    Join Date
    May 2005
    Posts
    568

    Default No Spk Adv in gmh-vn68vp68.xml

    As title says. Should or could it be in the xml?
    It's all good until it goes "Bang"

  2. #2
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,119

    Default

    Quote Originally Posted by limited cv8r View Post
    As title says. Should or could it be in the xml?
    The VN/VP PCM's data stream is very, very basic (and slow at 160 baud). It only contains the PIDs that are defined for it - as far as I can tell.

    Regards
    Paul
    Before asking for help, please read this.

  3. #3
    Lifetime Member limited cv8r's Avatar
    Join Date
    May 2005
    Posts
    568

    Default

    Here is a screenshot from tunerpro supposedly showing a spark pid. Can the pid data/offsets etc be entered into V4 to see if it works and what would need to be entered into the software?
    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	spark.JPG 
Views:	65 
Size:	178.9 KB 
ID:	17227  
    It's all good until it goes "Bang"

  4. #4
    EFILive Developer Site Admin Blacky's Avatar
    Join Date
    Mar 2003
    Posts
    9,119

    Default

    The offset for the spark advance defined by that app is byte 32. The size of each frame returned by the VN/VP controller is only 20 bytes long. So no PIDs can be defined after byte number 20.

    That is unless I got it wrong and the frame is longer than 20 bytes. To check that, turn on display serial I/O (View->Serial I/O) and then click the "Display ALDL Chatter (Ctrl+L)" toolbar icon. However, I'm not 100% sure if that works for 160 baud controllers or not and I don't have a spare VN/VP controller lying around to test it on.
    Anyway if that does show the raw data frames, can you post up that text data and I'll see if it really doe shave more than 20 bytes per frame.

    If it does you'd need to change the "Frame Length" setting in the "Dummy Request" entry in the vehicle definition to match the actual frame length. Then you can add in the spark PID at offset 32 - assuming the actual frame length is at least 32 bytes long

    Regards
    Paul
    Before asking for help, please read this.

Similar Threads

  1. E39 GMH 3.0 SIDI: 91 vs 98 Octane
    By swingtan in forum E39, E80, E82 & E92 SIDI ECM's
    Replies: 49
    Last Post: October 21st, 2015, 09:33 PM
  2. GMH V6 communication problem
    By davewanna in forum EFILive V4
    Replies: 16
    Last Post: April 11th, 2013, 08:58 AM
  3. Replies: 6
    Last Post: March 26th, 2011, 03:58 PM
  4. Why is there no 3.1L XML
    By JThein1989 in forum EFILive V4
    Replies: 1
    Last Post: April 30th, 2010, 06:44 PM
  5. Replies: 19
    Last Post: January 29th, 2009, 08:11 PM

Posting Permissions

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