FORD LDM Localization

Configuring a LIN Node is not a download. It uses a functional message to transfer data one time to the LIN node. The LIN node must retain this configuration information in EEPROM (or equivalent). To support a relatively large amount of configuration info (inclination/intrusion sensor) a multiplex message is used.

DLPL_LIN_19_001 – Configuration Data

Configuration information is limited to data that is downloaded when the LIN node is first installed and never changes. If the information can change, it is deemed to be personalization information and must be transmitted to the node using one or more normal (non-configuration) LINxx schedule tables.
To avoid limiting the amount of configuration information to what can fit into one LIN frame, we have chosen to use a multiplex type transmit style. The LIN controller will transmit an index byte (ConfigIndex) plus seven data bytes (ConfigData). The controller will always start with ConfigIndex = 0 and then increment the Config Index every time it transmits the next set of ConfigData. When all the data has been transmitted, the LIN controller will then go back and start transmitting from zero again. This is a simple algorithm in the LIN controller and allows different nodes to have differing amounts of ConfigData.

A LIN Node will "know" that it has completely received all the ConfigData when it sees ConfigIndex = 0 a second time. At this point, the LIN Node will need to write out the config data to EEPROM. Once the write is completed the LIN Node will lower the "I'm not configured" error flag (APINFO4 = 1).
DLPL_LIN_19_002 – Configuration Data Mapping

The table below explicitly lists how the multiplexed Config information signals are uniquely mapped in the LIN Node.

ConfigIndex Valuenumbe	ConfigData Byte	LIN Node Config Data
0	Data0	LINConfig0
0	Data1	LINConfig1
0	Data2	LINConfig2
0	Data3	LINConfig3
0	Data4	LINConfig4
0	Data5	LINConfig5
0	Data6	LINConfig6
1	Data0	LINConfig7
1	Data1	LINConfig8
1	Data2	LINConfig9
1	Data3	LINConfig10
1	Data4	LINConfig11
1	Data5	LINConfig12
1	Data6	LINConfig13
2	Data0	LINConfig14
2	Data1	LINConfig15
2	Data2	LINConfig16
2	Data3	LINConfig17
2	Data4	LINConfig18
2	Data5	LINConfig19
2	Data6	LINConfig20
3	Data0	LINConfig21
3	Data1	LINConfig22
3	Data2	LINConfig23
3	Data3	LINConfig24
3	Data4	LINConfig25
3	Data5	LINConfig26
3	Data6	LINConfig27

Table 38: Multiplexed ConfigIndex/ConfigData Mapping to Unique Internal LIN Node Config Data

The LDM supplier is responsible for providing full multiplexing information showing the location of each parameter within the LIN configuration frames.

Rule Num	Rule
DLPL_LIN_19_003	All LIN nodes shall store any configuration data in EEPROM/NVM. Configuration data will not be continuously transmitted during normal operation.
DLPL_LIN_19_004	A node shall infer that Configuration Mode has started when it first receives any of these signals:ConfigIndex signalConfigData signalPartNumIndex signalPartNumData signal (Note: Configuration information is repeatedly transmitted until all nodes on a subnet report "Configured" or 4 seconds elapse (whichever is sooner).)
DLPL_LIN_19_005	Once a node detects that the subnet as switched to Configuration Mode then it shall immediately start reporting "Not Configured" until the next requirement is met. The LIN Node must transmit the "Not Configured" status at least one time (even if the node does not support configuration information).
DLPL_LIN_19_006	The node shall only indicate that it is configured after:All config information has been receivedAll config information is saved in NVM/EEPROM
DLPL_LIN_19_007	Note 1: The node can detect that it has received all ConfigData when the ConfigIndex is zero the second time. Note 2: Even after a node has been completely configured, the node may continue to receive the configuration information repeatedly. This allows other LIN nodes with more configuration information to receive their config data. It also allows the LIN Controller to collect all LIN Node part numbers (see next section).

Table 39: Ford Configuration and Part Number Retrieval Requirements  