[X]Assistant

[antonio-dj]

Discussion MMS2190 / 2192 hardware & drivers

Primary theme on MMS |
This topic will discuss issues related to hardware MMS 2119/2192, as well as drivers and special programs.

Rules of conduct in the subject

1. Before asking a question, examine the header and use the search on this topic, as well as ontopic1, topic2. And read the joke:
   
   Joke

   Once the Chukchi brought his novel to the editor. The editor has read and says:
   - You see, weakly ... You would read the classics. Did you read Turgenev? And Tolstoy? And Dostoevsky? ..
   - However, no: the Chukchi is not a reader, the Chukchi is a writer.
   
   
   
2. Specify the brand of MMS (Grant, Kalina2 / Priora, Datsun), version of MMS, version of firmware MMC, version of firmware of can controller, etc.
   
3. Duplication of a question is PROHIBITED.
   
4. Questions and off-topic comments are FORBIDDEN.
   
5. To compare the device with competitors and on the choice of devices, please contact:Selection and Comparison
   
6. Before posting photos, read the topicWorking with Images on the forum
   
7. Messages that are not related to the topic of discussion (offtopic) are deleted without warning.
   

Read firstFAQ
Bt dll- Library for communication with the BlueTooth module in the MMS is locatedhere.
CAN DLL- the library for communication with the CAN controller in MMS ishere.
CAN controller firmware- firmware for the CAN controller in the MMC arehere.

Additional software

There will be links to additional software.

Photos of the visceraFoto_2190-2192.zip(35.74 MB)

We have to say on the forum "thank"by increasing your reputation! (see p. p 4)
Huge request when chatting / reading threads use buttonsand

Project Assistance

If someone wants to financially support the development of my projects, I will be very grateful!
Donut inprofile
Thanks for the help:Elkent, Andrej SARAN, alexpda_4, kukin-tuman

Post has been editedantonio-dj - 25.03.17, 09:16

[antonio-dj]

FAQ:

1. What is MMS?

MMS - multimedia system
MMS2190 (2190-79000010-00, -50) is installed on the cars LADA GRANTA, (2190-79000010-10, -30) on Datsun.

Appearance MMS2190

MMS2192 (2192-7900200 - the main unit, 2192-7900100 - display module) is installed on the cars LADA KALINA2 and LADA PRIORA2.

Appearance MMS2192

2. What are the "insides" of MMS?

Brief characteristics:
CPU: SiRF Atlas-V AT551
RAM: 128 MB DDR2 (NANYA NT5TU64M16GG)
Flash: 128 MB (SAMSUNG K9F1G08U0D-SIB0)
Board controller: Panasonic MN101EF31G
Display controller: TW8816
Audio mixer: TEF6616
Audio power amplifier: TDA7388
Tuner: TEF6616
CAN controller: S9S12G96F0CLF
More details can be read "Likbez on hardware".
Still "Likbez on Bluetooth"and"CAN on CAN"

3. How to restart MMS?

The MMC restarts from the on state when the power management button is held for 15 seconds.
When you turn off the MMS, it goes to sleep, and not completely power off. All RAM is saved.
Full shutdown is possible only when the power is disconnected from the MMC (dropping the battery terminal).

4. How to find out the software version (firmware)?

1. The version of the native software is indicated on the label, which is located on the MMC body.
2. In the standard shell in the INFO menu you can see the version of the installed firmware.
2+. For those who are too lazy to read the instructions:
Turn on MMS (I hope not to explain how to do it :-)), and go to the main menu. Next, click the arrow "Right" (located at the bottom of the screen) and see the continuation of the main menu. In the continuation of the main menu, press the button "INFO".

5. What is “Firmware”?

The firmware is a build of Windows CE with built-in add-ons and a standard shell.
The firmware consists of 4 files:
Chain.bin is the header file for the firmware, there are no files there, only the offsets that the loader needs.
chain.lst - a list of firmware files, needed for the bootloader, so that he knows what to sew.
NK.bin - archive of main files.
TINYNK.bin is a very important file, it contains firewood for flash SD memory cards, the registry and the main files needed to start the box before loading Windows.
Firmware for MMC Grants and Kalina / Priors are not compatible!

6. What is firmware needed for?

1. To enable access to the Windows desktop from the standard shell.
Access to the desktop is carried out by holding (about 5 seconds) the “Settings” button in the standard shell. Access to the desktop is impossible in the firmware version: 2.2.2.11
2. To Russify Windows CE. In some programs without Russification of Windows, the inscriptions in Russian are incorrectly displayed.
3. To upgrade to a newer / stable version.

7. How to upgrade firmware?

To download the firmware in the MMC, you must:
0. Remove all devices from USB.
1. Format the SD memory card (up to 4GB) in FAT format (FAT16).
2. Copy the firmware files to the root of the SD memory card.
3. Insert the memory card in the MMC.
4. Enable MMS, wait for the download.
5. With the MMS on, press and hold (for about 15 seconds) the power on / off button to reset the MMS.
6. After rebooting, the MMC checks the presence of a memory card and the presence of firmware files on it. If files are found, MMC starts updating the firmware.
7. The firmware consists of 4 stages, the course of which is displayed on the MMS screen.
8. After the firmware is completed, Windows CE starts up and the programs that are indicated to run this firmware in the registry.
P.S. MMS is stitched only from the memory card. With USB is not sewn.

8. What is Altmenu?

Altmenu is an alternative finger-oriented shell for displaying the necessary data, controlling devices (switching and setting up sound, Bluetooth, etc.) and launching applications.

9. After the firmware is hanging icon LADA. What to do?

Probable problem 1: incompatible firmware. Solution options:
1. Find "your" firmware and reflash.
Probable problem 2: the LADA icon hangs because nothing starts. Solution options:
1. Remove all devices from USB.
2. Turn off the power of the MMC (remove the battery terminal) for 5 minutes.
3. Reflash again by copying the files to the SD card using the new one.

10. Altenu does not work. What to do?

If this happens after installation or upgrade. Most likely some menu files are missing. This could happen for several reasons:
1. Not copied files to media (SD / USB) from which the installation / update was made.
2. Not enough memory in MMC to install this menu. Perhaps there were files from the past menu.
If this happened with a working menu. Menu files may be damaged.
Solution options:
1. Go to the desktop by creating an empty explorer.txt file in the root of the SD card or USB flash drive and restarting MMS. Then delete and set the menu again.
2. If it does not work on the desktop, then flash the MMS again and install the menu.
Tip: in order to avoid such a problem (it does not go to the desktop from the menu even when rebooting), do not set the autostart menu !!!

11. What firmware is right for me?

First of all, "dear". That is, the one that was from the factory.
Also there are "custom" (modified) firmware in which something is added. For example, Russian localization, a large keyboard, drivers for WiFi-USB adapter, etc.
But there are several types of iron, and therefore only the corresponding firmwares are suitable for each type.
In MMS 2190 without navigation, there are several types of hardware and, accordingly, firmware (rev.1, rev.2, rev.3).
ATpost with firmwareThere is an explanation of how to determine the firmware version.
There are also some copies of MMC with specific firmware, a dump which no one has shot. Therefore, on such MMS there are no firmware on the forum. Other firmware does not fit them and turn MMS into a "brick" or, at best, into a "disabled".
In general, the firmware usually does not "kill" MMS completely. The loader remains working and you can flash MMC with another firmware.

12. What is the CAN firmware?

CAN firmware is a CAN controller firmware that is in MMC. Lookpost with CAN firmware

13. After CAN firmware in the post, shows version 0

In the staff (standard shell), the version is updated when you turn on the MMS with the loaded staff.
That is, if you start up the desktop from the desktop, it will not send the read version request to the CAN controller.
If the loaded shtatku turn off and then turn on the MMC (do not restart, namely, OFF>ON), then the staff should send a read request to the CAN controller.
If this does not help, then perhaps the CAN controller has a broken firmware.

14. What players are used in Altmenu?

Nitrogen
VoPlayer
Singleplayer
NaviPlayer
TCPMP

15. What GPS receivers can I use with MMS?

1. USB GPS receivers:
- GlobalSat BU-353S4.
- Digma M1.
- VK-162, clone u-blox 6.
- VK-172, clone u-blox 7 (very often it works only through a USB hub).
2. Staff GPS receiverwhich is located in the instrument cluster and transmits data via the CAN bus.

16. Navitel does not catch satellites

Navitel should not catch satellites))
GPS check.

17. How to install drivers on ...

Information on drivers for WinCE and manual installation

18. Where to download the navigation program?

In the Internet ))
From the rules of the forum:
4.20. It is strictly forbidden to search and publish keys, cracks and other applications of software developers whose programs are prohibited on the forum.

19. How to install the program in MMS

As a rule, programs for MMS do not need to be installed by a special installer.
Practically all programs are “portable” (Portable), that is, they work directly from the folder when the main executable file (exe) runs.
However, it should be borne in mind that external drives (SD, USB) when you turn on the MMC "come to life" not immediately.
Therefore, the program is running or reading data from an external drive when you turn on (wake) MMS can give an error and "fly out".

20. In Altmenu, the sound does not work when playing music through BlueTooth

In the altmenu when playing music via BlueTooth you need to manually switch the sound source.
In the description of the menu is written how to do it.

21. WiFi

Post about WiFi
Instructions for connecting a WiFi adapter using the example of D-Link DWA-140 rev. B2from CrazyDron.

22. MMC does not see the SD card.

1. Tried to stick the card with the other side.
Most likely, the contact bent in the connector.
Solution: repair the connector.
2. The SD card is exactly working with the FAT or FAT32 file system. On the computer works.
Something "flashed" in WinCE (driver / cache / registry entries).
Solution: flash MMS.
The answer to the question "How can I flash if the MMS does not see the SD card?"
(MMS does not see the SD card) = (WinCE does not see the card), but (Boot Loader that is flashing MMS) Рњ (WinCE).
In other words: If the MMC (WinCE) does not see the SD card, this does not mean that the bootloader, which reflash the MMS, will not see it.

23. MMS does not see a USB flash drive.

1. The file system on the USB flash drive has an unsupported format.
Supported file systems: FAT, FAT32, ExFAT.
Solution: Use a supported file system.
2. Something "flown away" in WinCE (drivers / cache / registry entries).
Solution: flash MMS.
3. Faulty USB connector or cable.
Solution: repair the connector / cable.

24. Altmen does not display CAN data or all values ​​of 0.

1. The CAN bus is not connected to the MMC or is connected incorrectly.
Solution: Connect the CAN bus according to the diagram.Example 1. Search in Yandex.
2. The program (firmware) does not work in the CAN controller.
In this case, the CAN version will also not be read.
Solution: flash / restore the firmware in the CAN controller.
3. Malfunction in the CAN exchange scheme in MMC.
CAN controller or CAN transceiver may be faulty.
Solution: repair MMC (replace defective items).
PS: I have not heard about such a case yet.

25. Rear view camera does not work.

1. Camera switching is not activated in MMC. When you turn on the rear sound is muted, and the video signal does not switch.
Solution: activate using a program or menu.
Attention!When you start the regular MMS menu with navigation, the camera switch is deactivated. To use the camera with a regular menu, you need an MMC firmware with a camera deactivation patch.
2. The reverse gear enable signal is not connected to pin A1 of the ISO connector.
Solution: connect.
3. Camera malfunction.
Solution: repair or replace the camera.

26. In MMS with standard navigation does not work GPS.

The standard GPS receiver is located in the instrument cluster and transmits data via the CAN bus.
A large batch of cars was released, in which the instrument cluster stopped sending GPS data via CAN-bus. Helped complete power outage of the instrument cluster. The Officials changed the instrument cluster warranty to those who applied.
There may be other reasons:
1. Defective GPS module in the instrument cluster.
Solution: repair or replace instrument cluster.
2. Faulty connection to GPS antenna. GPS antenna is located in the body of the combined antenna on the roof. The cables from these antennas are on the right rack and are connected to the corresponding cables near the stove. The GPS antenna cable (has a pink connector case) connects to the cable that goes to the instrument cluster.
Solution: repair.
3. The CAN controller in MMC is faulty.
Solution: repair (flash or replace).

Post has been editedantonio-dj - 23.10.17, 08:42

[antonio-dj]

CAN DLL

You do not need to throw new DLLs in MMS, the developers of altmenu and additional buns post them in their assemblies.
From the fact that you change the old DLLKI on the new, most likely, nothing good from this will change.
A DLL is not a program, but simply a library that gives the program additional features (if the program uses these features).

mmc_can_V2.11.2.0.zip(153.63 KB)

Changes:
- when you turn on the cruise or limiter, the message about changing the status of the steering wheel buttons is not displayed.

CAN test program

mmc_can_test_V1.4.2.zip(65.8 KB)

Button "RESET ERRORS OBD2" - Reset of errors of the CSDC using the OBD2 command
Button "RESET ECU 1" - Reset KSUD with parameter 1 (simple reset)
Button "RESET ECU 144 (F)" - Reset KSUD with parameter 144 (90 hex) (Reset to factory settings)
Button "RESET ECU 145 (L)" - Reset KSUD with parameter 145 (91 hex) (Reset training)
Button "FAN 1 ON" - KSUD command to turn on the fan 1
Button "FAN 1 OFF" - KSUD team to transfer control of the fan 1 KSUD
Button "FAN 1 ON" - KSUD command to turn on the fan 2
Button "FAN 1 OFF" - KSUD command to transfer control of the fan 2 to KSUD
The field with the number - the required speed XX
"+" and "-" change the value of these revolutions
Button "SET IDLE" - Write the required speed in KSUD
Button "TESTER PRESENT" - Keeping in touch with KSUD (for personal tests)
Button "READ ERR 3 OBD2" - Sends a request to read errors via the OBD2 protocol (accumulated)
Button "READ ERR 7 OBD2" - Sends a request to read errors via the OBD2 protocol (current)
Below 2 fields - software odometer and fuel consumed.

Sources

mmc_can_src_2.9.0.zip(964.28 KB)

Older versions

mmc_can_V2.11.1.1.zip(153.66 KB)

Changes:
- Minor fixes

mmc_can_V2.11.0.0.zip(157.02 KB)

Changes:
- Added data from IR remote from Ahmed
- Added data of cruise control status and brake pedal (ID: 35D in firmware 1.11, 1.23)
- Added data from a 6-button steering wheel console (ID: 4A2 in firmware 1.11, 1.13 and 1.23).

mmc_can_V2.8.0.0.zip(166.41 KB)

Changes:
- Added climate data
- Added data from the instrument cluster (ID: 2DE in firmware 1.10)
- Added reading version of CAN.

mmc_can_V2.7.0.0.zip(165.68 KB)

Changes:
- Fixed OBD2 PID requests with MODE = 01
- Added the ability to receive GPS data from the receiver in the instrument cluster.

mmc_can_V2.6.0.0.zip(165.23 KB)

Changes:
- Added a change in bedtime.
- Added climate data.
- Added the ability to send requests and read OBD2 PID with MODE = 01
- Added the ability to get the engine speed (ID: 180). For implementation, you need to edit the firmware of the CAN controller so that it reads this ID.

mmc_can_V2.5.7.0.zip(164.15 KB)

Changes:
- Added reading more than 2 errors.

mmc_can_V2.5.6.1.zip(153.48 KB)

Changes:
- Added error code display string.

mmc_can_V2.5.5.3.zip(163.57 KB)

Changes:
- Fixes reading errors on OBD2.

CAN test program
mmc_can_test_2014-12-16_001.zip(68.41 KB)


V2.5.5.1
Changes:
- Added reading errors on OBD2.

mmc_can_V2.5.4.2.zip(161.05 KB)

Changes:
- Fixed possible loss of bus activity.

mmc_can_V2.5.4.1.zip(161.05 KB)

Changes:
- Fixed the air temperature overboard in Wparam.

mmc_can_V2.5.4.zip(163.1 KB)

Changes:
- Fixed team maintain communication.
- Changed the temperature values ​​in the transmitted parameters.
- Added instant consumption. May not work or not work at all!

mmc_can_V2.5.3.zip(162.96 KB)

Changes:
- Added a team to maintain communication.

mmc_can_V2.5.2.zip(162.88 KB)

Changes:
- Added control relay 2 cooling fans.

mmc_can_V2.5.1.zip(160.23 KB)

Changes:
- Small fixes.

mmc_can_V2.5.0.zip(162.71 KB)

Changes:
- Added data to the WPARAM variable in all messages.

mmc_can_V2.4.2.zip(160.71 KB)

Changes:
- Fixed odometer.

mmc_can_V2.4.1.zip(160.77 KB)

Changes:
- Odometer corrected. (Does not work :-))

mmc_can_V2.4.0.zip(162.73 KB)

added:
- resetting errors ABS, automatic transmission, SNPB;
- fixed odometer;
- the state of fuel consumption (for evaluating the engine running)
Attention! Changed the returned data. Instead of float, int is everywhere. Carefully read the description (in the archive).

mmc_can_V2.3.4.zip(130,02 KB)

Changes:
- Fixed possible loss of bus activity.

mmc_can_V2.3.2.zip(162.24 KB)

added:
- heated windshield (for cars with the central pulp and paper center)
- the value of the setpoint temperature of the cabin (for the grant with the climate)

mmc_can_V2.3.0.zip(162.1 KB)

added:
- brake pedal switch (for cars with ABS) on K2 (CAN version 1.13), data from ABS is not caught, therefore it does not work.
- heated rear window (for cars with the central pulp and paper center)
- dipped and main beam (for cars with a central processing unit
- door switches (for cars with TsBKE)
- Turning (for cars with PPM)
- cabin temperature (for grant with climate)

mmc_can_V2.2.0.zip(160.88 KB)

Added calculation of the path and fuel consumption.

Post has been editedantonio-dj - 26.09.16, 11:08

[antonio-dj]

Bt dll

You do not need to throw new DLLs in MMS, the developers of altmenu and additional buns post them in their assemblies.
From the fact that you change the old DLKI for new nothing good from this can not change.
A DLL is not a program, but simply a library that gives the program additional features (if the program uses these features).
Full version.
mmc_bt_V2_7_1_0.zip(307.01 KB)

- small changes in the algorithm for receiving data from the module.
- Added Uninit function.

Screenshots

Full

Lite

Old

Full and lite version.
mmc_bt_and_bt_lite_2.6.3.5.zip(564.94 KB)

- minor corrections to the registry and write to save the settings for auto-connect and auto-answer.

Full version with book and BT icon.
mmc_bt_V2_6_3_4.zip(265.84 KB)

- added icons to the settings window;
- minor fixes.
Full version with book and BT icon.
mmc_bt_V2_5_2.zip(254.98 KB)

Changes:
- Corrected badge.
- The call button in the book fixed the error.

Full version with book and BT icon.
mmc_bt_V2_5_0.zip(254.76 KB)

Changes:
- Added the ability to display the BT icon, change its color or use BMPs.
- Added a call button to the book.

Build of two versions (full and light)
mmc_bt_V2.4.2.zip(533.21 KB)

Changes:
- Added saving in the registry the status of auto-connect and auto-answer in both versions
- The book is in full version.

Build of two versions (full and light)
mmc_bt_V2.4.1.zip(527.51 KB)

Changes:
- Added auto answer to both versions (not verified).
- Minor bug fixes.
- The book in the full version does not work yet (I don’t know if there is enough time and energy for it).

Light version (only with pairing window)
mmc_bt_lite_V2.4.0.zip(235.67 KB)

Changes:
- Added auto answer (not verified).
- When you click on the Bluetooth icon (in the lower right corner of the settings window), the UpdateLocalDeviceStatus command is sent (the call and connection states are updated). Works in the previous version.
mmc_bt_V2.3.2.zip(200.88 KB)

Changes:
- Slightly modified the settings window.
mmc_bt_V2.3.1.zip(204.63 KB)

Changes:
- Added functions to work with the book.
- Slightly modified the settings window.
mmc_bt_V2.3.0.zip(204.14 KB)

Changes:
- Changed the functions of working with a book.
- Slightly modified the settings window.
mmc_bt_V2.2.0.zip(188.8 KB)

Changes:
- Added GetBatteryCharge () function and WM_BT_CHANGE_BATTERY_CHG message.
- Changed the message numbers !!!!! WM_BT_CHANGE_OUT_MUTE_STATE, WM_BT_START_INIT, WM_BT_FINISH_INIT, WM_BT_FINISH_READ_DEVICES, WM_BT_DISCONNECT_ACTION
- Slightly modified the settings window.
mmc_bt_V2.1.0.zip(183.55 KB)

Changes:
- Fixed bug when reading the book file.
- Added UpdateLocalDeviceStatus function. Changed message numbers !!!!!
- MicVol and SetRingToneLevel functions checked. The module responds with a "function not supported" error.
- Added ShowWndSettings function of opening the window for settings, searching and pairing devices (will be further refined).
mmc_bt_V1.0.0.zip(166.46 KB)

A completely new DLL. Description in the archive.
BluetoothMMC_V1_4_6.zip(161.76 KB)

Changes:
- Added dialW function
BluetoothMMC_V1_4_5.zip(161.64 KB)

Changes:
- the values ​​of the GetConnState function are changed
- added reset to the Init function at the first and repeated function call
BluetoothMMC_V1_4_4.zip(247.56 KB)

Changes:
- Added BT signal level
- added mute state
The archive also has icons for indicating states.
BluetoothMMC_V1_4_3.zip(162.02 KB)

Added by:
- Ability to read the name from the phone book book.bk if the number is defined.
- Slightly corrected events in the code.

BluetoothMMC_V1_4_2.zip(161.53 KB)

Added by:
- the ability to read entries in the phone book

Programfor testing BT.

Post has been editedantonio-dj - 23.07.16, 15:28

[antonio-dj]

Likbez on Bluetooth.

The built-in Bluetooth (also known as BT or BT) is built on the nFore NF2301 module.
This module has its own firmware and is connected to the processor MMS interface UART (COM-port).
The connection scheme is approximately the same as on the MDN-2640T radio tape recorder. The network has a service manual on it with the scheme.
He communicates according to the protocol of the developer company of the module.
Descriptions of this protocol are not publicly available, so I had to carry out a bunch of experiments in order to decipher part of the protocol.
The module (or rather its firmware) works only with profiles: HSP + A2DP + AVRCP.
CoD (Class of Device) of our MMS: 7A 00 09 (09 - Hands-free Device)
Decrypt watchhereorhere
The SPP profile does not work (or I do not know how it can work with it). So it will not be possible to connect ELM327-BT or GPS-BT or the Internet via BT, as long as there is no complete description of the protocol. Or maybe it will not work at all if there is no support for this in the module firmware.
If it is still not clear, then more:
Distribute the Internet from your phone via Bluetooth will not work, because (see above in bold)
Connect a GPS receiver via Bluetooth (for example, Holux M-1000 or GlobalSat BT-386), because (see above in bold)
Connect via Bluetooth as a GPS receiver to a smartphone or other device does not work, because (see above in bold)
Connect via the Bluetooth auto diagnostic device (for example, ELM327) does not work, because (see above in bold)

When installing an MMS pairing (or rather, a Bluetooth module), it requests the code 0000. But if the phone also has a password request configured, then MMS will not be able to connect to it. At least I don’t know how to instruct the Bluetooth module to send a pairing password to the paired device.

Wikipedia material:
- Headset Profile (HSP) - used to connect a wireless headset (Headset) and phone. Supports the minimum set of AT-commands of the GSM 07.07 specification for ensuring the possibility to make calls, answer calls, end the call, adjust the volume. Through the profile of the Headset, with Bluetooth 1.2 and above, you can display on the headset all the sound of the phone. For example, you can listen to all the operation confirmation signals on the headset, mp3 music from the player, ringtones, and a number of video clips. Headsets that support this profile have the ability to transmit stereo, unlike models that support only the Hands-Free profile.
- Advanced Audio Distribution Profile (A2DP) - designed to transmit two-channel stereo audio stream, such as music, to a wireless headset or any other device. The profile fully supports the low-compressed Sub_Band_Codec (SBC) codec and optionally supports MPEG-1.2 audio, MPEG-2.4 AAC and ATRAC, and is capable of supporting codecs defined by the manufacturer. [15]
- Audio / Video Remote Control Profile (AVRCP) - designed to control the standard functions of TVs, Hi-Fi equipment and other things. That is, it allows you to create devices with remote control functions. Can be used in conjunction with A2DP or VDPT profiles.
- Serial Port Profile (SPP) - based on the ETSI TS07.10 specification and uses the RFCOMM protocol. The profile emulates a serial port, providing the ability to replace the standard RS-232 wireless connection. It is the base for profiles DUN, FAX, HSP and AVRCP.

Post has been editedantonio-dj - 29.07.16, 08:52

[antonio-dj]

Educational program on the CAN bus.

Description of the CAN bus and controller firmware in MMC

useful links

https: //ru.wikipedia.o…ontroller_Area_Network
https://en.wikipedia.org/wiki/CAN_bus
http://wiki.zr.ru/CAN-%F8%E8%ED%E0

Before you begin, I recommend to get acquainted withMMC hardware.
CAN message (frame) consists of several parts. But we are only interested in 3 parts:
ID - identifier, 11 bits in our case.
Data field - up to 8 bytes.
Ack - confirmation of receipt of the message.
Each device on the CAN network can send a message to the bus.
And every device on the network can see this message and process it on its own.
But each device sends an acknowledgment of receiving only "its" messages. That is, messages with the corresponding ID.
To configure the reception of "their" messages in the CAN-bus controllers, as a rule, there are parameters: ID Addr, ID Mask.
In some controllers it is possible to set several groups of such parameters.
In our MC9S12 (judging by the documentation), you can use up to 4 ID Addr + ID Mask groups to filter 11-bit IDs.
In firmware 1.7 for receiving "your" message was ID 7F0, the mask is not known.
The ID in the firmware was found and changed to 7E8 (KSUD message for diagnostic requests). It worked.
The remaining IDs that were found in the firmware are not “their own” IDs.
These ID controllers in the MMC just read but do not confirm receipt.
Confirms the receipt of these messages any other device on the network.
In MMS, with navigation, a whole group of "their" GPS data messages (4A4 ... 4AE).
That is, there is a main ID and mask 00F or 00E is applied (and maybe another one).
GPS message IDs (4A4 ... 4AE) in the firmware are observed. But where the mask is installed is unknown.
At the request of members of the forum, I made 1.7 firmware with an ID for receiving GPS messages.
However, these messages were not "their". That is, without confirmation of receipt.
On this, the transmitter, attempting to transmit messages and did not receive confirmation, stopped sending new messages.
Thus, in order for the CAN controller in the MMC to accept 7E8 and 4Ax messages as “its own”, you need to use 2 groups ID Addr + ID Mask.
This can be done in the source for the firmware. However, we do not have the source code, and accordingly we will have to choose either a diagnostic system or a standard GPS.
Of course, there is another way - to put another device on the bus that will simply receive messages with a GPS ID (4A4 ... 4AE).
Then these messages will be caught by the firmware converted from 1.7.

Only the IDs that are transmitted to the COM port depend on the firmware of the CAN controller.
Further this data is taken and decrypted by the DLL, program, menu, anyone.
Now SM and NM use my DLL in which the data is being decrypted and this data is being output.
Thus, it depends on the DLL what data it can decrypt.
Further, the menu can take this data, and maybe not take it. It depends only on the menu.

MMC receives parameters via CAN-bus from various sources.

Speed ​​- instrument cluster (ID 280);
Outdoor temperature - instrument cluster (ID 280) (provided that the sensor is connected);
The remaining fuel in the tank - the instrument cluster (ID 280);
Engine temperature - KSUD (ID 551)
Check engine - KSUD (ID 551)
Battery Charge - KSUD (ID 551)
Low oil pressure - KSUD (ID 551)
Excess of temperature of the engine - KSUD (ID 551)
Fuel consumption - KSUD (ID 551)
Automatic transmission temperature - automatic transmission controller (ID 560)
Seat belt status - SNPB controller (ID 498)
Door status - central processing room (ID 481)
The state of the light near and far - TSBKE (ID 481)
The state of the blinkers - TSBKE (ID 481)
The state of the heating of the windows (wind and rear) - central processing room (IDKE) (ID 481)
The state of the brake pedal - ABS controller (ID 354) and KSUD (ID 35D)
Temperature in the cabin - the climate controller Kalina 2 (ID 555)
The state of the setpoint temperature controller climate Kalina 2 (ID 555)
Flow Directional Condition - Kalina 2 Climate Controller (ID 555)
Fan speed status - Kalina 2 climate controller (ID 555)
Handbrake condition - instrument cluster (ID 2DE)
Condition dimensions - instrument cluster (ID 2DE)
GPS data - instrument cluster (ID 4A4, 4A6 ... 4AE)
Data under the steering wheel 6-button switch on the instrument cluster with built-in GPS (ID 4A2)
Turns of the engine - KSUD (ID 180)
Answers to diagnostic requests KSUD - KSUD (ID 7E8)

Grant in pickings is standard and there is no CBKE
In Kalina 2, there is no standard equipment
In Priore 2, the climate has no CAN bus

Post has been editedantonio-dj - 12.07.17, 15:41

[antonio-dj]

Drivers for WinCE6.0.
On the Microsoft website there is a search for supported drivers.HERE.
From interesting only: UFNVideoCam.dll - universal webcam driver (as I understood it).
Also mentioned FTDI, but no Profilic PL2303 and Silabs CP210x.

A small educational program for drivers.

Here isherewritten to create a driver for WinCE and especially about the branches in the registry for it.
And fromMSDN.
I will decipher a little.
When a USB device is connected to WinCE, the identification data of the device is read according to the structureUSB_DRIVER_SETTINGS
dwVendorId: VID - manufacturer ID;
dwProductId: PID - product identifier;
dwReleaseNumber: REV - version;
dwDeviceClass: DEVCLASS - device class;
dwDeviceSubClass: DEVSUBCLASS - device subclass;
dwDeviceProtocol: DEVPROT — device protocol;
dwInterfaceClass: INTCLASS - interface class;
dwInterfaceSubClass: INTSUBCLASS - interface subclass;
dwInterfaceProtocol: INTPROT - interface protocol;
Next, the operating system tries to load a driver for this device (MSDN).
In the registry, the driver is written as follows (MSDN).:
[HKEY_LOCAL_MACHINE \ Drivers \ USB \ LoadClients \<Group1_ID>\<Group2_ID>\<Group3_ID>\<Drivername>\]
And the key pointing to the file (DLL) is:
[HKEY_LOCAL_MACHINE \ Drivers \ USB \ LoadClients \<Group1_ID>\<Group2_ID>\<Group3_ID>\<Drivername>\ DLL]
Group1_ID is the VID, PID and REV. May have priority values ​​Default,<Vid>, <Vid>_<PID>, <Vid>_<PID>_<Rev>. The values ​​of VID, PID and REV must be in decimal form.
Group2_ID is DEVCLASS, DEVSUBCLASS and DEVPROT. May have priority values ​​Default,<DEVCLASS>, <DEVCLASS>_<DEVSUBCLASS>, <DEVCLASS>_<DEVSUBCLASS>_<DEVPROT>. Values ​​are also in decimal.
Group3_ID is INTCLASS, INTSUBCLASS and INTPROT. May have priority values ​​Default,<INTCLASS>, <INTCLASS>_<INTSUBCLASS>, <INTCLASS>_<INTSUBCLASS>_<INTPROT>. Values ​​are also in decimal.
Thus, the drivers are loaded by priority:
1) [HKEY_LOCAL_MACHINE \ Drivers \ USB \ LoadClients \ Default \ Default \ Default \<Drivername>\ DLL].
2) [HKEY_LOCAL_MACHINE \ Drivers \ USB \ LoadClients \<Vid>\ Default \ Default \<Drivername>\ DLL]
3) [HKEY_LOCAL_MACHINE \ Drivers \ USB \ LoadClients \<Vid>_<PID>\ Default \ Default \<Drivername>\ DLL]
4) [HKEY_LOCAL_MACHINE \ Drivers \ USB \ LoadClients \<Vid>_<PID>_<Rev>\ Default \ Default \<Drivername>\ DLL]
5) [HKEY_LOCAL_MACHINE \ Drivers \ USB \ LoadClients \ Default \<DEVCLASS>\ Default \<Drivername>\ DLL].
6) [HKEY_LOCAL_MACHINE \ Drivers \ USB \ LoadClients \ Default \<DEVCLASS>_<DEVSUBCLASS>\ Default \<Drivername>\ DLL].
and so on.

Manual driver installation for USB↔COM converter.

1. Definition of USB↔UART chip. In order to determine the chip, you need to plug the GPS receiver (USB) into the PC, and in the device manager, view information about the hardware ID.
If VID = 067B and PID = 2303 then this is a PL2303 chip.
If VID = 0403 and PID = 6001 then this is an FTDI chip.
If VID = 10C4 and PID = EA60, then this is a CP210x chip.
If VID = 1546 and PID = 01A6 then this is u-blox 6.

In our case, the driver consists of one library that is not part of Windows CE (232usb.dll) and registry entries.
In order for the device to work, you must copy the file to the device and register it in the registry:
- Path: [HKEY_LOCAL_MACHINE \ Drivers \ USB \ LoadClients \ 1659_8963_1024 \ Default \ Default \ RS232_USB]
where 1659_8963_1024 is VID_PID_REV in decimal form (that is, VID = 067B, PID = 2303, REV = 0400). These data must be viewed in the device information by connecting it to a PC. If the VID, PID or REV is different from the above, but you are sure that the chip is PL2303, then you need to change the path according to your data.
- “FriendlyName” = “USB-Serial Controller D, pl2303” key (string parameter of the device name)
- “UsbMode” key = dword: 00000101 (DWORD value of USB operation mode decimal value 257)
- Key “SendEndp” = dword: 00000002 (DWORD parameter)
- Key “ReceiveEndp” = dword: 00000083 (DWORD parameter decimal value 131)
- “ClassEndp” key = dword: 00000081 (DWORD parameter decimal value 129)
- The key "DeviceType" = dword: 00000001 (parameter DWORD device type)
- Key “Index” = dword: 00000005 (parameter DWORD COM port number)
- Key "Tsp" = "Unimodem.dll" (string parameter of the additional driver)
- Key “Prefix” = “COM” (string parameter of the port name prefix)
- “Dll” key = “\ staticstore \ dll \ 232usb.dll” (a string parameter of the main driver with a location)
Notes:
* The driver file is best located in the internal memory of the MMC which does not return to its original form after a reboot. For example, such a place is StaticStore or ReadOnlyFlash, depending on the firmware. For example, in NewMenu, the driver is copied to staticstore \ dll \ 232usb.dll during installation.
* Registry entries can be added in several ways:
- With the help of the registry editor manually.
- Importing the .reg file (if you have one) using the registry editor. The "Dll" key must contain the correct path!
- By running the script (if you have one). The "Dll" key in the script must contain the correct path!

PS: There is still quite a simple way. If you have a driver in the form of a DLL, you need to place it in the internal memory of the MMC that does not return to its original form after a reboot (see above) and when connecting the device, specify the path to this driver. It worked for me with some devices. In this case, the necessary entries are created in the registry automatically.

Post has been editedantonio-dj - 31.03.17, 17:47

[antonio-dj]

CAN firmware.

Attention! CAN firmware is a controller firmware that is connected from one side to the CAN bus, and from the other to the COM port of the main MMC processor.
To understand, studyeducational program on hardware
CAN firmware is independent of MMC firmware.
The firmware is not flashed over, but instead. That is, FULLY replaces the existing one.

Description of the types of firmware

Versions 1.7 and 1.13 stock.
The in-car navigation only works on 1.13, 1.23 and 1.24.
1.9, 1.10, 1.11 are made on the basis of 1.7;
1.23 is made based on 1.13.
In 1.7 there are only 11 IDs that can be redirected to the COM port, no dividers, etc. No, and add them sooo difficult. In 1.13 there is a group ID (3 pieces 481, 551, 280) with dividers, a group ID without dividers (4Ax) and a group ID (8 pieces) without dividers disconnected in the firmware. Also, with some IDs, information is collected and processed within the CAN controller. However, I do not know how to get it.
In 1.24 (modified 1.23), it was possible to make a receive ID with a mask, that is, to allocate the range of received IDs. Made it with a range of 7E8..7EF for receiving diagnostic requests from all controllers in our cars.
ID 4A2 only for combinations with built-in GPS and only with a connected 6-button shift paddles.

Each version has its pros and cons:
Versions based on 1.7:
+ It is well reflashed even with the engine.
- Data transmission is being stunned (if you often send data to the CAN controller, they stop sending to the bus).
- Few id.
Versions based on 1.13:
+ Do not choke data transfer.
+ Many id.
+ There are dividers (it helps to reduce the load, because ID: 180 messages go 100 times per second.)
- Flashing is very sensitive to tire activity, etc. (there have been cases of scaling).

Description of the firmware process

1) Download the version of the firmware you need.
2) Extract the osfiles folder to the root of the memory card (SD). C USB is not sewn !!! I usually bring the firmware on a USB flash drive. With the help of TotalCommander on MMS I transfer the folder to SDMMC. Then I sew. With this, I never copy files to a USB flash drive (both USB and SD) by replacing. Many times at the same time turned out broken files.
3) Close all doors, turn off the ignition.
4) Turn off the MMC, wait at least 30 seconds (while the devices on the CAN bus "fall asleep"). Enable MMS.
5) Go to the desktop. Before flashing any other programs do not run. That is, close the altmenu or other applications using the CAN - bus and, accordingly, COM3.
6) Run \ sdmmc \ osfiles \ UPPwriter.exe with explorer
If the inscription "Standard S19 file not found" appears, it means that the folder was not thrown there. In the same window, the path is indicated where the firmware file should be located and what is the name.
7) We are waiting for the end of the firmware process. At first 20 seconds nothing will happen on the screen, then the firmware process will begin. MMS do not turn off!
Although some process did not start until you have turned OFF>ON (Do not reboot !!!).
8) At the end, we can close everything that hinders and restart the altmenu. Reboot is not required, but nothing bad will happen in this ..
* Description taken from Pulsar_85 and slightly corrected.

Firmware

osfiles (1.7) .zip(1.43 MB)

osfiles (1.7_07E8) .zip(1.43 MB)

osfiles (1.9) .zip(1.43 MB)

osfiles (1.10) .zip(1.53 MB)

osfiles (1.11) .zip(1.32 MB)

osfiles (1.13) .zip(1.4 MB)

osfiles (1.23) .zip(1.3 MB)

osfiles (1.24) .zip(1.39 MB)

Editing

CAN recovery using USBDM

In the archive instructions and files. Tested on MMS grants.
If Kalina, RESET, BKGD and GND search on the side service connector, VDD is possible next to the CAN controller.
Author:Akhmed_d
USBDM.rar(22.65 MB)

Post has been editedantonio-dj - 05.03.18, 09:52

[antonio-dj]

Check GPS operation.

Option 1.
Run the program PuTTY.putty.zip(209.7 KB)

Set up the connection as in the picture and click "OPEN"

PuTTY connection

In the window that opens, NMEA data from GPS should appear.

Option 2.
Launch GPS Viewer.mGpsCmd.zip(38.49 KB)

Set up the connection as in the picture and click "OPEN GPS"

GPS Viewer

Further you will understand

[antonio-dj]

About WiFi for FAQ.

List of supported WiFi drivers for WinCE on the Microsoft website.
On MMS, it was possible to launch WiFi-USB adapters on chips:
- RT2070
- RT2870
- RT3070
- RT3071
- RT3072
Link to Wiki (information) on adapters.
Information about the drivers from the manufacturer.rt2870_software_release_note_for_windows_ce.pdf(540.3 KB)

The main driver file is RT2870.DLL.
The driver also needs libraries in the Windows folder (eap.dll, eapol.dll, wzcsapi.dll) and in the folder with the main file (ethman.dll, ndisuio.dll, wzcsvc.dll).
The archive has all these files.wi-fi.zip(383.54 KB)

When you restart the MMC, files in the Windows folder that were not included in the firmware are deleted. Therefore, TarLink has created firmware with built-in WiFi drivers.

To determine which chip is in the adapter, we connect it to the BB (For reference, BB is Big Brother, it is a desktop computer) and we learn the VID and PID.
For those who do not know how to know the VID and PID, enter in the search engine "how to find out the vid pid of the device".
Herelist of supported devices by VID PID.
Perhaps this list is not complete. To determine the exact data on the chip, it is better to use the search on the "global web" (Internet).

People tried to make friends adapters on other Ralink chips, but it does not work.
There is a driver for RTL8188CU / RTL8192CU / RTL8188EU, however it is designed for WinCE7 and does not work on our MMS.

Not finished yet.
I take information fromof my article

Post has been editedantonio-dj - 29.07.17, 10:19

[antonio-dj]

Likbez on the hardware of the MMC.

* Pinout ISO connector

*Structural scheme

Processor module (composition may differ on new MMC):

A photo

The central processor - SiRF Atlas-V AT551
SiRFatlasV_AT551 Datasheet.pdf(5.48 MB)

RAM - 128 MB DDR2 (NANYA NT5TU64M16GG) - the maximum supported CPU size is 128 MB (p. 19 DATASHEET)
Flash Memory - 128 MB Flash Chip (SAMSUNG K9F1G08U0D-SIB0)

Hardware Controller - Panasonic MN101EF31G
MN101E31_E.pdf(461.09 KB)

The display controller is TW8816 (there is still an LVDS transmitter in the Kalina MMC and a receiver in the monitor)
TW8816spec_05152008.pdf(945.59 KB)

Display - Innolux AT070TN94
AT070TN94.pdf(720.31 KB)

Radio receiver - TEF6616
Sound Switching and Hardware Equalizer - TDA7419
TDA7419.pdf(539.26 KB)

Sound Amplifier - TDA7388 (Can be replaced by TDA7560)
Bluetooth module - nFore nf2301
CAN and LIN bus controller - Freescale S9S12G96F0CLF (TXCAN-48pin, RXCAN-47pin, TXLIN-40pin, RXLIN-39pin).
MC9S12GRMV1-220424.pdf(5 MB)


The central processor controls all external devices via UART interfaces (COM port).
Panasonic MN101EF31G is connected to COM1.
Port parameters: 19200, 8 bits, no parity.
He in turn:
- controls the TW8816 display controller (via I2C bus);
- controls the radio receiver TEF6624 (via I2C bus);
- controls the sound switch and hardware equalizer TDA7419 (on the I2C bus);
- controls power on and off;
- controls the display backlight;
- reads the state of the buttons, encoder, signal input backing;
- controls the hardware reset of some devices (for example, Bluetooth-module);
- contains a real time clock;
- the power supply is connected to the ionistor (0.22F 5.5V) to continue the clock when the power is off (the duration of the work is not known).
- has an additional external memory EEPROM (24C16).
A Bluetooth module NF2301 is connected to COM2. The control protocol of this module is invented by the manufacturer (nFore) is hidden and not disclosed.
Port parameters: 115200, 8 bits, no parity.
A CAN and LIN controller for the Freescale S9S12G96F0CLF bus is connected to COM3. The control protocol of this controller is invented by the manufacturer (Itelma) is hidden and not disclosed.
Port parameters: 115200, 8 bits, no parity.
COM4 is present in the system, but where it is connected is unknown.

* Video and rear view camera

A 16-bit (5-6-5 bit) bus with an RGB signal goes from the central processor to the display controller. A display controller converts this signal to an LCD format.
A signal from the view of the input (for the rear view camera) is connected to the display controller.
Switching inputs and setting the display controller performs the Panasonic MN101EF31G bus I2C.
Switching to the input of the rear-view camera is carried out when 12V is applied to pin A1 of the ISO connector. Switching occurs only if this feature is activated by software. Switching is controlled by the Panasonic MN101EF31G regardless of the running shell. Activation is the resolution of the video switching. The activation setup is stored in the Panasonic MN101EF31G.

*Sound

Sources are connected to the sound switch and hardware equalizer TDA7419:
- central processor;
- radio;
- Bluetooth module
- hardware mono input (pin C7 of the green connector) is connected via a coupling capacitor to the 28 foot TDA7419 (Mix input / Additional subwoofer output / 2nd rear right output I / O).

* Bluetooth

Likbez on Bluetooth
The Bluetooth module is connected:
- audio output;
- microphone (connected directly or through a preamplifier);
- MUTE hardware input (it is controlled by Panasonic MN101EF31G);
- hardware reset input (it is controlled by Panasonic MN101EF31G);
- UART interface for control is connected to the central processor.

* CAN and LIN

Educational program on the CAN bus in MMC
CAN tranceiver - TJA1042
TJA1042.pdf(143.97 KB)

LIN tranceiver - TJA1020
TJA1020.pdf(129.17 KB)

* MMS with navigation

The GPS receiver is integrated in the instrument cluster.
Data from the GPS receiver is transmitted over the CAN bus in the form of pieces of NMEA 0183 protocol messages
ID go in a circle: 4A4 - 4A6 - 4A8 - 4AA - 4AC - 4AE -
Each message contains 8 bytes of the GPS message string.
The line ends with newline characters: 0D 0A

* Versions of software versions PP and CAN

Grant
Software: 2.2.2.11 (without access to the work desk)
PP: A01310: 70F0: 00042 (42hex = 66dec)
CAN: 1.7

Grant
Software: 21.0.2.34
PP: MMC21-BOH3-00100
CAN: 1.7

Grant with navigation
Software: 21.1.2.39 (without access to the work desk)
PP:?
CAN:?

Lada Granta, full-time navigation, equipment 42-711
Software: 21.1.2.64 (without access to the desktop. Table)
PP: MMS21-BOH3-00139
CAN: 1.13

Kalina 2
Software: 23.0.2.23 (without access to the desktop. Table)
PP: MMS23: 70FO: 00066 (66hex = 102dec)
CAN: 1.13

Kalina 2
Software: 23.0.2.27 (without access to the desktop. Table)
PP:?
CAN:?

Kalina 2
Software: 23.0.2.32
PP: MMC23-BOH3-00082
CAN: 1.13

Kalina 2
Software: 23.0.2.35
PP: MMC23-BOH3-00082
CAN: 1.13

Kalina 2
Software: 23.02.38
PP: MMC23-BOH3-00082
CAN: 1.13

Kalina2 Lux with integrated navigation.
Software: 23.1.2.5 (without access to the desktop. Table)
PP: MMC23-BOH3-00139
CAN: 1.13

PrioraLux, April 2015
Launcher.exe (namely Launcher, not Launch) is present.
Software: 23.0.2.38
PP: MMC23-BOH3-00100
CAN: v1.7 (before the flashing it was 1.1.3, or 1.13, I don’t remember if there was an extra point there ...)

*Rest

Service connector for programming the MK on the board

Post has been editedantonio-dj - 23.10.17, 08:45

[kumarai]

M

The topic has been moved to the section.destination

[azazello002]

Hello. I want to flash the CAN and as a result, the inscription "Standard S19 file not found" appears, I can not understand, I throw everything on the SD card into the archive, I don’t have anything else on it, and it’s not sewn, tell the wrong person what I am doing wrong in plain language ???

[antonio-dj]

[email protected], 12:45

Hello. I want to flash the CAN and as a result, the inscription "Standard S19 file not found" appears, I can not understand, I throw everything on the SD card into the archive, I don’t have anything else on it, and it’s not sewn, tell the wrong person what I am doing wrong in plain language ???

In the description of the firmware process in p.4, all this is written.

Post has been editedantonio-dj - 29.07.16, 12:48

[kumarai]

M

The topic is closed until the completion of registration!
The topic is open! All the pleasant communication!

Post has been editedkumarai - 29.07.16, 09:02

[slutkin19]

Grant Suite 2015 with navigation, 127 engine.
I changed the CAN to 1.23. It has become to show turnovers, etc.
And most importantly, the SINGLE MENU 4.4.1 has earned noticeably faster. : thank_you:

[kondalvl]

I stitched the cannon, now on the radio tape recorder the instantaneous consumption shows and there is no on the instrument panel. There was someone like that. In general, everything else is not bad.

[val9001]

Kondalvl @ 07.29.2016, 23:24

I stitched the cannon, now on the radio tape recorder the instantaneous flow rate shows and there is no on the instrument panel

Firmware CAN module on the MMC does not have any relation to the gearbox (instrument cluster).
To show the gearbox, you need to flash the gearbox itself, if possible. Here is read -https://www.drive2.ru/l/8259674/

Post has been editedval9001 - 30.07.16, 05:10

[kalimit]

Slutkin19 @ 07.29.2016, 14:18

And most importantly, the SINGLE MENU 4.4.1 has earned noticeably faster.

I did not understand something, is there a poll in this firmware that is less common? It seems like a plus sign is not less than 1.10

Post has been editedkalimit - 30.07.16, 08:29

[Elkent]

[email protected], 08:18

I did not understand something, is there a poll in this firmware that is less common?

It is betterantonio-djNobody will explain to us whether antonio is possible after a flashing of can before versions 1.11 and 1.23 any improvement in the speed of SM?
Or slutkin19just seemed?

[antonio-dj]

Elkent @ 07/30/2016, 12:59

...
It is betterantonio-djNobody will explain to us whether antonio is possible after a flashing of can before versions 1.11 and 1.23 any improvement in the speed of SM?
Or slutkin19just seemed?

In 1.23, the frequency of revenues is 10 times less. That is, not 100, but 10 times per second. This is enough and less load system.