FORD LDM Localization

Many of the signals defined in the Command Frames provide functionality that appear to overlap and do to some extent. For instance, Ignition_Status and the WFSuperstate:RunStart are both use for Ignition “On” detection, however the level of logic processing in the BCM differs. The Ignition_Status provides a debounced read and state generation from the Raw Switch. The WFSuperstate provides a minor delay in Welcome/Farewell transition to RunStart to allow Ambient Light – Autolamps make a smooth pickup of functionality in the Position Lamps. This signal incorporates more functional logic of the vehicle feature behavior from the BCM. This provides a consistent vehicle behavior for Ford vehicles based on the developed logic already in production.
In general, the intent is to use the feature content processing of the BCM were possible. Known exceptions will be noted.

The primary signals driving the Position and Headlamp logic in the LDMs will be:

o Position_Park_Left_Cmd
o Position_Park_Right_Cmd
o Headelamps_Low_Beams_Out
o Headlamps_High_Beams_Out

These signals will be the executed logic for basic headlamp functions and are equivalent to the states the lamps would be driven with if directly attached to the BCM. The configuration of lamp activations (Multiple DRL/Signature Lamps) based on these inputs are given in the LDM configuration tables. Headlight_Status, FTP_Status and High_Beam_Status are signals provided for triggering and processing in addition to the basic BCM logic or for triggering alternate functions as required.
Vehicles (LDMs) configured for ECE Markets will support Single Sided Position Lamps. The LDM will receive a Left OR Right Position_Park_xxx_Cmd with Headlight_Status = Off. This will request a single LDM (Corresponding Left or Right to received command) to illuminate the Position Lamp.

Ignition_Status	LDM will use this signal as a transition from Welcome/Farewell into Vehicle Operation Mode. Will also be used to enable/disable features based on Ignition state per market configuration.
Turn_Signal_ Light_Cmd	Turn signals are directly controlled by the BCM, however if the LDM receives Left or Right Turn Cmd without detecting the direct Turn Signal pulse, this signal should override the appropriate DRL if configured to do this function from the direct feed.
Position_Park_Left_Cmd	This signal is the logic that drives the Left POS/Park Lamp. If European Single Sided Position is enabled in the BCM, this line will activate in Headlamp OFF with the Left Turn signal switch. BCM will assert both Left and Right for normal Position Functionality
Position_Park_Right_Cmd	This signal is the logic that drives the Right POS/Park Lamp. If European Single Sided Position is enabled in the BCM, this line will activate in Headlamp OFF with the Right Turn signal switch. BCM will assert both Left and Right for normal Position Functionality
Headlamp_Low_Beams_Out	Full BCM Feature Logic Low Beam Signal. This signal will represent the Low Beam active state for the LDM and will drive Low Beam operation across the LIN Bus for ECE Low Beam elements.
Headlamps_High_Beams_Out	Full BCM Feature Logic High Beam Signal. High Beam driving functions are not part of the Signal LDM. This signal will be used for features that react with High Beam BCM feature logic.
Headlight_Status	Allows features to be tied to Headlamp switch state, none currently defined.
FTP_Status	Fast Reaction Input to allow logic to determine lamp response rate based on Auto or Manual High Beam Request. High Beam is not current part of Signal LDM function.
High_Beam_Status	Fast Reaction Input to allow logic to determine lamp response rate based on Auto or Manual High Beam Request. High Beam is not current part of Signal LDM function.
Veh_Speed	Vehicle speed data for speed dependent functionality.
Day_Night_Status	BCM Day Night Status for Autolamp feature, provided to allow function sync with Day/Night Behaviors. See Lighting Logic Diagram
DRL_Rqst	This signal is a fully arbitrated DRL control signal from the BCM. It includes the basic operation of the DRL lamps as well as regional overrides (Trans Park (US/Canada) and Cluster Select (US)).It should be used to directly drive the DRL state in the LDM.

Table 30: Exterior Lighting Functional Description
Many of the signals defined in the Command Frames provide for future defined functionality or to link Exterior Behaviors with internal activity. For instance, Door Ajar signals. Some interior functions are linked to individual door opening. Providing these signals on the LIN bus allow the same potential linking with the LDM/FCM functionality.

DF_Door_Ajar_Status	Potential trigger for interior coordination.
PF_Door_Ajar_Status	Potential trigger for interior coordination.
DR_Door_Ajar_Status	Potential trigger for interior coordination.
PR_Door_Ajar_Status	Potential trigger for interior coordination.
LG_Ajar_Status	Potential trigger for interior coordination.
Any_Door_Ajar_Status	Potential trigger for interior coordination.
Front_Foglamp_Rqst	Direct Front Fog activation logic for LDM Front Fog feature support
Rear_Foglamp_Rqst	Direct Rear Fog activation logic for LDM Front Fog feature support
Reverse_Gear_Status	Direct Reverse Gear Logic, backup lights.
License_Lamps_Cmd	For use with Rear LDM to drive License Plate Lamps
Trailer_Hitch_Lamp	For use with Rear LDM to drive Trailer Hitch (Backup Assist) Lamps
Bedlamp_Rqst	For use with Rear LDM to drive Pickup Truck Bed Lamps

Table 31: Exterior Lighting Future Functionality Support