Page 1 of 2 12 LastLast
Results 1 to 20 of 32

Thread: Standalone datalogging with Openport 2.0

  1. #1
    AderC's Avatar

    Offline
     
    Name
    Adrian
    Join Date
    Jun 2005
    Last Online
    22-09-2023
    Posts
    556
    Country
    United Kingdom
    Location
    Widnes UK
    Car
    2021 Mazda CX30
     

    Standalone datalogging with Openport 2.0

    Has anyone else tried out the standalone logging function of the Openport 2.0 cable? The beta version of ECUFlash updates the firmware to support logging to an SD card in the slot on the Openport unit, without the need for a laptop to be connected during logging.

    All seems to work fine, although there's something odd going on with the coolant temp logging - it decreases with time?!

    aDe

  2. #2
    Nutter_John's Avatar

    Offline
     
    Name
    John
    Join Date
    Sep 2005
    Last Online
    Membership ID
    269
    Posts
    11,656
    Country
    United Kingdom
    Location
    Luton
    Car
    FL Galant VR4
    My Garage
    Visit
     
    ooo thats good to know , I have yet to try the beta version but have been waiting for the datalogging for ages cos it could help diag so many issues

  3. #3
    AderC's Avatar

    Offline
     
    Name
    Adrian
    Join Date
    Jun 2005
    Last Online
    22-09-2023
    Posts
    556
    Country
    United Kingdom
    Location
    Widnes UK
    Car
    2021 Mazda CX30
     
    I've a modified config file (see attachment) that logs the AFRMAP and 2-Byte Load correctly - the example config file provided with ECUFlash beta doesn't.
    Attached Files Attached Files

  4. #4
    Kenneth's Avatar

    Offline
     
    Name
    Kenneth
    Join Date
    Nov 2004
    Last Online
    12-01-2024
    Membership ID
    NZ002
    Posts
    6,968
    Country
    New Zealand
    Location
    Cambridge
    Car
    Kia Sorento :P
    My Garage
    Visit
     
    Thanks for your work AderC. If I had found this post earlier, I probably would have saved some time... Rep given.


    Some additional info for logging parameters and some efficiency increases in calculations. Some of the calculations are a bit inefficient. I'll update if Jo (resident math guru!) gets back to me on a more efficient way to do them.


    In the following case there is some accuracy lost as 1/1.8 seems to be 0.55 recurring, however I don't see that more than 2 decimal places of temperature is going to make any significant difference. If you want more, just add more 5s in there!

    paramname = AirTemp(F)
    paramid = 0x3A
    scalingrpn = x,32,-,0.55556,*


    It appears that the formula is incorrect to begin with though, see 2 posts down.


    Coolant temp appears to be somthing like the following. I'll have to get my temperature probe out to actually check it though.
    NOTE: see two posts down, this is definitely incorrect

    paramname = CoolantTemp(C)
    paramid = 0x07
    scalingrpn = 128,x,-
    To get Degrees F 128,x,-,1.8,*,32,+ should do it. Again, I would be tempted to just use a spreadsheet to do this.


    Additionally, AFRMap can be simplifed to

    paramname = AFRMap
    paramid = 0x32
    scalingrpn = 1881.6,x,/
    Last edited by Kenneth; 06-06-2010 at 02:23 AM.

  5. #5
    Kenneth's Avatar

    Offline
     
    Name
    Kenneth
    Join Date
    Nov 2004
    Last Online
    12-01-2024
    Membership ID
    NZ002
    Posts
    6,968
    Country
    New Zealand
    Location
    Cambridge
    Car
    Kia Sorento :P
    My Garage
    Visit
     

    paramname = AirTemp(C)
    paramid = 0x3A
    scalingrpn = x,89.599,-,0.3068,*


    New formula for air temp in degrees C. Provided kindly by Dr Joanne

  6. #6
    Kenneth's Avatar

    Offline
     
    Name
    Kenneth
    Join Date
    Nov 2004
    Last Online
    12-01-2024
    Membership ID
    NZ002
    Posts
    6,968
    Country
    New Zealand
    Location
    Cambridge
    Car
    Kia Sorento :P
    My Garage
    Visit
     
    hmmm, no the coolant temp is out. From cold it started at -10 Looks closer when warmed up... I looked for my multimeter temperature probe, but I appear to have packed it already for moving.

    Air temp does not look right. it is too low to start with, then climbs quite high under load. IIRC the air temp sensor is in the MAF, so unless this temp is derived from load as well, then surely it cannot be right.

    The AFRMap looks good and is what would be expected from the High Octane fuel map and the reported RPM and Load

  7. #7

    Offline
     
    Name
    Rob
    Join Date
    Jan 2009
    Last Online
    17-02-2024
    Posts
    29
    Country
    Australia
    Location
    Adelaide
    Car
    2001 VR4 Legnum
     
    Does anyone have the formula for Load Calc to add to the config file?

  8. #8
    Kenneth's Avatar

    Offline
     
    Name
    Kenneth
    Join Date
    Nov 2004
    Last Online
    12-01-2024
    Membership ID
    NZ002
    Posts
    6,968
    Country
    New Zealand
    Location
    Cambridge
    Car
    Kia Sorento :P
    My Garage
    Visit
     
    ECU load in the logcfg file attached by Aderc.

    You would be advised to do the 2 byte mod and use that (it is also defined in the logcfg.txt file attached by AderC)

  9. #9

    Offline
     
    Name
    Rob
    Join Date
    Jan 2009
    Last Online
    17-02-2024
    Posts
    29
    Country
    Australia
    Location
    Adelaide
    Car
    2001 VR4 Legnum
     
    Thanks for that

  10. #10

    Offline
     
    Name
    Rob
    Join Date
    Jan 2009
    Last Online
    17-02-2024
    Posts
    29
    Country
    Australia
    Location
    Adelaide
    Car
    2001 VR4 Legnum
     
    Been searching through threads at openecu to try and find a correct formula for air temp and coolant temp, but so far I have found nothing that seems to work. Has anyone had any success yet?

  11. #11
    Hotwire's Avatar

    Offline
     
    Name
    Lee
    Join Date
    Dec 2007
    Last Online
    25-04-2023
    Posts
    161
    Country
    Australia
    Location
    Adelaide, South
    Car
    98 Facelift Leg
     
    Rob,
    I've been playing with OP2 logging for my MAP sensor, and i seem to be finding it doesnt like a complex formula. I suggest just log each with the scaling = x then convert this value in the log/spreadsheet after. simply add in a column and apply the formula's as you'll find them in evoscan.
    that being said, being JDM car, I'm pretty sure each are just in ºc when logging x anyway (dont have evoscan on this computer to check)
    But give that a go
    edit yes the metric definition is simply x

    As for my topic, I have the MAP wired into the rear O2 circuit, and the forumula i use in evoscan is x*0.25 - 21.25
    However, when I log address 0x3C and try scale it with that formula, the op2 has a hissy fitt as soon as i touch the throttle and wont log any more. so I removed teh formula and it logs fine :S Anyone got any ideas why?
    1998 Legnum VR4
    Facelift, Trigger Mauve, 5sp Auto, Momo, Recaro's, Lowered, Brembos, Rays Gram Lights 57Fs, Exhaust, IC Hard Piping

  12. #12
    Hotwire's Avatar

    Offline
     
    Name
    Lee
    Join Date
    Dec 2007
    Last Online
    25-04-2023
    Posts
    161
    Country
    Australia
    Location
    Adelaide, South
    Car
    98 Facelift Leg
     
    oh and if you want to use that tool for tracking knock, simply change the header to be Load Calc instead of Load2Byte - it will log 2byte load but give that program the impression its the calculated load much more accurate like Kenneth hinted.

  13. #13

    Offline
     
    Name
    Rob
    Join Date
    Jan 2009
    Last Online
    17-02-2024
    Posts
    29
    Country
    Australia
    Location
    Adelaide
    Car
    2001 VR4 Legnum
     
    Cheers Lee, I will give it a go when I get back from Perth in 2 weeks.

  14. #14
    Hotwire's Avatar

    Offline
     
    Name
    Lee
    Join Date
    Dec 2007
    Last Online
    25-04-2023
    Posts
    161
    Country
    Australia
    Location
    Adelaide, South
    Car
    98 Facelift Leg
     
    Has anyone else had issues with the OP2 not logging properly? i.e. it wont begin to log, and then when it does it will only log for 10-20 seconds then stop again?

    Its been giving me the ****s... I thought it may have been due to complex formulas causing speed issues, but I have removed all scalings and it seems to still do it. I have also ordered the parameters to be logged in order (i.e. MUt2 0x00 first, 0x1's then 0x2s etc) which seems to have helped but I still have instances where it will just randomly stop logging.

    Finally, the coolant temp is very odd. It is the same address as evoscan (0x07) BUT when logging the raw value only (x) it begins high and reduces. This is simply incorrect as logging only x via EVOScan you get 100% true temp readings by logging only x so it leads me to think there is something not quite programmed correctly with the OP2 MUTII logging - i.e. it is looking at incorrect addresses. Comments Kenneth or AderC?

  15. #15
    Kenneth's Avatar

    Offline
     
    Name
    Kenneth
    Join Date
    Nov 2004
    Last Online
    12-01-2024
    Membership ID
    NZ002
    Posts
    6,968
    Country
    New Zealand
    Location
    Cambridge
    Car
    Kia Sorento :P
    My Garage
    Visit
     
    Not had any problems with logging myself.

    How many parameters are you trying to log?
    What is your start/stop condition?
    How much space is left on your SD card?

    I didn't have much luck getting good data out of the temperatures... I left it at that as I didn't have time to fiddle around. Sorry I couldn't be more help.

  16. #16
    Hotwire's Avatar

    Offline
     
    Name
    Lee
    Join Date
    Dec 2007
    Last Online
    25-04-2023
    Posts
    161
    Country
    Australia
    Location
    Adelaide, South
    Car
    98 Facelift Leg
     
    I'm only logging 8 parameters to try and get reasonable resolution - below is my logcfg.txt file.
    I found that if I plug in the OP2 before starting the engine, and then start it wont start logging. but if I then remove the OP2, and plug back in it may or may not start... last 3 times this method has worked, BUT still a bit hit and miss....

    EDIT oh and 2MB used of 1GB SD card. Also used 2MB of 64MB SD card.... 1GB card seems to give less errors....

    type=mut2

    setpinvoltage=1,-2

    paramname=LoadMUT2Byte
    paramid=0x00
    databits=16
    scalingrpn=x,0.3125,*

    paramname=TimingAdv
    paramid=0x06
    scalingrpn=x,20,-

    paramname=TPS
    paramid=0x17
    scalingrpn=x,0.392157,*

    paramname=RPM
    paramid=0x21
    scalingrpn=x,31.25,*

    paramname=KnockSum
    paramid=0x26

    paramname=OCTNumber
    paramid=0x27
    scalingrpn=x,0.392157,*

    paramname=Man_PSi
    paramid=0x3C
    databits=8
    scalingrpn=x,0.25,*,21.25,-

    paramname=WGDC
    paramid=0x86
    scalingrpn=x,0.5,*

    ;-------------triggers---------------

    ; only log when the engine is running

    conditionrpn = RPM,0,>
    action = start

    conditionrpn = RPM,0,==
    action = stop


  17. #17
    Kenneth's Avatar

    Offline
     
    Name
    Kenneth
    Join Date
    Nov 2004
    Last Online
    12-01-2024
    Membership ID
    NZ002
    Posts
    6,968
    Country
    New Zealand
    Location
    Cambridge
    Car
    Kia Sorento :P
    My Garage
    Visit
     
    Looks pretty stardard and there is no way you are logging too many parameters.

    hmm, I wonder if it is OP2 or if it could be something to do with the ECU not being in diagnostic mode or not sending the data? No data = no logging. Try manually grounding pin 1 and seeing if that makes any difference.

    think I just left mine permanently grounded...

  18. #18

    Offline
     
    Name
    Rob
    Join Date
    Jan 2009
    Last Online
    17-02-2024
    Posts
    29
    Country
    Australia
    Location
    Adelaide
    Car
    2001 VR4 Legnum
     
    Finally got around to tyring to work out IAT and coolant temp logging, and after talking to steve knight about locations and formula's, this appears to work (only logged when hot today)

    paramname=CoolantTemp
    paramid=0x10
    scalingrpn=x,40,-

    paramname=AirTemp
    paramid=0x11
    scalingrpn=x,40,-

    The data logged is about 5 degrees out from evoscan's coolant temp (request 07) and air temp (request 3a) figures, but the same as their coolant temp scaled (request 10) and MAF air temp scaled (request 11).

    Does anyone know why the two different values in Evoscan?

  19. #19
    ersanalamin's Avatar

    Offline
     
    Name
    Ersan
    Join Date
    Mar 2005
    Last Online
    21-01-2024
    Posts
    754
    Country
    Other
    Location
    Jakarta
    Car
    EC5A
     
    Hi guys, could you please share the newest version of logcfg.txt file? I try to log without laptop using the given text file from Ecuflash directory, but nothing happen. what should I do to make it work?
    Last edited by ersanalamin; 18-06-2014 at 03:21 PM.

  20. #20
    Davezj's Avatar

    Offline
     
    Name
    Dave
    Join Date
    Jan 2006
    Last Online
    09-01-2024
    Membership ID
    255
    Posts
    16,245
    Country
    England
    Location
    Manchester
    Car
    VR-4
    My Garage
    Visit
     
    i presume the MicroSD card has to be pre formated to either FAT32 or NTFS but i don't know which. but one will probably not work.

    it is only a thought.

    i have not tryed this yet but it is something i have been meaning to do for ages.
    just to set it up to log when the knock is above 2 counts say.
    Last edited by Davezj; 18-06-2014 at 06:27 PM.

    Bye for Now!

Page 1 of 2 12 LastLast

Posting Permissions

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