Typos, spelling

This commit is contained in:
Carsten Schmiemann 2024-03-30 00:08:57 +01:00
parent 0d158eaa78
commit ccf81d6ca6
1 changed files with 10 additions and 10 deletions

View File

@ -28,12 +28,12 @@ I then try to reverse engineer the frames sent to control the Easylink system.
## What needs to be done
- Control ESP via GPIOs
- Control ESP via Serial connection
- Reverse engineer of anti-theft / VIN protection calculation
- Test microphone connection
- CAN msg Full MUTE of Easylink
- CAN msg for speed signal (for rising and lowering volume)
[] Control ESP via GPIOs
[] Control ESP via Serial connection
[] Reverse engineer of anti-theft / VIN protection calculation
[] Test microphone connection
[] CAN msg Full MUTE of Easylink
[] CAN msg for speed signal (for rising and lowering volume)
## Picture of dumping
@ -58,7 +58,7 @@ The EXT-CAN which is used to control the Easylink is terminated in CAN gateway w
### Touchdisplay
Likely you will connect a touch display to it, it will use LVDS signaling over a HSD cable. You can buy one off Aliexpress or similar, use the Z Coding (universal can plug into all color coded sockets) so you dont need mess up with color codes to match the connectors.
Likely you will connect a touch display to it, it will use LVDS signaling over a HSD cable. You can buy one off Aliexpress or similar, use the Z Coding (cyan, universal can plug into all color coded sockets) so you dont need mess up with color codes to match the connectors.
The display will be controlled via M-CAN bus which is driven from the Easylink itself. So you need to connect CAN lines from the Easylink to the display and back, because CAN is terminated in the Easylink itself. Of course you can install termination resistors on the display itself.
@ -178,13 +178,13 @@ Fakra to SMA antenna adapters for example, use the cyan ones which can plug into
# Programming with pyren, DDT4all, CLIP or something
You can program the Easylink with mentioned tools like in your car, just make another connection to the EXT-CAN (of course no termination on this point).
I have buied a OBD2 socket to breakout cable and connected some dunpont connectors to it, but you can buy a OBD2 Socket and connect it permanent to it, to use standard OBD2 dongles.
I have buied a OBD2 socket to breakout cable and connected some dunpont connectors to it, but you can buy a OBD2 Socket and connect it permanent to it for using standard OBD2 dongles.
## Setup vehicle configuration
I unplugged my unit from my car and replaced it with a big screen one, so I left my vehicle / CAN bus configuration as is.
If your unit is from another car brand and the unit is not behaving as it should with these CAN messages in my program, set the vehicle configuratio to:
If your unit is from another car brand and the unit is not behaving as it should with these CAN messages in my program, set the vehicle configuration to:
- Renault Message Set
- Slot 1 (C1A)
@ -218,7 +218,7 @@ Connect the clip again and erase, write and verify the contents.
If the unit is from a car which ECUs is partly working (Easylink is starting up in that car it will removed) you can read the CAN message which contains the VIN. You need to connect a CAN sniffer, dongle or something to the V-CAN, M-CAN or EXT-CAN and note the contents of the CAN ID 0x69F.
If you can not capture the 0x69F frame from the donor car, you need to connect via DDT (it will work even it will says locked) and copy the entered VIN. Then calculate the neccessary CAN bytes with the last 7 digits from the VIN number backwards and add a F at the last byte. Here is an example:
If you can not capture the 0x69F frame from the donor car, you need to connect via DDT (it will work even it will says locked) and copy the entered VIN. Then calculate the neccessary CAN bytes with the last 7 digits from the VIN number in reverse order and add a F at the last byte. Here is an example:
![Can frame calculation](doc/can_at_calc.png)