Pages: [1]
Author Topic: Calibration Interface vszw  (Read 7567 times)
phila_dot
Hero Member
*****

Karma: +172/-11
Offline Offline

Posts: 1709


« on: November 08, 2011, 05:08:35 PM »

How can we take advantage of the calibration interface vszw in ZUE from VS_VERST?

Is it possible to tune ignition angle live using the calibration interface?

Does anyone know what equipment is required for this (VS20?, VCDS?)?

vstdzw (TKMWL) also a calibration interface in ZUE, but this is one of the adaptation channels (lemmi).


Function VS_VERST is the only information that I could find in the FR.
Quote from: Funktionsrahmen
VS VERST 2.40 Calibration parameters for McMess

FDEF VS VERST 2.40 Function definition

Position | Label | adjustment variable | Initial Value | Size | limit        | Quantity / Increment | raster |% section
1        | vszw  | firing angle        |        0 KW   |Byte  |-96..95.25 KW |       0.75 KW        |        | ZUE


%VS VERST describes the parameters to be adjusted by means of McMess. The effects of the adjustment are described in the pertinent
sections on the individual functions (refer to above table in %Section).

The RAM cells are set once to the initialization values given above for the following conditions:

1. C ini
2. For B mcacti = 0 (McMESS is not active ). B mcacti is updated in the 1-sec time frame.
3. For entry and exit in McMESS communication (item 3 not applicable as required, corresponds to item 2).

If CWVSV = 0 VS VERST isn‘t active. Only for CWVSV > 0 adjustment with McMess is possible.


APP VS VERST 2.40 Application hint
The updating of the adjustment values ​​is dependent on the McMess communication (approximate value: about every 30 ms).
Logged
Gonzo
Sr. Member
****

Karma: +20/-30
Offline Offline

Posts: 483


« Reply #1 on: November 08, 2011, 09:11:32 PM »

I assume you need to a way to interface with McMESS first.

I think its pointless:
Quote
The Bosch McMESS-Protocol in the ME7
====================================

The McMESS protocol is a proprietary protocol of Bosch. It is a calibration protocol
for the K-line (should be same use case as the CAN calibration protocol CCP).
McMESS is used in the process of tuning and optimizing the ECU for a certain combination of
engine and vehicle model.  Normally a special application system of the vehicle manufacturer
will communicate with the ECU using McMESS over the K-line.

The name of the protocol would mean something like "microcontroller measurement protocol",
so "mess" stands for measurement (in german: "Messung").  But I think the english term "mess"
is quite good - it's just a mess. McMESS is a braindead, obfuscating protocol implementation.
It uses: 9bit transfer - hard to achieve on a PC, but possible when abusing the parity bit,
10400baud and 125000baud communication speed - the latter not possible with a standard PC serial port
(could be possible with USB-Serial converters or special serial itf cards or when using a microcontroller).

Mainly, the protocol provides the possibility to read and write values in the RAM, also while the engine
is running (change parameters in the ECU, log variables), but the reachable speed is not very high
(270..1000bytes/second). So most of this is not very interesting for normal tuning/logging purposes.
Taken from: http://nefariousmotorsports.com/forum/index.php/topic,778.0.html
Logged
phila_dot
Hero Member
*****

Karma: +172/-11
Offline Offline

Posts: 1709


« Reply #2 on: November 08, 2011, 09:47:17 PM »

Thanks.

I remember that thread, but never really read the attachment.

It does look basically useless for logging, but I think it would be very useful on the dyno.

Live tuning without emulation, what drawback am I missing?
Logged
TTQS
Guest
« Reply #3 on: November 09, 2011, 06:18:34 AM »

Live tuning without emulation, what drawback am I missing?

A 2 million Euro engine dyno cell as shown on page 22 of Engine Management: Advanced Tuning by Greg Banish? Grin

TTQS
Logged
NOTORIOUS VR
Administrator
Hero Member
*****

Karma: +58/-7
Offline Offline

Posts: 1056


« Reply #4 on: November 09, 2011, 10:00:48 AM »

Does this PDF help at all?
Logged

SCHNELL ENGINEERING BLOG ·  STANDALONE ECUS · TUNING · DYNO · WIRING · PARTS · VEMS
Google Talk: NOTORIOUS.VR
n00bs start here: http://s4wiki.com/wiki/Tuning
phila_dot
Hero Member
*****

Karma: +172/-11
Offline Offline

Posts: 1709


« Reply #5 on: November 10, 2011, 03:53:18 PM »

Does this PDF help at all?

Thanks. The documentation linked in this thread is all that I have been able to find and the FR refers to a VS20.

It sounds like maybe setzi has already put something together for this while working out his logger. I would try to put something together, but I have no idea where to start as far as communicating with the ECU.

Hopefully someone who has experimented with this will chime in.
Logged
phila_dot
Hero Member
*****

Karma: +172/-11
Offline Offline

Posts: 1709


« Reply #6 on: December 16, 2011, 04:43:11 PM »

VS_VERST Variables
|Position|Label|Adjusting   Variable|Initial   Value|Variable|Limit|Quant./Inc|Frame|Section|Notes
1vszwIgnition timing0° KWByte-96 - 95.25°KW0.75 ° KWZUEAdded to ZWAPPL to adjust zwbas
2vsfrkMixture factor1.0Byte0.75 - 1.250.001953ESGRUMultiplier for FRKAP (multiplier for KFLF)
3vsvwAdvancement angle0° KWByte-768° - 762°6° KWESVWAdditive for weenst for injection angle
4vsnsNominal speed0 RPMByte0 - 2550/min10 RPMLLRNSAdditive for nsol (idle reference speed)
5vszwkr[0]Ignition timing firing 1Byte-96 - 95.25°KW0.75 ° KWKRRAAdded to wkr[0] for dwkrz[0]
6vszwkr[1]Ignition timing firing 2Byte-96 - 95.25°KW0.75 ° KWKRRAAdded to wkr[1] for dwkrz[1]
7vszwkr[2]Ignition timing firing 3Byte-96 - 95.25°KW0.75 ° KWKRRAAdded to wkr[2] for dwkrz[2]
8vszwkr[3]Ignition timing firing 4Byte-96 - 95.25°KW0.75 ° KWKRRAAdded to wkr[3] for dwkrz[3]
9vszwkr[4]Ignition timing firing 5Byte-96 - 95.25°KW0.75 ° KWKRRAAdded to wkr[4] for dwkrz[4]
10vszwkr[5]Ignition timing firing 6Byte-96 - 95.25°KW0.75 ° KWKRRAAdded to wkr[5] for dwkrz[5]
11vszwkr[6]Ignition timing firing 7Byte-96 - 95.25°KW0.75 ° KWKRRAAdded to wkr[6] for dwkrz[6]
12vszwkr[7]Ignition timing firing 8Byte-96 - 95.25°KW0.75 ° KWKRRAAdded to wkr[7] for dwkrz[7]
13vskeKnock detection threshold0Byte-8 - 80.0627KRKEAdditive to kek
14vsdmrTorque reserve0 %Byte0 - 99.6%0.3906%MDKOLAdditive to mifal
15vsfpsesManifold air pressure1Byte0 - 20.0078AESps_w (int. manifold press) multiplier in calc. of inj on time
16vsrlmxmax.rl for LDR0%ByteConv.: rel sb q0p75LDRLMXAdditive to rlmax_w
17vsldtvTV LDR for appl. control0%ByteConv.:tv ub q0p64LDTVMABecomes input for KFLDRL?
18vswnwsAngle NW for VANOSBytewkw ub q0p250.25 ° KWWNWEINNot documented
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.528 seconds with 15 queries. (Pretty URLs adds 0.006s, 0q)