Hello All,
My Name is Jens and live in Denmark. I´m here because interest and because I´m stuck with my Vems project.
Project Car:
Nissan 200sx Ca18det 1992 EU Model.
Norris Designs 2009 Fast road engine with H steel rods.
GT2860RS, 550cc injectors, big intercooler/oil/water, 60mm TB, Ca16de inlet cam on 118", 3" Exhausts and Cat.
Transmission: 5.5Kg flywheel, Exedy Paddle clutch, Kaaz 1.5 LSD.
Suspension: HSD coilover.
Brakes: Front 299x32 sky brakes.
Wheels: Rota et10 16x8 Toyo/R888 225/45.
I am totally new in the world of engine management.
I use most of the original wiring with an adapter connection.
Vems:
Assembled v3.6 controller prepared for 300kpa, 2xEGT, knock and lcd.
Nissan 24slot+sync CAS trigger.
LSU4 Wideband.
MAT sensor.
Pneumatic valve 3way.
I have connection between my PC and Vems Controller.
Megatune2.25
VemsMT?1.1.27beta2
Vems Genboard V3 16x14 High-boost
Config: http://www.vems.hu/filethingie.php?action=list&subdir=jensdahl
JensDahl
The 2-April-10 progress.
I read:
Engine Speed: 220Rpm at the starter.
Throttle Position: OK
Spark Angle: 0deg
Pulse Width: ?
Engine Map: 1.025Kpa
Manifold Air Temp: 21C Outdoor temperature was 10C
Coolant Temp: 22C Outdoor temperature was 10C
Battery Voltage: 12V- 13.5V
Today I tried to find cyl.1 TDC on the pulley with strope but even if I have spark at spark plugs the mark.0 fly around on the pulley.
I tried to adjust the 'TDC after the trigger(deg)' from 0-127.5
I had a few days ago a good stable signal but my settings in "Ignition outputs" were wrong.
I adjusted Coil4 after Cyl1.
New adapter connection
cyl2 ec36 pin35
cyl4 ec36 pin12
cyl3 ec36 pin33
cyl1 ec36 pin24
Ignitions outputs
0 ec36 Pin 35
5 ec36 pin 12
1 ec36 pin 33
6 ec36 pin 24
I hope that someone has time to read my config please.
I opened your msq with my 1.1.27 megatune and get 35 error messages. Your msq is full of scratch.
Could you try to find some working msq and start from it?
May be ask some help to Rob. I think he had plenty of Nissans on 1.1.18 - firmware close related to 1.1.27
First up - do you have one of my 24+1 CAS disks?
Next - Gints is correct, you need to get things working with 1.1.18
Yes the trigger disks is from you Rob (skassa) Rob can you help with a running config. Also the adapter maybe not made the way rob use to make them. As I know he have a stabile trigger signal and ignition is firing as the should due.
Quote from: [email protected] on April 05, 2010, 01:04:17 AM
First up - do you have one of my 24+1 CAS disks?
Next - Gints is correct, you need to get things working with 1.1.18
It should work on 1.1.27 too. I had some cars on coil type triggers on this f/w. But not Nissan.
Thanks for the fast response.
Quote from: [email protected] on April 05, 2010, 01:04:17 AM
First up - do you have one of my 24+1 CAS disks?
Yes, as Peter writes ;D is an easy replacement.
Quote from: GintsK on April 04, 2010, 04:46:11 PM
I opened your msq with my 1.1.27 megatune and get 35 error messages. Your msq is fulchl of scrat.
???
QuoteMay be ask some help to Rob. I think he had plenty of Nissans on 1.1.18 - firmware close related to 1.1.27
QuoteNext - Gints is correct, you need to get things working with 1.1.18
QuoteIt should work on 1.1.27 too. I had some cars on coil type triggers on this f/w. But not Nissan.
Should I download 1.1.18 from
http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FFirmwareChanges
and then use it as I'm using 1.1.27
I bought yesterday a new quality battery because the old quickly lost power when I adjust the ignition.
Perhaps it has made it unstable.
It would be ideal for you to start with a known working config yes.
Then later you can upgrade.
Quote from: gunni on April 05, 2010, 07:42:33 PM
It would be ideal for you to start with a known working config yes.
Then later you can upgrade.
But how do I get a known working config.
Can I just "steal" a config from a Nissan Ca18det profile.
Ok! I will try firmware 1.1.18 later today with my new battery and a better ground connection to the coils.
Try this:
http://www.vems.co.uk/VEMSInstalls/VemsMT1.1.18Nissan.zip
Quote from: [email protected] on April 05, 2010, 08:50:13 PM
Try this:
http://www.vems.co.uk/VEMSInstalls/VemsMT1.1.18Nissan.zip
Thanks Rob ;D
I'll be back
It does not work for me.
I get all sorts of warnings and even my small screen mouse becomes nervous and starts shaking.
When I try to run "download-config" I get back "overwriting saved config"
And when I try "generate-config" I get back "Something went wrong with the download config.bat"
With "upload config" I get back "no access through COM4"
Maybe everything as it should be?
For the first time since I got the connection between my PC and Vems 8 days behind, I have been close to going berserk.
It should have been a diy intimate experience between me and my car.
But now I'm close to finding another solution.
I would not recommend using MegaTune at all, the test versions of VemsTune are a much better and less frustrating method. All the functionality you are looking for is integrated.
http://www.vems.hu/download/v3gui/
Check the download link regularly, download and use the latest one, remember to use the built-in firmware web tool to download the firmware you want to work with, the recent 1.1.70 is recommended (or 1.1.18 if you feel like going medieval).
Someone should make a configlet for the Nissan trigger. I would if I had a car to upgrade to 1.1.70.
Mattias, IMHO you are too optimistic. :)
VT still have stability problems. It do not work on dual cores. It hangs time to time on older PCs too. It have problems with communications. E.g. my prolific works OK, but FDTI - not. Instead - MT works with any. For me different hot key configuration cause headaches.
I will try 1.1.70 with VT and write my review shortly. More constructive than this post. I have some list on paper already.
Gints
Still struggling
I use this:
http://195.159.109.134/vemsuk/forum/index.php/topic,120.0.html
1.Download the configs And Tables = OK
When I come to this:
2. Generate the configs and tables
I save: config.txt = ok
And going to save tables.txt
"Warning: table t has less than 8 items
Table l contains too many rows, it should have no more than k table has columns "
I run generate-config = No error messages.
3.Upload the firmware
I double clicking on upload-firmware (I have not upload-firmware12x12.bat)
Unable to open COM port: COM4
I'm connected to Vems
TB. is moving on PC :D
Port COM4 / data rate 19,200
Quote from: GintsK on April 06, 2010, 04:40:38 PM
Mattias, IMHO you are too optimistic. :)
VT still have stability problems. It do not work on dual cores. It hangs time to time on older PCs too. It have problems with communications. E.g. my prolific works OK, but FDTI - not. Instead - MT works with any. For me different hot key configuration cause headaches.
I will try 1.1.70 with VT and write my review shortly. More constructive than this post. I have some list on paper already.
Gints
I may be lucky to have a pretty solid mobile platform then, it's single core Pentium M 1.5 GHz running Windows XP with a Prolific adapter.
Did you know the hotkeys are configurable ? ;) (Tools -> Gauge group editor)
Anyway, look out towards the weekend when another test release will come - you may want to verify all your problems against that version, but please submit your list for the current 2010-03-08 version as well, ASAP in fact as Emil is in Budapest and pushing things along!
Quote from: [email protected] on April 05, 2010, 08:50:13 PM
Try this:
http://www.vems.co.uk/VEMSInstalls/VemsMT1.1.18Nissan.zip
Nothing happens when I press "download-config"
Overwriting saved config
Quote from: mattias on April 06, 2010, 07:20:00 AM
I would not recommend using MegaTune at all, the test versions of VemsTune are a much better and less frustrating method. All the functionality you are looking for is integrated.
http://www.vems.hu/download/v3gui/
Check the download link regularly, download and use the latest one, remember to use the built-in firmware web tool to download the firmware you want to work with, the recent 1.1.70 is recommended (or 1.1.18 if you feel like going medieval).
Someone should make a configlet for the Nissan trigger. I would if I had a car to upgrade to 1.1.70.
Mattias think you 1.1.70 could work for me?
And can it work with Nissan 24slot 1 CAS trigger made by Rob
What about the config and tables to ca18det
Best regards
Jens
Take the config.txt and tables.txt from that zip file I linked to - and store them somewhere.
Use VEMSTune to upgrade to 1.1.70 and read through this http://www.vems.hu/wiki/index.php?page=VemsTune/FirmwareUpgradeExample
Rather than copy the config, drag your config on to the main screen and you will be prompted to upload it.
Jens: Do what Rob says. ;)
Quote from: [email protected] on April 08, 2010, 01:35:33 AM
Take the config.txt and tables.txt from that zip file I linked to - and store them somewhere.
Use VEMSTune to upgrade to 1.1.70 and read through this http://www.vems.hu/wiki/index.php?page=VemsTune/FirmwareUpgradeExample
Rather than copy the config, drag your config on to the main screen and you will be prompted to upload it.
config.txt and tables.txt is it the same as config.mtt and tables.mtt ?
cause I can´t find the txt files
I just downloaded the zip file and in the config directory I see:
config.mtt
config.txt
configKevDuckworthIdling.txt
tables.mtt
tables.txt
tablesKevDuckworthIdling.txt
wbo2defaults.txt
Quote from: [email protected] on April 08, 2010, 05:31:31 AM
I just downloaded the zip file and in the config directory I see:
config.mtt
config.txt
configKevDuckworthIdling.txt
tables.mtt
tables.txt
tablesKevDuckworthIdling.txt
wbo2defaults.txt
OK! With me is that just called:
wbo2defaults
tablesKevDuckworthIdling
tables
tables.mtt
configKevDuckworthIdling
config
tables.mtt
But thanks again Rob
That's just Micro$oft Windows f**cking with you. Make sure to disable the explorer feature that hides filename extensions, and apply that as the global default.
Quote from: mattias on April 08, 2010, 04:17:36 PM
That's just Micro$oft Windows f**cking with you.
I can not connect 1.1.70 / Windows7 / USB with Vems controller.
1.1.18 connects fine.
I'll try the new VEMSTune 13 April 2010 tomorrow
Quote from: Pedersen on April 14, 2010, 08:09:19 AM
I'll try the new VEMSTune 13 April 2010 tomorrow
No connection with new VemsTune ???
USB-RS232 adapter can only be set to Port COM3, COM4, COM5, COM6 as there are 4 USB ports
VemsTune, "ECU Communication":
(X) Serial
Port: COM4
Preferred baudrate: 9600/19200
Timeout (ms): 15
Ignored real-time error count. 3
Internal write delay (ms): 25
SD CARD baud Rate: 115200/57600
ECU not found: 100.0
Default Protocol
Protocol: SIPR
Default read realtime command
read real time: SIPR_RT_MT_EXT.
I bought an old Dell D600 with XP and serial.
Now works both Mega Tune and Vemstune smoothly.
Quote from: [email protected] on April 08, 2010, 01:35:33 AM
Take the config.txt and tables.txt from that zip file I linked to - and store them somewhere.
Use VEMSTune to upgrade to 1.1.70 and read through this http://www.vems.hu/wiki/index.php?page=VemsTune/FirmwareUpgradeExample
Rather than copy the config, drag your config on to the main screen and you will be prompted to upload it.
What should I do with tables.txt
Quote from: Pedersen on April 17, 2010, 06:53:33 PMWhat should I do with tables.txt
Drag it onto the main window with your ECU online.
Quote from: mattias on April 18, 2010, 02:48:56 AM
Quote from: Pedersen on April 17, 2010, 06:53:33 PMWhat should I do with tables.txt
Drag it onto the main window with your ECU online.
OK! Thanks Mattias. ;D
Vemstune run well and all sensors working fine..... but I have no contact with Wideband O2 sensor.
When I run "WBO2 Calibration" in the "tools" I get no readings on O2 gauge, but I can feel that the sensor gets hot.
Quote
Vemstune run well and all sensors working fine..... but I have no contact with Wideband O2 sensor.
When I run "WBO2 Calibration" in the "tools" I get no readings on O2 gauge, but I can feel that the sensor gets hot.
Now fine at 20.9% ;D
A big victory for a small car .....
I have more questions?
1: What should be the "primary trigger settings" 24+1 Trigger
Trigger Edge = Rising
TDC after the trigger = 60 deg.
First tooth trigger = 2
Next trigger tooth = 6
Angular Width Of Tooth = 30.00 degree
Crank My. Period = 768 USEC
2: Ignition Settings <=> Ignition Dwell Settings?
Coil charge
[email protected] = 1.98 ms?
Coil Charge Time Map Scale = 10?
3: Knock Knock Sampling & Control Action ???
I have today made a very serious attempt to start the engine.
Everything is as it should be Engine Map, Lamda, TP, MAT ..................
Engine Speed Rpm shows 230 cranking.
PULSE WIDTH 1-2 cranking on gauge ???????????????
I read 20 degrees at the crankshaft with a light gun Cyl1.
Fuel pump works and plugs smell of fuel.
No signs of firing.
I've tried to advance ignition 360 crank degrees.
No signs of firing.
Here's the Config
http://www.vems.hu/filethingie.php?action=list&subdir=jensdahl
JensDahl
VemsTune 1.1.70
First of all, NEVER power your injectors until you have verified that the ignition fires at the right instance for each cylinder.
Secondly, 1-2 ms is not enough fuel.
I can take a look at your config later, probably something easy hiding there.
Remember that it's even better if you upload just a log file, the vemslog format also contains the configuration, while letting us see what you experienced.
I have started the engine.
It has only been running a few minutes and sounds good.
When the engine has been running a few minutes get the problems with idle.
I'm having trouble uploading log file
I am so happy
Thanks for everything
Suggests that the problems start when the afterstart/warm-up enrichments tail off.
Hi Jens
a lot of things have to be corrected in your setup:
Disable SD card log (ecu logger)
Primepulse = 0
Crank ve = 60 %
Add some data to the Warm-up enrichment curve.
Degrees from -30 to +70
amount from 185% to 100%
You may have to put a smaller amount in the Ve table.
In the log it seams that you ran out of fuel is your fuel pump running and making pressure.
Log http://www.vems.hu/files/MembersPage/JensDahl/v3.3_n002625-2010.04.28-15.08.45.zip (http://www.vems.hu/files/MembersPage/JensDahl/v3.3_n002625-2010.04.28-15.08.45.zip)
Quote from: [email protected] on April 28, 2010, 09:53:07 PM
Suggests that the problems start when the afterstart/warm-up enrichments tail off.
Yes Rob, problems began at 40 degrees, I've tried to give a little more fuel.
Quote from: peter_jensen on April 29, 2010, 05:05:29 AM
Hi Jens
a lot of things have to be corrected in your setup:
Disable SD card log (ecu logger)
Primepulse = 0
Crank ve = 60 %
Add some data to the Warm-up enrichment curve.
Degrees from -30 to +70
amount from 185% to 100%
You may have to put a smaller amount in the Ve table.
In the log it seams that you ran out of fuel is your fuel pump running and making pressure.
Log http://www.vems.hu/files/MembersPage/JensDahl/v3.3_n002625-2010.04.28-15.08.45.zip (http://www.vems.hu/files/MembersPage/JensDahl/v3.3_n002625-2010.04.28-15.08.45.zip)
Peter thanks for uploading my log file .....
I am 100% sure that the fuel pump running, because I can keep it running with my right foot.
Smaller amount in the Wo table .... Can you be a little more accurate 10% of everything ....
Ok my Warm-up enrichment is also nearly flat at 105%
Disable SD card log (ECU logger)
Prime Pulse = 0
Crank vc = 60%
Ok! I can not do wrong
Now is the time to keep an eye on what the dials are doing.
You'll either see the injector PWs drop and the engine stall.
Or they'll remain fine, and something related to the ingition or IAC will be causing the issue.
New Vemslog.
http://www.vems.hu/filethingie.php?subdir=MembersPage/JensDahl
1. Starts easily with a little help from the accelerator.
2. Drove idling reasonable stable up to 80 degrees when it became unstable. Lambda and spark angle gauge began to jump.
Not a big problem but clearly hear it.
3. Took it to 95 degrees when I started cooling fan. and let it fall to 84 degrees.
Maybe the engine sounded a little more stable at the end.
4. I tried gently to tread a little on the accelerator .... The engine dies immediately!
It appears that lambda move just when I touch the accelerator.
http://www.vems.hu/files/MembersPage/JensDahl/2.zip (http://www.vems.hu/files/MembersPage/JensDahl/2.zip)
Jens log correct ulr.
Hi Jens
Hint.
Make the ve table a bit smaller amount like 50 and the other cells close to that value. Its important that the values not jumping around but must be smooth
Disable “ECU calibration†“Map filter†Triggers Num for map filter = disable and map samples per trigger = 1
There is a trigger error at 1:20
Take my config and drag some reasonable defaults to some dialogs, the acceleration enrichment is just not configured at all and there is too much warmup enrichement.
Look over the "Assign Output Channels" dialog under the "Outputs" menu, disable all items that you do not use.
The ignition table is just scary, too much advance for this engine overall.
The VE table, try 60-70 % overall, this engine has a very flat map.
The map filter is nice, just set them to the recommendation in the "F1 for help" dialog, which is 1 and 15. Don't disable it.
Mattias
QuoteTake my config and drag some reasonable defaults to some dialogs
I can not read your 200sx-config from Vems.hu
http://www.vems.hu/files/MembersPage/MattiasSandgren/MattisNissan/
Yes I can read it but I do not understand all the codes.
QuoteLook over the "Assign Output Channels" dialog under the "Outputs" menu, disable all items that you do not use.
All right. I did not know it had a significance
QuoteThe ignition table is just scary, too much advance for this engine overall.
yes it is not good
QuoteThe VE table, try 60-70 % overall, this engine has a very flat map.
I will work with that
QuoteThe map filter is nice, just set them to the recommendation in the "F1 for help" dialog, which is 1 and 15. Don't disable it.
I will do tomorrow
Thanks Matt :)
I have today been playing with my VE table and ignition table and I can now idling up and down between 900-4500 rpm, with a lambda of about 1
When I give the accelerator a little pressure makes the engine to do a little dive and I get strong movement on my lambda-gauge for about 1 sec before it becomes stable again.
New Vemslog tomorrow.
Good weekend
Quote from: Pedersen on May 01, 2010, 05:55:08 AM
Mattias
QuoteTake my config and drag some reasonable defaults to some dialogs
I can not read your 200sx-config from Vems.hu
http://www.vems.hu/files/MembersPage/MattiasSandgren/MattisNissan/
Yes I can read it but I do not understand all the codes.
I should have specified that I meant the config I have linked to in my signature, so far over 100 downloads on that one.
New Vemslog from my first test drive today.....
Runs better now than with an Ebay chip I have run with the same engine setup.
However, it is not good when I press the throttle from under 1000Rpm.
http://www.vems.hu/files/MembersPage/JensDahl/v3.3_n002625-2010.05.02-11.03.18.zip
Please be specific about what changes you make to the config, to make it easier to understand what's been "fixed" or not. When I make a suggestion, please comment on what you did about, or just your reflection upon it.
It's quite apparent that you changed a lot this time. I think you have to look over your acceleration enrichment, I think there is just too little. Adjust the two tables; to match your throttle movement in the first table, and then increase the values in the added amount table.
Your "RPM actuator" output channel still reads "INVALID", change it to "Disabled". Also disable all other outputs you know you are not using. This is on top of the list of things to fix before even starting the engine the first time. You never know how things are involved.
Under the dialog "display settings", you could disable AIM. It should work but there have been known problems with serial communication - until it's known to be safe, please disable it.
New Vemslog from my second test drive.
http://www.vems.hu/files/MembersPage/JensDahl/v3.3_n002625-2010.05.03-20.27.32.zip
Quote from: mattias on May 02, 2010, 05:59:21 PM
Please be specific about what changes you make to the config, to make it easier to understand what's been "fixed" or not. When I make a suggestion, please comment on what you did about, or just your reflection upon it.
It's quite apparent that you changed a lot this time. I think you have to look over your acceleration enrichment, I think there is just too little. Adjust the two tables; to match your throttle movement in the first table, and then increase the values in the added amount table.
Your "RPM actuator" output channel still reads "INVALID", change it to "Disabled". Also disable all other outputs you know you are not using. This is on top of the list of things to fix before even starting the engine the first time. You never know how things are involved.
Under the dialog "display settings", you could disable AIM. It should work but there have been known problems with serial communication - until it's known to be safe, please disable it.
Mattias
I will try to be more precise with my changes.
1) I have Disabled RPM actuator and Boost control that I do not use them.
2) AIM. disable too.
3) Acceleration Dot vs. Scale
Tps speed first block 2 instead of 5
4) Acceleration RPM vs. Amount.
RPM speed. first block 1000 down to 800Rpm
5) ECU calibration
Mapfilter.
Trigger 1 and map Samples 15 as Mattias suggested.
I seemed to vibrate slightly during acceleration maybe it's just me who can not remember how hard the car is.
Run the VE analysis on that log and you'll see what you ought to fix. Basically, add 20 % (+/-10%) VE from 1200 rpm to redline, and even more than that above atmoshperic (100 kPa line).
(http://www.savarturbo.se/~mattias/motor/vems_data/vemstune-dev/pedersen-analysis.png)
I'm kind of surprised that EGO correction doesn't catch up with you but I didn't give enough time to hunt down what setting caused that. You can clearly see in that screenshot that the marked instance has 15% EGO correction, so.. simply increase VE by that amount in that VE map cell.
OK Matt, I will work on that now - Thanks :o
My last Vemslog from last weekend.
The car running really really well although I can see that there are several things to be adjusted.
http://www.vems.hu/files/MembersPage/JensDahl/v3.3_n002625-2010.05.09-13.18.42.zip
You are letting EGO correction work for you, make sure that you only use "VE tuning by statistics" where you know you have held a steady or slowly accelerating load.
Skip correcting the sites that have:
Few hits (lower left corner)
High variance (lower right corner)
(http://www.savarturbo.se/~mattias/motor/vems_data/vemstune-dev/ve-tune-bad.png)
Correct the sites that have many hits and and low variance :
(http://www.savarturbo.se/~mattias/motor/vems_data/vemstune-dev/ve-tune-good.png)
A high variance is usually an indication of acceleration enrichment or rarely visited (highly transient) cells. These cells must be tuned manually, interpolate their value to match neighbouring cells that have more confident values. Always check the 3D view of the VE table, it will tell you if something is out of place. There are a few such places in your VE map.
VE rarely goes down with increasing pressure unless it's a turbo engine that is a victim of too much back pressure. VE is very linear. Chances are your tuning would be easier with fewer cells, it's such a simple engine.
Thanks Mattias
I will run some more log and avoid Aacceleration Enrichment and fuelcut throughout the area.
Is possible to filter out the acc. enrichement-ed values with aid of acc, enrichment gauge?
It already does a pretty good job of filtering those out, just don't trust a computer to do your job.
Use your intuition, correct the cells with more hits than the others and low variance. Manually edit the table to smooth out the cells that are rarely visited (and not auto-corrected).