Vems
Collapse
X
-
the old linkECU had that issue too 255 was to set as max.
not used vemstune myself prefer megatune. had my first go with vemstune on S2Martyns's UR last week. im not a fan yet but i always liked windows 3.1 also.
i found that the usb-serial adapter is nowhere near as good as serial straight on vemstune. Martyn couldn't get a good connection with the USB.
im gonna go 1.1.57 maybe at weekend. im gonna scale my map and lower the REQ_Fuel numbers and have a play in general.
shame vems is so easy as it makes for lazy gazzaComment
-
There was a topic about how to imporve connection via USB->SERIAL for VemsMT/VemsTune (@VEMS forum). Do as search
Upd:
I hope this helpsCommunication problems with MegaTune using USB - RS232 converters are common.
It all comes down to how the converters work due the vast speed differences between the 2 interface types.
As USB is sooo much faster, what the adapter does is store a bunch of data internally (buffer) and then transmit it all in one go either when the buffer is full or after a time out. This buffering is what is messing stuff up.
The RS232 setting you gave are right and flow control should be set to off.
To fix the problem may needs admin right on your laptop, so as it is a work machine that may be an issue.
What you need to do is go into the device manager, select the USB com4 port, go into properties, then port settings, then Advanced, then reduce the buffer size (both if receive and transmit are listed seperately) to minimum (1msec).
This will then mean that as the ECU send or receives data it will get dealt with by the PC straight away instead of waiting for a load to get stored up then sent in one great big chunk.
Hilly
Comment
however, thanks!
Comment