Adamw
-
Posts
21,082 -
Joined
-
Last visited
-
Days Won
1,370
Content Type
Profiles
Forums
Events
Gallery
Blogs
Posts posted by Adamw
-
-
Good work, definitely sounds like the GT101 is the problem. The easy fix will be to drop in that cherry sensor I mentioned earlier. They can be found quite cheap in most countries, try mouser, digikey or farnell.
-
So to just pull numbers out of the air... if your MAP was 202kpa, your VE was 110% and your IAT trim was +2% - perhaps you'd end up with 202 x 1.10 x 1.02 = 227 MagicLithUnits and it'd be a familiar looking scale... and one which would arguably be more portable, if you know what I mean?
On the other hand g/cyl is locked to that engine's displacement etc.
Interesting topic for sure and Im curious enough to try to understand more about it... I'm not sure I agree with the "familiar looking scale" comment though. For instance at idle and cruise - say where you typically have 50Kpa & 50% VE, then wouldnt your load axis number end up something like 25 - how would that be a familiar looking scale or more portable? I can see how it will make the table flatter but that seems only because the axis scale has been exaggerated.
Obviously airflow is the best load source but it rarely be practical to work with. For instance how would you tune such a table? With a more traditional load axis you can use a dyno to hold MAP and RPM constant to tune a cell but with this suggested load axis, your tuning cell would drift around as soon charge temp increases.
If you have some experience with another ecu brand that uses this strategy can you PM me the details just so I can try to understand better how they use it or what the idea behind it is?
-
Actually, if it were an option (I just pulled estimated airflow/cylinder out because it was an existing parameter which was arguably a better load measure than just MAP) would be:
(MAP x VE) / IAT
I think there are different "nicknames" for that by other brands, but it basically adds up as meaning that the ignition table look up is done off cylinder filling at that moment but is still semi-intuitive to work with as it is normalised - the airflow numbers would be relatively arbitrary by comparison. Apologies for not making the first post a bit clearer in regards to what was hoping to achieve.
The parameter name "Air per cylinder estimated" would indicate to me that VE & Charge temp are probably already factored into it and will give you exactly what you are looking for. Maybe Scott can confirm by trying a demo on his simulator by adjusting charge temp input only, then adjust VE only and see how/if they affect the "estimated air per cylinder" parameter.
-
Can you post a PC log, preferably showing the oscillation.
-
g4+ Logging
in G4+
Scott beat me to it, I had a similar reply half written...
There are 8 megabits in a megabyte.
However in my experience even in fairly complex applications this is plenty with proper consideration of logging rate for each channel. You should be able to achieve much more than 17mins with 60ch of typical parameters. Most temp sensors for instance will only need 0.5 or 1Hz. Many others such as wheel speed, aux outs etc don't need anymore than about 10Hz. 25Hz is plenty for most of the critical engine/fuel parameters. You should only need 50 or 100Hz for a few select channels or when you are chasing a specific problem. I have never noticed the downloads to be slow - from memory it only seems like maybe 30 seconds for a full log? How long is yours taking?
-
Further to Simon's advice, if you still have access to your scope could you connect it to the crank sensor and do a capture of the engine cranking.
Although I have seen the GT101 work quite successfully on many applications, I have heard many experienced people say never to use them on missing tooth wheels even if your tooth count and size fits within the recommended range. The reason is they are not just a hall sensor but they also have some logic built into them to correct for minor wheel run-out and tooth timing variations - so when a missing tooth appears they try to correct for it and distort the wave form around that area. This may be what is happening at cranking speeds so a scope trace should hopefully confirm if this is the case.
If this turns out to be your problem then there is an alternative sensor from Cherry or ZF that is a direct drop in replacement (search for Cherry GS101202), it does not have this built in "logic" and has higher frequency range so is more suitable for missing tooth wheels.
-
Can you pull the fuel pump fuse/relay out and do a PC log of the engine cranking. Post the log and your map here and we will have a look if anything looks odd.
Video of how to do the log here: https://www.youtube.com/watch?v=_P1LRANeO4A&t=3s
-
Or provided you have 2 aux outs available, it will probably be tidier to do it like this:
-
You should not have any problem from a noise perspective with the igniter next to the ecu. You do not need shielded cable between ecu, igniter or coils. Most igniters need to be mounted on an aluminium heat sink and have some airflow around it for full service life.
-
Multitooth will be the correct mode. In trigger 2 settings did you set that to "none"?
-
Hello
Anyone here has an experience with honda CRV coils , it comes with built in igniter 3 pins diagram
I want to know , it goes rising or falling edge ?and how do I figure it out .
Thank you.v much
I dont have any experience with these specific coils but I'm fairly sure they will be the normal falling edge. As far as I know it was only the old honda "coil in distributor" types from the early '90s that were rising edge.
Here's a quick test that should confirm; Remove #2 coil from its hole, but leave it connected to the wiring and insert a spare spark plug into the coil and ground the body of the spark plug. In PC link, temporarily set ignition mode to distributor and do a store. With ignition turned on, now go to "aux outputs - ign" and while watching the spark plug, set ignition drive #2 to "test (on)" (polarity setting should be low). You might have to try clicking between "test (on)" and "off" a couple of times to get a good feel for what is happening. If you see a spark the instant you turn "test on" then the coil is falling edge. If you see a spark the instant you turn test off then it is a rising edge coil.
-
-
Yes, my logic says your proposed set up is correct and should work as expected. LED off and DI is high when switch is open, LED on and DI goes low when switch closes.
-
-
Sorry but just to clarify if I required an Injection duration of 4ms @ 100Kpa MAP and my master Fuel was set at 8ms I would enter 50%. But If I required 4ms duration @ 50Kpa what would the value be then? it would be 100% yes?
You are correct.
Also do you have an equation to calculate mass air flow at different given MAP load points? I'd like to check them against the calculator I have?
Engine capacity x VE = Volume air flow. Volume air flow x air density = Mass Air Flow.
The problem is you dont know VE so Mass air flow cant be calculated. As a starting point, If I have ever needed to build a starting map I would typically build my basic fuel map based on VE, using say 50% at idle ramping up to 100% at peak torque and drop back to 90% at redline, that will get you something that will run the engine. Then you have to tune it from there. I have seen various excel based fuel map calculators around but I doubt any will give you anything much closer than my guess approach above. With link there are also many base maps supplied you with the software so I would suggest you just copy a fuel map out of one of these that is a similar config to your engine and change the master fuel until it runs.
-
Still set up an analog input as a AC pressure sensor but you don't need to connect a pressure sensor. On the analog input setup screen set the hi and low error volts so that it is in error condition full time (say both at 2V), then set your error pressure value to a pressure that will allow your system to run (ie somewhere between your low and hi pressure lock outs).
-
If using the "traditional" fuel equation with the equation load source set to "MAP", then the MAP multiplication happens in the background. The number in the fuel table is percent of the master fuel number @ a MAP of 100KPa.
So to make that clearer, here's an example based on my simplified table shown below:
At 100KPa MAP & 1000RPM, my injector pulse width would be 100% x 8ms = 8ms.
At 50KPa MAP & 1000RPM, my injector pulse width would be 50KPa/100KPa x 100% x 8ms = 4ms
Note there are many other factors that come into the final pulsewidth such as all the comps/trims and open loop table, but this should give you enough info to understand how the main fuel table number works.
-
Can you do a PC log of it cranking for a few seconds and post that and your map here.
-
I'm just wondering if torque/load, TPS and vehicle speed over the CAN bus?
As far as I can see, the G4+ is capable of doing this with a user defined stream.
On the factory auto/DSG models there is also a Torque output from the factory ECU. I don't think this is in our CAN stream. I can check with the engineers when they are back after new years.
I think the existing "load (abs)" parameter would be almost directly proportional to torque output so you could probably use this to create the torque message. I think you could then just use the CAN multiplier/divider/offset to convert the load parameter into the correct range of "torque numbers" that the gearbox expects to receive. I have a hunch however it might not actually want just predicted "torque output" - I vaguely remember seeing parameters more like "driver requested torque" associated with the few gear shift controls I have seen. - But I reckon even that should be possible to simulate with the existing tools.
So the biggest challenge for the OP will be finding all the OEM CAN ID's and message structure etc and then finding someone who understands enough of it to translate it into the G4+ template and that will likely incur significant time and cost.
-
Both are fixed unfortunately. I can remember another forum member mentioning setting the cam sensor as a Hall effect rising edge? Would this have something to do with the zero crossings? The car runs fine with the crank sensor wires swapped then timing adjusted from -85 to 271?
With crank sensor swapped as you have now you will see massive timing drift vs RPM. There is another post here somewhere, where another user said setting the cam to hall got around the problem. (i will see if I can find it soon). I would only do so however if you get advice from Link support that it is ok to do this and it wont void your warranty. I dont know the internal trigger circuit inside the G4+ but with many ecu's you can fry them if you send VR voltage into a hall circuit. Another option might be to grind one side of the cam tooth a little which may offset that zero crossing enough. Also did you try changing trigger priority? that can sometimes help.
Edit - added later:
Here is the post i mentioned - it looks like you where part of that discussion anyway... http://forums.linkecu.com/index.php?/topic/6280-random-high-engine-rpm-data-logging/&do=findComment&comment=45071
Perhaps Simon can comment if it is acceptable to set the trigger 2 to hall.
-
I would like to be able to select functions for digital inputs via CAN. Like traction control disable switch.
It seems this is already possible:
Also I would like to be able to select different temp inputs under Analoge voltage via external pullup resistor. I want to have diff and gearbox oil temp and already have used the four temp inputs.
You can already do this too:
-
It is mentioned in the Help file for the GTR plugin but I agree it is not particularly obvious, I havent seen the paper manual for a long time so I'm not sure how clear or unclear that makes things.
4mm ID hose is what you want.
Once you connect this MAP sensor you may have to put your master fuel number back to where it was originally but it will hopefully now run pretty reasonable.
-
Jon,
Assuming your GTR/GTS plugin is reasonably new, it should have a map sensor built in the ECU (I think from memory some old revisions might not have had the built in MAP). Can you check if yours is as pictured below, the red circle is the MAP sensor, this is where your vacuum hose should attach, it sounds like you might be assuming some other sensor in the engine bay is the MAP sensor?
BTW, The fault code for the O2 sensor is not part of your problem so you can ignore that.
-
Jon, what ECU do you have - is it a PNP or wire in? Can you check if the MAP sensor has any numbers on it or maybe post a photo?
A quick n dirty check you can do on the map sensor calibration is to view the "MAP" runtime value on the main tuning screen, like below:
With ignition on and engine not running it should read about 100KPa (+/-~10).
Then if you suck on map sensor hose with your mouth you should be able to pull it down to roughly 70KPa, and if you blow, about 115KPa at a guess.
iVTS on V-series
in ViPEC V Series
Posted
iVTS is only for the newer i88 & i44. For the V88 you need the old VTS software. Try the the latest version (4.10) first which you will find here: http://www.vi-pec.com/software/vts-v4-10-2.1784
This version 4.10 may not work if your ecu is still running very old firmware but start with that and it will give you an error message if you need an older version.
Once you have successful connection to the ECU, follow this guide on how to do a PC log and download the map: https://www.youtube.com/watch?v=_P1LRANeO4A Post the map and log here and one of us might be able to help.