Bawest
Active Member
- First Name
- Brooke
- Joined
- Oct 28, 2021
- Threads
- 5
- Messages
- 25
- Reaction score
- 28
- Location
- Houston, tx
- Vehicle(s)
- 2019 d ranger
- Occupation
- Engineer
- Thread starter
- #31
Thanks
Sponsored
Sponsored
Bawest
Active Member
- First Name
- Brooke
- Joined
- Oct 28, 2021
- Threads
- 5
- Messages
- 25
- Reaction score
- 28
- Location
- Houston, tx
- Vehicle(s)
- 2019 d ranger
- Occupation
- Engineer
- Thread starter
- #32
Issue that I came across. as built data doesn't match computer module. Module has line for 737-05 and 06, as built does not contain these numbers.
Also, there are some boxes on forscan that do not give me the option to write but the numbers do not match what is in the as built data.
As built data:
VIN# in Hex Data Format
Hex Lines:
737-01-01 - VIN# 1-5
737-01-02 - VIN# 6-10
737-01-03 - VIN# 11-15
737-01-04- VIN# 16-17
The other hex lines should be the same for all trims
Also, there are some boxes on forscan that do not give me the option to write but the numbers do not match what is in the as built data.
As built data:
|
VIN# in Hex Data Format
Hex Lines:
737-01-01 - VIN# 1-5
737-01-02 - VIN# 6-10
737-01-03 - VIN# 11-15
737-01-04- VIN# 16-17
The other hex lines should be the same for all trims
RangerBill
Well-Known Member
The boxes on the extreme right are a checksum calculated by the software and you cannot change them. This is normal.
Bawest
Active Member
- First Name
- Brooke
- Joined
- Oct 28, 2021
- Threads
- 5
- Messages
- 25
- Reaction score
- 28
- Location
- Houston, tx
- Vehicle(s)
- 2019 d ranger
- Occupation
- Engineer
- Thread starter
- #34
Do I need to worry about lines 5 and 6?
airline tech
Well-Known Member
- Joined
- Aug 24, 2022
- Threads
- 28
- Messages
- 4,482
- Reaction score
- 8,551
- Location
- Midwest - KS
- Vehicle(s)
- 2022 Ranger Lariat-Super Crew, Cactus Gray
- Occupation
- Aircraft Tech
I am not 100% certain on this but I think the software version PN may drive what data lines are available to configure.
I know that my 2022 with my module configuration run:
Shows the following:
RCM PN: KB3T-14B321-BD - Software Version: GN15-14C028-CA
All of my As-Built compares do not show 737-05-01 or 737-06-01 in any of the database runs.
If we reference the As-Built Database files (All Fords)
here is what those 2 lines breakdown into:
Being that the Ranger does not use those lines, then if it is listing them I am not 100% if if really matters for those lines.
The most important I guess would be to ensure that they read like this:
0000-xx
so write (zero) 0000 and then write it, it may give a pop up message about check-sum and then write it - the check sum should be auto populated with the correct check-sum for the line.
To point out what the check-sum is:
Its the last (2) hex data of every line, and generally when you write a line (if you leave the last 2 characters alone) they will auto populate the correct (Check-Sum)
Note: this goes for all As-Built Lines such as 1234-ABCD-12xx (xx) = the check sum
I am not sure, I do not remember if Forscan will display the Module SW Number or not, I think it does in the module run.
I know when I played with FDRS last year there were no updates to the software of the RCM.
So I am not 100% but I think the extra lines are due to the module being somewhat universal and another model may require those lines of data and if it follows the rest of the As-Built files then all (0's) on the line equals a non configurable or non optioned line of data.
I know that my 2022 with my module configuration run:
Shows the following:
RCM PN: KB3T-14B321-BD - Software Version: GN15-14C028-CA
All of my As-Built compares do not show 737-05-01 or 737-06-01 in any of the database runs.
If we reference the As-Built Database files (All Fords)
here is what those 2 lines breakdown into:
Being that the Ranger does not use those lines, then if it is listing them I am not 100% if if really matters for those lines.
The most important I guess would be to ensure that they read like this:
0000-xx
so write (zero) 0000 and then write it, it may give a pop up message about check-sum and then write it - the check sum should be auto populated with the correct check-sum for the line.
To point out what the check-sum is:
Its the last (2) hex data of every line, and generally when you write a line (if you leave the last 2 characters alone) they will auto populate the correct (Check-Sum)
Note: this goes for all As-Built Lines such as 1234-ABCD-12xx (xx) = the check sum
I am not sure, I do not remember if Forscan will display the Module SW Number or not, I think it does in the module run.
I know when I played with FDRS last year there were no updates to the software of the RCM.
So I am not 100% but I think the extra lines are due to the module being somewhat universal and another model may require those lines of data and if it follows the rest of the As-Built files then all (0's) on the line equals a non configurable or non optioned line of data.
Sponsored
