Lightning FORScan HCM spreadsheet

[Iroc34a]

I'm slightly embarrassed to have to ask this but am I right that the values in the far right column are the settings needed for the glare-free headlights?

Ignore the x's. Replace the numerals or numbers. In this case the asterisk is either 1 or 2.

Sponsored

 

[Firn]

Has anyone tested if the camera and map based dynamic bending works on US roads?
734-04-02 first bit set x4xx? I see in the glare free guide we don't change it, so I didn't try it yet.

I have tried and it doesn't work, it also disables auto headlights, glare free, and dynamic bending.

I'm assuming that we need some bits set elsewhere for it to work, probably from the camera module. Hopefully someday we can get those off of a foreign truck.

 

[Tom Jensen]

Ignore the x's. Replace the numerals or numbers. In this case the asterisk is either 1 or 2.

Thank you.

 

[Firn]

Thank you. I’m a total novice at this kind of vehicle brain surgery and need all the help I can get. I really don’t want to mess this up.

Save, save, and save again.

With OTA updates and the fact our trucks push our current values back to the Ford servers as "factory" make SURE you have save files. Save everything when you first start, every module. Then save the module you are changing BEFORE you make any changes. Then save the module after you have made changes.

Also, FORSCAN instructions usually tell you to change a bit to a set value. Since each vehicle, each trim, each configuration, can have different starting values you sometimes have to research which value to change too, especially if the changes come from a non-lightning source (livingitup's sheet for example). An example of this is the "cameras at speed", since the instructions came from a gas truck (that's doesn't have 1pd) it said to change to a value that did not have 1pd enabled, as a result a lot of folks lost 1pd. What needed to be done is instead of changing that value to an "E" like the instructions said, instead Lightning owners needed to change it to an "F".

It's worth looking at each change in the Livingitup spreadsheets, diving into each module. Use your current value and make sure the value you are changing to makes sense.

In general most instructions are fine, just know that each truck might be a bit different.

 

[Robob]

I have tried and it doesn't work, it also disables auto headlights, glare free, and dynamic bending.

I'm assuming that we need some bits set elsewhere for it to work, probably from the camera module. Hopefully someday we can get those off of a foreign truck.

Ah same thing I found out after testing.
Next, I was looking at 734-01-01 and enabling DHL leveling and dynamic mode but unsure if this is working. I will need to wait for next night drive to see if it actually levels and has glare free enabled

 

[Firn]

Ah same thing I found out after testing.
Next, I was looking at 734-01-01 and enabling DHL leveling and dynamic mode but unsure if this is working. I will need to wait for next night drive to see if it actually levels and has glare free enabled

Tried that too, threw a bunch of errors due to lacking wheel height sensors

 

[Robob]

Ah so it seems, too bad there is not a way to have the software find out the dependencies and report back what bits need to be flipped to enable certain options.

 

[Firn]

Ah so it seems, too bad there is not a way to have the software find out the dependencies and report back what bits need to be flipped to enable certain options.

I know enough about software programming to be a problem, but not enough to actually do it.

If there was a way to collect lots and lots (and lots) of As Built files it would be possible to look for patterns in the data to try and determine just that.

I expect cross comparison would work between all Ford models, not just Lightnings or even trucks.

 

[21st Century Truck]

I know enough about software programming to be a problem, but not enough to actually do it.

If there was a way to collect lots and lots (and lots) of As Built files it would be possible to look for patterns in the data to try and determine just that.

I expect cross comparison would work between all Ford models, not just Lightnings or even trucks.

Agree... control modules are likely practically the same across Ford product lines.

I know that some are (were?) made by Research In Motion, the old Blackberry manufacturer.

 

[Firn]

I wonder how many VINs motorcraft let's you run through their website...

 

[Dynamo]

Then I'll need a way to calculate the proper CRC for 734-11-01 so it's not throwing a checksum DTC/MIL.

Hello, do you know or can share how to properly calculate CRC? Bacause I want to try activate it on another vehcile, where HCM values a little bit different

 

[bmwhitetx]

Hello, do you know or can share how to properly calculate CRC? Bacause I want to try activate it on another vehcile, where HCM values a little bit different

FORScan will automatically calculate it for you. When you do a Write, it says the checksum doesn't match but if you click Continue it will do it for you.

It is the sum (in hex) of all the parameter values including the parameter (like 7D0-01-01). Round to two places.

 

[Dynamo]

FORScan will automatically calculate it for you. When you do a Write, it says the checksum doesn't match but if you click Continue it will do it for you.

It is the sum (in hex) of all the parameter values including the parameter (like 7D0-01-01). Round to two places.

Yes, it counts automatically for each line at the end, but this is a little different
According to Livnitup's FORScan - 2021-24 F150 spreadsheet
734-11-01
**xx -- CRC_LOW_BYTE (CRCLOWBYTE)
734-11-01
xx** -- CRC_HIGH_BYTE (CRCHIGHBYTE)
And as I understand it, Forscan will not be able to count where **** is, it will only count at the end, where --
And in my case, I need these CRC calculations, because I want to try activate Glare Free on another car, where the HCM different and the encoding for it are different and this CRC parameter is generally contained in 734-01-04

 

[evowner]

Any other ways to get the extended license since Forscan halted licenses due to banking rules?

 

[bmwhitetx]

Yes, it counts automatically for each line at the end, but this is a little different
According to Livnitup's FORScan - 2021-24 F150 spreadsheet
734-11-01
**xx -- CRC_LOW_BYTE (CRCLOWBYTE)
734-11-01
xx** -- CRC_HIGH_BYTE (CRCHIGHBYTE)
And as I understand it, Forscan will not be able to count where **** is, it will only count at the end, where --
And in my case, I need these CRC calculations, because I want to try activate Glare Free on another car, where the HCM different and the encoding for it are different and this CRC parameter is generally contained in 734-01-04

The whole HCM module is complex. Livnitup has 4 different tabs for HCM depending on ICE and year!

I see what you're saying about the entire parameter being a CRC for the ICE truck. That's strange to me. CRC looks to be different than a two-byte checksum so have no idea. I suggest posting in the vehicle forum you're trying to modify. Or contact Livnitup. Sorry.

Sponsored