Lightning FORScan guide.

Read this first. Everything here is at your own risk. Writing to your truck's modules can disable features, store fault codes, brick a module, and cost you a dealer visit. An experienced owner on the Lightning forum: "It's WAY too easy to screw it up with no way out and forscan has almost ZERO safety net." [1] Neither I nor anyone else is responsible for what happens to your truck, your warranty, or your record if you follow this. If you're not comfortable with that, stop here.

On the law. Ford sells the Lightning in the US without glare-free lighting switched on, and I have found no statement from Ford about why, or about whether this system would pass the US test. What is on the record: NHTSA's February 2022 final rule "amends NHTSA's lighting standard to permit the certification of adaptive driving beam (ADB) headlamps," with a test that "follows SAE J3069 in many significant respects, but also differs from it in significant ways"; industry commenters said "current ADB systems would not comply" with parts of it [2]. In December 2024 NHTSA denied every petition for reconsideration, Ford's included [3]. The first adaptive matrix headlights actually activated in the US were Rivian's, in 2025 [4]. The federal "make inoperative" rule applies to manufacturers, dealers and repair businesses; NHTSA's own counsel says those prohibitions "do not apply to the owner of a vehicle," and in the same letter tells owners to "ensure your system complies with any and all applicable State laws" [5]. So: nothing I found says an owner enabling this breaks federal law, nothing I found says it's legal on your state's roads either, and your state's equipment law is the one that matters. Assume it is not street-legal where you live until you have checked. I turned mine back off.

Where this came from. These are the steps that worked on my 2023 Lightning Lariat Extended Range on 2026-09-30, checked line by line against the Lightning forum's FORScan threads, Ford's owner's manual, order guide and warranty guide, FORScan's own documentation, and the Federal Register. Every factual sentence has a numbered source at the bottom. Where something comes only from my own truck, it says so. Other years, trims and regions can differ. Read the whole thing before you touch anything.

Guide 1: FORScan and the glare-free (matrix) headlights

What you need

• A Lightning with the LED projector headlamps with dynamic bending (they swivel in turns). Ford's 2023 order guide lists "LED Projector with Dynamic Bending Headlamps" as standard on the Pro, and each higher series "includes the standard equipment of the previous series," so all four 2023 trims have the hardware [6]. Owners report the mod working on a '24 Pro and a '25 Lariat [7], and on a '23 XLT and a '24 Flash [8]. Some Canadian trucks shipped with the option already on; not all did [9][10].
• A FORScan-compatible OBD2 adapter. FORScan's own recommended USB adapters for Windows are the OBDLink EX and the vLinker FS, and it says it does "not recommend any 'ELM327' anymore" [11]. The Lightning thread's equipment post recommends the same two plus a Mongoose J2534 [12]. I used a vLinker FS (USB, about $37 to $48 depending on the seller as of September 2026). One caveat: FORScan de-listed the vLinker FS from February to May 2025 over a USB 3.0 hub enumeration problem on some computers, then restored it after a new revision; if yours won't enumerate, FORScan's thread suggests a USB hub [13].
• A laptop. Windows is the simple path. A Mac works through CrossOver, see step 1b.
• The truck parked and fully on, not accessory mode. (My practice; FORScan needs the modules awake to identify the vehicle.)

Step 1a: install FORScan on Windows

1. Download the current Windows version from forscan.org. As of this writing that is 2.3.71, released 2026-05-08 [14]. FORScan's server will tell you "This version of FORScan is outdated" and require an update when an older build asks it to identify a vehicle it doesn't recognise [15]; on my Mac, 2.3.67 was refused that way and 2.3.71 worked.
2. Run the installer. Defaults are fine.
3. Plug the adapter into the laptop. If Windows doesn't install a driver on its own, the adapter's listing has one.

Step 1b: install FORScan on an Apple Silicon Mac

FORScan supports only x86/x64 Windows; its home page says "ARM architecture is not supported!" [16], though FORScan staff do publish a "Safe emulation" workaround for ARM Windows machines [17]. The route that worked for me, and for the Lightning forum's Apple Silicon guide, is CrossOver (a paid Wine wrapper with a free 14-day trial) with the USB adapter mapped to a COM port in Wine's registry [18]. That guide found 2.3.68 through 2.3.70 "would hang indefinitely" and used 2.3.67; it predates 2.3.71, which is what ran for me.

Easiest way: paste this prompt into Claude or ChatGPT and let it do the terminal work.

I have an Apple Silicon Mac and a USB OBD2 adapter (FTDI-based vLinker FS). I want to run FORScan for Windows on this Mac through CrossOver. Do this for me step by step, running the commands yourself where you can:

1. Confirm CrossOver is installed at /Applications/CrossOver.app (I'll install the trial from codeweavers.com if not). Its command-line tools are in /Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin.
2. I've downloaded the newest FORScan Windows installer (FORScanSetup2.3.71.release.exe or newer) to ~/Downloads from forscan.org/download.html. Do not use 2.3.67 or older; FORScan's server refuses them.
3. Plug-in check: run `ls /dev/cu.usb*` with the adapter plugged into the Mac and tell me the device name (mine looks like /dev/cu.usbserial-XXXXXXXX). If nothing shows up, stop and tell me.
4. Create a CrossOver bottle named FORScan from the win10 template: `cxbottle --create --bottle FORScan --template win10`
5. Copy the installer into the bottle's C: drive at drive_c/inst/ (the bottle lives at ~/Library/Application Support/CrossOver/Bottles/FORScan) and run it silently: `wine --bottle FORScan --wait-children --cx-app "C:\\inst\\FORScanSetup2.3.71.release.exe" /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-`
6. Map the adapter to COM1. Write drive_c/inst/ports.reg containing:
   REGEDIT4
   [HKEY_LOCAL_MACHINE\Software\Wine\Ports]
   "COM1"="/dev/cu.usbserial-XXXXXXXX"
   "COM2"="/dev/tty.usbserial-XXXXXXXX"
   (use my real device name), import it with `wine --bottle FORScan --cx-app regedit /S "C:\\inst\\ports.reg"`, and also symlink dosdevices/com1 and com2 in the bottle to the same two device paths.
7. Turn off demo mode: in drive_c/users/crossover/AppData/Roaming/FORScan/settings.ini set DEMO_MODE=false. FORScan writes that file on first launch, so launch it once, quit, then edit.
8. Launch FORScan with the working directory set to its own folder, otherwise it can't find its certificate bundle and vehicle identification fails: `wine --bottle FORScan --workdir "C:\\Program Files\\FORScan" --cx-app "C:\\Program Files\\FORScan\\FORScan.exe"`
9. Tell me when the FORScan window is up. In FORScan's settings I will leave the connection type on Auto. It should find the adapter on COM1 at 115200.

Notes: if FORScan crashes with "has encountered a serious problem", relaunch it with the command in step 8. If the first connect to the truck fails, I'll unplug and replug the adapter and try again. When I'm done, deleting the bottle folder removes FORScan completely; I'll copy my backup files out of the bottle's C: drive first.

What that prompt already accounts for, all first-hand from my Mac on 2026-09-30: 2.3.67 refused by FORScan's server; FORScan's demo mode set to true in settings.ini, which stops it talking to any adapter (demo mode is a Settings checkbox that lets FORScan "be tried w/o vehicle or adapter" [19]); FORScan needing its own folder as the working directory, otherwise it fails with curl error 77 and can't identify the vehicle; and the connection type left on "Auto," which is FORScan's recommended setting [20]. Picking the FTDI-driver option instead failed for me, because the bottle has no FTDI driver.

Step 2: the Extended Licence (needed before you can write anything)

Reading is free. FORScan: "Base FORScan functionality (connection, retrieving vehicle information, reading parameters, read and reset diagnostic trouble codes, run tests and service functions etc) do NOT require Extended License." Writing configuration does: "Extended License provides access to Configuration and Programming functions of FORScan." [21] The trial is free for two months [22], no forum account needed any more [23], and when it expires "you will be able to issue another 2 months one, also for free" [24]. FORScan caps you at "no more than two active trial keys" [22].

1. Open FORScan on the computer you'll plug into the truck. Click the About icon (the question mark, last item in the left-hand icon bar). Next to the Hardware ID, click Copy to Clipboard; FORScan says "do not enter the ID manually but copy it to the clipboard, to avoid any typos" [25]. Version 2.3.71 also added an "Obtain free trial license" link right there that passes the ID automatically [14].
2. On the request form (forscan.org > Download > free trial Extended License), fill in your name, your email twice, and the Hardware ID [22].
3. Wait. "The request's review may take 20-30 minutes or more" [26]. The key is not emailed: "you will be able to download the license key on this page as soon as the generation process is completed, by reloading the result page or by resubmitting the form using the same data" [22]. Keep the .key extension; FORScan "looks for *.key or *.reg files" [26].
4. Load it: About > Load License Key > pick the file. "After successful key loading FORScan will ask to restart the application." If About still says Standard after the restart, "most likely the date on your computer is wrong" [26].

The Hardware ID is tied to the computer; FORScan says it "may change if some PC components are replaced" [25] or after an OS reinstall [22], and moving to another computer needs a new key [27]. On my Mac under CrossOver it also changed when I went from 2.3.67 to 2.3.71, which FORScan doesn't document; a new key fixed it.

Step 3: connect to the truck

1. Truck fully on, not accessory.
2. Adapter into the OBD2 port under the dash, driver side. USB into the laptop. The Apple Silicon guide: "the left side USB-C ports works for me, but i couldn't get the right side USB-C port to work at all, displaying a red LED on the OBD adapter" [18].
3. FORScan > Connect. Wait for it to identify the vehicle and list the modules.
4. If the first connect fails, unplug the adapter, plug it back in, connect again. Same guide: "it fails for some odd reason the first time after opening the application... I have to disconnect the OBD adapter and plug it back in for it to work" [18]. I hit it too.

Step 4: back up everything. This is not optional.

The original thread, in capitals: "MAKE SURE YOU BACK UP YOUR ASBUILT DATA BEFORE MAKING CHANGES. SOME CHANGES WILL BE UPLOADED TO THE MOTORCRAFT SERVICES ASBUILT SITE AND YOU WILL NOT BE ABLE TO RECOVER THE ORIGINAL SETTINGS." [28] Your local files may be the only copy of your truck's factory configuration.

1. In FORScan's Configuration and Programming section, open Module Configuration (As Built format) for each module you'll touch: APIM, IPMA, SCCM, IPC, HCM. Do BdyCM and ABS too while you're there. The plain "Module Configuration" (easy mode) "has no import/export (load/save) functions" [29].
2. Click Save All before changing anything. FORScan's own doc: "Make backup of module configuration: press 'Save All' button, type filename, confirm writing. Configuration will be saved to a file with .ABT extension." [29] A Lightning owner: "It will automatically save the file with the name vin_module_date_time (to the second). After the update (especially if using Easy mode), do another Save All." [1] There is no one-click backup of every module; do each one.
3. Take a photo or screenshot of each as-built screen before you change it. Owners in the best-practices thread do exactly this [1].
4. Run a full DTC scan and save the report, so you know what codes were already stored.
5. Copy the backup folder somewhere that isn't the laptop. Livnitup's tutorial: "copy the backed-up module files to a secondary location such as a usb drive" [30].

Step 5: write the headlight values

The masks, exactly as both forum threads list them [28][12]. "x" means leave that digit alone; "-" is the checksum FORScan recalculates: "'x' means leave the value as is and '-' is the checksum value that FORScan will re-calculate for you when you write the data" [12].

Read this before you type anything:

• Your originals will not all match mine, and that's expected. Another owner's stock 2022 Platinum dump shows different bytes on 7D0-09-01, 706-01-01 and 720-01-01, and the same bytes as mine on the other six lines [31]. Change only the digit the mask marks. Everything else on the line stays whatever your truck has.
• SCCM 724-04-01 is a short line on the Lightning: "one of the addresses that has less than 10 bytes of info, only 6. So it's 'xxxx xx--' instead of 'xxxx xxxx xx--'" [32]. The 4th digit is still the one that changes.
• HCM 734-11-01 is not a mask. Livnitup's spreadsheet labels its two bytes CRC_LOW_BYTE and CRC_HIGH_BYTE, and the whole line is replaced with 0735 89 [33]. FlasherZ, who worked out the HCM lines: "turns out this worked, I had forgotten to update the 734-11-01 CRC value." [33]
• When you click Write, FORScan says the checksum doesn't match and asks you to Continue. That's normal: "When you do a Write, it says the checksum doesn't match but if you click Continue it will do it for you." [33]
• The forum does not prescribe a write order. On my truck, writing 734-11-01 before the other two HCM lines produced a checksum warning, and both HCM lines needed a second write before they read back correctly. So: one module at a time, HCM last, 734-11-01 last of all, and re-read every module after writing to confirm it took. That order is mine, not the forum's.
• Don't use values from the gas-truck spreadsheets. The maintained thread: "Blindly pasting in those values can cause issues with the Lightning" [12], with examples of ICE values disabling the Drive Modes screen and the Key Detection Alert toggle [34]. For this mod specifically: "some people were using values from the non-Lightning HCM spreadsheet for the Glare-Free Lighting mod but some of the addresses are different on a Lightning" [33].

Step 6: make it show up, and check the HCM

1. The forum: "May take a couple of restarts to take effect." [12] Turn the truck fully off, open the door, wait, turn it back on. Repeat if needed.
2. If it still isn't there, reboot the APIM. The thread's how-to: "Click wrench icon, then choose the reboot option for the module (APIM shown below). Hit the Play button at the bottom and follow instructions for turning vehicle off and waiting 10 seconds." [12] In 2.3.71 that lives under Service Procedures [35]; FORScan renamed "Module Reset" to "Module Reboot" in 2.3.59 [19]. One owner: "Resetting APIM module did the trick." [36]
3. Another owner only got the menu after cycling the headlight switch: "turned my light switch from auto to off and back to auto and.... It worked!" [36]
4. The toggle is in the sync screen at Settings > Vehicle > Lighting; the owner's manual's path is "Press SETTINGS. Press Vehicle. Press Lighting. Switch Glarefree Lighting on or off." [37] It replaces the Auto High Beam toggle rather than sitting next to it: "Yes, you replaced Auto-High Beam with Glare-free. It is an enhanced Auto High Beam." [8]
5. Check for an HCM checksum code. FlasherZ: "Then you have to check to make sure there aren't any checksum DTC's set for the HCM - that will prevent glare-free and bendy beams from working." [38] The code looks like "U3000 - Control Module... General Checksum Failure... Module: Headlamp Control Module," and "Clearing DTC's doesn't work - it just comes right back" until the values are right [39]. If you see it, re-read the three HCM lines against the table and fix them.

Step 7: how to tell it's working

• Headlight switch in Auto, Glare-free toggle on. The owner's manual: the system turns on when "You switch the system on. You set the lighting control to the autolamps position. The ambient light level is low enough. Your vehicle speed is greater than approximately 32 mph (52 km/h)," and turns off when "The vehicle speed falls below approximately 19 mph (30 km/h)." [37] US owners report it engaging a bit lower: "in the U.S., folks are reporting a lower engagement speed, e.g. 25 mph." [8]
• The cluster's "A" headlight icon: "Illuminates Green to confirm when the system is ready to assist. If your icon is white that is Auto High Beam, not Glare-free." [8] The green icon alone isn't proof: one owner "had the green icon and didn't notice a difference" until an APIM reset [36].
• What you see on a dark road, from the operation guide: the high beam on the side of the oncoming car drops out while the rest stays lit [8].
• Dynamic bending keeps working: "The swiveling (dynamic bending) lights continue to work with these settings." [28] If it stops, the HCM is wrong; a different value in 734-04-02 turned bending off on FlasherZ's truck [33].

Step 8: turning it off, or undoing a mistake

FORScan's restore procedure: "press 'Load All' button, select previously created file with *.ABT extension, confirm loading. Please make sure the configuration has applied properly then press 'Write All' button and confirm, to program new data to ECU." [29] Do that for each module you changed, re-read each one afterward, then the restarts from step 6. Or type the originals back from your saved files, one module at a time.

Two cautions from the forum:

• Ford's over-the-air updates can change module configuration. "It's also been confirmed that an OTA change, or a module update, can in fact UNDO a FORScan change" [40]; other owners say their mods have survived every OTA [40]. After the 10.1.0/10.1.1 SYNC updates, owners who had the toggle saw it renamed to Auto High Beam, and one explained the 10.1.0 APIM update "could have restored the setting in the touchscreen from glare-free to auto high beams. You would need to re-enable the toggle for it with FORScan." [10]
• Restoring an old backup after an OTA has its own risk: "OTAs could change the size of that configuration, location of bits in the configuration, and the bit values themselves." [40] Keep a fresh Save All after every OTA.

Guide 2: reading your real battery health

Ford doesn't show the pack's state of health in the truck or in the app. The battery energy control module (BECM) has it, and FORScan can read it with the free licence [21]. Nothing is written to the truck.

What you need

Same FORScan setup as Guide 1, steps 1 and 3. No Extended Licence needed [21].

The read

1. Charge to 100%. Set the charge limit to 100 in the FordPass app or on the screen and let it finish.
2. Read it soon after, while the pack is warm. Owners consistently see lower energy-to-empty on a cold pack: "We see the usual lower useable energy at the lower temps" [41]; "Best taken at 77 degrees and after a 100% charge." [42] One owner saw 119 kWh at 100% on a cold ER pack and was told to measure "with the battery preconditioned and at 100%" [43].
3. Truck fully on, adapter in, FORScan connected.
4. Open FORScan's live-data screen (the oscilloscope icon; it has Table, Dashboard and Oscilloscope modes [19]), double-click an empty square, and pick the BECM parameters. The ones to add:
   • HVBAT_HEALTH (%): state of health. A Lightning owner's instructions, verbatim: "FORScan, oscilloscope tool, double-click an empty square, choose HVBAT_HEALTH, %" [44]. It's the same number Car Scanner calls "HVB State of Health. Abbreviated as HvbSoh." [45]
   • BAT_TO_EMPTY_ESTIM (kWh): "Hybrid/EV Battery Energy to Empty – Estimated" [46]. At 100% this is the usable energy in your pack right now.
   • BATT_CHAR (%) and BAT_CHA_DIS (%): the pack's actual state of charge and the displayed one. They differ; on one owner's screen they read 75.22% and 79.50% at the same moment [47]. This is why the dash percentage can't be used for exact math.
   • HVBAT_CAP (A·h): a capacity figure in amp-hours that FORScan showed on my truck (392.8 A·h at about 51,500 miles, 2023 Extended Range). I could not find this parameter documented or reported by anyone else, so treat it as an unlabelled extra until someone with Ford's PID definitions explains it.
5. Press Play, let it settle, screenshot it.

What the numbers mean

• HVBAT_HEALTH is the straightforward one: percent of beginning-of-life capacity as the BECM estimates it, "always presented to the nearest 0.5%" [48]. Owner-reported pairs: 99.0% at 7,500 miles, 97.5% at 35k, 98.5% at 21k [48]; 95.5% at 63k miles in a hot climate [41]; 95% at 100,350 miles with frequent DC fast charging [44]; and outliers both ways.
• BAT_TO_EMPTY_ESTIM at 100% divided by the rating gives the same idea in energy. Ford's figures: "98 kWh of usable energy" for Standard Range and "131 kWh of usable energy" for Extended Range [49]. One owner at 8,400 miles saw "131.07 kWh" at full [48].
• The gross pack size is not published by Ford. Third-party sources put the ER pack at 142 kWh total, 408 Ah, 349 V nominal (batterydesign.net, which notes limited data) [50], and a battery refurbisher's teardown calls the 2024 pack 143 kWh [51]. I use 131 for the math because that's Ford's number.
• Treat all of it as an estimate. From the forum: "SOH fluctuates down and back up... It's a ball park guess into the health of the battery, not a measurement of battery degradation." [41] Take two readings a few days apart if you want to be careful, and don't panic over one low number.
• The warranty is not measured against 131. Ford's 2023 BEV warranty guide: the high-voltage battery is warranted "against excessive capacity loss for a period of 8 years/100,000 miles, whichever comes first," capacity "less than 70 percent of the high voltage battery's beginning of life capacity" is considered excessive, and "the measurement method used to determine the high voltage battery capacity... are at the sole discretion of Ford Motor Company." [52] Your FORScan number is a guide, not the warranty test.

If you read it below 100%

A rough number: BAT_TO_EMPTY_ESTIM ÷ (actual state of charge ÷ 100), using BATT_CHAR, not the dash. Mine at a displayed 52% was 68.6 kWh, which works out to about 132 kWh, but each percent of SOC error moves the answer about 2.5 kWh. Sanity check only.

Why bother

Consumer Reports on buying a used EV: "Third-party tools that plug into a vehicle's onboard diagnostics port (known as an OBD-II) can also analyze the health of an EV battery directly." [53] AAA's expert: "The high voltage battery's state of health, and ultimately, the range capability are the most important things to check." [54]

More you can do with FORScan on a Lightning

The headlights are one line in a long list. Same tool, same backup-first process, same forum. Every row below is taken from post #1 of the Lightning FORScan thread, Version 2 (maintained by bmwhitetx, last edited September 2026) [12], with the thread's own wording for what each mod does and what it needs. Open the thread for the actual addresses and values; I'm deliberately not repeating them here, because several change by model year. The original thread is where the headlight values came from.

Before you do any of them:

• The thread's own rule, verbatim: "make sure you backup your current settings or write them down before making any changes!"
• Its warning about the gas-truck spreadsheets, verbatim: "Blindly pasting in those values can cause issues with the Lightning." The linked example [34] shows ICE values disabling the CEA egress warning, the Drive Modes screen, and the Key Detection Alert toggle on Lightnings.
• Lightning FORScan HCM spreadsheet, by Livnitup [33]: "some people were using values from the non-Lightning HCM spreadsheet for the Glare-Free Lighting mod but some of the addresses are different on a Lightning."
• Livnitup's FORScan tutorial (backups, checksums, method), linked from post #2 of the Lightning thread [30] and from the 2021+ F-150 FORScan list. The gas-truck lists are where most mods were first worked out; use the Lightning thread's values.
• FORScan best practices and procedures: an owner's question thread with useful answers on folder structure and when to save, not an official procedure.
• FORScan's own forum for software problems, adapter compatibility, and licence questions.

Same rules every time: back up the module first, change one thing, re-read it, test it, then move on.

Sources

1. f150lightningforum.com, "FORSCAN best practices and procedures?" (Oct 2024): Firn #424878 ("almost ZERO safety net", OTA/as-built warning), bmwhitetx #425074 (Save All), rugedraw #424999 (photos), Lytning #424946 (quoting Livnitup's tutorial). https://www.f150lightningforum.com/forum/threads/forscan-best-practices-and-procedures.21703/
2. NHTSA, Final rule, FMVSS No. 108 adaptive driving beam headlamps, 87 FR 9916, February 22, 2022, Docket NHTSA-2022-0013. https://www.govinfo.gov/content/pkg/FR-2022-02-22/html/2022-02451.htm
3. NHTSA, Denial of petitions for reconsideration, 89 FR 106365, December 30, 2024 (petitioners include Ford Motor Company). https://www.govinfo.gov/content/pkg/FR-2024-12-30/html/2024-31141.htm
4. Rivian, "Dynamic Adventure Lighting": "launched in 2025, these were the first adaptive matrix headlights to be activated in the United States." https://rivian.com/stories/rivian-dynamic-adventure-lighting-matrix-headlights
5. NHTSA Chief Counsel interpretation NCC-230420-001 (April 16, 2025): the make-inoperative prohibitions "do not apply to the owner of a vehicle"; check State laws. See also 49 U.S.C. 30122(b). https://www.nhtsa.gov/interpretations/ncc-230420-001-571108-angelina-twardawa-auxiliary-side-lamps-interpretation-signed
6. Ford Motor Company, 2023 F-150 Lightning Order Guide (08/09/22), Pro series standard equipment: "LED Projector with Dynamic Bending Headlamps"; each higher series "includes the standard equipment of the previous series". https://dealerimages.dealereprocess.com/image/upload/v1680045244/1/ford/PDFs/F-150_Lightning_Order_Guide.pdf
7. f150lightningforum.com, "Glare-free headlights on 2025" (owner reports on a '24 Pro and a '25 Lariat). https://www.f150lightningforum.com/forum/threads/glare-free-headlights-on-2025.28505/
8. f150lightningforum.com, "Glare Free light operation", incl. post #477276 (operation guide), #482930 ("you replaced Auto-High Beam with Glare-free"), #421311 (2023 XLT), #477008 (switch in Auto). https://www.f150lightningforum.com/forum/threads/glare-free-light-operation.21435/
9. f150lightningforum.com, "Canadian Lightning Owners: does your headlight settings menu show an option for glare-free headlights?" https://www.f150lightningforum.com/forum/threads/canadian-lightning-owners-does-your-headlight-settings-menu-show-an-option-for-glare-free-headlights.11461/
10. f150lightningforum.com, "After 10.1.1 update - Glare Free renamed to Auto High Beam?" (rugedraw #453102, GDN #453283, s_c #463397). https://www.f150lightningforum.com/forum/threads/after-10-1-1-update-glare-free-renamed-to-auto-high-beam.23381/
11. forscan.org support, "Recommended adapters for FORScan for Windows": OBDLink EX and vLinker FS; USB over wireless; and home page notes on ELM327 clones. https://forscan.org/support/show_content.php?lang=en&product_id=fswf&issue=win_recommend_adapter
12. f150lightningforum.com, "F150 Lightning FORScan thread - Version 2", post #1 (maintained list, last edited Sep 2026) and post #2 (equipment, how to reboot a module). https://www.f150lightningforum.com/forum/threads/f150-lightning-forscan-thread-version-2.23634/
13. forum.forscan.org, FORScan staff: vLinker FS removed from the recommended list Feb 2025 over a USB 3.0 hub issue, restored 2025-05-30 after a new revision. https://forum.forscan.org/viewtopic.php?f=4&t=28290
14. forscan.org, Download page (FORScan for Windows 2.3.71, 2026-05-08; 2.3.71 adds "Obtain free trial license" link on the About page). https://forscan.org/download.html
15. forum.forscan.org, FORScan staff, 16 Jan 2025: the "This version of FORScan is outdated" message and the update requirement. https://forum.forscan.org/viewtopic.php?p=101019
16. forscan.org home page: "only x86/x64 architecture is supported for Windows. ARM architecture is not supported!"; and FORScan staff's ARM workaround thread. https://forscan.org/home.html
17. forum.forscan.org, FORScan staff, 28 Sep 2024, "How to run FORScan on Windows computer with ARM CPU" (Safe emulation). https://forum.forscan.org/viewtopic.php?f=5&t=27650
18. f150lightningforum.com, "GUIDE: FORScan on Apple Silicon MacBook Air" (Storx, Feb 2026): CrossOver, Wine Ports registry mapping, versions, left-side port, replug. https://www.f150lightningforum.com/forum/threads/guide-forscan-on-apple-silicon-macbook-air.35117/
19. forscan.org, version history: Demo mode checkbox (2.1.18), "Module Reset" renamed "Module Reboot" (2.3.59), Dashboard/Oscilloscope/Table modes. https://forscan.org/changes_history.html
20. forscan.org support, "Unable to connect to adapter": "Recommended settings in FORScan is 'Auto' for all parameters." https://forscan.org/support/show_content.php?lang=en&product_id=fswf&issue=technical_unable_connect_adapter
21. forscan.org support, "What is Extended License, why and when do I need it?" https://forscan.org/support/show_content.php?lang=en&product_id=fswf&issue=el_what_is_it
22. forscan.org, "Generate free 2 months trial Extended License Key" (the request form): fields, no email delivery, two active keys, Hardware ID changes with device configuration. https://forscan.org/support/prepare_trial_el_request.php?lang=en
23. forscan.org support, "Do I need an account on the forum to get a trial license?" https://forscan.org/support/show_content.php?lang=en&product_id=fswf&issue=forum_account_need_trial_license
24. forscan.org support, "What to do when the trial license expires": another free 2 months. https://forscan.org/support/show_content.php?lang=en&product_id=fswf&issue=el_how_to_get_after_trial
25. forscan.org support, "What is the Hardware ID and how to get it?" https://forscan.org/support/show_content.php?lang=en&issue=el_what_is_hw_id
26. forscan.org support, "How to generate and install free trial Extended License key": 20-30 minutes, About > Load License Key, restart. https://forscan.org/support/show_content.php?lang=en&product_id=fswf&issue=el_how_to_generate_install_trial
27. forscan.org support, "Transfer license to another computer" (Revoke/Uninstall, new Hardware ID). https://forscan.org/support/show_content.php?lang=en&product_id=fswf&issue=el_transfer_license
28. f150lightningforum.com, "F150 Lightning FORscan thread" (original), post #1 (vandy1981): masks, the all-caps backup warning, "swiveling (dynamic bending) lights continue to work". https://www.f150lightningforum.com/forum/threads/f150-lightning-forscan-thread.11406/
29. forum.forscan.org, FORScan staff, "How to manage module configuration in FORScan" (Feb 2021): .ABT format, Save All / Load All / Write All. https://forum.forscan.org/viewtopic.php?p=60000
30. Livnitup, FORScan tutorial (Google Doc, updated 6/14/26): backups to a secondary location, APIM reset under the wrench icon. https://docs.google.com/document/d/1-8dKaS_Spu4Zw4hV_CrKC4tLoP9G8yejqegF1wxIqxY/
31. f150lightningforum.com, original FORScan thread page 11, post #281984 (FordTough98198): stock 2022 Platinum as-built dump. https://www.f150lightningforum.com/forum/threads/f150-lightning-forscan-thread.11406/page-11
32. Same thread, post #9 (SCCM 724-04-01 is a 6-byte line). https://www.f150lightningforum.com/forum/threads/f150-lightning-forscan-thread-version-2.23634/
33. f150lightningforum.com, "Lightning FORScan HCM spreadsheet" (Livnitup, Aug 2022): Lightning HCM addresses differ from the gas truck; FlasherZ #248344 ("forgotten to update the 734-11-01 CRC value"), #247873 (734-04-02 turned bending off); page 3 #472914 (checksum prompt), #472921 (CRC byte labels). https://www.f150lightningforum.com/forum/threads/lightning-forscan-hcm-spreadsheet.11807/
34. Same thread, page 5, post #465042 (what pasting ICE-truck values did to Lightnings). https://www.f150lightningforum.com/forum/threads/f150-lightning-forscan-thread-version-2.23634/page-5
35. forum.forscan.org, user post May 2026 (v2.3.71): module reboot entries live under "Service Procedures". https://forum.forscan.org/viewtopic.php?p=109008
36. f150lightningforum.com, "Glare free headlights enabled with FORScan but no difference" (2026): #685564 (switch Auto>Off>Auto), #685573 (APIM reset), #685567. https://www.f150lightningforum.com/forum/threads/glare-free-headlights-enabled-with-forscan-but-no-difference.36912/
37. Ford, 2023 F-150 Lightning Owner's Manual (US), "Glare Free Lighting (If Equipped)": requirements and limitations, 32 mph / 19 mph; and the touchscreen path Settings > Vehicle > Lighting. https://www.fordservicecontent.com/Ford_Content/vdirsnet/OwnerManual/Home/Content?variantid=9334&languageCode=en&countryCode=USA&moidRef=G2160194&Uid=G2182639&ProcUid=G2193326&userMarket=USA&div=f&vFilteringEnabled=False&buildtype=web
38. f150lightningforum.com, original FORScan thread page 5, post #248349 (FlasherZ): the HCM recipe and "check to make sure there aren't any checksum DTC's set for the HCM". https://www.f150lightningforum.com/forum/threads/f150-lightning-forscan-thread.11406/page-5
39. f150lightningforum.com, original FORScan thread page 4, post #245609 (FlasherZ): U3000 General Checksum Failure on the HCM. https://www.f150lightningforum.com/forum/threads/f150-lightning-forscan-thread.11406/page-4
40. f150lightningforum.com, "How do OTAs affect FORScan changes?" (RickLightning #474923, Henry Ford #474690, Firn quoted in #474350). https://www.f150lightningforum.com/forum/threads/how-do-otas-affect-forscan-changes.24559/
41. f150lightningforum.com, "SOH is not battery capacity" (Zprime29, Jul 2026): 95.5% at 63k miles, temperature effect, "ball park guess". https://www.f150lightningforum.com/forum/threads/soh-is-not-battery-capacity.38958/
42. f150lightningforum.com, "Connected with CarScanner, now what?" (RickLightning, Nov 2024): 77 degrees and after a 100% charge; actual vs displayed SOC. https://www.f150lightningforum.com/forum/threads/connected-with-carscanner-now-what.22541/
43. f150lightningforum.com, "HVB Energy to Empty" (Dec 2024): 119 kWh at 100% on a cold pack. https://www.f150lightningforum.com/forum/threads/hvb-energy-to-empty.23540/
44. f150lightningforum.com, "How are we holding up?" (bmwhitetx, Apr 2026: HVBAT_HEALTH in FORScan; AZT9: 95% at 100,350 miles). https://www.f150lightningforum.com/forum/threads/how-are-we-holding-up.36157/
45. f150lightningforum.com, "My first time using Car Scanner" (bmwhitetx): HVB State of Health = HvbSoh. https://www.f150lightningforum.com/forum/threads/my-first-time-using-car-scanner.25131/
46. electricvehiclewiki.com, Focus Electric diagnostic PIDs: BAT_TO_EMPTY_ESTIM = "Hybrid/EV Battery Energy to Empty – Estimated". https://www.electricvehiclewiki.com/focus-electric-diagnostic-pids/
47. f150lightningforum.com, "FORScan HVB capacity number... should I be concerned?" (jallen, 2023 Pro): BATT_CHAR 75.22% vs BAT_CHA_DIS 79.50% on the same screen. https://www.f150lightningforum.com/forum/threads/forscan-hvb-capacity-number%E2%80%A6should-i-be-concerned.14846/
48. f150lightningforum.com, "What is your SOH, mileage and how do you use your battery?" (page 1 and page 7): 131.07 kWh at 8,400 miles, nearest 0.5%, assorted SOH/mileage pairs. https://www.f150lightningforum.com/forum/threads/what-is-your-soh-mileage-and-how-do-you-use-your-battery.18964/
49. Ford, 2023 F-150 Lightning Technical Specifications (media.ford.com, archived copy): "98 kWh of usable energy" / "131 kWh of usable energy"; warranty footnote. http://web.archive.org/web/20240919084403/https://media.ford.com/content/dam/fordmedia/North%20America/US/product/2023/f150lightning/F-150%20Lightning%20Tech%20Specs.pdf
50. batterydesign.net, "2022 Ford F-150 Lightning ER": total energy 142 kWh, usable 131 kWh, 408 Ah, 349 V nominal (page notes limited data). https://www.batterydesign.net/ford-f-150-lightning-er/
51. GreenTec Auto, YouTube, "Teardown of the New 2024 Ford Lightning 143kWh Battery" (Dec 2024). https://www.youtube.com/watch?v=oGjXIwx5gGA
52. Ford, 2023 Model Year Battery Electric Vehicle Warranty Guide: High Voltage Lithium-Ion Battery Capacity Coverage. https://www.fordservicecontent.com/Ford_Content/Catalog/owner_information/US_Ford_BEV_Warranty_Guide_9.5.23.pdf
53. Consumer Reports, "Buying a Used Electric Vehicle: What to Know" (updated Aug 2026). https://www.consumerreports.org/cars/hybrids-evs/buying-a-used-electric-vehicle-what-to-know-a7139266510/
54. AAA, "Expert Q&A: How to shop for a used EV like a pro" (Dec 2024). https://ev.aaa.com/articles/expert-qa-how-to-shop-for-a-used-ev-like-a-pro/