Page 4 of 6 FirstFirst ... 23456 LastLast
Results 31 to 40 of 53

Thread: MEFI 4 ECM definition file

  1. #31
    Senior Member
    Join Date
    Oct 2005
    Posts
    158

    Default

    Click image for larger version. 

Name:	Tunerpro to EFILive data file.jpg 
Views:	194 
Size:	83.5 KB 
ID:	13833Ok, I am now finally working on building the .xml file. If you guys would be so kind as to take a look at the attached screenshot (example attribute is IAC Base Pos, I have a couple of questions:

    1. What V4 field do I put the hex value of 18 into (0x18)?
    2. What V4 field do I put the hex value of 24 into?

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

    Default

    0x18 hex is 24 decimal, its just the same value represented two different ways.
    The 24 is the position (offset) of the data byte in the data steam packet. That value is called the "Start" value in EFILive, so put 24 in "Start".
    The source data size is the same as EFILive's "Bits" field.

    Note: If you have a 16 bit field, you have to specify the second byte as the start byte in EFILive, I'm not sure if the other package specifies the first byte.
    For example, say the RPM was 16 bits and the two 8 bit bytes took byte positions 14 and 15 in the data stream.
    In EFILive you would need to put 15 as the start byte and 16 as the bit size.
    In the other package, they may specify it as an offset of 14 - just something to watch out for.

    Regards
    Paul
    Before asking for help, please read this.

  3. #33
    Senior Member
    Join Date
    Oct 2005
    Posts
    158

    Default

    Quote Originally Posted by Blacky View Post
    0x18 hex is 24 decimal, its just the same value represented two different ways.
    The 24 is the position (offset) of the data byte in the data steam packet. That value is called the "Start" value in EFILive, so put 24 in "Start".
    The source data size is the same as EFILive's "Bits" field.

    Note: If you have a 16 bit field, you have to specify the second byte as the start byte in EFILive, I'm not sure if the other package specifies the first byte.
    For example, say the RPM was 16 bits and the two 8 bit bytes took byte positions 14 and 15 in the data stream.
    In EFILive you would need to put 15 as the start byte and 16 as the bit size.
    In the other package, they may specify it as an offset of 14 - just something to watch out for.

    Regards
    Paul
    Quote Originally Posted by kangsta View Post
    First step would be to open the ADX in TunerPro and understand how the communications work then translate that info into how EFILive defines the data stream. It should be pretty straigh forward with that ECM. One thing to watch out for is that in the ADX the data item is defined by its starting offset and length (8,16bit). In EFILive its defind by the end offset and the length (8,16bit) so say if RPM was at offset 0x01 and 16bit in the ADX in EFILive it would be 0x03 and 16bit.
    OK, thanks for the tips guys. So just to make sure I understand the offset situation for 16 bit fields, I will use the RPM field which is a 16 bit field. It is 0x26|38, so in EFILive I need to put 39 as the start bit, is that correct?

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

    Default

    If the RPM was defined as 16 bits and taking up byte positions 38 and 39, then in EFILive you have to specify the byte that contains "Bit 0" as the start byte. That means byte 39 is the start byte. See image below.
    Click image for larger version. 

Name:	16bit.png 
Views:	111 
Size:	23.6 KB 
ID:	13839
    The concept is that the bytes in the data stream are numbered left (low) to right (high). However, the bits in each 8-bit BYTE or 16-bit WORD are numbered right (low) to left (high).


    Regards
    Paul
    Before asking for help, please read this.

  5. #35
    Senior Member
    Join Date
    Oct 2005
    Posts
    158

    Default

    OK, still moving through populating all of the data fields. If you guys wouldn't mind taking a look at this example screen shot - have I left anything out that I need to populate in to the EFILive configuration (haven't started working on the dashboard or charts yet, that will come later - is that really required for the .xml file?)?Click image for larger version. 

Name:	Tunerpro to EFILive data file.png 
Views:	258 
Size:	876.7 KB 
ID:	13843

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

    Default

    That looks ok, although you should make the EFILive "Code" field a nicer description than "4". It really should be "RPM" as that is what is displayed on the gauges and in the menus, see image.
    Click image for larger version. 

Name:	captions.png 
Views:	227 
Size:	105.1 KB 
ID:	13844

    The "Chart", "Series" and "Dashboard" values simply tell the other parts of the EFILive software where to display the data. They are automatically set when you select the attribute (i.e. parameter) for display. Each chart and series and each gauge have a unique value associated with them that can be assigned to each attribute to cause that attribute to be displayed at that particular location. (see the documentation: Reference->Requests->Attributes for a list of the values)

    In the screen shot above, the RPM parameter would have its "Dashboard" value set to 9, which is the unique value for the large gauge at the top of the dashboard.

    Regards
    Paul
    Before asking for help, please read this.

  7. #37
    Senior Member
    Join Date
    Oct 2005
    Posts
    158

    Default

    Quote Originally Posted by Blacky View Post
    That looks ok, although you should make the EFILive "Code" field a nicer description than "4". It really should be "RPM" as that is what is displayed on the gauges and in the menus, see image.
    Click image for larger version. 

Name:	captions.png 
Views:	227 
Size:	105.1 KB 
ID:	13844

    The "Chart", "Series" and "Dashboard" values simply tell the other parts of the EFILive software where to display the data. They are automatically set when you select the attribute (i.e. parameter) for display. Each chart and series and each gauge have a unique value associated with them that can be assigned to each attribute to cause that attribute to be displayed at that particular location. (see the documentation: Reference->Requests->Attributes for a list of the values)

    In the screen shot above, the RPM parameter would have its "Dashboard" value set to 9, which is the unique value for the large gauge at the top of the dashboard.

    Regards
    Paul
    OK, thanks for the advice. Somehow I thought the EFILIVE "Code" field corresponded to the Tunerpro "Unique ID" field and that it was something the ECM read uniquely.

    Now, to the 64 dollar question. How do create an external input parameter? The whole intent of this exercise is to use my flashscan blackbox (I have both the early FSP V1.2 and the latest handheld) to get an oxygen sensor input in to the data stream?

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

    Default

    Quote Originally Posted by Extinct View Post
    OK, thanks for the advice. Somehow I thought the EFILIVE "Code" field corresponded to the Tunerpro "Unique ID" field and that it was something the ECM read uniquely.

    Now, to the 64 dollar question. How do create an external input parameter? The whole intent of this exercise is to use my flashscan blackbox (I have both the early FSP V1.2 and the latest handheld) to get an oxygen sensor input in to the data stream?
    Right now it is not possible to log ALDL data streams with FlashScan V1 or V2. That will be available once the V8 Scan Tool software is released for FlashScan V2.

    Regards
    Paul
    Before asking for help, please read this.

  9. #39
    Senior Member
    Join Date
    Oct 2005
    Posts
    158

    Default

    Quote Originally Posted by Blacky View Post
    Right now it is not possible to log ALDL data streams with FlashScan V1 or V2. That will be available once the V8 Scan Tool software is released for FlashScan V2.

    Regards
    Paul
    Wow, major bummer. I'm sure there is a thread with a hundred people bugging you about when that will be. So I take it the ALDL data stream is significantly different than the later models? So to use the V4 to log data I guess a different cable is required?

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

    Default

    Quote Originally Posted by Extinct View Post
    Wow, major bummer. I'm sure there is a thread with a hundred people bugging you about when that will be. So I take it the ALDL data stream is significantly different than the later models? So to use the V4 to log data I guess a different cable is required?
    Yes a different cable is required but you can make an RS232-ALDL cable yourself for around $10 in parts if you have a real serial port on you laptop or you can purchase an ALDL-USB cable for around $80-$100 from various places on the net.

    Reagrds
    Paul
    Before asking for help, please read this.

Page 4 of 6 FirstFirst ... 23456 LastLast

Similar Threads

  1. Need definition for 16197427
    By serial_killer in forum EFILive V4
    Replies: 3
    Last Post: October 7th, 2009, 07:59 AM
  2. DSP Output definition
    By killerbee in forum General (Diesel)
    Replies: 6
    Last Post: July 5th, 2009, 02:12 PM
  3. Mercruiser MEFI ECM's (MEFI-3 in particular)
    By MichaelsTractors in forum General (Petrol, Gas, Ethanol)
    Replies: 0
    Last Post: January 24th, 2008, 05:37 PM
  4. Custom/DIY calibration definition file?
    By jimter in forum General (Diesel)
    Replies: 5
    Last Post: October 10th, 2007, 08:25 AM
  5. MEFI Controller
    By Fran D in forum General (Petrol, Gas, Ethanol)
    Replies: 4
    Last Post: August 18th, 2006, 12:54 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
  •