Hi there,
I have been having some communication problems between my ecu and the laptop. I have checked that they are both using the same port but keep getting a "no response" message when testing the connection. Having read some other people's issues with the same problem it would appear that the usb to serial adapter is causing a bit of a headache across the board. I'm using version 1.0.69 of megatune. I'm assuming I probably just need to find a serial cable to fit straight into the serial port on the laptop to be sure that's what the problem is, yes?
Any other suggestions would be gratefully received?
Have a good weekend everyone,
Al.
Alan,
You should be using the MegaTune that comes with 1.1.18:
http://www.vems.co.uk/VEMSInstalls/VemsMT1.1.18Nissan.zip
If you have a serial port on the laptop then use that every time, you need a 'straight-through' RS232 cable - that is pin2->pin2, pin3->pin3 and pin5->pin5
Hi there,
Thanks for the help, although sadly it doesn't appear to have changed matters. I have now tried with a laptop that has a serial input but i still got the same message of no response. Hmmm....not really sure where to go from here. I'm assuming that there's no coding that is required at this early stage...in theory at least? I've also tried messing around with different port numbers to no avail...
Have just been checking connections etc and there's continutity from the serial input to the vems unit so that rules out an ill functioning serial wire...
The way i got mine talking was; open the vems software, open the megatune folder then mtCfg, then there should be a file called "megatune.cfg" open it with notepad and the first line of text will tell you the com port it is using.
I left this as it was then plugged in the usb/serial converter, opened the device manager on the pc, look in ports (COM &LPT), right click on "USB Serial port" open properties then port settings, click advanced, then change the COM port number to whatever the megatune file stated! (i ignored the warning about sharing ports etc.)
It worked for me :) so might be worth a try.
Sweet, I will give that a try tomorrow. I was disappointed with myself for falling at the first hurdle but hopefully your method may resolve my problem. Many thanks:)
I'm not trying to be a prune here, but double check that 2&3 are not crossed or shorted.
And if you check Nismo's thread I've written a few words on how to use the Serial port program: Terminal to see if you have a good connection.
The saga continues....
Ok, tried your method Nismo, as well as varying combos, and had no joy sadly.
Tried the terminal program too. It said connected and would transmit but wouldn't receive. i was typing "Man" as suggested by rob. I assume that's the test code as it were? I checked the settings at the top of the page and it was all as suggested in Nismo's thread. Hmm...
Had a gander inside the serial cable too - there's no apparent shorts and the earth wire is making a good connection. The Tx and Rx wires do go to the right pins on the serial and the econoseal connector.
As the tree said to the lumberjack....I'm stumped....
Also meant to say that I got a random warning message that may shed some light on the situation: It only happened twice but it said:
Controller code version does not match signature in vemsv3.ini (see audit.log for where the above file was found)
Expected " vems v1.1 12x12 kpa = 2,2" (found in ini file)
Received "0x51" from controller table" Table corruption may occur. This is usually serious.
Terminate?"
I was worried to say the least....
Hi,
I've seen that one too ;)
It's basically telling you it's the wrong MT for your ECU.
Have you changed the firmware in the ECU since you've had it?
Mine came with something like 1.0.53 in it, I had the same problems as you until I used an "old enough" MT
Cheers,
Gavin :)
I haven't changed the firmware as I only began trying to connect it a couple of days ago but I've been using the version recommended by rob (1.0.89 off the top of my head). Can you remember what version it was that worked with yours please?
It's also stopped asking me which table I wish to select (12x12 etc) Is this a syptom of anything in particular?!
Cheers for the help:)
Hi,
Just checked mine was 1.0.53, it came direct from VEMS.
If yours came from Rob he may have upgraded it for you?
Try 53 won't hurt, I just kept trying different ones till I got it talking.
You do have to be using the correct com port though or you'll never get it talking.
You'll need to change the com port number in each version you try ;)
Cheers,
Gavin :)
Cheers mate, I will give that a try tomorrow. Hopefully it'll have stopped raining by then! :-[
The Nissan trigger only works with 1.1.18 firmware, the link in the previous posting gives you the zipped software.
Those messages do indicate that the VEMS and Laptop are communicating, as the signature from the VEMS is being read when asked for.
You will want to select 12x12 High Boost for your setup.
BTW 1.0.53 is in serious need of an upgrade to 1.0.73, they seem to shove on any old firmware for testing in Hungary.
Quote from: [email protected] on February 26, 2008, 08:35:02 AM
BTW 1.0.53 is in serious need of an upgrade to 1.0.73, they seem to shove on any old firmware for testing in Hungary.
Hi,
That's what made it difficult to start with, I never expected to need a version that old! :o
Running 1.0.73 now ;)
Cheers,
Gavin :)
Quote from: young_un1 on February 25, 2008, 06:21:45 PM
Also meant to say that I got a random warning message that may shed some light on the situation: It only happened twice but it said:
Controller code version does not match signature in vemsv3.ini (see audit.log for where the above file was found)
Expected " vems v1.1 12x12 kpa = 2,2" (found in ini file)
Received "0x51" from controller table" Table corruption may occur. This is usually serious.
Terminate?"
I was worried to say the least....
If its said this then you have had MegaTune start-up, open the serial port, send the VEMS a versionInfo request, and the VEMS respond with 'something'.
Ok, the saga continues....
Firstly, many thanks to rob for his time checking over the serial connection on the VEMS unit.
I was hoping that there would be something wrong with the unit but everything is working fine on the test bed so the question remains...why cant I connect to the VEMS Unit from my laptop?
Has anyone had a similar experience? The terminal program shows that the serial port is working, however I cannot get a "Success!" message when testing my com links.
I have checked the .cfg files and the first line is displaying the same com number as I am trying to use.
I have tried multiple laptops as well as different usb serial and pcmcia to serial adapters but am getting the same problem.
The earth is also strong and shows good continuity throughout the vehicle.
I'm at a loss as to what else to try.
Does anyone have any suggestions please? It doesnt matter how wacky or far flung they are; i'll try anything at this point - I just want to hear the car run!!!!
Many thanks,
Alan
Hi,
I'm no expert on this, but it seems to me you're using the wrong version of MT.
The serial program isn't bothered what version of firmware the ECU is running, but MT won't play ball unless both ECU and MT versions match.
Cheers,
Gavin :)
Damn! This is really puzzling...
Bearing in mind what Bat has jus written:
http://www.vems.co.uk/VEMSTech/VemsMT1.1.18.zip
Thats the right one to use, its the same as was on the CD that came with your ECU
If you are getting the Hello response in terminal and then go directly to MegaTune then you'll never get a response.
Make sure that you type byebye then click disconnect, and then close Terminal before you start-up MegaTune
Rob
Well the good news is that I've finally managed to get the laptop and VEMS unit to connect successfully!
The bad news is that I'll probably be asking you guys lots more questionos from now on:)
To that note: have been doing the usual things like calibrating the TPS etc today however I haven't burnt the settings to the ECU as I'm worried that I'll end up overwriting the values already loaded up by Rob. I noticed that the fuel cut value was showing up as 23300 rpm and I'm assuming that the map you already loaded has a sensible value for this, which I dont want to lose. If i click burn to ECU will i have a fuel cut at 23k rpm?! Sorry this is probably a silly question...
Quote from: young_un1 on March 07, 2008, 06:51:49 PM
Well the good news is that I've finally managed to get the laptop and VEMS unit to connect successfully!
The bad news is that I'll probably be asking you guys lots more questionos from now on:)
RESULT 8)
Quote from: young_un1 on March 07, 2008, 06:51:49 PM
To that note: have been doing the usual things like calibrating the TPS etc today however I haven't burnt the settings to the ECU as I'm worried that I'll end up overwriting the values already loaded up by Rob. I noticed that the fuel cut value was showing up as 23300 rpm and I'm assuming that the map you already loaded has a sensible value for this, which I dont want to lose. If i click burn to ECU will i have a fuel cut at 23k rpm?! Sorry this is probably a silly question...
Go ahead an burn away - I have a backup of the settings here. But you should also make backups as you go - use download-config.bat and rename the config and tables files to something memorable before each change.
Fuel Cut is at 25500 as a rule - this is effectively turned off, which is the idea as you dont want a feature like that activated until you've got some of the tuning done.
Questions are good, please put them into your project page or a pertinent section in the forum, then it makes the questions and answers easily available to others.
Rob
Awesome, time to tinker!
Am I right in thinking that I will need to calibrate / adjust the following before cranking and hoping it fires using the supplied nissan maps...
TPS
Battery Power
MAP
Injectors
I'm sure i've forgotten something...
I set the battery and MAP at the same time as calibrating the wideband sensor.
Setup the TPS.
Then the timing.
And then work out the Req fuel and we can start the firing up process :D
Rob