Jump to content

rich888

Members
  • Content Count

    88
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by rich888

  1. 2 ways to fix foggy dials. 3 if you include filling with dry nitrogen! 1: heat the glass - this doesn't require the dial to be completely airtight. 2: seal the dial so it's 100% airtight with a good desicator inside. Never tried either! Just my experience with keeping CCTV cameras fog free.
  2. I had some MIVVs on my V11 and although it sounded great, I found that it was just too loud after about 20 mins in the saddle! I put some stock cans on and it's now really quiet - maybe too quiet (LOL!), but I have noticed that there seems to be a loss of power in the midrange. Is that likely to be due to the stock cans, or just coincedence? I haven't checked TPS, valves etc etc lately, so might just have drifted off tune a bit or are the stock cans really that restrictive? Cheers!
  3. Looking for a pair of V11 Sport silencers in the UK.
  4. Good find as Delphi Aptiv don't make the mating half (the side that is part of the TPS). I guess kojaykat got some made somewhere? In the end I broke out the whole ECU connector! (I was connecting into some other pins too though...)
  5. I will defo check phase sensor. Anyone know how the tach signal is generated? Does the ECU generate it or does it come from the TDC sensor?
  6. Sorry, missed this question! Signals for injectors comes direct from injector drive wires, T'ed off where they come out of the ECU. RPM is from the tacho wire going to the gauge and the glitchy RPM data is read from the ECU via the diagnostics port.
  7. I ignore the tach and am in the process of making a nice digital dashboard! I found that the tacho gauge is very sensitive to the tacho signal drive level. Doesn't take much to stop it working. I expect that there are dry capacitors inside the gauge which are making it malfunction. At some point I will muster enough enthusiasm to get inside it and have a look... The missfire is still there, even with a different map. I am also in the process of building a data logger to capture injection times and spark timings while riding to see if I can see what casuses the missfire. I got a bit distracted by finding out that the ECU reported RPM ws glitchy, but this appears to be 'normal'.
  8. Best way to find drop outs is with a digital scope. Needn't be expensive. Hantek 20mhz scope to put on a laptop is £60 here in UK. There are even cheaper scope kits. You'll see a nice plot of the TPS voltage and the knee point.
  9. Here's a plot showing injector timing too. Looks like the glitches reported by the ECU are just errors. Doesn't seen to change fueling... This is 32 seconds long, with two gear changes. The glitches are there in blue and the red trace is the tacho signal to the rev counter. Green is injector pulse duration.
  10. Yes, your right, just leaning out or richening.
  11. Re hall effect TPS. You'd have to be really really sure it was impervious to stray magnetic effects. Imagine if it read full scale suddenly... I wonder if an optical encoder or resolver would be better? Both need additional electronics to generate an analog output though. We used to use 'pots' in CCTV cameras for position sensing. There wore out regularly. Then we moved to plastic track pots, as used in servo motors etc. These lasted 10 times longer. Then we moved to resolvers which last forever as there are no contact points at all. Very accurate. We tested a hall type sensor, actually a magnetic angle sensor from AMS. It worked but it wasn't completely linear and needed a calibration run to iron out the bumps. According to AMS these are used for automotive drive by wire applications. I wonder if the ECU range checks the TPS readings?
  12. Got my datalogger to record the tacho signal directly and this is the log: The green trace is RPM reported by the ECU. The red trace is RPM calculated from the frequency of the tacho signal. I also found that the tacho signal can't handle much of a load. An extra 5mA load of the opto isolator led I'm using is enough to drop the tacho voltage down sufficiently to stop the tacho dial working. Anyway, it seems clear that the glitches reported by the ECU are not there on the Tacho signal! Need to check the RPM/TDC signal too. Question is, is the ECU reporting the glitches because its using this value of RPM in computing injector timing? I need to repeat the logging with injector timing to check...
  13. Maybe there are two sensors in the one housing...
  14. So there's a TDC and RPM sensor? I was looking at the service manual for a 2002 V11 LeMans and found item 34 Phase/Revolution sensor.
  15. Thanks! I will stick a scope on mine today. Do you know if the Tacho signal from the ECU is derived directly from the TDC sensor or generated by the ECU software? I'll scope both and see what they look like....
  16. Not thought of that! It's not going to be easy to verify the TDC sensor operation, will probably have to datalog the pulse timing from it directly, together with the ECU RPM values.
  17. And this is whats lurking under the seat...
  18. Just for interest, this is a log of a gearchange: Speed is updated every second via GPS - hence the steps! There are some disturbances in the injector timings but hard to say if they match RPM glitches. The sample rate is too slow to be sure at only 15 times per second, but I have just improved that to 30 times per second, so it may show up better... When it drys up a bit outside, I'll take another plot and keep the bike in a lower gear to keep the rpms in the 5000-6000 band for longer. I'm actually looking for the reasons for the occasional missfire / hiccup as well as the misbehaving tacho.
  19. Maybe. The glitches get progressivley bigger as the RPM's go up. I assume the ECU measures RPM from the crank sensor (TDC sensor). If it is actually reading these glitches, I would expect it to cause glitches in fueling too... I would assume that the TDC sensor provides pulses, so don't know how it could trigger early and then late? Mabe the ECU is doing some averaging and getting it wrong!??
  20. Using my homebrew datalogger, I noticed that the RPM value reported by the ECU also has glitches in: Not sure if this helps explain the dodgy Tacho Gauge or is some other issue?
  21. £450 to alter a few hex codes in the bin file? Good money for someone!
  22. I wanted to buy some wideband lambda controller boards from wide-band.com. They are cheap at only $20 each. "Shipping" for a board smaller than a credit card? $93.... Can't stuff just be posted in US Mail? I can buy stuff from China for a £ or two including 'shipping' and while it may take a couple of weeks, it always gets here...
  23. I actually have a PC3 too. It has this map in (which the previous owner paid a lot of money for!)
  24. Looking at the stock fuel map for a 2001 V11, it has some odd peaks and troughs in: Anyone know why this is? For example at 2000 rpm tps 48, is a peak of 193, which drops off at higher and lower rpms and higher and lower tps. There is also a low fuelling trough at 4000 rpm at wider TPS values.
  25. Got the GPS module today. Just amazing that these things are so small and cheap... Imagine showing one to John Harrison... Anyway, thanks to Beard over on Guzzi-Forum.De of GuzziDiag fame, for helping with a few pointers regarding the ECU and the interface. The trick will be packaging it so that it's descrete and readable.
×
×
  • Create New...