编程vdm

一辆行驶里程约11.3万km、配置N52发动机的2011年宝马X3。客户反映：该车仪表会亮故障灯“转弯性能受到影响”，中央显示屏显示“动态减震控制系统”，如图

1、图2所示。在综合修理厂更换了右前减震器，行驶一段时间后仪表还是会报故障。

故障诊断：接车后试车，发现打开点火开关后仪表就会报故障。使用ISTA（宝马原厂诊断系统，以下简称ISTA）诊断，存有VDM（垂直动态管理系统，以下简称VDM）无通信故障。检查发现后备箱右侧VDM安装处有进水；VDM针脚有腐蚀。怀疑VDM泡水造成内部损坏。向客户报价，客户同意更换。订货，处理VDM处泡水的插头线束，更换VDM编程、底盘高度匹配，试车，确认故障排除后交车。

时隔半个月，客户返厂反映故障灯又亮了，接车后发现故障现象与上次一致，打开点火开关仪表报故障，中央显示屏显示“动态减震控制系统故障”。经ISTA诊断存有故障码（如图3所示）：EDC：垂直加速传感器一左前一数值不可信EDC：垂直加速传感器一右前一数值不可信检查4支减震器上的EDC（减震器卫星式控制单元，以下简称EDC）插头针脚，未发现异常；测量左前、右前的EDC的供电5V正常，测量搭铁正常，车辆信号未见异常；测量减震电磁阀供电和搭铁正常，插头针脚都未见异常。测量左前、右前、左后、右后电磁阀线圈电阻均为5.3Ω。

检查信号和执行器都是正常的，删除故障码，需要行驶很长一段路程可以重现故障，故障一旦出现，打开点火开关后仪表和中央显示器就会报故障。到底哪里出现遗漏了呢？查阅维修历史发现每次出现故障时，ISTA诊断都存有故障码：0X4809ABDSC：车辆中电压过低0X482947EDC：垂直加速传感器一右前一数值不可信检查VDM供电线23针脚有点松，于是调整针脚的松紧，如图

4、图5所示。

【1】【2】【3】下一页关键词：宝马X3分享到：QQ空间新浪微博腾讯微博人人网网易微博相关阅读宝马X3动态减震控制系统亮故障灯检修宝马X3行驶中发动机故障灯突然点亮宝马X3发动机噪音大、机油温度过低宝马X3行驶中自动熄火且加速无力检修宝马X3胎压等多个报警灯常亮检修宝马X3泊车距离报警故障检修宝马X3发动机偶尔抖动、故障灯点亮宝马X3仪表板中发动机故障灯亮上一文章：路虎发现运动插电式混合动力系统技术亮点

（一）下一文章：奔驰E260轿车发动机故障灯亮【返回上一页】 【打印】

（图/文/摄：太平洋汽车网问答叫兽）

‘捌’ 进程管理 os编程

创建进程的api函数
BOOL CreateProcess(
LPCWSTR pszImageName,
LPCWSTR pszCmdLine,
LPSECURITY_ATTRIBUTES psaProcess,
LPSECURITY_ATTRIBUTES psaThread,
BOOL fInheritHandles,
DWORD fdwCreate,
LPVOID pvEnvironment,
LPWSTR pszCurDir,
LPSTARTUPINFOW psiStartInfo,
LPPROCESS_INFORMATION pProcInfo
);
Parameters
pszImageName
[in] Pointer to a null-terminated string that specifies the mole to execute.
The string can specify the full path and filename of the mole to execute or it can specify a partial path and filename.

The lpszImageName parameter must be non-NULL and must include the mole name.

pszCmdLine
[in, out] Pointer to a null-terminated string that specifies the command line to execute.
The system adds a null character to the command line, trimming the string if necessary, to indicate which file was used.

The lpszCmdLine parameter can be NULL. In that case, the function uses the string pointed to by lpszImageName as the command line.

If lpszImageName and lpszCmdLine are non-NULL, * lpszImageName specifies the mole to execute, and * lpszCmdLine specifies the command line.

C runtime processes can use the argc and argv arguments.

If the filename does not contain an extension, .EXE is assumed.

If the filename ends in a period (.) with no extension, or if the filename contains a path, .EXE is not appended.

psaProcess
[in] Not supported; set to NULL.
psaThread
[in] Not supported; set to NULL.
fInheritHandles
[in] Not supported; set to FALSE.
fdwCreate
[in] Specifies additional flags that control the priority and the creation of the process.
The following creation flags can be specified in any combination, except as noted.

Value Description
CREATE_DEFAULT_ERROR_MODE Not supported.
CREATE_NEW_CONSOLE The new process has a new console, instead of inheriting the parent's console.
CREATE_NEW_PROCESS_GROUP Not supported.
CREATE_SEPARATE_WOW_VDM Not supported.
CREATE_SHARED_WOW_VDM Not supported.
CREATE_SUSPENDED The primary thread of the new process is created in a suspended state, and does not run until the ResumeThread function is called.
CREATE_UNICODE_ENVIRONMENT Not supported.
DEBUG_PROCESS If this flag is set, the calling process is treated as a debugger, and the new process is a process being debugged. Child processes of the new process are also debugged.
The system notifies the debugger of all debug events that occur in the process being debugged.

If you create a process with this flag set, only the calling thread (the thread that called CreateProcess) can call the WaitForDebugEvent function.

DEBUG_ONLY_THIS_PROCESS If this flag is set, the calling process is treated as a debugger, and the new process is a process being debugged. No child processes of the new process are debugged.
The system notifies the debugger of all debug events that occur in the process being debugged.

DETACHED_PROCESS Not supported.
INHERIT_CALLER_PRIORITY If this flag is set, the new process inherits the priority of the creator process.

Windows CE does not support the concept of a priority class. The priority of a thread is the only parameter that determines a thread's scheling priority.

pvEnvironment
[in] Not supported; set to NULL.
pszCurDir
[in] Not supported; set to NULL.
psiStartInfo
[in] Not supported; set to NULL.
pProcInfo
[out] Pointer to a PROCESS_INFORMATION structure that receives identification information about the new process.
Return Values
Nonzero indicates success.

Zero indicates failure.

To get extended error information, call GetLastError.

Remarks
In addition to creating a process, it also creates a thread object.

The size of the initial stack for the thread is described in the image header of the specified program's executable file.

The thread begins execution at the image's entry point.

The new process and the new thread handles are created with full access rights. For either handle, the handle can be used in any function that requires an object handle to that type.

The process is assigned a 32-bit process identifier. The identifier is valid until the process terminates. It can be used to identify the process, or specified in the OpenProcess function to open a handle to the process.

The initial thread in the process is also assigned a 32-bit thread identifier. The identifier is valid until the thread terminates and can be used to uniquely identify the thread within the system. These identifiers are returned in the PROCESS_INFORMATION structure.

The following list shows the directories indicated by the pszImageName parameter in the order that Windows CE searches them:

The windows (\windows) directory
The root (\) directory of the device
An OEM-dependent directory, which include the Windows CE Debug shell directory for Platform Builder users only
The following list shows the directories indicated by the pszImageName parameter in the order that Windows CE 2.10 and later search them:

The windows (\windows) directory
The root (\) directory of the device
An OEM-dependent directory
The OEM-defined shell (\ceshell) directory (Platform Builder users only)
The following list shows the directories indicated by the pszImageName parameter in the order Windows CE 1.0 through 2.01 search them:

The root of the PC Card, if it exists
The windows (\windows) directory
The root (\ ) directory of the device
When specifying an application name in the pszImageName string, it does not matter whether the application name includes the filename extension.

Do not call CreateProcess from a DllMain function. This causes the application to stop responding.

The following registry subkey specifies a search path to use with the LoadLibrary function and CreateProcess:

HKEY_LOCAL_MACHINE\Loader
"SystemPath" = multi_sz:"\\path1\\"
"\\path2\\"
For efficiency, the path is searched before CESH but after the ROM and built in file systems. The path is only searched if the path of the file being looked for is not explicitly specified.

If the length of the SystemPath value exceeds 260 characters, the path is ignored. A change to the SystemPath key does not take effect until a Windows CE-based device is reset.

ExitThread, CreateThread, and a process that is starting (as the result of a call by CreateProcess) are serialized between each other within a process. Only one of these events can happen in an address space at a time. The following list shows the restrictions ring the process:

During process startup and DLL initialization routines, new threads can be created but they do not begin execution until DLL initialization is completed.
In a process, only one thread at a time can be in a DLL initialization or detach routine.
The created process remains in the system until all threads within the process are terminated and all handles to the process and its threads are closed through calls to CloseHandle.

The handles for the process and the main thread must be closed through calls to CloseHandle. If these handles are not needed, close them immediately after the process is created.

The following events occur when the last thread in a process terminates:

All objects opened by the process are implicitly closed.
The process's termination status, which is returned by GetExitCodeProcess, changes from its initial value of STILL_ACTIVE to the termination status of the last thread to terminate.
The thread object of the main thread is set to the signaled state, satisfying threads that were waiting on the object.
The process object is set to the signaled state, satisfying threads that were waiting on the object.
The handle returned by the CreateProcess function has PROCESS_ALL_ACCESS access to the process object.

Requirements
OS Versions: Windows CE 1.0 and later.
Header: Winbase.h.
Link Library: Coredll.lib.

创建线程的api函数
HANDLE CreateThread(
LPSECURITY_ATTRIBUTES lpsa,
DWORD cbStack,
LPTHREAD_START_ROUTINE lpStartAddr,
LPVOID lpvThreadParam,
DWORD fdwCreate,
LPDWORD lpIDThread
);
Parameters
lpsa
[in] Ignored. Must be NULL.
cbStack
[in] Ignored unless the STACK_SIZE_PARAM_IS_A_RESERVATION flag is used; in that case the cbStack parameter specifies the virtual memory reserved for the new thread.
When ignored, the default stack size for a thread is determined by the linker setting /STACK.

lpStartAddr
[in] Long pointer to the application-defined function of type LPTHREAD_START_ROUTINE to be executed by the thread; represents the starting address of the thread. For more information on the thread function, see ThreadProc.
Note It is invalid to set lpStartAddr to NULL. If this value is passed in the parameter, the function will return ERROR_INVALID_PARAMETER.
lpvThreadParam
[in] Long pointer to a single 32-bit parameter value passed to the thread.
fdwCreate
[in] Specifies flags that control the creation of the thread.
The following table shows the values for this parameter.

Value Description
CREATE_SUSPENDED The thread is created in a suspended state and does not run until the ResumeThread function is called.
The thread can be run immediately after creation if the flag is not specified.

STACK_SIZE_PARAM_IS_A_RESERVATION The cbStack parameter specified the maximum stack size instead of being ignored.
This is a Windows CE only flag for the CreateThread function and is used to reserve the stack size for the thread created.

By default, a thread is created with 64 KB stack reserved. You can use this flag to increase the stack size for the new thread that was created.

lpIDThread
[out] Long pointer to a 32-bit variable that receives the thread identifier.
If this parameter is NULL, the thread identifier is not returned.

Return Values
A handle to the new thread indicates success.

NULL indicates failure.

To get extended error information, call GetLastError.

Remarks
The number of threads a process can create is limited by the available virtual memory and depends on the default stack size.

If every thread has 1 MB of stack space, you can create a maximum of 32 threads.

If you rece the default stack size, you can create more threads.

Your application will perform better if you create one thread per processor and build queues of requests for which the application maintains the context information. That is because a thread processes all requests in a queue before processing requests in the next queue.

The new thread handle is created with THREAD_ALL_ACCESS to the new thread. The handle can be used in any function that requires a thread object handle.

Thread execution begins at the function specified by the lpStartAddr parameter. If this function returns, the DWORD return value is used to terminate the thread in an implicit call to the ExitThread function. Use the GetExitCodeThread function to get the thread's return value.

If the start address is invalid when the thread runs, an exception occurs, and the thread terminates. Thread termination e to a invalid start address is handled as an error exit for the thread's process. This behavior is similar to the asynchronous nature of CreateProcess, where the process is created even if it refers to invalid or missing .dll files.

The thread is created with a thread priority of THREAD_PRIORITY_NORMAL.

Use the GetThreadPriority and SetThreadPriority functions to get and set the priority value of a thread.

When a thread terminates, the thread object attains a signaled state, satisfying threads that were waiting on the object.

The thread object remains in the system until the thread has terminated and all handles to it are closed through a call to CloseHandle.

The ExitThread function, CreateThread function, and a process that is starting (as the result of a call by CreateProcess) are serialized between each other within a process. Only one of these events can happen in an address space at a time.

The following list shows the restrictions ring the process:

During process startup and DLL initialization routines, threads can be created, but they do not begin execution until DLL initialization is done for the process.
In a process, only one thread at a time can be in a DLL initialization or detach routine.
Requirements
OS Versions: Windows CE 1.01 and later.
Header: Winbase.h.
Link Library: Coredll.lib.