Then I fit a 900watt Mitsubishi alternator to the front of the boxer engine on a shive drive not so different to how BMW changed their modern machines, that has certainly helped in adding fuel injection, even carrying a lap top, as well the welder (just kidding). I have a 400watt invertor onboard during tuning runs to take the lap top battery component out of the equation, and with all systems running the dead idle bike voltage never drops below the 13.8 that it develops @ speed. Actually the invertor may become standard equipment as in my search for small ultra high pressure (above 200psi at flow) water pumps, I find the 120vac piston style to be emerging as best ( for a water injection system which joins the parade this winter).
I seem to have moved far away from the original promo phrase for the airhead product, which was "Simple by Choice".
I only seem to manage the briefest of tweaks nowadays, as I'm always working, but today I set time aside to do some more WUE & cranking tweaks. I was getting slightly confused last time as noted previously, but coming to the bike after a few weeks clarifies things. I tried to start the bike were I had left off, and it kept missing almost catching until it backfired and cleared the exhaust. I then noticed on cranking that the MAP portion on VETable2 was starting off top left, and dropping three cells before shifting right when it started in.24c wrote: Unfortunately, I got as little carried away, and it now takes slightly longer from hot, then when I started. One step forward, two back, but at least I saved the previous tune, so I can start again.
Once I noticed this under cranking, ... so I reduced the crankingPW downwards,
and then the after cranking first column VE values hugely downward, which are affected by MAP in VETable2 The result of this was much faster starting when hot, and I'll probably have to tweak the WUE % from cold, but it is encouraging again. Laptop tuning is so much faster than unscrewing carb bodies and altering jets.
I also managed prior to this to tweak my WUE downwards, as these too are way rich, and it was a little bit colder today, so I got more time to do it.
I also tweaked the lower part throttle MAP areas in VETable2 between 2000-4500 rpm, I just wish I had the bike on the dyno for some load data, but that'll happen one day.
PS Earlier in the week the new potted adaptive VR conditioner from jbperformance dropped through the letterbox, so I'll be playing with B&G2.890 to see if it improves the GTS1000 OEM cam sensor issue. If it does, I'll be fitting this to the GTS1000 and ordering another naked board to go in the full sequential MicroSquirt module project.
It really is the simple things...most times, which leads me onto todays attempt. Go to the bike hook up the MacBook, connect the jump/boost battery and hit the button, and nothing crank and crank, pop etc. Hang on it's not -8ÂºC, there is no way the CLT temperature is that... check the Thermistor Settings, there are none! I made some custom ones some time ago, and there gone, yep I updated TunerStudio last night. Select Toyota for now, it's close enough, send the values into the MicroSquirt and bingo straight away the bike fires, and then dies suddenly.
A few tweaks of ASE, WUE and then VETable2, but it's still not right, as it's been better before. Cranking was around 250-290, so I moved the cranking limit from 300 to 400 rpm. Ignition off & on, and hit the button...bingo, slow idle but ASE holds it and then slows after ASE finishes ( I have a short ASE cycle times) and WUE takes over. A few tweaks, needed to be richer based on AFR at 7ÂºC to 14ÂºC, but as the bike warmed from 15ÂºC to 41ÂºC I had to lessen the WUE %. I had a gradual taper, but it looks like I need a stepped approach.
Now for a few cold start repeats over the next few days, and hopefully refine the process.
PS I am going to look at the injection ms/battV correction too, as I think this is the reason for the variations I have seen previously.
So I tried another cold start, but didn't hook up the computer, the engine cranked, & cranked, then missed, then popped, but it wouldn't start without a squirt of brake cleaner into the throttle bodies. Once it started ASE cut in and the revs climbed, then gradually dropped as the engine warmed. If I stopped the bike and hit the starter button, the bike started no problem, but as it got warm it didn't like it.24c wrote:Now for a few cold start repeats over the next few days, and hopefully refine the process.
So after tweaking the VETable2 downwards at hot idle, to get the AFRs something like. I decided to work on the hot start and tweak the cranking and priming pulsewidths. I don't know if this is the right approach, but I zeroed the Priming PW from 70ÂºC upwards, and reduced the Cranking PWs to 10%., and not surprisingly the engine never caught on the starter. I bumped it up to 30%, and it started after a few seconds, but the LC1 was still suggesting it was rich, so I looked at VETable2, and watched what happened when I hit the starter.
My VE values were high from a previous import and as I haven't loaded the engine up on the dyno yet, so some areas haven't been tweaked to the required AFR.
However, as soon as I reduced the bins in these areas (upper left) the engine took longer to start, so I bumped up the Cranking PW % until it got better, it went from this
Now I am going to wait for another cold start tomorrow and hopefully improve at the colder temps, but I must admit it's quite confusing having a load of msqs from different dates and keep changing the variables. It is becoming obvious, there are quite a few permutations out there, and not one size for all.
Today, after looking at the documentation a little more, especially MAT Retard for Ignition, and realised I was using it not as intended. I saw the Cold Start Advance section and thought I'd check mine, and sure enough loads of extra advance was added, another 5Âº & more by default. I reduced this to zero and the bike was still not 100%, so it had to be elsewhere. I set & checked my ignition timing at hot idle, but I have been moving the rpm bins around, and I made a mistake by not keeping up with the changes, as it seems Ignition Table 2 had a load of extra advance at cranking.
As you crank, the bins follow the trace from left to right... so my ignition advance as I cranked started at 12Âº dropped to 3Âº climbed back to 12Âº before dropping to 3 again once idling and that's all it was, now I have to reset a few other bits, adjust the IgnTable2 bins to follow the factory ignition curve. At least I get a pretty quick initial start, if I add extra fuel, and cranking speeds are increased, because the starter is not getting slowed by over advanced ignition.
I tried reloading the firmware, but the port wasn't recognised, and I had no way of jumpering the bootloader, as the loom has been modified to suit the OEM connectors.
In the end, I had to take it home, couldn't open the TunerStudio Projects as they were corrupted, and eventually worked out what was happening. I had to delete the current Tune, and any modded/corrupted ones by TunerStudio, and use the last saved tune from an earlier session instead. I could only do this after reloading the firmware using the boot loader jumpers/switch on the bench/desktop rig, and it was troublesome and not straightforward as the COM port was not recognised, even though the same set up was seen by MegaTunix in OSX. After a dozen or so attempts I was able to reload the later MSExtra3.1.0 firmware, but it was a bit of a scare.
The only good thing is I am a lot wiser at restoring these cased MicroSquirts now, and how to mod/tweak my TunerStudio project files. It also means when I fit the module I will build in a switch for bootloader mode
Hopefully today, on the way back from work, I can tweak the bikes starting & WUE some more, and as a backup I have three MicroSquirts all loaded with MSExtra3.1 & the same msq.
Well I did, except using the same msq settings in MSExtra3.1, the bike wouldn't start without additional fuel (brake cleaner) being squirted down the throttle bodies, and it idled hardly at all. I had to richen things up, but it still sounded dreadful. The LC-1 was playing up, but this is a settings issue, as I need to look at this again. The last bit is me not reading the manual, after a firmware upgrade methinks, as I was getting a lot of AFR spikes in Narrowband mode.24c wrote:Hopefully today, on the way back from work, I can tweak the bikes starting & WUE some more, and as a backup I have three MicroSquirts all loaded with MSExtra3.1 & the same msq.
The really daft thing I did, and I add it here for the benefit to others, I switched identically programmed MicroSquirts and two of the units wouldn't start the bike. I could smell fuel, and then it hit me... the jumpers inside were set to logic level output. The really daft thing was I tested them on my COPs bench rig which had an ignition amplifier/driver module, but forgot I was running wasted spark coils on the bike. Incidentally, leaving the jumpers set to direct trigger the coils and connecting to COPs via an ignition amplifier will still create a spark on the bench rig, and this is what fooled me.
Hopefully after work today, I can try and get the bike started from cold, and calibrate my Innovate LC-1, and get back to where I was before I had a config error.
I'm not where I was before, but at least I got a cold start, after pumping up the cranking pulsewidths to 200%. I then had to tweak the WUE curve to stabilise the AFR reading, although it doesn't sound the same as before.24c wrote:Hopefully after work today, I can try and get the bike started from cold, and calibrate my Innovate LC-1, and get back to where I was before I had a config error.
I've been retarding the ignition and increasing the VETable values, but it doesn't still sound right. I am going to reload the previous firmware onto a spare MicroSquirt, and load my last known msq, to see if it runs any better. Something isn't right, and I've got more work to do.
On a more positive note, I have been able to use the developmental branch modular_0.4 version of MegaTunix 0.9.24, as well as TunerStudio 0.9.999h seamlessly with either MicroSquirt running MSExtra3.1.0.
MSExtra3.1.0 is definitely different to my previous 3.0.3 versions. Going to have another go tomorrow, with increased cranking pulses and increased ASE %, so that after the engine catches, I can hold through to WUE phase.
Got three cased MicroSquirts set up on MSExtra3.1, but going to revert one back to 3.0.3 with a previous successful msq, as a double check. I'm definitely convinced there is something different happening with the 3.1 upgrade.