sure thing... might as well have a look see

 

sent

 

Hmm, the local guys here tuned with ECUTek haven't given me trouble with mode 23.

 

Yeah, I've only seen it in a few cases so I guess it's not all USDM. I sent one to tephra and he confirmed it changed the mode23 routine.

 

Trying to get logging of AFRs through the standalone logger working.

I've read that the LC-1 is only supported device that works at present, but I've a LM-1 with same bosch sensor as LC-1, are the analogue output values different between the two models? I thought they outputted the same range of voltages and the LM-1 would work.

This is what it spits out to logcfg.out when I have it running

02: type=inno
: name[type,8] value[inno,0,0.000000]
03: ; log from an innovate bus via the 3/32" jack
04: ; currently the LC-1 is the only supported device
05: ; in the "inno" case the parameters are already pre-defined, you just
06: ; need to reference them by name so that they are included in the log
07: ; output. note that these parameters won't become valid until the LC-1
08: ; has been calibrated and the sensor is warmed up.
09: paramname = inno.afr
: name[paramname,16] value[inno.afr,0,0.000000]
10: paramname = inno.lambda
: name[paramname,16] value[inno.lambda,0,0.000000]

--- log config dump ---


channel type: inno
protocol id: 9
baud: 19200

param name: inno.afr
param id: 0x00000000
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x

param name: inno.lambda
param id: 0x00000000
read width: 1 bytes
data width: 8 bits
data offset: 0 bits
float: 0
low priority: 0
scaling: x


--- storage info ---
log stringlist: 23 chars
log floatlist: 0 floats
logging interval will be 100000us

and no logs whatsoever.

Is there something I'm missing or expecting the standalone to work when it never will. I assumed the LM-1 would work fine as the analogue output can be hooked up to a guage as LC-1 can ie similar outputs.

Here's my logcfg

;----------------inno----------------
type=inno
; log from an innovate bus via the 3/32" jack
; currently the LC-1 is the only supported device
; in the "inno" case the parameters are already pre-defined, you just
; need to reference them by name so that they are included in the log
; output. note that these parameters won't become valid until the LC-1
; has been calibrated and the sensor is warmed up.

paramname = inno.afr
paramname = inno.lambda




Any help assistance appreciated.

Thanks.

 

paramname = inno.afr
;paramname = inno.lambda

Try that^^^

 

Also Don't know if LM-1 LC-1 output same. Might go haywire.

 

Thanks,

Still nothing though.

The outputs are both voltages and can be programmed to the same range.

From LM-1 manual:

As factory programmed the first output simulates a typical narrow band oxygen sensor. The
second output is programmed to output between 1.0 V for an AFR of 10 (gasoline) and 2.0V for
an AFR of 20. This allows to connect it to a digital voltmeter or panel meter (0.2V input) to show
directly AFR. Other curves of course are easily programmable


From Lc-1 manual

The LC-1's analog output 2 is factory programmed to provide a
linear output between 0V and 5V for an AFR of 7.35 to 22.39. Any other linear output range
between 0 and 5V can be programmed.

Thought it would have worked

 

I thought this was a serial output.

Although the LC1 and LM1 have analog outs, the cable is getting serial data, which may be different from LC1 to LM1.

 

Does it log anything at all? like RPM,Timing, etc.
If not did you make sure you updated your OP2?


Reason I say this is if I remember right, if you don't update your OP2 that is what your output log looks like..

Try update it again. Make sure use "beta" ECUFlash version to do this on.

here is step by step.

Step by Step Instructions:
0 - NOTE: This is for the BETA release of the standalone logger. It takes some playing with text rather than a shiny GUI. It's difficult to predict the future, but I imagine that this logging ability will be simplified and made much nicer to setup.
1 - Download the required "beta" ECUFlash version. The most updated beta version will be in the first post of this
http://forums.openecu.org/viewtopic.php?f=57&t=4319,
but the direct link to the version I used when this was written was here
http://mail.tactrix.com/ecuflash/ecu...0_win_beta.exe
2 - Install it, accepting any agreements and driver installations that pop up.
3 - Plug your Open Port cable into a USB port, start up ECUFlash.
4 - Run the Help -> Licensing to force a firmware update of your adapter. Once completed, you can close every open window.

 

I know when I did it, I could log everything else besides the LC-1..... it did not matter what adjustments I made.

 

Thanks for instructions

Beta version and firmware upgrade was performed, and i went through the steps again. Still no go.

But it does log rpm parameter and value and I get columns in the csv file for inno.afr and inno.lambda but no values, just zero's for both innos.

Have test both analogue outputs of the LM-1 and both are outputing voltages in the ranges I would expect for the ranges I have programmed so at least I know it should be working.

It might be a total DOH on my behalf

LC-1 analogue outputs both have there own jack, one each for each channel, is that correct?
and rather than connect a "stereo jack" to the standalone logger it requires a "mono" with only the analogue 2 channel connected?

I did have a stereo jack wired with both channels, and I tried to hack it to be a mono but still no go, maybe a proper mono jack will solve the problems.

If anyone can confirm if the 2.5mm jack to fit Standalone logger needs to be the mono type????

 

http://forums.openecu.org/viewtopic.php?f=57&t=4319

This website is temporarily unavailable. Please check back later.
Unfortunately there were no suitable nodes available to serve this request.

what's up?

 

Working now, not sure what was up.

 

Hi,

Managed to pick up a mono jack and attached the anologue output #2 from LM-1 to it.

And I've got a value logged in the .csv for inno.afr but as you can see below its a constant value of 128 throughout the logging session and this .csv is definitly when the sensor is warmed up and reading AFR and lambda readings on the LM-1 screen.
[Scratching my head

Could someone answer as well why this line is important in the logcfg.txt file. Nothing at all is logged without it:

type=mrmacan

I've attached my logcfg.txt and logcfg.out for the above log. I would love to get this working