https://the07k.wiki/api.php?action=feedcontributions&feedformat=atom&user=ArteThe 07K Wiki - User contributions [en]2026-05-13T08:34:28ZUser contributionsMediaWiki 1.38.2https://the07k.wiki/index.php?title=File:Knock_control_map_list.pdf&diff=7749File:Knock control map list.pdf2026-04-27T13:24:27Z<p>Arte: Arte uploaded a new version of File:Knock control map list.pdf</p>
<hr />
<div></div>Artehttps://the07k.wiki/index.php?title=File:Knock_control_map_list.pdf&diff=7748File:Knock control map list.pdf2026-04-27T13:20:29Z<p>Arte: </p>
<hr />
<div></div>Artehttps://the07k.wiki/index.php?title=File:Tranny_swap_auto_to_02Q.docx&diff=7743File:Tranny swap auto to 02Q.docx2026-04-21T07:13:37Z<p>Arte: </p>
<hr />
<div>== Summary ==<br />
Transmission swap from auto to 02Q. This was provided by a member of the VW 2.5l Group<br />
<br />
PDF version available here: [[:File:Tranny swap auto to 02Q.pdf|File:Tranny swap auto to 02Q.pdf]]</div>Artehttps://the07k.wiki/index.php?title=File:Tranny_swap_auto_to_02Q.pdf&diff=7742File:Tranny swap auto to 02Q.pdf2026-04-21T07:13:02Z<p>Arte: Transmission swap from auto to 02Q. This was provided by a member of the VW 2.5l Group</p>
<hr />
<div>== Summary ==<br />
Transmission swap from auto to 02Q. This was provided by a member of the VW 2.5l Group</div>Artehttps://the07k.wiki/index.php?title=File:Tranny_swap_auto_to_02Q.docx&diff=7741File:Tranny swap auto to 02Q.docx2026-04-21T07:11:43Z<p>Arte: Transmission swap from auto to 02Q. This was provided by a member of the VW 2.5l Group</p>
<hr />
<div>== Summary ==<br />
Transmission swap from auto to 02Q. This was provided by a member of the VW 2.5l Group</div>Artehttps://the07k.wiki/index.php?title=Can-bus_emulation_for_cruise_control&diff=7693Can-bus emulation for cruise control2026-03-08T08:02:38Z<p>Arte: /* Emulating the cruise control switch */</p>
<hr />
<div>==Introduction==<br />
This is intended as a reference for those who would like to emulate the can-bus messages for the cruise control.<br />
<br />
'''Application''': Any swapped vehicles that do not have can-bus support. It would cover both the Bosch ME7.1.1 and a ME17.5/ME17.5.6<br />
<br />
==Hardware required==<br />
You can use any microcontroller that have CAN-bus capability, such as an Arduino or ESP32. You could also use the SpeedPulser Pro that already has a GPS and CAN-bus capability, you would only need to alter the source code and implement the new CAN-bus message:<br />
<br />
*https://forbes-automotive.com/products/speedpulser-pro<br />
*https://github.com/adamforbes92/speedPulserPro<br />
<br />
==CAN-bus: What is this sorcery?==<br />
CAN-bus is a network used by modules to transmit data/information with each other. With only two wires, you can transmit a multitude of messages between modules ([[wikipedia:Multiplexing|multiplexing]]).<br />
<br />
In the past, you would have a single wire for every input. In those instances, every button of your cruise control switch has its own signal wire.<br />
<br />
The '''objective''' of the CAN-bus emulation is to take all those signals, feed them into your microcontroller and output CAN-bus messages that the ECU will understand, as if it was on a factory MK5/MK6 2.5 chassis.<br />
<br />
CAN-bus messages required:<br />
<br />
#State of the cruise control switch (Ex.: Main switch, SET, RES, etc.), normally provided by the '''steering column module'''<br />
#Vehicle speed, normally provided by the '''ABS module'''<br />
<br />
==Vehicle speed acquisition==<br />
The vehicle speed can be retrieved through the following means:<br />
<br />
*GPS module<br />
*VSS sensor<br />
*Hall-effect sensor mounted into the instrument cluster to read the speed of the speedometer cable<br />
*There are more ways to gather this information depending on your creativity<br />
<br />
==Emulating the cruise control switch==<br />
The ECU receive the cruise control switch information through the CAN message '''0x38A'''. Here is a detailed description of this CAN message<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+ID '''0x38A''', '''4 bytes''', Sent every '''20 ms'''<br />
!Signal!!Byte!!Start bit!!Bits!!Range / Values!!Notes<br />
|-<br />
|Checksum (See below)||1||0||8||0..255 (Phys = Hex)||—<br />
|-<br />
|Main switch||2||0||1||0 = OFF<br>1 = ON||Latching ON/OFF<br />
|-<br />
|Tip switch OFF||2||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch DECEL||2||2||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch ACCEL||2||3||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Cruise decelerate (hold)||2||4||1||0 = not decelerating<br>1 = decelerating||—<br />
|-<br />
|Cruise accelerate (hold)||2||5||1||0 = not accelerating<br>1 = accelerating||—<br />
|-<br />
|Cruise control stalk error||2||6||1||0 = OK<br>1 = stalk error||—<br />
|-<br />
|Not used||2||7||1||—||—<br />
|-<br />
|Tip switch SET||3||0||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch RESUME||3||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Sender coding||3||2||2||00 = Body network<br>01 = Steering column module<br>10 = Engine||Values per spec<br />
|-<br />
|Message counter||3||4||4||0..15 (Phys = Hex)||Rolling counter<br />
|-<br />
|Not used||4||0||8||—||Byte 4 unused for this purpose<br />
|}<br />
<br />
===Checksum===<br />
The checksum is a formula used to validate the integrity of the message, and detect possible data corruption during the transmission of the message. If the checksum does not match the data, the ECU might reject the message. (Implausible message)<br />
<br />
[[File:Checksum GRAneu.png|747x747px]]<br />
<br />
This checksum is calculated only with Exclusive OR ([[wikipedia:Exclusive_or|XOR]]) operations<br />
<br />
===Code example===<br />
This is a very rough sketch to show a possible implementation. This example would be for an Arduino controller using a MCP2515 shield (hat).<br />
<br />
<syntaxhighlight lang="c" line="1"><br />
// demo: Cruise control switch, analog to can-bus message for VW PQ35<br />
// Very rough sketch, but should work. Feel free to improve<br />
<br />
#include <SPI.h><br />
<br />
#define CAN_2515<br />
<br />
// Set SPI CS Pin according to your hardware<br />
<br />
#if defined(SEEED_WIO_TERMINAL) && defined(CAN_2518FD)<br />
const int SPI_CS_PIN = BCM8;<br />
const int CAN_INT_PIN = BCM25;<br />
#else<br />
<br />
// For Arduino MCP2515 Hat:<br />
// the cs pin of the version after v1.1 is default to D9<br />
// v0.9b and v1.0 is default D10<br />
const int SPI_CS_PIN = 9;<br />
const int CAN_INT_PIN = 2;<br />
#endif<br />
<br />
<br />
#ifdef CAN_2518FD<br />
#include "mcp2518fd_can.h"<br />
mcp2518fd CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
#ifdef CAN_2515<br />
#include "mcp2515_can.h"<br />
mcp2515_can CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
const int buttonMain = 4;<br />
const int buttonRes = 2; <br />
const int buttonSet = 0;<br />
<br />
byte oldSwitchState = 0x0;<br />
byte sequence = 0x0;<br />
<br />
void setup() {<br />
SERIAL_PORT_MONITOR.begin(115200);<br />
while(!Serial){};<br />
<br />
while (CAN_OK != CAN.begin(CAN_500KBPS)) { // init powertrain can bus : baudrate = 500k <br />
SERIAL_PORT_MONITOR.println("CAN init fail, retry...");<br />
delay(100);<br />
}<br />
SERIAL_PORT_MONITOR.println("CAN init ok!");<br />
pinMode(buttonMain, INPUT_PULLUP);<br />
pinMode(buttonRes, INPUT_PULLUP);<br />
pinMode(buttonSet, INPUT_PULLUP); // default state 12v<br />
}<br />
<br />
void loop() {<br />
<br />
byte switchState = 0x0;<br />
<br />
// Read analog inputs<br />
int stateMain = digitalRead(buttonMain);<br />
int stateRes = digitalRead(buttonRes);<br />
int stateSet = digitalRead(buttonSet);<br />
<br />
// You can add more inputs and adjust the logic according the the can-bus chart<br />
if (stateMain == LOW) {<br />
switchState |= (1 << 0); // Set bit 0<br />
}<br />
if (stateSet == LOW) {<br />
switchState |= (1 << 1); // Set bit 1<br />
}<br />
if (stateRes == LOW) {<br />
switchState |= (1 << 2); // Set bit 2<br />
}<br />
<br />
<br />
// Check if the switch state has changed<br />
if (switchState != oldSwitchState) {<br />
Serial.println(switchState); // Print new state for monitoring purposes<br />
oldSwitchState = switchState; // Update oldSwitchState<br />
}<br />
<br />
// Define bytes for can message (0x38A)<br />
byte byteTwo = switchState & 1;<br />
<br />
byte byteThree = switchState >> 1;<br />
byteThree = byteThree | 0xC; // Could also be 0x4 (See Sender coding)<br />
byteThree = (sequence << 4) | byteThree;<br />
<br />
byte checksum = byteTwo ^ byteThree;<br />
<br />
unsigned char payload[4] = {checksum, byteTwo, byteThree, 0x00};<br />
CAN.sendMsgBuf(0x38A, 0, 4, payload);<br />
<br />
sequence = (sequence + 1) & 0x0F; // increment for the next frame<br />
<br />
delay(20); // Send every 20ms<br />
}<br />
</syntaxhighlight><br />
<br />
== Emulating the ABS module (Vehicle speed) ==<br />
The ABS module needs to be emulated as the ECU track the vehicle speed for the cruise control.<br />
<br />
In practice, it would be possible to do Assembly patches and make the ECU track the engine speed. Although, this extensive work would need to be repeated across multiple firmwares. It makes more sense to emulate the ABS module, especially considered that this requires a skill set out of reach for most readers.<br />
<br />
Regarding the ABS, more CAN message will need to be emulated:<br />
{{Note|note-reminder|This section is under development. Feel free to add content.}}<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+ '''ID 0x1A0, 8 bytes, Sent every 10 ms'''<br />
! Signal!!Byte!! Start bit !!Bits!!Range / Values!!Notes<br />
|-<br />
|ASR request<br />
|1||0||1||0 = no request; 1 = ASR request||Request also present in Byte 5 or 6<br />
|-<br />
|MSR request|| 1||1||1||0 = no request; 1 = MSR request||Request also present in Byte 7, Byte 6 contains updated info<br />
|-<br />
|ABS braking active||1||2||1||0 = inactive; 1 = ABS braking active||<br />
|-<br />
|EDS intervention active||1||3||1||0 = inactive; 1 = EDS active||Electronic Differential Lock<br />
|-<br />
|FDR intervention active||1||4||1||0 = inactive; 1 = FDR active||<br />
|-<br />
|ASR shift influence||1||5||2||00 = no request; 01 = ASR shift map; 02 = downshift request; 03 = shift inhibit||Transmission interaction<br />
|-<br />
|EBV intervention active||1||7||1||0 = inactive; 1 = EBV active||Electronic Brake Force Distribution<br />
|-<br />
|ABS warning lamp||2||0||1||0 = off; 1 = lamp on||<br />
|-<br />
|ASR/FDR warning lamp||2||1||1||0 = off; 1 = lamp on||<br />
|-<br />
|Brake warning lamp||2||2||1||0 = off; 1 = lamp on||<br />
|-<br />
|Brake light switch||2||3||1||0 = brake not applied; 1 = brake applied||Without brake booster this bit transmits the brake light switch<br />
|-<br />
|Brake pressure threshold exceeded||2||3||1||0 = threshold not exceeded; 1 = threshold exceeded||From PQ46 driver brake pressure threshold exceeded<br />
|-<br />
|Brake test switch||2||4||1||0 = brake not applied; 1 = brake applied||RB-ABS systems<br />
|-<br />
|Brake pressure threshold status||2||4||1||0 = status valid; 1 = status unavailable||From PQ46<br />
|-<br />
|Rough-road suppression||2||5||1||0 = disabled; 1 = active||<br />
|-<br />
|Rough-road suppression status||2||6||1||0 = valid; 1 = invalid||<br />
|-<br />
|ABS diagnostic active||2||7||1||0 = no diagnostic; 1 = diagnostic active||<br />
|-<br />
|Brake booster active||3||0||1|| ||<br />
|-<br />
|Vehicle speed low byte||3||1||7||0 – 1.27 km/h||HEX VALUE = speed (km/h) × 100<br />
|-<br />
|Vehicle speed high byte||4||0||8||0 – 325.12 km/h||HEX VALUE = speed (km/h) / 1.28<br />
|-<br />
|ASR torque intervention slow||5||0||8||0 – 99.06 %||VALUE = torque intervention / 0.39<br />
|-<br />
|ASR torque intervention fast||6||0||8||0 – 99.06 %||Bit-inverted MSR torque during MSR request<br />
|-<br />
|MSR torque intervention||7||0||8||0 – 99.06 %||<br />
|-<br />
|Message counter||8||0||4||0 – 15||Rolling counter<br />
|-<br />
|ASR controller present||8||4||1||0 = ABS; 1 = ASR||<br />
|-<br />
|ESP passive button pressed||8||5||1||0 = ESP active; 1 = ESP passive||Driver pressed ESP button<br />
|-<br />
|ESP system status||8||6||1||0 = OK; 1 = fault||ESP disabled due to fault<br />
|-<br />
|Speed substitute value||8||7||1||0 = valid speed; 1 = substitute value||<br />
|}<br />
<br />
Speed signal constants for the combined value of '''Byte 3 and Byte 4'''<br />
*'''Initial value''' = '''FF88h''' or '''FF89h''' = `1111 1111 1000 100x` (binary)<br />
*'''Supply voltage value''' = '''FFAAh''' or '''FFABh''' = `1111 1111 1010 101x` (binary)<br />
*'''Error value''' = '''FFCCh''' or '''FFCDh''' = `1111 1111 1100 110x` (binary)<br />
<br />
<small>These constants correspond to the '''complete 16-bit value composed of Bytes 3 and Byte 4'''</small><br />
<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+'''ID 0x4A0, 8 bytes, Sent every 10 ms'''<br />
!Signal!!Byte!!Start Bit!!Bit Length!!Range / Values!!Notes<br />
|-<br />
|Front left direction||1||0||1||0 = forward; 1 = reverse||Direction detection<br />
|-<br />
|Front left wheel speed||1 & 2||1||15||0..326 km/h||HEX VALUE = vehicle speed (km/h) × 100<br />
|-<br />
|Front right direction||3||0||1||0 = forward; 1 = reverse||<br />
|-<br />
|Front right wheel speed||3 & 4||1||15||0..326 km/h||<br />
|-<br />
|Rear left direction||5||0||1||0 = forward; 1 = reverse||<br />
|-<br />
|Rear left wheel speed||5 & 6||1||15||0..326 km/h||<br />
|-<br />
|Rear right direction||7||0||1||0 = forward; 1 = reverse||<br />
|-<br />
|Rear right wheel speed||7 & 8||1||15||0..326 km/h||<br />
|}<br />
<br />
Speed signal constants for the combined value of '''Byte 1 and Byte 2 (same for 3&4, 5&6, 7&8)'''<br />
*'''Initial value''' = '''FF88h''' or '''FF89h''' = `1111 1111 1000 100x` (binary)<br />
*'''Supply voltage value''' = '''FFAAh''' or '''FFABh''' = `1111 1111 1010 101x` (binary)<br />
*'''Error value''' = '''FFCCh''' or '''FFCDh''' = `1111 1111 1100 110x` (binary)<br />
If you report more than '''327.42km/h (included)''', the ECU will interpret it as an error.<br />
<br />
==Monitoring the values received by the ECU==<br />
You can use any suitable scanner, such as VCDS, and monitor the channel '''066''' in the measurement values.<br />
<br />
This channel lists:<br />
<br />
*Vehicle speed<br />
*Clutch/Brake switch values<br />
*Cruise control switch values<br />
*Cruise control status</div>Artehttps://the07k.wiki/index.php?title=Can-bus_emulation_for_cruise_control&diff=7692Can-bus emulation for cruise control2026-03-08T08:01:29Z<p>Arte: /* Emulating the ABS module (Vehicle speed) */</p>
<hr />
<div>==Introduction==<br />
This is intended as a reference for those who would like to emulate the can-bus messages for the cruise control.<br />
<br />
'''Application''': Any swapped vehicles that do not have can-bus support. It would cover both the Bosch ME7.1.1 and a ME17.5/ME17.5.6<br />
<br />
==Hardware required==<br />
You can use any microcontroller that have CAN-bus capability, such as an Arduino or ESP32. You could also use the SpeedPulser Pro that already has a GPS and CAN-bus capability, you would only need to alter the source code and implement the new CAN-bus message:<br />
<br />
*https://forbes-automotive.com/products/speedpulser-pro<br />
*https://github.com/adamforbes92/speedPulserPro<br />
<br />
==CAN-bus: What is this sorcery?==<br />
CAN-bus is a network used by modules to transmit data/information with each other. With only two wires, you can transmit a multitude of messages between modules ([[wikipedia:Multiplexing|multiplexing]]).<br />
<br />
In the past, you would have a single wire for every input. In those instances, every button of your cruise control switch has its own signal wire.<br />
<br />
The '''objective''' of the CAN-bus emulation is to take all those signals, feed them into your microcontroller and output CAN-bus messages that the ECU will understand, as if it was on a factory MK5/MK6 2.5 chassis.<br />
<br />
CAN-bus messages required:<br />
<br />
#State of the cruise control switch (Ex.: Main switch, SET, RES, etc.), normally provided by the '''steering column module'''<br />
#Vehicle speed, normally provided by the '''ABS module'''<br />
<br />
==Vehicle speed acquisition==<br />
The vehicle speed can be retrieved through the following means:<br />
<br />
*GPS module<br />
*VSS sensor<br />
*Hall-effect sensor mounted into the instrument cluster to read the speed of the speedometer cable<br />
*There are more ways to gather this information depending on your creativity<br />
<br />
==Emulating the cruise control switch==<br />
The ECU receive the cruise control switch information through the CAN message '''0x38A'''. Here is a detailed description of this CAN message<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+ID '''0x38A''', '''4 bytes''', Sent every '''20 ms'''<br />
!Signal!!Byte!!Start bit!!Bits!!Range / Values!!Notes<br />
|-<br />
|Checksum (See below)||1||0||8||0..255 (Phys = Hex)||—<br />
|-<br />
|Main switch||2||0||1||0 = OFF<br>1 = ON||Latching ON/OFF<br />
|-<br />
|Tip switch OFF||2||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch DECEL||2||2||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch ACCEL||2||3||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Cruise decelerate (hold)||2||4||1||0 = not decelerating<br>1 = decelerating||—<br />
|-<br />
|Cruise accelerate (hold)||2||5||1||0 = not accelerating<br>1 = accelerating||—<br />
|-<br />
|Cruise control stalk error||2||6||1||0 = OK<br>1 = stalk error||—<br />
|-<br />
|Not used||2||7||1||—||—<br />
|-<br />
|Tip switch SET||3||0||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch RESUME||3||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Sender coding||3||2||2||00 = Body network<br>01 = Steering column module<br>10 = Engine||Values per spec<br />
|-<br />
|Message counter||3||4||4||0..15 (Phys = Hex)||Rolling counter<br />
|-<br />
|Not used||4||0||8||—||Byte 4 unused<br />
|}<br />
<br />
===Checksum===<br />
The checksum is a formula used to validate the integrity of the message, and detect possible data corruption during the transmission of the message. If the checksum does not match the data, the ECU might reject the message. (Implausible message)<br />
<br />
[[File:Checksum GRAneu.png|747x747px]]<br />
<br />
This checksum is calculated only with Exclusive OR ([[wikipedia:Exclusive_or|XOR]]) operations<br />
<br />
===Code example===<br />
This is a very rough sketch to show a possible implementation. This example would be for an Arduino controller using a MCP2515 shield (hat).<br />
<br />
<syntaxhighlight lang="c" line="1"><br />
// demo: Cruise control switch, analog to can-bus message for VW PQ35<br />
// Very rough sketch, but should work. Feel free to improve<br />
<br />
#include <SPI.h><br />
<br />
#define CAN_2515<br />
<br />
// Set SPI CS Pin according to your hardware<br />
<br />
#if defined(SEEED_WIO_TERMINAL) && defined(CAN_2518FD)<br />
const int SPI_CS_PIN = BCM8;<br />
const int CAN_INT_PIN = BCM25;<br />
#else<br />
<br />
// For Arduino MCP2515 Hat:<br />
// the cs pin of the version after v1.1 is default to D9<br />
// v0.9b and v1.0 is default D10<br />
const int SPI_CS_PIN = 9;<br />
const int CAN_INT_PIN = 2;<br />
#endif<br />
<br />
<br />
#ifdef CAN_2518FD<br />
#include "mcp2518fd_can.h"<br />
mcp2518fd CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
#ifdef CAN_2515<br />
#include "mcp2515_can.h"<br />
mcp2515_can CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
const int buttonMain = 4;<br />
const int buttonRes = 2; <br />
const int buttonSet = 0;<br />
<br />
byte oldSwitchState = 0x0;<br />
byte sequence = 0x0;<br />
<br />
void setup() {<br />
SERIAL_PORT_MONITOR.begin(115200);<br />
while(!Serial){};<br />
<br />
while (CAN_OK != CAN.begin(CAN_500KBPS)) { // init powertrain can bus : baudrate = 500k <br />
SERIAL_PORT_MONITOR.println("CAN init fail, retry...");<br />
delay(100);<br />
}<br />
SERIAL_PORT_MONITOR.println("CAN init ok!");<br />
pinMode(buttonMain, INPUT_PULLUP);<br />
pinMode(buttonRes, INPUT_PULLUP);<br />
pinMode(buttonSet, INPUT_PULLUP); // default state 12v<br />
}<br />
<br />
void loop() {<br />
<br />
byte switchState = 0x0;<br />
<br />
// Read analog inputs<br />
int stateMain = digitalRead(buttonMain);<br />
int stateRes = digitalRead(buttonRes);<br />
int stateSet = digitalRead(buttonSet);<br />
<br />
// You can add more inputs and adjust the logic according the the can-bus chart<br />
if (stateMain == LOW) {<br />
switchState |= (1 << 0); // Set bit 0<br />
}<br />
if (stateSet == LOW) {<br />
switchState |= (1 << 1); // Set bit 1<br />
}<br />
if (stateRes == LOW) {<br />
switchState |= (1 << 2); // Set bit 2<br />
}<br />
<br />
<br />
// Check if the switch state has changed<br />
if (switchState != oldSwitchState) {<br />
Serial.println(switchState); // Print new state for monitoring purposes<br />
oldSwitchState = switchState; // Update oldSwitchState<br />
}<br />
<br />
// Define bytes for can message (0x38A)<br />
byte byteTwo = switchState & 1;<br />
<br />
byte byteThree = switchState >> 1;<br />
byteThree = byteThree | 0xC; // Could also be 0x4 (See Sender coding)<br />
byteThree = (sequence << 4) | byteThree;<br />
<br />
byte checksum = byteTwo ^ byteThree;<br />
<br />
unsigned char payload[4] = {checksum, byteTwo, byteThree, 0x00};<br />
CAN.sendMsgBuf(0x38A, 0, 4, payload);<br />
<br />
sequence = (sequence + 1) & 0x0F; // increment for the next frame<br />
<br />
delay(20); // Send every 20ms<br />
}<br />
</syntaxhighlight><br />
<br />
== Emulating the ABS module (Vehicle speed) ==<br />
The ABS module needs to be emulated as the ECU track the vehicle speed for the cruise control.<br />
<br />
In practice, it would be possible to do Assembly patches and make the ECU track the engine speed. Although, this extensive work would need to be repeated across multiple firmwares. It makes more sense to emulate the ABS module, especially considered that this requires a skill set out of reach for most readers.<br />
<br />
Regarding the ABS, more CAN message will need to be emulated:<br />
{{Note|note-reminder|This section is under development. Feel free to add content.}}<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+ '''ID 0x1A0, 8 bytes, Sent every 10 ms'''<br />
! Signal!!Byte!! Start bit !!Bits!!Range / Values!!Notes<br />
|-<br />
|ASR request<br />
|1||0||1||0 = no request; 1 = ASR request||Request also present in Byte 5 or 6<br />
|-<br />
|MSR request|| 1||1||1||0 = no request; 1 = MSR request||Request also present in Byte 7, Byte 6 contains updated info<br />
|-<br />
|ABS braking active||1||2||1||0 = inactive; 1 = ABS braking active||<br />
|-<br />
|EDS intervention active||1||3||1||0 = inactive; 1 = EDS active||Electronic Differential Lock<br />
|-<br />
|FDR intervention active||1||4||1||0 = inactive; 1 = FDR active||<br />
|-<br />
|ASR shift influence||1||5||2||00 = no request; 01 = ASR shift map; 02 = downshift request; 03 = shift inhibit||Transmission interaction<br />
|-<br />
|EBV intervention active||1||7||1||0 = inactive; 1 = EBV active||Electronic Brake Force Distribution<br />
|-<br />
|ABS warning lamp||2||0||1||0 = off; 1 = lamp on||<br />
|-<br />
|ASR/FDR warning lamp||2||1||1||0 = off; 1 = lamp on||<br />
|-<br />
|Brake warning lamp||2||2||1||0 = off; 1 = lamp on||<br />
|-<br />
|Brake light switch||2||3||1||0 = brake not applied; 1 = brake applied||Without brake booster this bit transmits the brake light switch<br />
|-<br />
|Brake pressure threshold exceeded||2||3||1||0 = threshold not exceeded; 1 = threshold exceeded||From PQ46 driver brake pressure threshold exceeded<br />
|-<br />
|Brake test switch||2||4||1||0 = brake not applied; 1 = brake applied||RB-ABS systems<br />
|-<br />
|Brake pressure threshold status||2||4||1||0 = status valid; 1 = status unavailable||From PQ46<br />
|-<br />
|Rough-road suppression||2||5||1||0 = disabled; 1 = active||<br />
|-<br />
|Rough-road suppression status||2||6||1||0 = valid; 1 = invalid||<br />
|-<br />
|ABS diagnostic active||2||7||1||0 = no diagnostic; 1 = diagnostic active||<br />
|-<br />
|Brake booster active||3||0||1|| ||<br />
|-<br />
|Vehicle speed low byte||3||1||7||0 – 1.27 km/h||HEX VALUE = speed (km/h) × 100<br />
|-<br />
|Vehicle speed high byte||4||0||8||0 – 325.12 km/h||HEX VALUE = speed (km/h) / 1.28<br />
|-<br />
|ASR torque intervention slow||5||0||8||0 – 99.06 %||VALUE = torque intervention / 0.39<br />
|-<br />
|ASR torque intervention fast||6||0||8||0 – 99.06 %||Bit-inverted MSR torque during MSR request<br />
|-<br />
|MSR torque intervention||7||0||8||0 – 99.06 %||<br />
|-<br />
|Message counter||8||0||4||0 – 15||<br />
|-<br />
|ASR controller present||8||4||1||0 = ABS; 1 = ASR||<br />
|-<br />
|ESP passive button pressed||8||5||1||0 = ESP active; 1 = ESP passive||Driver pressed ESP button<br />
|-<br />
|ESP system status||8||6||1||0 = OK; 1 = fault||ESP disabled due to fault<br />
|-<br />
|Speed substitute value||8||7||1||0 = valid speed; 1 = substitute value||<br />
|}<br />
<br />
Speed signal constants for the combined value of '''Byte 3 and Byte 4'''<br />
*'''Initial value''' = '''FF88h''' or '''FF89h''' = `1111 1111 1000 100x` (binary)<br />
*'''Supply voltage value''' = '''FFAAh''' or '''FFABh''' = `1111 1111 1010 101x` (binary)<br />
*'''Error value''' = '''FFCCh''' or '''FFCDh''' = `1111 1111 1100 110x` (binary)<br />
<br />
<small>These constants correspond to the '''complete 16-bit value composed of Bytes 3 and Byte 4'''</small><br />
<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+'''ID 0x4A0, 8 bytes, Sent every 10 ms'''<br />
!Signal!!Byte!!Start Bit!!Bit Length!!Range / Values!!Notes<br />
|-<br />
|Front left direction||1||0||1||0 = forward; 1 = reverse||Direction detection<br />
|-<br />
|Front left wheel speed||1 & 2||1||15||0..326 km/h||HEX VALUE = vehicle speed (km/h) × 100<br />
|-<br />
|Front right direction||3||0||1||0 = forward; 1 = reverse||<br />
|-<br />
|Front right wheel speed||3 & 4||1||15||0..326 km/h||<br />
|-<br />
|Rear left direction||5||0||1||0 = forward; 1 = reverse||<br />
|-<br />
|Rear left wheel speed||5 & 6||1||15||0..326 km/h||<br />
|-<br />
|Rear right direction||7||0||1||0 = forward; 1 = reverse||<br />
|-<br />
|Rear right wheel speed||7 & 8||1||15||0..326 km/h||<br />
|}<br />
<br />
Speed signal constants for the combined value of '''Byte 1 and Byte 2 (same for 3&4, 5&6, 7&8)'''<br />
*'''Initial value''' = '''FF88h''' or '''FF89h''' = `1111 1111 1000 100x` (binary)<br />
*'''Supply voltage value''' = '''FFAAh''' or '''FFABh''' = `1111 1111 1010 101x` (binary)<br />
*'''Error value''' = '''FFCCh''' or '''FFCDh''' = `1111 1111 1100 110x` (binary)<br />
If you report more than '''327.42km/h (included)''', the ECU will interpret it as an error.<br />
<br />
==Monitoring the values received by the ECU==<br />
You can use any suitable scanner, such as VCDS, and monitor the channel '''066''' in the measurement values.<br />
<br />
This channel lists:<br />
<br />
*Vehicle speed<br />
*Clutch/Brake switch values<br />
*Cruise control switch values<br />
*Cruise control status</div>Artehttps://the07k.wiki/index.php?title=Can-bus_emulation_for_cruise_control&diff=7691Can-bus emulation for cruise control2026-03-08T07:58:48Z<p>Arte: /* Emulating the ABS module (Vehicle speed) */</p>
<hr />
<div>==Introduction==<br />
This is intended as a reference for those who would like to emulate the can-bus messages for the cruise control.<br />
<br />
'''Application''': Any swapped vehicles that do not have can-bus support. It would cover both the Bosch ME7.1.1 and a ME17.5/ME17.5.6<br />
<br />
==Hardware required==<br />
You can use any microcontroller that have CAN-bus capability, such as an Arduino or ESP32. You could also use the SpeedPulser Pro that already has a GPS and CAN-bus capability, you would only need to alter the source code and implement the new CAN-bus message:<br />
<br />
*https://forbes-automotive.com/products/speedpulser-pro<br />
*https://github.com/adamforbes92/speedPulserPro<br />
<br />
==CAN-bus: What is this sorcery?==<br />
CAN-bus is a network used by modules to transmit data/information with each other. With only two wires, you can transmit a multitude of messages between modules ([[wikipedia:Multiplexing|multiplexing]]).<br />
<br />
In the past, you would have a single wire for every input. In those instances, every button of your cruise control switch has its own signal wire.<br />
<br />
The '''objective''' of the CAN-bus emulation is to take all those signals, feed them into your microcontroller and output CAN-bus messages that the ECU will understand, as if it was on a factory MK5/MK6 2.5 chassis.<br />
<br />
CAN-bus messages required:<br />
<br />
#State of the cruise control switch (Ex.: Main switch, SET, RES, etc.), normally provided by the '''steering column module'''<br />
#Vehicle speed, normally provided by the '''ABS module'''<br />
<br />
==Vehicle speed acquisition==<br />
The vehicle speed can be retrieved through the following means:<br />
<br />
*GPS module<br />
*VSS sensor<br />
*Hall-effect sensor mounted into the instrument cluster to read the speed of the speedometer cable<br />
*There are more ways to gather this information depending on your creativity<br />
<br />
==Emulating the cruise control switch==<br />
The ECU receive the cruise control switch information through the CAN message '''0x38A'''. Here is a detailed description of this CAN message<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+ID '''0x38A''', '''4 bytes''', Sent every '''20 ms'''<br />
!Signal!!Byte!!Start bit!!Bits!!Range / Values!!Notes<br />
|-<br />
|Checksum (See below)||1||0||8||0..255 (Phys = Hex)||—<br />
|-<br />
|Main switch||2||0||1||0 = OFF<br>1 = ON||Latching ON/OFF<br />
|-<br />
|Tip switch OFF||2||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch DECEL||2||2||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch ACCEL||2||3||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Cruise decelerate (hold)||2||4||1||0 = not decelerating<br>1 = decelerating||—<br />
|-<br />
|Cruise accelerate (hold)||2||5||1||0 = not accelerating<br>1 = accelerating||—<br />
|-<br />
|Cruise control stalk error||2||6||1||0 = OK<br>1 = stalk error||—<br />
|-<br />
|Not used||2||7||1||—||—<br />
|-<br />
|Tip switch SET||3||0||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch RESUME||3||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Sender coding||3||2||2||00 = Body network<br>01 = Steering column module<br>10 = Engine||Values per spec<br />
|-<br />
|Message counter||3||4||4||0..15 (Phys = Hex)||Rolling counter<br />
|-<br />
|Not used||4||0||8||—||Byte 4 unused<br />
|}<br />
<br />
===Checksum===<br />
The checksum is a formula used to validate the integrity of the message, and detect possible data corruption during the transmission of the message. If the checksum does not match the data, the ECU might reject the message. (Implausible message)<br />
<br />
[[File:Checksum GRAneu.png|747x747px]]<br />
<br />
This checksum is calculated only with Exclusive OR ([[wikipedia:Exclusive_or|XOR]]) operations<br />
<br />
===Code example===<br />
This is a very rough sketch to show a possible implementation. This example would be for an Arduino controller using a MCP2515 shield (hat).<br />
<br />
<syntaxhighlight lang="c" line="1"><br />
// demo: Cruise control switch, analog to can-bus message for VW PQ35<br />
// Very rough sketch, but should work. Feel free to improve<br />
<br />
#include <SPI.h><br />
<br />
#define CAN_2515<br />
<br />
// Set SPI CS Pin according to your hardware<br />
<br />
#if defined(SEEED_WIO_TERMINAL) && defined(CAN_2518FD)<br />
const int SPI_CS_PIN = BCM8;<br />
const int CAN_INT_PIN = BCM25;<br />
#else<br />
<br />
// For Arduino MCP2515 Hat:<br />
// the cs pin of the version after v1.1 is default to D9<br />
// v0.9b and v1.0 is default D10<br />
const int SPI_CS_PIN = 9;<br />
const int CAN_INT_PIN = 2;<br />
#endif<br />
<br />
<br />
#ifdef CAN_2518FD<br />
#include "mcp2518fd_can.h"<br />
mcp2518fd CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
#ifdef CAN_2515<br />
#include "mcp2515_can.h"<br />
mcp2515_can CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
const int buttonMain = 4;<br />
const int buttonRes = 2; <br />
const int buttonSet = 0;<br />
<br />
byte oldSwitchState = 0x0;<br />
byte sequence = 0x0;<br />
<br />
void setup() {<br />
SERIAL_PORT_MONITOR.begin(115200);<br />
while(!Serial){};<br />
<br />
while (CAN_OK != CAN.begin(CAN_500KBPS)) { // init powertrain can bus : baudrate = 500k <br />
SERIAL_PORT_MONITOR.println("CAN init fail, retry...");<br />
delay(100);<br />
}<br />
SERIAL_PORT_MONITOR.println("CAN init ok!");<br />
pinMode(buttonMain, INPUT_PULLUP);<br />
pinMode(buttonRes, INPUT_PULLUP);<br />
pinMode(buttonSet, INPUT_PULLUP); // default state 12v<br />
}<br />
<br />
void loop() {<br />
<br />
byte switchState = 0x0;<br />
<br />
// Read analog inputs<br />
int stateMain = digitalRead(buttonMain);<br />
int stateRes = digitalRead(buttonRes);<br />
int stateSet = digitalRead(buttonSet);<br />
<br />
// You can add more inputs and adjust the logic according the the can-bus chart<br />
if (stateMain == LOW) {<br />
switchState |= (1 << 0); // Set bit 0<br />
}<br />
if (stateSet == LOW) {<br />
switchState |= (1 << 1); // Set bit 1<br />
}<br />
if (stateRes == LOW) {<br />
switchState |= (1 << 2); // Set bit 2<br />
}<br />
<br />
<br />
// Check if the switch state has changed<br />
if (switchState != oldSwitchState) {<br />
Serial.println(switchState); // Print new state for monitoring purposes<br />
oldSwitchState = switchState; // Update oldSwitchState<br />
}<br />
<br />
// Define bytes for can message (0x38A)<br />
byte byteTwo = switchState & 1;<br />
<br />
byte byteThree = switchState >> 1;<br />
byteThree = byteThree | 0xC; // Could also be 0x4 (See Sender coding)<br />
byteThree = (sequence << 4) | byteThree;<br />
<br />
byte checksum = byteTwo ^ byteThree;<br />
<br />
unsigned char payload[4] = {checksum, byteTwo, byteThree, 0x00};<br />
CAN.sendMsgBuf(0x38A, 0, 4, payload);<br />
<br />
sequence = (sequence + 1) & 0x0F; // increment for the next frame<br />
<br />
delay(20); // Send every 20ms<br />
}<br />
</syntaxhighlight><br />
<br />
== Emulating the ABS module (Vehicle speed) ==<br />
The ABS module needs to be emulated as the ECU track the vehicle speed for the cruise control.<br />
<br />
In practice, it would be possible to do Assembly patches and make the ECU track the engine speed. Although, this extensive work would need to be repeated across multiple firmwares. It makes more sense to emulate the ABS module, especially considered that this requires a skill set out of reach for most readers.<br />
<br />
Regarding the ABS, more CAN message will need to be emulated:<br />
{{Note|note-reminder|This section is under development. Feel free to add content.}}<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+ '''ID 0x1A0, 8 bytes, Sent every 10 ms'''<br />
! Signal!!Byte!! Start bit !!Bits!!Range / Values!!Notes<br />
|-<br />
|ASR request<br />
|1||0||1||0 = no request; 1 = ASR request||Request also present in Byte 5 or 6<br />
|-<br />
|MSR request|| 1||1||1||0 = no request; 1 = MSR request||Request also present in Byte 7, Byte 6 contains updated info<br />
|-<br />
|ABS braking active||1||2||1||0 = inactive; 1 = ABS braking active||<br />
|-<br />
|EDS intervention active||1||3||1||0 = inactive; 1 = EDS active||Electronic Differential Lock<br />
|-<br />
|FDR intervention active||1||4||1||0 = inactive; 1 = FDR active||<br />
|-<br />
|ASR shift influence||1||5||2||00 = no request; 01 = ASR shift map; 02 = downshift request; 03 = shift inhibit||Transmission interaction<br />
|-<br />
|EBV intervention active||1||7||1||0 = inactive; 1 = EBV active||Electronic Brake Force Distribution<br />
|-<br />
|ABS warning lamp||2||0||1||0 = off; 1 = lamp on||<br />
|-<br />
|ASR/FDR warning lamp||2||1||1||0 = off; 1 = lamp on||<br />
|-<br />
|Brake warning lamp||2||2||1||0 = off; 1 = lamp on||<br />
|-<br />
|Brake light switch||2||3||1||0 = brake not applied; 1 = brake applied||Without brake booster this bit transmits the brake light switch<br />
|-<br />
|Brake pressure threshold exceeded||2||3||1||0 = threshold not exceeded; 1 = threshold exceeded||From PQ46 driver brake pressure threshold exceeded<br />
|-<br />
|Brake test switch||2||4||1||0 = brake not applied; 1 = brake applied||RB-ABS systems<br />
|-<br />
|Brake pressure threshold status||2||4||1||0 = status valid; 1 = status unavailable||From PQ46<br />
|-<br />
|Rough-road suppression||2||5||1||0 = disabled; 1 = active||<br />
|-<br />
|Rough-road suppression status||2||6||1||0 = valid; 1 = invalid||<br />
|-<br />
|ABS diagnostic active||2||7||1||0 = no diagnostic; 1 = diagnostic active||<br />
|-<br />
|Brake booster active||3||0||1|| ||<br />
|-<br />
|Vehicle speed low byte||3||1||7||0 – 1.27 km/h||HEX VALUE = speed (km/h) × 100<br />
|-<br />
|Vehicle speed high byte||4||0||8||0 – 325.12 km/h||HEX VALUE = speed (km/h) / 1.28<br />
|-<br />
|ASR torque intervention slow||5||0||8||0 – 99.06 %||VALUE = torque intervention / 0.39<br />
|-<br />
|ASR torque intervention fast||6||0||8||0 – 99.06 %||Bit-inverted MSR torque during MSR request<br />
|-<br />
|MSR torque intervention||7||0||8||0 – 99.06 %||<br />
|-<br />
|Message counter||8||0||4||0 – 15||<br />
|-<br />
|ASR controller present||8||4||1||0 = ABS; 1 = ASR||<br />
|-<br />
|ESP passive button pressed||8||5||1||0 = ESP active; 1 = ESP passive||Driver pressed ESP button<br />
|-<br />
|ESP system status||8||6||1||0 = OK; 1 = fault||ESP disabled due to fault<br />
|-<br />
|Speed substitute value||8||7||1||0 = valid speed; 1 = substitute value||<br />
|}<br />
<br />
Speed signal constants for the combined value of '''Byte 3 and Byte 4'''<br />
*'''Initial value''' = '''FF88h''' or '''FF89h''' = `1111 1111 1000 100x` (binary)<br />
*'''Supply voltage value''' = '''FFAAh''' or '''FFABh''' = `1111 1111 1010 101x` (binary)<br />
*'''Error value''' = '''FFCCh''' or '''FFCDh''' = `1111 1111 1100 110x` (binary)<br />
<br />
<small>These constants correspond to the '''complete 16-bit value composed of Bytes 3 and Byte 4'''</small><br />
<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+'''ID 0x4A0, 8 bytes, Sent every 10 ms'''<br />
!Signal!!Byte!!Start Bit!!Bit Length!!Range / Values!!Notes<br />
|-<br />
|Front left direction||1||0||1||0 = forward; 1 = reverse||Direction detection<br />
|-<br />
|Front left wheel speed||1 & 2||1||15||0..326 km/h||HEX VALUE = vehicle speed (km/h) × 100<br />
|-<br />
|Front right direction||3||0||1||0 = forward; 1 = reverse||<br />
|-<br />
|Front right wheel speed||3 & 4||1||15||0..326 km/h||<br />
|-<br />
|Rear left direction||5||0||1||0 = forward; 1 = reverse||<br />
|-<br />
|Rear left wheel speed||5 & 6||1||15||0..326 km/h||<br />
|-<br />
|Rear right direction||7||0||1||0 = forward; 1 = reverse||<br />
|-<br />
|Rear right wheel speed||7 & 8||0||15||0..326 km/h||<br />
|}<br />
<br />
Speed signal constants for the combined value of '''Byte 1 and Byte 2 (same for 3&4, 5&6, 7&8)'''<br />
*'''Initial value''' = '''FF88h''' or '''FF89h''' = `1111 1111 1000 100x` (binary)<br />
*'''Supply voltage value''' = '''FFAAh''' or '''FFABh''' = `1111 1111 1010 101x` (binary)<br />
*'''Error value''' = '''FFCCh''' or '''FFCDh''' = `1111 1111 1100 110x` (binary)<br />
If you report more than '''327.42km/h (included)''', the ECU will interpret it as an error.<br />
<br />
==Monitoring the values received by the ECU==<br />
You can use any suitable scanner, such as VCDS, and monitor the channel '''066''' in the measurement values.<br />
<br />
This channel lists:<br />
<br />
*Vehicle speed<br />
*Clutch/Brake switch values<br />
*Cruise control switch values<br />
*Cruise control status</div>Artehttps://the07k.wiki/index.php?title=Maps_helper_(Editor)&diff=7690Maps helper (Editor)2026-03-05T09:48:13Z<p>Arte: /* Fuel Trim Configuration */</p>
<hr />
<div>= ACCELERATOR PEDAL: =<br />
<br />
== Desired Torque Profile (0/1/2/3/4/Reverse) ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Accelerator pedal position (%)<br />
<br />
'''Map:''' Target engine torque<br />
<br />
This map defines the relationship between accelerator pedal position and requested engine torque (throttle response).<br />
<br />
* Lower values → smoother and more progressive response<br />
* Higher values → more aggressive and dynamic response<br />
<br />
Adjust carefully to maintain drivability and traction.<br />
<br />
= BOOST CONTROL =<br />
<br />
== Boost Solenoid Duty Cycle ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Actual gear<br />
<br />
'''Map:''' Boost control solenoid duty cycle (%)<br />
<br />
This map controls the duty cycle of the boost control solenoid.<br />
<br />
Continuous high-duty operation may reduce solenoid valve lifespan.<br />
<br />
To prevent unnecessary solenoid activity:<br />
<br />
* Set appropriate minimum engine speed<br />
* Set appropriate minimum MAP pressure<br />
<br />
----<br />
<br />
= FUEL: =<br />
All fuel-related adjustments must be performed responsibly. Incorrect settings may cause severe engine damage.<br />
----<br />
<br />
== Cold Start Factor ==<br />
'''X axis:''' Engine coolant temperature (°C)<br />
<br />
'''Map:''' Cold start fuel correction factor<br />
<br />
A cold engine requires additional fuel for stable operation.<br />
<br />
Adjust this map if:<br />
<br />
* Idle is unstable during warm-up<br />
* AFR/lambda is incorrect during cold start<br />
* Engine stalls or runs excessively rich during warm-up<br />
<br />
----<br />
<br />
== Fuel Mass to Injection Time Conversion ==<br />
'''Map type:''' Single value<br />
<br />
Defines the conversion factor between calculated fuel mass and injector opening time.<br />
<br />
Adjustment is required when replacing injectors.<br />
<br />
* Larger injectors → lower map value<br />
* Smaller injectors → higher map value<br />
<br />
Always verify changes using logs.<br />
----<br />
<br />
== Injector Linearization Correction ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Injection time (ms)<br />
<br />
'''Map:''' Fuel correction factor<br />
<br />
This map corrects injector non-linearity.<br />
<br />
* Higher values → more injected fuel<br />
* Lower values → less injected fuel<br />
<br />
Adjust using lambda correction logs.<br />
<br />
Ensure actual lambda matches target lambda under all load conditions.<br />
----<br />
<br />
== Fuel Trim Configuration ==<br />
<br />
* To disable the long-term fuel trim, set value to '''135'''<br />
* To re-enable the long-term fuel trim, set value to '''132'''<br />
<br />
----<br />
<br />
== Injector Dead Time ==<br />
'''X axis:''' Battery voltage (V)<br />
<br />
'''Map:''' Injector dead time (ms)<br />
<br />
Dead time values are injector-specific.<br />
<br />
Adjustment is not required unless injectors are replaced.<br />
----<br />
<br />
== Lambda Target ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Target lambda value<br />
<br />
Defines the target air-fuel ratio.<br />
<br />
Adjust this map to:<br />
<br />
* Optimize performance<br />
* Improve fuel economy<br />
* Ensure safe operation under boost<br />
<br />
----<br />
<br />
== Minimum Measurable Lambda ==<br />
'''Map type:''' Single value<br />
<br />
Defines the diagnostic lower limit for the lambda sensor.<br />
<br />
If your target lambda is lower than this limit, adjust this value to avoid diagnostic fault codes.<br />
----<br />
<br />
= IDLE =<br />
<br />
== Idle Target Speed ==<br />
'''X axis:''' Engine coolant temperature (°C)<br />
<br />
'''Y axis:''' Actual gear<br />
<br />
'''Map:''' Target idle speed (RPM)<br />
<br />
Defines engine idle speed under different temperature and gear conditions.<br />
----<br />
<br />
== RPM Curve After Start ==<br />
'''X axis:''' Time since engine start (s)<br />
<br />
'''Y axis:''' Engine coolant temperature (°C)<br />
<br />
'''Map:''' Target idle speed (RPM)<br />
<br />
Defines elevated idle speed strategy immediately after engine startup.<br />
<br />
Used for:<br />
<br />
* Improved cold-start stability<br />
<br />
----<br />
<br />
= IGNITION =<br />
Incorrect ignition settings may cause engine knock and severe engine damage.<br />
<br />
Always validate changes using knock logs and dyno testing.<br />
----<br />
<br />
== Ignition Advance ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Ignition timing advance (°)<br />
<br />
Defines base ignition timing.<br />
<br />
Adjust to optimize:<br />
<br />
* Power output<br />
* Efficiency<br />
* Knock resistance<br />
<br />
Avoid large changes unless you fully understand ignition tuning principles.<br />
----<br />
<br />
== Minimum Ignition Angle ==<br />
''(Recommended rename from "Latest possible ignition angle")''<br />
<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Minimum allowed ignition angle (°)<br />
<br />
Defines the lower safety limit for ignition timing.<br />
<br />
Adjust only if calculated ignition values fall below this threshold.<br />
----<br />
<br />
== Minimum Ignition Angle During Catalyst Heating ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Minimum ignition angle during catalyst heating (°)<br />
<br />
Defines ignition timing lower limit during catalyst warm-up phase.<br />
----<br />
<br />
== Dwell Maps ==<br />
Modification is generally not recommended unless:<br />
<br />
* Ignition coils are replaced<br />
* System voltage behavior changes<br />
<br />
Improper dwell settings may damage ignition coils.<br />
----<br />
<br />
= Overrun Fuel Cut-Off (Deceleration) =<br />
<br />
== Fuel Cut-Off Delay During Gear Change ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Delay time (s)<br />
<br />
Defines how long fuel is delivered after accelerator release during gear change (clutch engaged).<br />
----<br />
<br />
== Overrun Fuel Cut-Off Delay ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Delay time (s)<br />
<br />
Defines how long fuel is delivered after accelerator release during engine braking.<br />
----<br />
<br />
== Fuel Cut-Off Delay at High RPM and High Catalyst Temperature ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Catalyst temperature (°C)<br />
<br />
'''Map:''' Delay time (s)<br />
<br />
Defines delay before fuel cut-off under high thermal load conditions.<br />
----<br />
<br />
= Project Configuration =<br />
<br />
== Catalyst Diagnosis ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → Catalyst diagnosis enabled<br />
* 0 → Catalyst diagnosis disabled (cat-less setup)<br />
<br />
----<br />
<br />
== Catalyst Diagnosis (OBD2 Mode) ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → Enabled<br />
* 0 → Disabled (cat-less setup)<br />
<br />
----<br />
<br />
== Lambda Sensor Configuration ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → Post-catalyst lambda sensor disabled<br />
* 0 → Sensor enabled<br />
<br />
----<br />
<br />
== EVAP / Tank Ventilation System ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → System enabled<br />
* 0 → EVAP system removed<br />
<br />
----<br />
<br />
= VVT Control =<br />
<br />
== Intake Camshaft Advance ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Intake camshaft advance angle (°)<br />
<br />
Adjust this map to optimize torque and power delivery.<br />
<br />
Dyno validation is strongly recommended for optimal results.</div>Artehttps://the07k.wiki/index.php?title=Maps_helper_(Editor)&diff=7689Maps helper (Editor)2026-03-05T09:41:55Z<p>Arte: /* Fuel Trim Configuration */</p>
<hr />
<div>= ACCELERATOR PEDAL: =<br />
<br />
== Desired Torque Profile (0/1/2/3/4/Reverse) ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Accelerator pedal position (%)<br />
<br />
'''Map:''' Target engine torque<br />
<br />
This map defines the relationship between accelerator pedal position and requested engine torque (throttle response).<br />
<br />
* Lower values → smoother and more progressive response<br />
* Higher values → more aggressive and dynamic response<br />
<br />
Adjust carefully to maintain drivability and traction.<br />
<br />
= BOOST CONTROL =<br />
<br />
== Boost Solenoid Duty Cycle ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Actual gear<br />
<br />
'''Map:''' Boost control solenoid duty cycle (%)<br />
<br />
This map controls the duty cycle of the boost control solenoid.<br />
<br />
Continuous high-duty operation may reduce solenoid valve lifespan.<br />
<br />
To prevent unnecessary solenoid activity:<br />
<br />
* Set appropriate minimum engine speed<br />
* Set appropriate minimum MAP pressure<br />
<br />
----<br />
<br />
= FUEL: =<br />
All fuel-related adjustments must be performed responsibly. Incorrect settings may cause severe engine damage.<br />
----<br />
<br />
== Cold Start Factor ==<br />
'''X axis:''' Engine coolant temperature (°C)<br />
<br />
'''Map:''' Cold start fuel correction factor<br />
<br />
A cold engine requires additional fuel for stable operation.<br />
<br />
Adjust this map if:<br />
<br />
* Idle is unstable during warm-up<br />
* AFR/lambda is incorrect during cold start<br />
* Engine stalls or runs excessively rich during warm-up<br />
<br />
----<br />
<br />
== Fuel Mass to Injection Time Conversion ==<br />
'''Map type:''' Single value<br />
<br />
Defines the conversion factor between calculated fuel mass and injector opening time.<br />
<br />
Adjustment is required when replacing injectors.<br />
<br />
* Larger injectors → lower map value<br />
* Smaller injectors → higher map value<br />
<br />
Always verify changes using logs.<br />
----<br />
<br />
== Injector Linearization Correction ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Injection time (ms)<br />
<br />
'''Map:''' Fuel correction factor<br />
<br />
This map corrects injector non-linearity.<br />
<br />
* Higher values → more injected fuel<br />
* Lower values → less injected fuel<br />
<br />
Adjust using lambda correction logs.<br />
<br />
Ensure actual lambda matches target lambda under all load conditions.<br />
----<br />
<br />
== Fuel Trim Configuration ==<br />
<br />
* To disable the long-term fuel trim, set value to '''132'''<br />
* To re-enable the long-term fuel trim, set value to '''135'''<br />
<br />
----<br />
<br />
== Injector Dead Time ==<br />
'''X axis:''' Battery voltage (V)<br />
<br />
'''Map:''' Injector dead time (ms)<br />
<br />
Dead time values are injector-specific.<br />
<br />
Adjustment is not required unless injectors are replaced.<br />
----<br />
<br />
== Lambda Target ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Target lambda value<br />
<br />
Defines the target air-fuel ratio.<br />
<br />
Adjust this map to:<br />
<br />
* Optimize performance<br />
* Improve fuel economy<br />
* Ensure safe operation under boost<br />
<br />
----<br />
<br />
== Minimum Measurable Lambda ==<br />
'''Map type:''' Single value<br />
<br />
Defines the diagnostic lower limit for the lambda sensor.<br />
<br />
If your target lambda is lower than this limit, adjust this value to avoid diagnostic fault codes.<br />
----<br />
<br />
= IDLE =<br />
<br />
== Idle Target Speed ==<br />
'''X axis:''' Engine coolant temperature (°C)<br />
<br />
'''Y axis:''' Actual gear<br />
<br />
'''Map:''' Target idle speed (RPM)<br />
<br />
Defines engine idle speed under different temperature and gear conditions.<br />
----<br />
<br />
== RPM Curve After Start ==<br />
'''X axis:''' Time since engine start (s)<br />
<br />
'''Y axis:''' Engine coolant temperature (°C)<br />
<br />
'''Map:''' Target idle speed (RPM)<br />
<br />
Defines elevated idle speed strategy immediately after engine startup.<br />
<br />
Used for:<br />
<br />
* Improved cold-start stability<br />
<br />
----<br />
<br />
= IGNITION =<br />
Incorrect ignition settings may cause engine knock and severe engine damage.<br />
<br />
Always validate changes using knock logs and dyno testing.<br />
----<br />
<br />
== Ignition Advance ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Ignition timing advance (°)<br />
<br />
Defines base ignition timing.<br />
<br />
Adjust to optimize:<br />
<br />
* Power output<br />
* Efficiency<br />
* Knock resistance<br />
<br />
Avoid large changes unless you fully understand ignition tuning principles.<br />
----<br />
<br />
== Minimum Ignition Angle ==<br />
''(Recommended rename from "Latest possible ignition angle")''<br />
<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Minimum allowed ignition angle (°)<br />
<br />
Defines the lower safety limit for ignition timing.<br />
<br />
Adjust only if calculated ignition values fall below this threshold.<br />
----<br />
<br />
== Minimum Ignition Angle During Catalyst Heating ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Minimum ignition angle during catalyst heating (°)<br />
<br />
Defines ignition timing lower limit during catalyst warm-up phase.<br />
----<br />
<br />
== Dwell Maps ==<br />
Modification is generally not recommended unless:<br />
<br />
* Ignition coils are replaced<br />
* System voltage behavior changes<br />
<br />
Improper dwell settings may damage ignition coils.<br />
----<br />
<br />
= Overrun Fuel Cut-Off (Deceleration) =<br />
<br />
== Fuel Cut-Off Delay During Gear Change ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Delay time (s)<br />
<br />
Defines how long fuel is delivered after accelerator release during gear change (clutch engaged).<br />
----<br />
<br />
== Overrun Fuel Cut-Off Delay ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Delay time (s)<br />
<br />
Defines how long fuel is delivered after accelerator release during engine braking.<br />
----<br />
<br />
== Fuel Cut-Off Delay at High RPM and High Catalyst Temperature ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Catalyst temperature (°C)<br />
<br />
'''Map:''' Delay time (s)<br />
<br />
Defines delay before fuel cut-off under high thermal load conditions.<br />
----<br />
<br />
= Project Configuration =<br />
<br />
== Catalyst Diagnosis ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → Catalyst diagnosis enabled<br />
* 0 → Catalyst diagnosis disabled (cat-less setup)<br />
<br />
----<br />
<br />
== Catalyst Diagnosis (OBD2 Mode) ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → Enabled<br />
* 0 → Disabled (cat-less setup)<br />
<br />
----<br />
<br />
== Lambda Sensor Configuration ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → Post-catalyst lambda sensor disabled<br />
* 0 → Sensor enabled<br />
<br />
----<br />
<br />
== EVAP / Tank Ventilation System ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → System enabled<br />
* 0 → EVAP system removed<br />
<br />
----<br />
<br />
= VVT Control =<br />
<br />
== Intake Camshaft Advance ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Intake camshaft advance angle (°)<br />
<br />
Adjust this map to optimize torque and power delivery.<br />
<br />
Dyno validation is strongly recommended for optimal results.</div>Artehttps://the07k.wiki/index.php?title=Maps_helper_(Editor)&diff=7688Maps helper (Editor)2026-03-05T09:34:24Z<p>Arte: Created page with "= ACCELERATOR PEDAL: = == Desired Torque Profile (0/1/2/3/4/Reverse) == '''X axis:''' Engine speed (RPM) '''Y axis:''' Accelerator pedal position (%) '''Map:''' Target engine torque This map defines the relationship between accelerator pedal position and requested engine torque (throttle response). * Lower values → smoother and more progressive response * Higher values → more aggressive and dynamic response Adjust carefully to maintain drivability and traction...."</p>
<hr />
<div>= ACCELERATOR PEDAL: =<br />
<br />
== Desired Torque Profile (0/1/2/3/4/Reverse) ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Accelerator pedal position (%)<br />
<br />
'''Map:''' Target engine torque<br />
<br />
This map defines the relationship between accelerator pedal position and requested engine torque (throttle response).<br />
<br />
* Lower values → smoother and more progressive response<br />
* Higher values → more aggressive and dynamic response<br />
<br />
Adjust carefully to maintain drivability and traction.<br />
<br />
= BOOST CONTROL =<br />
<br />
== Boost Solenoid Duty Cycle ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Actual gear<br />
<br />
'''Map:''' Boost control solenoid duty cycle (%)<br />
<br />
This map controls the duty cycle of the boost control solenoid.<br />
<br />
Continuous high-duty operation may reduce solenoid valve lifespan.<br />
<br />
To prevent unnecessary solenoid activity:<br />
<br />
* Set appropriate minimum engine speed<br />
* Set appropriate minimum MAP pressure<br />
<br />
----<br />
<br />
= FUEL: =<br />
All fuel-related adjustments must be performed responsibly. Incorrect settings may cause severe engine damage.<br />
----<br />
<br />
== Cold Start Factor ==<br />
'''X axis:''' Engine coolant temperature (°C)<br />
<br />
'''Map:''' Cold start fuel correction factor<br />
<br />
A cold engine requires additional fuel for stable operation.<br />
<br />
Adjust this map if:<br />
<br />
* Idle is unstable during warm-up<br />
* AFR/lambda is incorrect during cold start<br />
* Engine stalls or runs excessively rich during warm-up<br />
<br />
----<br />
<br />
== Fuel Mass to Injection Time Conversion ==<br />
'''Map type:''' Single value<br />
<br />
Defines the conversion factor between calculated fuel mass and injector opening time.<br />
<br />
Adjustment is required when replacing injectors.<br />
<br />
* Larger injectors → lower map value<br />
* Smaller injectors → higher map value<br />
<br />
Always verify changes using logs.<br />
----<br />
<br />
== Injector Linearization Correction ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Injection time (ms)<br />
<br />
'''Map:''' Fuel correction factor<br />
<br />
This map corrects injector non-linearity.<br />
<br />
* Higher values → more injected fuel<br />
* Lower values → less injected fuel<br />
<br />
Adjust using lambda correction logs.<br />
<br />
Ensure actual lambda matches target lambda under all load conditions.<br />
----<br />
<br />
== Fuel Trim Configuration ==<br />
I don't know what this map doing :D<br />
----<br />
<br />
== Injector Dead Time ==<br />
'''X axis:''' Battery voltage (V)<br />
<br />
'''Map:''' Injector dead time (ms)<br />
<br />
Dead time values are injector-specific.<br />
<br />
Adjustment is not required unless injectors are replaced.<br />
----<br />
<br />
== Lambda Target ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Target lambda value<br />
<br />
Defines the target air-fuel ratio.<br />
<br />
Adjust this map to:<br />
<br />
* Optimize performance<br />
* Improve fuel economy<br />
* Ensure safe operation under boost<br />
<br />
----<br />
<br />
== Minimum Measurable Lambda ==<br />
'''Map type:''' Single value<br />
<br />
Defines the diagnostic lower limit for the lambda sensor.<br />
<br />
If your target lambda is lower than this limit, adjust this value to avoid diagnostic fault codes.<br />
----<br />
<br />
= IDLE =<br />
<br />
== Idle Target Speed ==<br />
'''X axis:''' Engine coolant temperature (°C)<br />
<br />
'''Y axis:''' Actual gear<br />
<br />
'''Map:''' Target idle speed (RPM)<br />
<br />
Defines engine idle speed under different temperature and gear conditions.<br />
----<br />
<br />
== RPM Curve After Start ==<br />
'''X axis:''' Time since engine start (s)<br />
<br />
'''Y axis:''' Engine coolant temperature (°C)<br />
<br />
'''Map:''' Target idle speed (RPM)<br />
<br />
Defines elevated idle speed strategy immediately after engine startup.<br />
<br />
Used for:<br />
<br />
* Improved cold-start stability<br />
<br />
----<br />
<br />
= IGNITION =<br />
Incorrect ignition settings may cause engine knock and severe engine damage.<br />
<br />
Always validate changes using knock logs and dyno testing.<br />
----<br />
<br />
== Ignition Advance ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Ignition timing advance (°)<br />
<br />
Defines base ignition timing.<br />
<br />
Adjust to optimize:<br />
<br />
* Power output<br />
* Efficiency<br />
* Knock resistance<br />
<br />
Avoid large changes unless you fully understand ignition tuning principles.<br />
----<br />
<br />
== Minimum Ignition Angle ==<br />
''(Recommended rename from "Latest possible ignition angle")''<br />
<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Minimum allowed ignition angle (°)<br />
<br />
Defines the lower safety limit for ignition timing.<br />
<br />
Adjust only if calculated ignition values fall below this threshold.<br />
----<br />
<br />
== Minimum Ignition Angle During Catalyst Heating ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Minimum ignition angle during catalyst heating (°)<br />
<br />
Defines ignition timing lower limit during catalyst warm-up phase.<br />
----<br />
<br />
== Dwell Maps ==<br />
Modification is generally not recommended unless:<br />
<br />
* Ignition coils are replaced<br />
* System voltage behavior changes<br />
<br />
Improper dwell settings may damage ignition coils.<br />
----<br />
<br />
= Overrun Fuel Cut-Off (Deceleration) =<br />
<br />
== Fuel Cut-Off Delay During Gear Change ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Delay time (s)<br />
<br />
Defines how long fuel is delivered after accelerator release during gear change (clutch engaged).<br />
----<br />
<br />
== Overrun Fuel Cut-Off Delay ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Delay time (s)<br />
<br />
Defines how long fuel is delivered after accelerator release during engine braking.<br />
----<br />
<br />
== Fuel Cut-Off Delay at High RPM and High Catalyst Temperature ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Catalyst temperature (°C)<br />
<br />
'''Map:''' Delay time (s)<br />
<br />
Defines delay before fuel cut-off under high thermal load conditions.<br />
----<br />
<br />
= Project Configuration =<br />
<br />
== Catalyst Diagnosis ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → Catalyst diagnosis enabled<br />
* 0 → Catalyst diagnosis disabled (cat-less setup)<br />
<br />
----<br />
<br />
== Catalyst Diagnosis (OBD2 Mode) ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → Enabled<br />
* 0 → Disabled (cat-less setup)<br />
<br />
----<br />
<br />
== Lambda Sensor Configuration ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → Post-catalyst lambda sensor disabled<br />
* 0 → Sensor enabled<br />
<br />
----<br />
<br />
== EVAP / Tank Ventilation System ==<br />
'''Map type:''' Single value<br />
<br />
Set to:<br />
<br />
* 1 → System enabled<br />
* 0 → EVAP system removed<br />
<br />
----<br />
<br />
= VVT Control =<br />
<br />
== Intake Camshaft Advance ==<br />
'''X axis:''' Engine speed (RPM)<br />
<br />
'''Y axis:''' Engine load (%)<br />
<br />
'''Map:''' Intake camshaft advance angle (°)<br />
<br />
Adjust this map to optimize torque and power delivery.<br />
<br />
Dyno validation is strongly recommended for optimal results.</div>Artehttps://the07k.wiki/index.php?title=Can-bus_emulation_for_cruise_control&diff=7687Can-bus emulation for cruise control2026-02-25T06:04:36Z<p>Arte: /* Code example */</p>
<hr />
<div>==Introduction==<br />
This is intended as a reference for those who would like to emulate the can-bus messages for the cruise control.<br />
<br />
'''Application''': Any swapped vehicles that do not have can-bus support. It would cover both the Bosch ME7.1.1 and a ME17.5/ME17.5.6<br />
<br />
==Hardware required==<br />
You can use any microcontroller that have CAN-bus capability, such as an Arduino or ESP32. You could also use the SpeedPulser Pro that already has a GPS and CAN-bus capability, you would only need to alter the source code and implement the new CAN-bus message:<br />
<br />
*https://forbes-automotive.com/products/speedpulser-pro<br />
*https://github.com/adamforbes92/speedPulserPro<br />
<br />
==CAN-bus: What is this sorcery?==<br />
CAN-bus is a network used by modules to transmit data/information with each other. With only two wires, you can transmit a multitude of messages between modules ([[wikipedia:Multiplexing|multiplexing]]).<br />
<br />
In the past, you would have a single wire for every input. In those instances, every button of your cruise control switch has its own signal wire.<br />
<br />
The '''objective''' of the CAN-bus emulation is to take all those signals, feed them into your microcontroller and output CAN-bus messages that the ECU will understand, as if it was on a factory MK5/MK6 2.5 chassis.<br />
<br />
CAN-bus messages required:<br />
<br />
#State of the cruise control switch (Ex.: Main switch, SET, RES, etc.), normally provided by the '''steering column module'''<br />
#Vehicle speed, normally provided by the '''ABS module'''<br />
<br />
==Vehicle speed acquisition==<br />
The vehicle speed can be retrieved through the following means:<br />
<br />
*GPS module<br />
*VSS sensor<br />
*Hall-effect sensor mounted into the instrument cluster to read the speed of the speedometer cable<br />
*There are more ways to gather this information depending on your creativity<br />
<br />
==Emulating the cruise control switch==<br />
The ECU receive the cruise control switch information through the CAN message '''0x38A'''. Here is a detailed description of this CAN message<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+ID '''0x38A''', '''4 bytes''', Sent every '''20 ms'''<br />
!Signal!!Byte!!Start bit!!Bits!!Range / Values!!Notes<br />
|-<br />
|Checksum (See below)||1||0||8||0..255 (Phys = Hex)||—<br />
|-<br />
|Main switch||2||0||1||0 = OFF<br>1 = ON||Latching ON/OFF<br />
|-<br />
|Tip switch OFF||2||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch DECEL||2||2||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch ACCEL||2||3||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Cruise decelerate (hold)||2||4||1||0 = not decelerating<br>1 = decelerating||—<br />
|-<br />
|Cruise accelerate (hold)||2||5||1||0 = not accelerating<br>1 = accelerating||—<br />
|-<br />
|Cruise control stalk error||2||6||1||0 = OK<br>1 = stalk error||—<br />
|-<br />
|Not used||2||7||1||—||—<br />
|-<br />
|Tip switch SET||3||0||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch RESUME||3||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Sender coding||3||2||2||00 = Body network<br>01 = Steering column module<br>10 = Engine||Values per spec<br />
|-<br />
|Message counter||3||4||4||0..15 (Phys = Hex)||Rolling counter<br />
|-<br />
|Not used||4||0||8||—||Byte 4 unused<br />
|}<br />
<br />
===Checksum===<br />
The checksum is a formula used to validate the integrity of the message, and detect possible data corruption during the transmission of the message. If the checksum does not match the data, the ECU might reject the message. (Implausible message)<br />
<br />
[[File:Checksum GRAneu.png|747x747px]]<br />
<br />
This checksum is calculated only with Exclusive OR ([[wikipedia:Exclusive_or|XOR]]) operations<br />
<br />
===Code example===<br />
This is a very rough sketch to show a possible implementation. This example would be for an Arduino controller using a MCP2515 shield (hat).<br />
<br />
<syntaxhighlight lang="c" line="1"><br />
// demo: Cruise control switch, analog to can-bus message for VW PQ35<br />
// Very rough sketch, but should work. Feel free to improve<br />
<br />
#include <SPI.h><br />
<br />
#define CAN_2515<br />
<br />
// Set SPI CS Pin according to your hardware<br />
<br />
#if defined(SEEED_WIO_TERMINAL) && defined(CAN_2518FD)<br />
const int SPI_CS_PIN = BCM8;<br />
const int CAN_INT_PIN = BCM25;<br />
#else<br />
<br />
// For Arduino MCP2515 Hat:<br />
// the cs pin of the version after v1.1 is default to D9<br />
// v0.9b and v1.0 is default D10<br />
const int SPI_CS_PIN = 9;<br />
const int CAN_INT_PIN = 2;<br />
#endif<br />
<br />
<br />
#ifdef CAN_2518FD<br />
#include "mcp2518fd_can.h"<br />
mcp2518fd CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
#ifdef CAN_2515<br />
#include "mcp2515_can.h"<br />
mcp2515_can CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
const int buttonMain = 4;<br />
const int buttonRes = 2; <br />
const int buttonSet = 0;<br />
<br />
byte oldSwitchState = 0x0;<br />
byte sequence = 0x0;<br />
<br />
void setup() {<br />
SERIAL_PORT_MONITOR.begin(115200);<br />
while(!Serial){};<br />
<br />
while (CAN_OK != CAN.begin(CAN_500KBPS)) { // init powertrain can bus : baudrate = 500k <br />
SERIAL_PORT_MONITOR.println("CAN init fail, retry...");<br />
delay(100);<br />
}<br />
SERIAL_PORT_MONITOR.println("CAN init ok!");<br />
pinMode(buttonMain, INPUT_PULLUP);<br />
pinMode(buttonRes, INPUT_PULLUP);<br />
pinMode(buttonSet, INPUT_PULLUP); // default state 12v<br />
}<br />
<br />
void loop() {<br />
<br />
byte switchState = 0x0;<br />
<br />
// Read analog inputs<br />
int stateMain = digitalRead(buttonMain);<br />
int stateRes = digitalRead(buttonRes);<br />
int stateSet = digitalRead(buttonSet);<br />
<br />
// You can add more inputs and adjust the logic according the the can-bus chart<br />
if (stateMain == LOW) {<br />
switchState |= (1 << 0); // Set bit 0<br />
}<br />
if (stateSet == LOW) {<br />
switchState |= (1 << 1); // Set bit 1<br />
}<br />
if (stateRes == LOW) {<br />
switchState |= (1 << 2); // Set bit 2<br />
}<br />
<br />
<br />
// Check if the switch state has changed<br />
if (switchState != oldSwitchState) {<br />
Serial.println(switchState); // Print new state for monitoring purposes<br />
oldSwitchState = switchState; // Update oldSwitchState<br />
}<br />
<br />
// Define bytes for can message (0x38A)<br />
byte byteTwo = switchState & 1;<br />
<br />
byte byteThree = switchState >> 1;<br />
byteThree = byteThree | 0xC; // Could also be 0x4 (See Sender coding)<br />
byteThree = (sequence << 4) | byteThree;<br />
<br />
byte checksum = byteTwo ^ byteThree;<br />
<br />
unsigned char payload[4] = {checksum, byteTwo, byteThree, 0x00};<br />
CAN.sendMsgBuf(0x38A, 0, 4, payload);<br />
<br />
sequence = (sequence + 1) & 0x0F; // increment for the next frame<br />
<br />
delay(20); // Send every 20ms<br />
}<br />
</syntaxhighlight><br />
<br />
== Emulating the ABS module (Vehicle speed) ==<br />
The ABS module needs to be emulated as the ECU track the vehicle speed for the cruise control.<br />
<br />
In practice, it would be possible to do Assembly patches and make the ECU track the engine speed. Although, this extensive work would need to be repeated across multiple firmwares. It makes more sense to emulate the ABS module, especially considered that this requires a skill set out of reach for most readers.<br />
<br />
Regarding the ABS, more CAN message will need to be emulated:<br />
{{Note|note-reminder|This section is under development. Feel free to add content.}}<br />
<br />
== Monitoring the values received by the ECU ==<br />
You can use any suitable scanner, such as VCDS, and monitor the channel '''066''' in the measurement values.<br />
<br />
This channel lists:<br />
<br />
* Vehicle speed<br />
* Clutch/Brake switch values<br />
* Cruise control switch values<br />
* Cruise control status</div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Sidebar&diff=7685MediaWiki:Sidebar2026-02-20T17:12:29Z<p>Arte: </p>
<hr />
<div><br />
* Navigation:<br />
** mainpage|Main Page<br />
** recentchanges-url|Recent Changes<br />
* General:<br />
** Common_Problems | Common Problems<br />
** Engine_Specs | Engine Specs<br />
* Engine:<br />
** Aftermarket_Parts | Aftermarket Parts<br />
** Engine_Builds | Builds<br />
** Forced_Induction_(Turbocharger) | Forced Induction<br />
** Engine_Swaps | Engine Swaps<br />
** Engine_Repair_Guides | Repair Procedures<br />
* Tuning:<br />
** Standalone_Management | Standalone Management<br />
* Hardware (ECU):<br />
** ME7.1.1_Pinout | ME7.1.1 Pinout<br />
** ME17.5_Pinout | ME17.5 Pinout<br />
* Miscellaneous:<br />
** Can-bus_emulation_for_cruise_control | Can-bus emulation for cruise control<br />
* Additional Information:<br />
** Wiring_Diagrams | Wiring Diagrams<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Artehttps://the07k.wiki/index.php?title=Can-bus_emulation_for_cruise_control&diff=7684Can-bus emulation for cruise control2026-02-20T17:10:00Z<p>Arte: </p>
<hr />
<div>==Introduction==<br />
This is intended as a reference for those who would like to emulate the can-bus messages for the cruise control.<br />
<br />
'''Application''': Any swapped vehicles that do not have can-bus support. It would cover both the Bosch ME7.1.1 and a ME17.5/ME17.5.6<br />
<br />
==Hardware required==<br />
You can use any microcontroller that have CAN-bus capability, such as an Arduino or ESP32. You could also use the SpeedPulser Pro that already has a GPS and CAN-bus capability, you would only need to alter the source code and implement the new CAN-bus message:<br />
<br />
*https://forbes-automotive.com/products/speedpulser-pro<br />
*https://github.com/adamforbes92/speedPulserPro<br />
<br />
==CAN-bus: What is this sorcery?==<br />
CAN-bus is a network used by modules to transmit data/information with each other. With only two wires, you can transmit a multitude of messages between modules ([[wikipedia:Multiplexing|multiplexing]]).<br />
<br />
In the past, you would have a single wire for every input. In those instances, every button of your cruise control switch has its own signal wire.<br />
<br />
The '''objective''' of the CAN-bus emulation is to take all those signals, feed them into your microcontroller and output CAN-bus messages that the ECU will understand, as if it was on a factory MK5/MK6 2.5 chassis.<br />
<br />
CAN-bus messages required:<br />
<br />
#State of the cruise control switch (Ex.: Main switch, SET, RES, etc.), normally provided by the '''steering column module'''<br />
#Vehicle speed, normally provided by the '''ABS module'''<br />
<br />
==Vehicle speed acquisition==<br />
The vehicle speed can be retrieved through the following means:<br />
<br />
*GPS module<br />
*VSS sensor<br />
*Hall-effect sensor mounted into the instrument cluster to read the speed of the speedometer cable<br />
*There are more ways to gather this information depending on your creativity<br />
<br />
==Emulating the cruise control switch==<br />
The ECU receive the cruise control switch information through the CAN message '''0x38A'''. Here is a detailed description of this CAN message<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+ID '''0x38A''', '''4 bytes''', Sent every '''20 ms'''<br />
!Signal!!Byte!!Start bit!!Bits!!Range / Values!!Notes<br />
|-<br />
|Checksum (See below)||1||0||8||0..255 (Phys = Hex)||—<br />
|-<br />
|Main switch||2||0||1||0 = OFF<br>1 = ON||Latching ON/OFF<br />
|-<br />
|Tip switch OFF||2||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch DECEL||2||2||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch ACCEL||2||3||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Cruise decelerate (hold)||2||4||1||0 = not decelerating<br>1 = decelerating||—<br />
|-<br />
|Cruise accelerate (hold)||2||5||1||0 = not accelerating<br>1 = accelerating||—<br />
|-<br />
|Cruise control stalk error||2||6||1||0 = OK<br>1 = stalk error||—<br />
|-<br />
|Not used||2||7||1||—||—<br />
|-<br />
|Tip switch SET||3||0||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch RESUME||3||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Sender coding||3||2||2||00 = Body network<br>01 = Steering column module<br>10 = Engine||Values per spec<br />
|-<br />
|Message counter||3||4||4||0..15 (Phys = Hex)||Rolling counter<br />
|-<br />
|Not used||4||0||8||—||Byte 4 unused<br />
|}<br />
<br />
===Checksum===<br />
The checksum is a formula used to validate the integrity of the message, and detect possible data corruption during the transmission of the message. If the checksum does not match the data, the ECU might reject the message. (Implausible message)<br />
<br />
[[File:Checksum GRAneu.png|747x747px]]<br />
<br />
This checksum is calculated only with Exclusive OR ([[wikipedia:Exclusive_or|XOR]]) operations<br />
<br />
===Code example===<br />
This is a very rough sketch to show a possible implementation. This example would be for an Arduino controller using a MCP2515 shield (hat).<br />
<br />
<syntaxhighlight lang="c" line=""><br />
// demo: Cruise control switch, analog to can-bus message for VW PQ35<br />
// Very rough sketch, but should work. Feel free to improve<br />
<br />
#include <SPI.h><br />
<br />
#define CAN_2515<br />
<br />
// Set SPI CS Pin according to your hardware<br />
<br />
#if defined(SEEED_WIO_TERMINAL) && defined(CAN_2518FD)<br />
const int SPI_CS_PIN = BCM8;<br />
const int CAN_INT_PIN = BCM25;<br />
#else<br />
<br />
// For Arduino MCP2515 Hat:<br />
// the cs pin of the version after v1.1 is default to D9<br />
// v0.9b and v1.0 is default D10<br />
const int SPI_CS_PIN = 9;<br />
const int CAN_INT_PIN = 2;<br />
#endif<br />
<br />
<br />
#ifdef CAN_2518FD<br />
#include "mcp2518fd_can.h"<br />
mcp2518fd CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
#ifdef CAN_2515<br />
#include "mcp2515_can.h"<br />
mcp2515_can CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
const int buttonMain = 4;<br />
const int buttonRes = 2; <br />
const int buttonSet = 0;<br />
<br />
byte oldSwitchState = 0x0;<br />
byte sequence = 0x0;<br />
<br />
void setup() {<br />
SERIAL_PORT_MONITOR.begin(115200);<br />
while(!Serial){};<br />
<br />
while (CAN_OK != CAN.begin(CAN_500KBPS)) { // init powertrain can bus : baudrate = 500k <br />
SERIAL_PORT_MONITOR.println("CAN init fail, retry...");<br />
delay(100);<br />
}<br />
SERIAL_PORT_MONITOR.println("CAN init ok!");<br />
pinMode(buttonMain, INPUT_PULLUP);<br />
pinMode(buttonRes, INPUT_PULLUP);<br />
pinMode(buttonSet, INPUT_PULLUP); // default state 12v<br />
}<br />
<br />
void loop() {<br />
<br />
byte switchState = 0x0;<br />
<br />
// Read analog inputs<br />
int stateMain = digitalRead(buttonMain);<br />
int stateRes = digitalRead(buttonRes);<br />
int stateSet = digitalRead(buttonSet);<br />
<br />
// You can more inputs and adjust the logic according the the can-bus chart<br />
if (stateMain == LOW) {<br />
switchState |= (1 << 0); // Set bit 0<br />
}<br />
if (stateSet == LOW) {<br />
switchState |= (1 << 1); // Set bit 1<br />
}<br />
if (stateRes == LOW) {<br />
switchState |= (1 << 2); // Set bit 2<br />
}<br />
<br />
<br />
// Check if the switch state has changed<br />
if (switchState != oldSwitchState) {<br />
Serial.println(switchState); // Print new state for monitoring purposes<br />
oldSwitchState = switchState; // Update oldSwitchState<br />
}<br />
<br />
// Define bytes for can message (0x38A)<br />
byte byteTwo = switchState & 1;<br />
<br />
byte byteThree = switchState >> 1;<br />
byteThree = byteThree | 0xC; // Could also be 0x4 (See Sender coding)<br />
byteThree = (sequence << 4) | byteThree;<br />
<br />
byte checksum = byteTwo ^ byteThree;<br />
<br />
unsigned char payload[4] = {checksum, byteTwo, byteThree, 0x00};<br />
CAN.sendMsgBuf(0x38A, 0, 4, payload);<br />
<br />
sequence = (sequence + 1) & 0x0F; // increment for the next frame<br />
<br />
delay(20); // Send every 20ms<br />
}<br />
</syntaxhighlight><br />
<br />
== Emulating the ABS module (Vehicle speed) ==<br />
The ABS module needs to be emulated as the ECU track the vehicle speed for the cruise control.<br />
<br />
In practice, it would be possible to do Assembly patches and make the ECU track the engine speed. Although, this extensive work would need to be repeated across multiple firmwares. It makes more sense to emulate the ABS module, especially considered that this requires a skill set out of reach for most readers.<br />
<br />
Regarding the ABS, more CAN message will need to be emulated:<br />
{{Note|note-reminder|This section is under development. Feel free to add content.}}<br />
<br />
== Monitoring the values received by the ECU ==<br />
You can use any suitable scanner, such as VCDS, and monitor the channel '''066''' in the measurement values.<br />
<br />
This channel lists:<br />
<br />
* Vehicle speed<br />
* Clutch/Brake switch values<br />
* Cruise control switch values<br />
* Cruise control status</div>Artehttps://the07k.wiki/index.php?title=Can-bus_emulation_for_cruise_control&diff=7683Can-bus emulation for cruise control2026-02-20T16:44:16Z<p>Arte: Initial page</p>
<hr />
<div>==Introduction==<br />
This is intended as a reference for those who would like to emulate the can-bus messages for the cruise control.<br />
<br />
'''Application''': Any swapped vehicles that do not have can-bus support. It would cover both the Bosch ME7.1.1 and a ME17.5/ME17.5.6<br />
<br />
==Hardware required==<br />
You can use any microcontroller that have CAN-bus capability, such as an Arduino or ESP32. You could also use the SpeedPulser Pro that already has a GPS and CAN-bus capability, you would only need to alter the source code and implement the new CAN-bus message:<br />
<br />
*https://forbes-automotive.com/products/speedpulser-pro<br />
*https://github.com/adamforbes92/speedPulserPro<br />
<br />
==CAN-bus: What is this sorcery?==<br />
CAN-bus is a network used by modules to transmit data/information with each other. With only two wires, you can transmit a multitude of messages between modules ([[wikipedia:Multiplexing|multiplexing]]).<br />
<br />
In the past, you would have a single wire for every input. In those instances, every button of your cruise control switch has its own signal wire.<br />
<br />
The '''objective''' of the CAN-bus emulation is to take all those signals, feed them into your microcontroller and output CAN-bus messages that the ECU will understand, as if it was on a factory MK5/MK6 2.5 chassis.<br />
<br />
CAN-bus messages required:<br />
<br />
#State of the cruise control switch (Ex.: Main switch, SET, RES, etc.), normally provided by the '''steering column module'''<br />
#Vehicle speed, normally provided by the '''ABS module'''<br />
<br />
==Vehicle speed acquisition==<br />
The vehicle speed can be retrieved through the following means:<br />
<br />
*GPS module<br />
*VSS sensor<br />
*Hall-effect sensor mounted into the instrument cluster to read the speed of the speedometer cable<br />
*There are more ways to gather this information depending on your creativity<br />
<br />
==Emulating the cruise control switch==<br />
The ECU receive the cruise control switch information through the CAN message '''0x38A'''. Here is a detailed description of this CAN message<br />
{| class="wikitable sortable" style="width:100%;"<br />
|+ID '''0x38A''', '''4 bytes''', Sent every '''20 ms'''<br />
!Signal!!Byte!!Start bit!!Bits!!Range / Values!!Notes<br />
|-<br />
|Checksum (See below)||1||0||8||0..255 (Phys = Hex)||—<br />
|-<br />
|Main switch||2||0||1||0 = OFF<br>1 = ON||Latching ON/OFF<br />
|-<br />
|Tip switch OFF||2||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch DECEL||2||2||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch ACCEL||2||3||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Cruise decelerate (hold)||2||4||1||0 = not decelerating<br>1 = decelerating||—<br />
|-<br />
|Cruise accelerate (hold)||2||5||1||0 = not accelerating<br>1 = accelerating||—<br />
|-<br />
|Cruise control stalk error||2||6||1||0 = OK<br>1 = stalk error||—<br />
|-<br />
|Not used||2||7||1||—||—<br />
|-<br />
|Tip switch SET||3||0||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Tip switch RESUME||3||1||1||0 = not pressed<br>1 = pressed||—<br />
|-<br />
|Sender coding||3||2||2||00 = Body network<br>01 = Steering column module<br>10 = Engine||Values per spec<br />
|-<br />
|Message counter||3||4||4||0..15 (Phys = Hex)||Rolling counter<br />
|-<br />
|Not used||4||0||8||—||Byte 4 unused<br />
|}<br />
<br />
===Checksum===<br />
The checksum is a formula used to validate the integrity of the message, and detect possible data corruption during the transmission of the message. If the checksum does not match the data, the ECU might reject the message. (Implausible message)<br />
<br />
[[File:Checksum GRAneu.png|747x747px]]<br />
<br />
This checksum is calculated only with Exclusive OR ([[wikipedia:Exclusive_or|XOR]]) operations<br />
<br />
===Code example===<br />
This is a very rough sketch to show a possible implementation. This example would be for an Arduino controller using a MCP2515 shield (hat).<br />
// demo: Cruise control switch, analog to can-bus message for VW PQ35<br />
// Very rough sketch, but should work. Feel free to improve<br />
<br />
#include <SPI.h><br />
<br />
#define CAN_2515<br />
<br />
// Set SPI CS Pin according to your hardware<br />
<br />
#if defined(SEEED_WIO_TERMINAL) && defined(CAN_2518FD)<br />
const int SPI_CS_PIN = BCM8;<br />
const int CAN_INT_PIN = BCM25;<br />
#else<br />
<br />
// For Arduino MCP2515 Hat:<br />
// the cs pin of the version after v1.1 is default to D9<br />
// v0.9b and v1.0 is default D10<br />
const int SPI_CS_PIN = 9;<br />
const int CAN_INT_PIN = 2;<br />
#endif<br />
<br />
<br />
#ifdef CAN_2518FD<br />
#include "mcp2518fd_can.h"<br />
mcp2518fd CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
#ifdef CAN_2515<br />
#include "mcp2515_can.h"<br />
mcp2515_can CAN(SPI_CS_PIN); // Set CS pin<br />
#endif<br />
<br />
const int buttonMain = 4;<br />
const int buttonRes = 2; <br />
const int buttonSet = 0;<br />
<br />
byte oldSwitchState = 0x0;<br />
byte sequence = 0x0;<br />
<br />
void setup() {<br />
SERIAL_PORT_MONITOR.begin(115200);<br />
while(!Serial){};<br />
<br />
while (CAN_OK != CAN.begin(CAN_500KBPS)) { // init powertrain can bus : baudrate = 500k <br />
SERIAL_PORT_MONITOR.println("CAN init fail, retry...");<br />
delay(100);<br />
}<br />
SERIAL_PORT_MONITOR.println("CAN init ok!");<br />
pinMode(buttonMain, INPUT_PULLUP);<br />
pinMode(buttonRes, INPUT_PULLUP);<br />
pinMode(buttonSet, INPUT_PULLUP); // default state 12v<br />
}<br />
<br />
void loop() {<br />
<br />
byte switchState = 0x0;<br />
<br />
// Read analog inputs<br />
int stateMain = digitalRead(buttonMain);<br />
int stateRes = digitalRead(buttonRes);<br />
int stateSet = digitalRead(buttonSet);<br />
<br />
// You can more inputs and adjust the logic according the the can-bus chart<br />
if (stateMain == LOW) {<br />
switchState |= (1 << 0); // Set bit 0<br />
}<br />
if (stateSet == LOW) {<br />
switchState |= (1 << 1); // Set bit 1<br />
}<br />
if (stateRes == LOW) {<br />
switchState |= (1 << 2); // Set bit 2<br />
}<br />
<br />
<br />
// Check if the switch state has changed<br />
if (switchState != oldSwitchState) {<br />
Serial.println(switchState); // Print new state for monitoring purposes<br />
oldSwitchState = switchState; // Update oldSwitchState<br />
}<br />
<br />
// Define bytes for can message (0x38A)<br />
byte byteTwo = switchState & 1;<br />
<br />
byte byteThree = switchState >> 1;<br />
byteThree = byteThree | 0xC; // Could also be 0x4 (See Sender coding)<br />
byteThree = (sequence << 4) | byteThree;<br />
<br />
byte checksum = byteTwo ^ byteThree;<br />
<br />
unsigned char payload[4] = {checksum, byteTwo, byteThree, 0x00};<br />
CAN.sendMsgBuf(0x38A, 0, 4, payload);<br />
<br />
sequence = (sequence + 1) & 0x0F; // increment for the next frame<br />
<br />
delay(20); // Send every 20ms<br />
}</div>Artehttps://the07k.wiki/index.php?title=File:Checksum_GRAneu.png&diff=7682File:Checksum GRAneu.png2026-02-20T16:27:13Z<p>Arte: </p>
<hr />
<div>Checksum GRAneu</div>Artehttps://the07k.wiki/index.php?title=How_to_use_the_wiki&diff=7681How to use the wiki2025-11-15T19:10:36Z<p>Arte: /* What is a wiki */</p>
<hr />
<div>== What is a wiki ==<br />
A wiki is a website where registered members can create and edit pages that contain information regarding a particular topic.<br />
<br />
The wiki keeps track of recent changes and new pages. It offers the possibility to revert modifications if they are considered wrong.<br />
<br />
The navigation menu on the left regroups the main pages and the content of interest. Please note that if you wish to add a page to the navigation menu, you can contact the support at support@the07k.wiki or any admin/moderator of [https://www.facebook.com/groups/590065341160110 The 07K Project group].<br />
<br />
The main advantage of a wiki is its ability to make links between other pages. References are a powerful tool that helps readers to find the information they need. We invite you to use this powerful feature.<br />
== Creating a page ==<br />
You might be looking to create a new page if the topic has not been covered on the wiki. There are multiples ways to create a new page, here are the easiest ones:<br />
==== Using the search bar ====<br />
You can search the page with the search bar. If the page does not exist, the wiki will propose you the option to create it.<br />
<br />
[[File:Search bar.png|frameless|887x887px]]<br />
<br />
[[File:Search create page.png|frameless|816x816px]]<br />
<br />
By clicking on the red link, this will create your new page and you can start editing it.<br />
==== Using the URL system ====<br />
To create a new page, you can also use the url system. (An URL is the address of a web resource, in our case, it would be a page address)<br />
<br />
For example, if you wish to create a new page called "My new page", you can simply access this URL :<br />
<br />
[[File:Url create page.png|frameless|909x909px]]<br />
<br />
(<nowiki>https://the07k.wiki/index.php?title=</nowiki>'''My new page''')<br />
<br />
If '''My new page''' does not exist, it will be created and you can then start editing it.<br />
==== Clicking on any red link ====<br />
A red link means the link leads to a page that does not yet exist. If you click on the link, it will create the page and you can start editing it. A red link can occur when a member creates a page and references to page/topic that has not been documented. Other fellow members can then click on the red link to create and complete those topics.<br />
<br />
Here is an example of a red link:<br />
<br />
[[File:Red link.png|frameless|599x599px]]<br />
<br />
In this instance, the page refers to another page called "Emulator", a page that has not been documented yet, but any member can decide to create it by clicking on the link.<br />
== Editing a page ==<br />
'''You need to be registered and logged in to edit a page'''<br />
<br />
Simply access the page you wish to edit, click on '''Actions''' -> '''Edit'''<br />
<br />
[[File:Edit page.png|frameless|394x394px]]<br />
==== Saving you modifications ====<br />
[[File:Save changes.png|frameless|501x501px]]<br />
== View old revision of a page ==<br />
The wiki keeps track of every revisions for each page. Simply access the page of interest, click on '''Actions''' -> '''View History'''<br />
<br />
[[File:History.png|frameless|407x407px]]<br />
<br />
[[File:Old revision.png|frameless|567x567px]]<br />
== Uploading a file ==<br />
To upload a file click on '''Tools''' -> '''Upload file'''<br />
<br />
[[File:Upload file.png|frameless|368x368px]]<br />
<br />
For a list of all the uploaded file you can consult : [[Special:ListFiles]]<br />
==== Linking a file on a page ====<br />
Once you uploaded you file, take note of the file name (it starts with File:):<br />
<br />
[[File:File name.png|frameless|815x815px]]<br />
<br />
While in the page editor, click on this icon to add a link :<br />
<br />
[[File:Link icon.png|frameless|86x86px]]<br />
<br />
This will open a window, simply input your file name and it will add the link to your file:<br />
<br />
[[File:Add a link window.png|frameless|417x417px]]<br />
== Need more help ? ==<br />
Our wiki runs on MediaWiki, the same wiki system as Wikipedia. You can consult their help page if you seek more information on how to use the wiki : [[mediawikiwiki:Help:Contents|MediaWiki help page]]</div>Artehttps://the07k.wiki/index.php?title=File:2005-BEV.pdf&diff=7678File:2005-BEV.pdf2025-10-13T20:32:03Z<p>Arte: BEV 2005 Wiring diagram</p>
<hr />
<div>== Summary ==<br />
BEV 2005 Wiring diagram</div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Disclaimers&diff=7677MediaWiki:Disclaimers2025-10-03T21:30:55Z<p>Arte: Created page with "-"</p>
<hr />
<div>-</div>Artehttps://the07k.wiki/index.php?title=The_07K_Wiki:General_disclaimer&diff=7676The 07K Wiki:General disclaimer2025-10-03T21:29:59Z<p>Arte: Created page with "-"</p>
<hr />
<div>-</div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Privacy&diff=7675MediaWiki:Privacy2025-10-03T21:29:49Z<p>Arte: Created page with "-"</p>
<hr />
<div>-</div>Artehttps://the07k.wiki/index.php?title=Main_Page&diff=7674Main Page2025-10-03T21:25:38Z<p>Arte: </p>
<hr />
<div><strong>Welcome to the 07K Wiki</strong><br />
<br />
This Wiki is dedicated to the [[07K]] engine developed by Volkswagen. An engine known among enthusiast for its underrated potentials, reliability and its glorious 5-cylinders melody.<br />
You can expect to find anything from oil specs to engine tuning. The Wiki is in his debut, and we encourage anyone who wishes to contribute, whether it's small details or highly technical information.<br />
<br />
''You need to create an account to write / edit the Wiki.''<br />
<br />
'''First time using a wiki ? Consult our guide : [[How to use the wiki]]'''<br />
<br />
If you experience any issues, feel free to contact [mailto:support@the07k.wiki support@the07k.wiki]<br />
<br />
'''General:'''<br />
* [[Common Problems]]<br />
* [[Engine Specs]]<br />
'''Engine:'''<br />
* [[Aftermarket Parts]]<br />
* [[Engine Builds|Builds]]<br />
* [[Forced Induction (Turbocharger)]]<br />
* [[Engine Swaps]]<br />
* [[Engine Repair Guides|Repair Procedures]]<br />
'''Tuning:'''<br />
* [[Standalone Management]]<br />
'''Hardware (ECU):'''<br />
* [[ME7.1.1 Pinout]]<br />
* [[ME17.5 Pinout]]<br />
'''Additional Information:'''<br />
* [[Wiring Diagrams]]<br />
'''Facebook groups that might interest you:'''<br />
* [https://www.facebook.com/groups/247446985360343 VW 2.5l Group]<br />
* [https://www.facebook.com/groups/07kswap The 07K Project]</div>Artehttps://the07k.wiki/index.php?title=Main_Page&diff=7673Main Page2025-10-03T21:23:50Z<p>Arte: </p>
<hr />
<div><strong>Welcome to the 07K Wiki</strong><br />
<br />
This Wiki is dedicated to the [[07K]] engine developed by Volkswagen. An engine known among enthusiast for its underrated potentials, reliability and its glorious 5-cylinders melody.<br />
You can expect to find anything from oil specs to engine tuning. The Wiki is in his debut, and we encourage anyone who wishes to contribute, whether it's small details or highly technical information.<br />
<br />
''You need to create an account to write / edit the Wiki.''<br />
<br />
'''First time using a wiki ? Consult our guide : [[How to use the wiki]]'''<br />
<br />
If you experience any issues, feel free to contact [mailto:support@the07k.wiki support@the07k.wiki]<br />
<br />
'''[/cdn-cgi/l/email-protection#73000603031c010733071b164344185d041a181a General:]'''<br />
* [/cdn-cgi/l/email-protection#fb888e8b8b94898fbb8f939ecbcc90d58c929092 Common Problems]<br />
* [[Engine Specs]]<br />
'''Engine:'''<br />
* [[Aftermarket Parts]]<br />
* [[Engine Builds|Builds]]<br />
* [[Forced Induction (Turbocharger)]]<br />
* [[Engine Swaps]]<br />
* [[Engine Repair Guides|Repair Procedures]]<br />
'''Tuning:'''<br />
* [[Standalone Management]]<br />
'''Hardware (ECU):'''<br />
* [[ME7.1.1 Pinout]]<br />
* [[ME17.5 Pinout]]<br />
'''Additional Information:'''<br />
* [[Wiring Diagrams]]<br />
'''Facebook groups that might interest you:'''<br />
* [https://www.facebook.com/groups/247446985360343 VW 2.5l Group]<br />
* [https://www.facebook.com/groups/07kswap The 07K Project]</div>Artehttps://the07k.wiki/index.php?title=Main_Page&diff=7672Main Page2025-10-03T21:22:17Z<p>Arte: </p>
<hr />
<div><strong>Welcome to the 07K Wiki</strong><br />
<br />
This Wiki is dedicated to the [[07K]] engine developed by Volkswagen. An engine known among enthusiast for its underrated potentials, reliability and its glorious 5-cylinders melody.<br />
You can expect to find anything from oil specs to engine tuning. The Wiki is in his debut, and we encourage anyone who wishes to contribute, whether it's small details or highly technical information.<br />
<br />
''You need to create an account to write / edit the Wiki.''<br />
<br />
'''First time using a wiki ? Consult our guide : [[How to use the wiki]]'''<br />
<br />
If you experience any issues, feel free to contact [mailto:support@the07k.wiki][/cdn-cgi/l/email-protection <nowiki>[email protected]</nowiki>]<br />
<br />
'''[mailto:support@the07k.wiki General:]'''<br />
* [mailto:support@the07k.wiki Common Problems]<br />
* [[Engine Specs]]<br />
'''Engine:'''<br />
* [[Aftermarket Parts]]<br />
* [[Engine Builds|Builds]]<br />
* [[Forced Induction (Turbocharger)]]<br />
* [[Engine Swaps]]<br />
* [[Engine Repair Guides|Repair Procedures]]<br />
'''Tuning:'''<br />
* [[Standalone Management]]<br />
'''Hardware (ECU):'''<br />
* [[ME7.1.1 Pinout]]<br />
* [[ME17.5 Pinout]]<br />
'''Additional Information:'''<br />
* [[Wiring Diagrams]]<br />
'''Facebook groups that might interest you:'''<br />
* [https://www.facebook.com/groups/247446985360343 VW 2.5l Group]<br />
* [https://www.facebook.com/groups/07kswap The 07K Project]</div>Artehttps://the07k.wiki/index.php?title=Main_Page&diff=7671Main Page2025-10-03T21:21:42Z<p>Arte: </p>
<hr />
<div><strong>Welcome to the 07K Wiki</strong><br />
<br />
This Wiki is dedicated to the [[07K]] engine developed by Volkswagen. An engine known among enthusiast for its underrated potentials, reliability and its glorious 5-cylinders melody.<br />
You can expect to find anything from oil specs to engine tuning. The Wiki is in his debut, and we encourage anyone who wishes to contribute, whether it's small details or highly technical information.<br />
<br />
''You need to create an account to write / edit the Wiki.''<br />
<br />
'''First time using a wiki ? Consult our guide : [[How to use the wiki]]'''<br />
<br />
If you experience any issues, feel free to contact support@the07k.wiki<br />
<br />
'''General:'''<br />
* [[Common Problems]]<br />
* [[Engine Specs]]<br />
'''Engine:'''<br />
* [[Aftermarket Parts]]<br />
* [[Engine Builds|Builds]]<br />
* [[Forced Induction (Turbocharger)]]<br />
* [[Engine Swaps]]<br />
* [[Engine Repair Guides|Repair Procedures]]<br />
'''Tuning:'''<br />
* [[Standalone Management]]<br />
'''Hardware (ECU):'''<br />
* [[ME7.1.1 Pinout]]<br />
* [[ME17.5 Pinout]]<br />
'''Additional Information:'''<br />
* [[Wiring Diagrams]]<br />
'''Facebook groups that might interest you:'''<br />
* [https://www.facebook.com/groups/247446985360343 VW 2.5l Group]<br />
* [https://www.facebook.com/groups/07kswap The 07K Project]</div>Artehttps://the07k.wiki/index.php?title=Main_Page&diff=7670Main Page2025-10-03T21:21:13Z<p>Arte: </p>
<hr />
<div><strong>Welcome to the 07K Wiki</strong><br />
<br />
This Wiki is dedicated to the [[07K]] engine developed by Volkswagen. An engine known among enthusiast for its underrated potentials, reliability and its glorious 5-cylinders melody.<br />
You can expect to find anything from oil specs to engine tuning. The Wiki is in his debut, and we encourage anyone who wishes to contribute, whether it's small details or highly technical information.<br />
<br />
''You need to create an account to write / edit the Wiki.''<br />
<br />
'''First time using a wiki ? Consult our guide : [[How to use the wiki]]'''<br />
<br />
If you experience any issues, feel free to contact [/cdn-cgi/l/email-protection#f4878184849b8680b4809c91c4c39fda839d9f9d <span class="__cf_email__" data-cfemail="9ae9efeaeaf5e8eedaeef2ffaaadf1b4edf3f1f3"><nowiki>[email protected]</nowiki></span>]<br />
<br />
'''General:'''<br />
* [[Common Problems]]<br />
* [[Engine Specs]]<br />
'''Engine:'''<br />
* [[Aftermarket Parts]]<br />
* [[Engine Builds|Builds]]<br />
* [[Forced Induction (Turbocharger)]]<br />
* [[Engine Swaps]]<br />
* [[Engine Repair Guides|Repair Procedures]]<br />
'''Tuning:'''<br />
* [[Standalone Management]]<br />
'''Hardware (ECU):'''<br />
* [[ME7.1.1 Pinout]]<br />
* [[ME17.5 Pinout]]<br />
'''Additional Information:'''<br />
* [[Wiring Diagrams]]<br />
'''Facebook groups that might interest you:'''<br />
* [https://www.facebook.com/groups/247446985360343 VW 2.5l Group]<br />
* [https://www.facebook.com/groups/07kswap The 07K Project]</div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Grouppage-moderators&diff=7669MediaWiki:Grouppage-moderators2025-10-03T21:17:16Z<p>Arte: Created page with "Moderators"</p>
<hr />
<div>Moderators</div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Group-moderators-member&diff=7668MediaWiki:Group-moderators-member2025-10-03T21:16:42Z<p>Arte: Created page with "Moderators"</p>
<hr />
<div>Moderators</div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Group-moderators&diff=7666MediaWiki:Group-moderators2025-10-03T21:15:31Z<p>Arte: Created page with "Moderators"</p>
<hr />
<div>Moderators</div>Artehttps://the07k.wiki/index.php?title=File:2.5_filage_MK5.pdf&diff=7650File:2.5 filage MK5.pdf2025-09-04T15:22:07Z<p>Arte: Simplified wiring diagram for running a 2.5 with the 2005-2008 engine management
Diagram in French</p>
<hr />
<div>== Summary ==<br />
Simplified wiring diagram for running a 2.5 with the 2005-2008 engine management<br />
<br />
Diagram in French</div>Artehttps://the07k.wiki/index.php?title=File:Backup_07K906032T.zip&diff=7407File:Backup 07K906032T.zip2025-08-09T15:57:36Z<p>Arte: </p>
<hr />
<div></div>Artehttps://the07k.wiki/index.php?title=File:Fuse-matrix.pdf&diff=2986File:Fuse-matrix.pdf2024-08-06T02:30:00Z<p>Arte: Fuse matrix for calculating power consumption going through a fuse</p>
<hr />
<div>== Summary ==<br />
Fuse matrix for calculating power consumption going through a fuse</div>Artehttps://the07k.wiki/index.php?title=The_07K_Wiki:About&diff=2982The 07K Wiki:About2024-07-27T00:31:26Z<p>Arte: Created page with "The 07K Wiki is being hosted by RevMap Performance for car enthusiasts who seek and wish to supply information regarding the 07K engine"</p>
<hr />
<div>The 07K Wiki is being hosted by RevMap Performance for car enthusiasts who seek and wish to supply information regarding the 07K engine</div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Sidebar&diff=2981MediaWiki:Sidebar2024-07-26T23:51:07Z<p>Arte: </p>
<hr />
<div><br />
* Navigation:<br />
** mainpage|Main Page<br />
** recentchanges-url|Recent Changes<br />
* General:<br />
** Common_Problems | Common Problems<br />
** Engine_Specs | Engine Specs<br />
* Engine:<br />
** Aftermarket_Parts | Aftermarket Parts<br />
** Engine_Builds | Builds<br />
** Forced_Induction_(Turbocharger) | Forced Induction<br />
** Engine_Swaps | Engine Swaps<br />
** Engine_Repair_Guides | Repair Procedures<br />
* Tuning:<br />
** Standalone_Management | Standalone Management<br />
* Hardware (ECU):<br />
** ME7.1.1_Pinout | ME7.1.1 Pinout<br />
** ME17.5_Pinout | ME17.5 Pinout<br />
* Additional Information:<br />
** Wiring_Diagrams | Wiring Diagrams<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Artehttps://the07k.wiki/index.php?title=Main_Page&diff=2980Main Page2024-07-26T23:49:29Z<p>Arte: </p>
<hr />
<div><strong>Welcome to the 07K Wiki</strong><br />
<br />
This Wiki is dedicated to the [[07K]] engine developped by Volkswagen. An engine known among enthusiast for its underated potentials, reliability and its glorious 5-cylinders melody.<br />
You can expect to find anything from oil specs to engine tuning. The Wiki is in his debut and we encourage anyone who wishes to contribute whether it's small details or highly technical informations.<br />
<br />
''You need to create an account to write / edit the Wiki.''<br />
<br />
'''First time using a wiki ? Consult our guide : [[How to use the wiki]]'''<br />
<br />
If you experience any issues, feel free to contact [mailto:support@the07k.wiki support@the07k.wiki]<br />
<br />
'''General:'''<br />
* [[Common Problems]]<br />
* [[Engine Specs]]<br />
'''Engine:'''<br />
* [[Aftermarket Parts]]<br />
* [[Engine Builds|Builds]]<br />
* [[Forced Induction (Turbocharger)]]<br />
* [[Engine Swaps]]<br />
* [[Engine Repair Guides|Repair Procedures]]<br />
'''Tuning:'''<br />
* [[Standalone Management]]<br />
'''Hardware (ECU):'''<br />
* [[ME7.1.1 Pinout]]<br />
* [[ME17.5 Pinout]]<br />
'''Additional Information:'''<br />
* [[Wiring Diagrams]]<br />
'''Facebook groups that might interest you:'''<br />
* [https://www.facebook.com/groups/247446985360343 VW 2.5l Group]<br />
* [https://www.facebook.com/groups/07kswap The 07K Project]</div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Loginprompt&diff=2979MediaWiki:Loginprompt2024-07-26T23:17:00Z<p>Arte: Blanked the page</p>
<hr />
<div></div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Loginprompt&diff=2966MediaWiki:Loginprompt2024-06-20T20:58:26Z<p>Arte: </p>
<hr />
<div>{{Note|note-reminder|In an effort to prevent '''leeching''' and encourage contributions between members, some areas of the wiki have been made private and '''require an account'''. To get an account, please email '''support@the07k.wiki'''. Let us know about your background and your motives<br />
}}</div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Loginprompt&diff=2965MediaWiki:Loginprompt2024-06-20T20:57:35Z<p>Arte: </p>
<hr />
<div>{{Note|note-reminder|In an effort to prevent '''leeching''' and encourage contributions between members, some areas of the wiki have been made private and '''require an account'''. To get an account, please email '''support@the07k.wiki'''<br />
<br><br />
Let us know about your background and your motives<br />
}}</div>Artehttps://the07k.wiki/index.php?title=MediaWiki:Loginprompt&diff=2964MediaWiki:Loginprompt2024-06-20T20:54:10Z<p>Arte: Created page with "In an effort to prevent '''leeching''' and encourage contributions between members, some areas of the wiki have been private and '''require an account'''. To get an account, please email '''support@the07k.wiki''' Let us know about your background and your motives"</p>
<hr />
<div>In an effort to prevent '''leeching''' and encourage contributions between members, some areas of the wiki have been private and '''require an account'''. To get an account, please email '''support@the07k.wiki'''<br />
<br />
Let us know about your background and your motives</div>Artehttps://the07k.wiki/index.php?title=File:Me711-swap.pdf&diff=2956File:Me711-swap.pdf2024-03-22T20:03:50Z<p>Arte: Author : Emile Morin</p>
<hr />
<div>== Summary ==<br />
Author : Emile Morin</div>Artehttps://the07k.wiki/index.php?title=File:Ida-graphic-overview.png&diff=2911File:Ida-graphic-overview.png2023-11-25T23:21:58Z<p>Arte: </p>
<hr />
<div>ida-graphic-overview</div>Artehttps://the07k.wiki/index.php?title=File:Ida-subroutine-graphic.png&diff=2910File:Ida-subroutine-graphic.png2023-11-25T23:20:56Z<p>Arte: </p>
<hr />
<div>ida subroutine graphic</div>Artehttps://the07k.wiki/index.php?title=File:IDA-CODE-EXAMPLE.png&diff=2908File:IDA-CODE-EXAMPLE.png2023-11-25T23:12:33Z<p>Arte: </p>
<hr />
<div>example IDA</div>Artehttps://the07k.wiki/index.php?title=File:Ida-defined.png&diff=2907File:Ida-defined.png2023-11-25T23:11:41Z<p>Arte: </p>
<hr />
<div>ida defined</div>Artehttps://the07k.wiki/index.php?title=File:IDA-ANALYZE.png&diff=2906File:IDA-ANALYZE.png2023-11-25T23:10:11Z<p>Arte: </p>
<hr />
<div>Analyze selected area</div>Artehttps://the07k.wiki/index.php?title=File:IDA-DPP.png&diff=2905File:IDA-DPP.png2023-11-25T23:03:14Z<p>Arte: </p>
<hr />
<div>Set default segment register</div>Artehttps://the07k.wiki/index.php?title=File:IDA-load-file.png&diff=2904File:IDA-load-file.png2023-11-25T23:00:37Z<p>Arte: </p>
<hr />
<div>Load additional file</div>Artehttps://the07k.wiki/index.php?title=File:IDA-create-segment.png&diff=2903File:IDA-create-segment.png2023-11-25T22:51:41Z<p>Arte: </p>
<hr />
<div>Create memory segment</div>Artehttps://the07k.wiki/index.php?title=File:IDA-information-type.png&diff=2902File:IDA-information-type.png2023-11-25T22:49:52Z<p>Arte: </p>
<hr />
<div>IDA information type</div>Artehttps://the07k.wiki/index.php?title=File:Ida-memory-organization.png&diff=2901File:Ida-memory-organization.png2023-11-25T22:47:13Z<p>Arte: </p>
<hr />
<div>IDA memory organization</div>Arte