Instructions to change fuel maps on 14CUX Griffith, Chimaera

Instructions to change fuel maps on 14CUX Griffith, Chimaera

Author
Discussion

stevesprint

Original Poster:

1,114 posts

178 months

Tuesday 20th September 2016
quotequote all
CGCobra
Welcome & thanks for your kind words, yes you are in the right place.

CGCobra said:
I don't believe for one minute the engine is actually producing those readings oscillating between 7.x and 20.x would give very poor running if at all, in-fact the engine runs reasonably well.
I agree, if your AFR is really fluctuating between 8 and 20 your engine would be very hesitant, shunting and wouldn’t accelerate smoothly especially when its 20, I guess you’ve tried re-calibrating your LC-1 sensor and also I’m sure you are aware the probe mounting angle is critical.

CGCobra said:
I have other issues with the Innovate software, sometimes it will detect the sensor other times it won't, may be my laptop, need to try on another. Eventually I'll be taking an analogue output into the MS and will see if that works any better than the serial into my laptop.
MPO and I run Innovate LC-2 without issues and merge the AFR logs with the RoverGauge logs to insert the AFR for the active cells in the fuel table. My LC-2 is 100% reliable, outputs records every 0.1 sec and you’re welcome to use my LC-2 AFR logger & merger.

CGCobra said:
I've used "TVR Griffith 400 Precat & TVR Chimmaera 400 CAT combined in Land Rovers final revision R3652" from Steve Sprints site. I'm assuming that 'precat' means the green map is programmed?
Thanks Dave

CGCobra said:
My understanding is this gives the latest program as well as a TVR map?
Correct
CGCobra said:
Only slight issue I have with this is the idle control seems different and not as good on my car as my previous chip, particularly when cold.
Sorry to hear you are experiencing idle issues with map 2 of “TVR Griffith 400 Precat & TVR Chimmaera 400 CAT combined in Land Rovers final revision R3652”, I’m surprised ‘it sometimes stalls when you come to a stop’, which interestingly is a similar symptom to a faulty road speed sensor. I’ve heard of high idle issues with R3652 while slowing down that I've since learnt how to control and fixed on my 4.3. Do you get a road speed sensor sensor fault code 68???

CGCobra said:
Is there a better "starting point" for my setup?
Yes, it might be worth taking a step back to help identify the where the issue lies, therefore please can you try “TVR Griffith 400 Precat & TVR Chimmaera 400 CAT combined in later TVR R2967” and let me know if its any better.

In addition the advantage of running map2 is you can set your idle AFR to 13.5 to improve idle and slow speed running by setting the CO Trim screw on the AFM to 1.4 volts as seen in RoverGauge. To see the CO Trim voltage change in real time you need to fire up and then turn off the ignition long enough to stop the engine and then quickly back on again.


CGCobra said:
My speed sensor gives an analogue output proportional to roadspeed (although about half the rate of a Rover unit apparently) not the binary (moving / not-moving) signal a TVR seems to have. Don't know if this makes the difference)
No, the exact road speed calibration is unimportant and is only used to set the target idle once stationary and to limit the max road speed which is by-passed in the program code of TVR R2967 & my R3652.

Good Luck and let us know how you get on.
Steve Sprint

stevesprint

Original Poster:

1,114 posts

178 months

Tuesday 20th September 2016
quotequote all
I’ve recently been informed that R2967 was also used on early MGR V8s which means back in 1993 (sound a familiar date??), therefore was R2967 originally for the MGR V8 and Rover by-passed the road speed limiter in the code for the MGR V8, makes more sense.

TVR wouldn’t have bothered removing the road speed limiter in the code because TVR went to the expense of installing a signal generator in the speedo calibration box to limit the road speed signal fed into into the 14CUX to 30 mph because the GKN and BTR crown wheels have too many teeth/pulses for the 14CUX.

Does anyone have a copy of R2967 from a MGR V8 I can compare with TVR's R2967 ???? Please smile.

CGCobra

48 posts

92 months

Wednesday 21st September 2016
quotequote all
Hi Steve, thanks for the replies and the welcome.
I feel a bit of an interloper on a TVR forum (with a kit car it's easy to feel like an interloper in most places!) but in my defence I do live only a stones throw from the home of TVR (and the other great British marque which my car shares parts with).

There's definitely an issue(s) with the Innovate setup, at the moment I'm assuming I've done something wrong. Although it's a few years old it has only been sitting in its box since I bought it until I got it mounted a couple of weeks ago. It's more of a problem that I can only get it communicating with my computer occasionally. You mention "you’re welcome to use my LC-2 AFR logger & merger." I must have missed this, do you have a link to it? I'm really interested in it as it will take the Innovate software out of the loop and by the sounds of things allow me to log the AFR against other meaningful data.
As far as I can tell the install location is good, it is after the header where the pipe turns through 90° to run horizontal, the bung is mounted more or less vertical. Only have one sensor, currently in RH bank but can move to LH as have a bung in that pipe too.

I'll try the other map you mention at the weekend if I get chance (time is my biggest enemy at the moment) but the problem was very small, I thought at first I wasn't getting a 'moving' signal but all seemed to improve as the car warmed up (or perhaps the system learned where to wind the valve to), Perhaps I'm best to test this a little further through some more cold start-up and run cycles just in case there is a learning process involved.
I didn't have RG connected at this time so don't know if the speed sensor was giving a good signal but I've had no problems with it previously and as I say only a few minutes later all was good. No fault code was given.
The speed value RG gets is out by (roughly) a factor of 2.3 (reading 13MPH when GPS is showing 30) do we know if there is any way to scale this value in the CUX. or is there any way in RG to apply a scale factor to the displayed value?
Only reason I ask is I'm toying with the idea of running an electronic/LCD dashboard, obviously would need speed to be correct. This is all way in the future though!

My system doesn't run the lambdas and I've always been happy with that, my understanding is they are only there as a legal requirement (for running cat's), don't really add any value and the added complexity just makes it more difficult to work with and gives more parts to fail.
Perhaps I'm wrong about some/all of this. Is there any positive value from running lambdas?

I'll keep you all posted on my results, thanks again.

stevesprint

Original Poster:

1,114 posts

178 months

Thursday 22nd September 2016
quotequote all
CGCobra
You can compare the main tuning parameters in my tune settings spreadsheet @ http://www.stevesprint.com/remap-14cux/LR-TVR-sett... . It's now also possible to compare the program source code thanks to Dan and Colin’s huge effort reverse engineering 10 different binary files and cleverly merging them into one rebuild project and commenting all 20,000 lines of assembler code & data, staggering, absolutely staggering. Dan’s source code is available at https://github.com/colinbourassa/14cux-firmware , be warned its not easy but Dan’s running commentary makes it less impossible to follow.

Sounds like you need to try your LC-1 on another computer to prove a point and agreed it should be alright after being in the box a few years.

Here’s a link to my AFR logger including a sample log file www.stevesprint.com/remap-14cux/AFR_Logger.zip
BUT !!! I’m not sure it will work 'out of the box' with your LC-1, unscrambling the LC2s output was stupidly complicated involving bit shifting the data and I still don’t know how I managed it. I don’t know if the LC1's output is in the same format but if not I’m prepared to have ago for you. We run both loggers in tandem and my AFR logger time stamps every AFR record in real time with the system time (like RG) so the AFR records can be matched by time afterwards with MPO's or my merger.

Here's a screen shot of my AFR logger and Rovergauge running in Tandem.


The only sad news is the 14CUX's serial port is starved out above 5,200rpm and stops logging, but at least you know above 5,200rpm your between the last two columns of the fuel table.

I should also warn you self remapping is an addictive time consuming slippery slope analysing and tweaking data, but personally I enjoy being busy and self-sufficient plus I'm too tight to pay someone else to do it for me. However, if I've put you off Joolz at Kits and Classic can fully remap your existing map/chip in an afternoon on his own rolling road for a reasonable price and I've heard lots of positive reports.

Here you can see I've mounted my wideband just above the centre line of the pipe after the Y to catch both banks and it works a treat.


The ECU does learn and store a stepper motor offset along with the fault codes and lamda trims, I've always struggled to understand how and when the stepper motor saved value is updated. Maybe we should ask Colin to add a new window to RoverGauge to display the battery saved data, it would make understand the steppers motor behaviour and issues a lot easier.

Dave has modified the 14CUX code in the past to recalibrate the RoverGauge Speedo, however your idea of adding a calibration multipler setting to RoverGauge is a much better idea because you can still run the OEM tune files.

Please don’t toy with the idea of relying on the 14CUX's speedo for your dashboard speedo, trust me its not reliable enough, use your road speed sensor and a programmable speedo.

Running Lambas is a disadvantage because you loose the flexibility to tweak the AFR to eliminate shunting, the lambda probes are used to help cycle the AFR around 14.7 to make the cats more efficient, I’ll let Mark explain in more detail.

Good luck with the further testing and please remember a road speed sensor fault will cause stalling while slowing down.
Good Night
Steve


stevesprint

Original Poster:

1,114 posts

178 months

Thursday 22nd September 2016
quotequote all
Colin

Further to my post above please can you consider displaying in RoverGauge the following battery saved data, especially the stprMtrSavedValue as it would help us understand stepper motor issues.
stprMtrSavedValue
throttlePotMinimum
hiFuelTemperature

I assume there’s no point displaying longLambdaTrimL/R as the trims are already on the main screen. I don’t mind if you squeeze them in on the main window or add a new window, what ever is easier.

Also, please can you consider CGCobra suggestion to add a calibration multiplier for the RoverGauge speedo and logs as it would save modifying and running bespoke bins.

No rush winter is on its way.

Much appreciated
Steve

CGCobra

48 posts

92 months

Friday 23rd September 2016
quotequote all
Hi Steve

Thanks for your pointers. I'll try and have a look at your AFR logger over the weekend (time permitting), if nothing else it will be useful information to others to know if this does/doesn't work with LC-1. I'll also see if the system has learned to behave better with the idle. Given that I have limited time though I really want to start concentrating on getting the ignition switched over to the MS, I won't be happy until I have control of the sparks.

My exhaust system doesn't join at any point so I can only monitor one side at a time, I'm not sure if this is an advantage or disadvantage, probably a bit of both. I can use the probe in either side though,

My understanding, possibly incorrect, is that on a closed throttle 14CUX drops into idle mode at a low speed (3MPH?) rather than zero. This may help explain why I don't have the same issue with a high moving idle that some do, as mine will be cutting off while the car is still moving so drops to stationary idle sooner after stopping.
Added to this my speed sensor is reading less than half speed so I hit this threshold at a higher actual speed (if the threshold is 3 I'll actually be doing about 7).

Thanks for clarifying the situation with the lambdas and confirming there is no advantage in my looking at this. I prefer things to be as simple as possible (and no simpler).

One thing I may look at doing is using the heated screen or AC inputs to elevate the idle speed when reversing, my car stalls quite easily (probably due to having a light flywheel), this tends to mean quite a bit of throttle blipping when manoeuvering and as the car is LOUD this is not really desirable, a higher idle in these conditions may help. I seem to remember reading that these input are inverted, that is a +12v signal is used for off, not sure if it was confirmed so may have to experiment with this.

Colin
Thanks in advance if you do make the changes Steve has suggested it will make a great system even greater.

CGCobra

48 posts

92 months

Sunday 25th September 2016
quotequote all
Well I've made a bit of headway this weekend, the good news is the AFR logger does appear to work with the LC-1 although I'm getting some results which I'm not sure are to be expected.
If I startup the AFR logger before I turn on the car I see messages indicating the sensor is warming up E.G.
Warm up A = 0220, B = 0031, AB=008156
I was then seeing readings in the form:-
O2 level in 1/10Per: 10.0
Where the accompanying value is generally between 9.9 & 10.5
I've since re-mounted the sensor and the exhaust section which it fits into as I has suspicions that there may be a leak, while doing this I also did a fresh air calibration while I had the sensor out.
After doing this I got a good reading on the logger with a single constantly changing value which was in about the range I would expect. I took the car for a spin and found that the "O2 level...." message appeared again which unfortunately pushes the reading out of the bottom of the window, however this only occurred once or twice unlike before when it was continuous, I wonder if this is Innovate's response to an out of limit condition.
Are these messages something you've seen on the LC-2 or is it something specific to the LC-1?
Is there any way I can stop them occurring?


I created an AFR log and a RG log file at the same time but I can't see any way to merge them, did I miss something?
Obviously both systems give a time stamp but the AFR logger appears to take readings at a greater frequency (about 4 times), also the format of the time stamp appears different from both systems.

I also checked the roadspeed with RG and was getting a good reading but no elevated moving idle at all, warm or cold,
I swapped the chip back to my original chip and immediately my moving idle was back again, I did notice that the amount of elevation is greater when the engine was cold (about 1500RPM dropping to about 1100 when warm) but was always there.

One thing I have realised is that my idle has the Neutral Gear Idle Adjustment added in (+100 for the TVR chip, +40 for my original), as far as I know this input is not connected so it looks like this has to get a positive signal to turn off (although I've no idea if this should be ground or +12v), will check the terminal when I get a chance. I don't have AC compressor connected either but this value is not being added in, heated window signal should also not be connected but can't tell if that is added as both chips have this setting at zero.

That's all for now, at least things are moving forward.

stevesprint

Original Poster:

1,114 posts

178 months

Monday 26th September 2016
quotequote all
CGCobra
I'm pleased your LC1 works and with my logger, sorry here's a link to my merger program, www.remap-14cux.info/MergeAFR&RGLogs.exe

Yes I do also get the Warm up & O2 level in 1/10Per messages going off the screen and never fixed them as it still logs and I usually closed the laptop while logging, I’ll try and fix them this winter.

I should explain that on a power run past 5,200 rpm the log merger inserts blank RoverGauge records above 5,200 rpm with the correct time and AFR which I then manually enter the active row/columns plus delete some records at the end of the file. I then import into excel and create a pivot table like the one below, I'm sure you realise in the log column 0 is the first column.


I wrote the merger for my personal use so its very basic & not robust as commercial software but does the job, maybe I should add it to the logger. I welcome any suggestions like creating fuel table row/column rounded columns for excel or removing the records at the end of the merged file without AFR reading.

Also one final thing, while logging try moving the throttle gradually and smoothly to reduce sudden throttle enrichment.

This wiring diagram should answer some of your other questions www.remap-14cux.info/14CUX Wire Diagram.pdf, connect the neutral/auto gear wire as per this diagram, pin 34.

You're very welcome & enjoy
Steve

Edited by stevesprint on Monday 26th September 19:52

CGCobra

48 posts

92 months

Monday 26th September 2016
quotequote all
Hi Steve

I read more of the detail on your site yesterday evening, found the section where you indicated you'd 'massaged' the data manually so I put together a macro on Excel to remove the non-numeric data (O2... & Warm up.... records), it then allocates the AFR data closest in time to the RG data and removes all other AFR data. This gives me an AFR reading generally within a few milliseconds of the RG settings.

Obviously you (or anybody else who's interested) are welcome to a copy of this if you think it will be of any use.

CGCobra

48 posts

92 months

Monday 26th September 2016
quotequote all
Just used your merge program, gives much same result as my spreadsheet, not a problem, it's been a while since I did some coding and I like to keep my eye in!

CGCobra

48 posts

92 months

Tuesday 27th September 2016
quotequote all
Hi Steve

Just been looking at your pivot table, didn't instantly understand what you were doing but think I've made sense of it now, you're plotting AFR values against the row and column data from RG, which will correspond to fuel table, very neat! Presumably you are taking the nearest row and column values as there are real numbers indicating an interpolation between adjacent cells. I like this but I'm not very good with pivot tables however I could write that into the macro I currently have for massaging/merging the data, I could also work out the maximum and minimum readings for each row/column pair, may even re-write the data into row/column order (I sometimes like to be able to look at raw data rather than just average readings).

I did notice that where I get the "O2 level in 1/10Per: 10.2" entries in AFR data the records immediately before and after are unrealistically high, typically heading to around 80 before the "O2..." message, I probably need to remove these readings too. I guess the Innovate system gives this reading when data is obviously wrong, Have you any idea why the readings go AWOL?
They typically seem to go out for 3-5 seconds, over a 22min logging period I had 16 "outages". Do you tend to see this level of poor readings (about 5%)?

CGCobra

48 posts

92 months

Thursday 29th September 2016
quotequote all
I've added a bit more code to examine and display the data similar to your pivot table, the difference is I'm using 4 cells for each RPM/load pair, this gives (clockwise from top-left, red text,cell) Average AFR, Minimum AFR, Maximum AFR and number of samples.
I've also gathered all the readings and put them into a comment.
As you can see from the image below my data is not very good (I only went for a quick blast, need to do another run(s) as you suggest) so some of the samples give a range which is too wide while others don't have enough samples to be meaningful.

Hope the image upload works!


stevesprint

Original Poster:

1,114 posts

178 months

Friday 30th September 2016
quotequote all
CGCobra said:
I read more of the detail on your site yesterday evening, found the section where you indicated you'd 'massaged' the data manually so I put together a macro on Excel to remove the non-numeric data (O2... & Warm up.... records), it then allocates the AFR data closest in time to the RG data and removes all other AFR data. This gives me an AFR reading generally within a few milliseconds of the RG settings.
I always use the AFR reading immediate after the RoverGauge record as I think gases move slower than '1's and 'o's, its only a hunch and not based on any scientific testing but seems to align the AFR readings correctly.

CGCobra said:
Just been looking at your pivot table, didn't instantly understand what you were doing but think I've made sense of it now, you're plotting AFR values against the row and column data from RG, which will correspond to fuel table, very neat!
Correct, sorry I should have explained.

CGCobra said:
I've added a bit more code to examine and display the data similar to your pivot table, the difference is I'm using 4 cells for each RPM/load pair, this gives (clockwise from top-left, red text,cell) Average AFR, Minimum AFR, Maximum AFR and number of samples.
I've also gathered all the readings and put them into a comment.
Woow, your far more advanced with Excel than I’ll ever be, my pivot table is so simple it only takes a few click to create and isn’t worth recording a macro to automatically create it but yours is very impressive.

CGCobra said:
As you can see from the image below my data is not very good (I only went for a quick blast, need to do another run(s) as you suggest) so some of the samples give a range which is too wide while others don't have enough samples to be meaningful.
Throttle enrichment and throttle lift off overrun really skew the readings and as a result I’ve leant to chop my logging sessions into very short logically tests like this power run and motorway cruise.




CGCobra said:
(I sometimes like to be able to look at raw data rather than just average readings).
Agreed, plus I have to fill in the row and column numbers above 5,200 rpm’s. Its save to assume once RoverGauge stops logging you're between the last two columns.

CGCobra said:
I did notice that where I get the "O2 level in 1/10Per: 10.2" entries in AFR data the records immediately before and after are unrealistically high, typically heading to around 80 before the "O2..." message, I probably need to remove these readings too. I guess the Innovate system gives this reading when data is obviously wrong, Have you any idea why the readings go AWOL?
They typically seem to go out for 3-5 seconds, over a 22min logging period I had 16 "outages". Do you tend to see this level of poor readings (about 5%)?
Only at the end of a full power run test, I’ll explain.
You should only see the "O2 level in 1/10Per:" message on overrun when the ECU temporarily cuts the fuel. I’ve disabled this overrun cut below 4,000 rpm in my R3652 and set the AFR between 18 and 20 on the top row to induce overrun cracks & bands, as a result I also don’t see “O2 level in 1/10Per:” message unless I suddenly lift off above 4,000 rpm. This overrun set point is controlled by chip offset 137 and the different values are listed half way down http://www.stevesprint.com/remap-14cux/addresses.h...

Once I finally got my AFR Logger and merger basically working last spring I abandoned working on them as the weather was improving and didn’t bother fixing the on screen error messages as it always carries on logging to file. I really welcome your interesting in my logger & merger as it will give me the kick up the bum I need to fix the “o2 Level messages” plus “Warming up messages” and remove the 0.00 AFR records at the end of the file. We should really remove all records with sudden throttle movement for up to a second afterwards to give the throttle enrichment time to decay.

Maybe we should also automatically remove all overrun records on a closed throttle on rows below 0 or 1 and say above 1,400 rpm, what do you think??

Glyn
Do you prune your AFR logs???


I’ll save the elevated moving idle for another night.

CGCobra

48 posts

92 months

Friday 30th September 2016
quotequote all
Good point about taking the next latest AFR reading it makes sense that the reading can't happen before the 'burn'. Why didn't I think of that?

It's a while since I've written macros for Excel but it's coming back slowly! It can still be polished a bit yet.

One thing I was thinking of is some way of registering when I want to start recording 'meaningful' data rather than having to start the RG & AFR logs running, I wouldn't want to stop on the hard-shoulder to do this! I was wondering if there is a phone app where I could simply press a button on the phone to register the time then when I get back to base I could work out which logs to keep.
I could alter my macro to allow input of start and stop times (maybe multiple events) and filter out any records out of these periods.

Maybe better still would be to build this into the AFR logger, perhaps add a simple key press (F key probably) on the computer which would control the AFR log writing, maybe invert the screen graphics to indicate when outputting data rather than just reading it, so a quick glance would indicate which mode you're in. If you're going to have a play with your code maybe you could have a think about this?

I didn't think of RG suspending it's logging above 5200, I could modify my script to include those AFR records too (I think!).

I did a bit of thinking about the "O2..." messages, particularly with the high AFR reading immediately prior and thought it may be due to the fuel cut off but this didn't seem to agree with when I saw them on the screen, maybe the event and the display are not quite in sync'. I'll check the RG data, that should show if I was in that area.
I don't get much popping on overrun which I'm a little disappointed about (childish I know but my bike does it and I quite like it)

I think I could alter my macro to filter based on any combination of readings.
Currently I run a sequence of macros which will eventually be joined but I'll maintain the ability to run 'stand-alone'
I firstly filter the AFR data, chucking out any "Warm up..." and "O2..." readings, any AFR readings earlier than the first RG reading and any AFR readings > 20 (or any other value I set), I then search through each line of RG data and look for the nearest AFR reading (need to change that to nearest higher AFR reading). Any earlier AFR readings are removed (I need to find a way to allow for RG reading which are missing due to too high RPM).
Once I've filtered the data I create the table scan through the data to fill in the cells.
I guess a bit more 'intelligence' could be added to this, to look for steady states with no sudden throttle movement.
I also correct my speed readings in case I want to use this data.



stevesprint

Original Poster:

1,114 posts

178 months

Sunday 2nd October 2016
quotequote all
CGCobra said:
I think I could alter my macro to filter based on any combination of readings.
Currently I run a sequence of macros which will eventually be joined but I'll maintain the ability to run 'stand-alone'
I firstly filter the AFR data, chucking out any "Warm up..." and "O2..." readings, any AFR readings earlier than the first RG reading and any AFR readings > 20 (or any other value I set), I then search through each line of RG data and look for the nearest AFR reading (need to change that to nearest higher AFR reading). Any earlier AFR readings are removed (I need to find a way to allow for RG reading which are missing due to too high RPM).
Once I've filtered the data I create the table scan through the data to fill in the cells.
I guess a bit more 'intelligence' could be added to this, to look for steady states with no sudden throttle movement.
I also correct my speed readings in case I want to use this data.
I did warn you its a slippery slop but you seem to be a natural and I’m very impressed with your progress & speadsheet.
CGCobra said:
Maybe better still would be to build this into the AFR logger, perhaps add a simple key press (F key probably) on the computer which would control the AFR log writing, maybe invert the screen graphics to indicate when outputting data rather than just reading it, so a quick glance would indicate which mode you're in. If you're going to have a play with your code maybe you could have a think about this?
If you put the following in a batch file you can fire up RG and my AFR logger and start both automatically logging with one click of an icon plus both log files end up in the same directory.

cd \????\logs
start /MAX \????\rovergauge.exe –a –l
cd \????\logs\logs
Start “Title” “\????\AFRLogger.exe" lc2log 7

However, I like your great idea to add a stop and start logging toggle key to my AFR logger and would be much better, I’ll try and change the font colour while logging, if not I could try changing the title or appending a L to the readings on the screen. I’ll have a go once its too cold to work in the garage, plus at the same time I’ll fix the “O2... “ warning messages and change the date format to match RoverGauge. Please be patience with me as I’m not in the computer industry and really struggled to write the logger and merger.

It would also be useful if Colin would be kind enough to assign different keyboard accelerators to RoverGauge’s ‘Start log’ and ‘Stop log’ buttons and make it more obvious while its logging, maybe a flashing message just above the 'Injector Duty Cycle' bar.

In the mean time if you don’t have a dash AFR gauge you may find Innovate’s LogWorks3 AFR gauge useful.


Dave - the Row scalar is from the Chimmy 430BV CAT map and is a perfect fit, Joolz helped me find the main table scalar. It's my latest effort and drives better and the idle never drifts up or down as I've properly lowered the coasting idle by raising offset C242 to 8C (Used to initialize 'stprMtrSavedValue'), my base idle set via the plenum top by-pass screw is 700rpm.

CGCobra said:
Obviously both systems give a time stamp but the AFR logger appears to take readings at a greater frequency (about 4 times)
You can increase RoveGauges log record frequency upto about 6 records a second by reducing the number of sensors logged by disabling them in “Options| Edit settings“

While I’m concentrating on remapping the fuel table I normally only have the following enabled;
Road Speed
Engine RPM
throttle Position
Fuel map Data
“Soft” fuel map cell highlight

I sometimes turn off the 'road speed' for power runs but always leave the throttle position on so I can see what I'm doing and filter on it, plus it's also a good way to check your RoverGauge records align correctly with the AFR records.

CGCobra said:
My exhaust system doesn't join at any point so I can only monitor one side at a time, I'm not sure if this is an advantage or disadvantage, probably a bit of both. I
can use the probe in either side though,
During closed loop the left and right lambda’s always run with different percent long term trims, therefore maybe you should do two identical tests with your wideband in each bank and then take the average.
Cheers, Steve

======== EDIT ========

I can pause logging by pressing my laptop’s sleep button and then pressing any key wakes it up again and luckily continues logging, its worth a try.

Edited by stevesprint on Tuesday 4th October 21:06

stevesprint

Original Poster:

1,114 posts

178 months

Sunday 9th October 2016
quotequote all
CGCobra
As requested I’ve sorted the following AFR logger issues and can be downloaded via the previous link above.

1 – Fixed & changed “Warming up” screen message to “Wait”
2 – Fixed & rounded down all “O2 level in 1/10Per:” screen messages to “99.9”
3 - Stopped logging “Warming up” records
4 – Log all “O2 level in 1/10Per:” readings with correct date/time and round down to 99.9.
5 – Added date to every record like RoverGauge (I’ll next fix my merger for date/time)

I've only given the above a very quick test in the garage so please don't hesitate to contact me if you have any issues or any suggestions.

Glyn
Please let me know if any of these changes cause you any issues.

Enjoy
Steve Sprint
RV8 - I'm doing my bit for global warming

Bluebottle

3,498 posts

239 months

Monday 10th October 2016
quotequote all
Quick question chaps, can rovergauge be run on a windows 10 tablet with a micro usb adaptor?

stevesprint

Original Poster:

1,114 posts

178 months

Monday 10th October 2016
quotequote all
Bluebottle said:
Quick question chaps, can rovergauge be run on a windows 10 tablet with a micro usb adaptor?
Sorry don’t know.

In theory it should work as I can confirm RoverGauge definitely runs on a Windows 10 64-bit laptop (see below) and tablet USB ports are usually standard USB2 or USB3 compatible, please check the spec.

Also, if the tablet doesn’t output enough power to drive the RoverGauge USB cable controller you may require a powered USB hub.


CGCobra

48 posts

92 months

Monday 10th October 2016
quotequote all
Hi Steve

Sorry not to have been back sooner but been very busy last week and that looks set to continue until about mid November. I'll try and do a run with your new AFR logger at the weekend weather permitting and let you know how it goes.


CGCobra

48 posts

92 months

Monday 10th October 2016
quotequote all
Bluebottle said:
Quick question chaps, can rovergauge be run on a windows 10 tablet with a micro usb adaptor?
Good question, interested in that too. Pity Android never came about.