Sponsored

Ruffiano99

Well-known member
First Name
Joe
Joined
Jan 11, 2022
Threads
2
Messages
107
Reaction score
29
Location
NY
Vehicles
2021 f150
This truck and this process has been fighting me every inch of the way ?. Ill try the reinstall, in a few days when my Mongoose gets here. Amazon updated my delivery date from April 14th to April 6th! My FDRS 2 day license already expired. I’ll probably spring for the 1 month again. At this rate it probably would have been more cost effective to just buy the whole year, ill already be about $450 into license fees. ??? Ford should reimburse us all for this.
@Ford Motor Company
Sponsored

 

Shoebox72069

Well-known member
Joined
Dec 3, 2021
Threads
4
Messages
138
Reaction score
64
Location
MN
Vehicles
2021 F150 Powerboost Lariat
@Ruffiano99 , @Shoebox72069

Those odd errors have been fixed in the past by reinstalling FDRS. If you go that route, be sure to release your license before you uninstall so that it is is available again after you get done.

This was a good suggestion!

I released the license, removed the software and reinstalled. Reboots between everything....

No change unfortunately.
 

RapidRedRick

Active member
First Name
Rick
Joined
Jan 19, 2022
Threads
0
Messages
35
Reaction score
7
Location
Northern Virginia
Vehicles
Ford F150 Platinum Powerboost
Got it figured out. There was a DSM SW update today so I did that and it fixed everything. So with the DSM update it put the boards back to factory original settings but instead of the annoying locking the truck from the door outside button the steps going up and not even 2 seconds later they come back down, it appears Ford fixed the bars and they stay up when pressing the outside door button, door outside keypad lock, or fob lock button is pushed and you around the vehicle walking away. This is nice that's finally fixed as that was annoying.

Now before I did the DSM update I was doing some testing in Forscan and found a great setting with the step bars only coming down when the door was opened but as you approach they stay up and your approach lighting still works (as long as you don't have Lincoln AutoFold Mirrors set instead of the original AutoFold Mirrors) as well as the step bar switches will work. This is great when you are walking around your vehicle but tired of the steps going up and down constantly. My settings on the sync screen are Power Running Boards Auto, Timer 5 min, Approach Setting and Lighting set to on. After you have this all set leave it and don't touch. Make the changes below in Forscan then do the module reset and away you go. So the settings I used were the following.

744-23-01 > 0001-0001-00XX
744-23-02 > 0101-0000-XX
or for those with older block setup for that line 744-23-02 > 0101-00XX
Awesome board tip! When you say “reset module” is there a specific procedure you follow to reset the module?
 

Sponsored

Shoebox72069

Well-known member
Joined
Dec 3, 2021
Threads
4
Messages
138
Reaction score
64
Location
MN
Vehicles
2021 F150 Powerboost Lariat
Anyone see anything out of the ordinary with this? The FDRS logs from the run are super chewy... and this is Java :sick:


BECM - Battery Energy Control Module
- No DTCs Detected
- DID F166 - 19092510
- DID F15F - 08080001500444020000
- DID F163 - 04
- DID D03F - 40888D0148537F811B10ECF471FEEAA5167D615EEDDF4DC6F62A5AFDD7E8FBC5
- DID F188 - ML38-14C197-AD
- DID DA01 - ML38-10B687-AD
- DID F110 - DSML38-10B687-AD
- DID F162 - 06
- DID F111 - ML38-14F092-AA
- DID F113 - ML38-10B687-AD
- DID F18C - H388E21008000784

2022-04-02T07:24:03,139 INFO host.moduletoolbox.ToolboxManagerSingleton - Download of BECM - Battery Energy Control Module (BECM) Software Update started.
2022-04-02T07:24:03,279 WARN cache.helper.GeneralCacheHelper - Failed to obtain resource creation date (resource not in cache) ApplicationManifestResourceKey {applicationId='G2232623', applicationType='OTX', applicationXmlUri='null', resourceType='APPLICATION_MANIFEST', uid='1FTFW1ED8MFA91029', nodeAddress='null', languageCode='en', countryCode='US'}
2022-04-02T07:24:03,280 INFO fdsp.applicationpackaging.ApplicationPackagingService - Requesting application manifest for G2232623
2022-04-02T07:24:06,626 I/O client.fdsp.AbstractRestService - [REST] Response loaded: GetApplicationManifestResponse
2022-04-02T07:24:06,632 INFO fdsp.applicationpackaging.ApplicationPackagingService - Application manifest received G2232623
2022-04-02T07:24:06,635 WARN client.application.ApplicationManifestFactory - No Node to HMI Color mappings for applications
2022-04-02T07:24:06,731 WARN cache.helper.GeneralCacheHelper - Failed to obtain resource creation date (resource not in cache) ResourceKey {resourceType='RND_MDX', uid='G2159032', languageCode='null', countryCode='null', rndVersion='null'}
2022-04-02T07:24:06,732 I/O dflt.provider.FdspResourceProvider - [REST] Retrieve resource (id=G1818186, type=RND_ODX) from FDSP
2022-04-02T07:24:06,732 I/O dflt.provider.FdspResourceProvider - [REST] Retrieve resource (id=G1818205, type=OTX_APP) from FDSP
2022-04-02T07:24:06,732 I/O dflt.provider.FdspResourceProvider - [REST] Retrieve resource (id=G2232623, type=OTX_APP) from FDSP
2022-04-02T07:24:06,733 I/O dflt.provider.FdspResourceProvider - [REST] Retrieve resource (id=G2159032, type=RND_MDX) from FDSP
2022-04-02T07:24:07,049 I/O dflt.provider.FdspResourceProvider - [REST] Response status - OK. Download time - 295 ms
2022-04-02T07:24:07,075 I/O dflt.provider.FdspResourceProvider - [REST] Response status - OK. Download time - 328 ms
2022-04-02T07:24:07,547 I/O dflt.provider.FdspResourceProvider - [REST] Response status - OK. Download time - 788 ms
2022-04-02T07:24:08,357 I/O dflt.provider.FdspResourceProvider - [REST] Response status - OK. Download time - 1599 ms
2022-04-02T07:24:08,660 INFO host.moduletoolbox.ToolboxManagerSingleton - #######> toolDownloadCompleted : BECM - Battery Energy Control Module (BECM) Software Update
2022-04-02T07:24:09,253 INFO host.moduletoolbox.ToolboxManagerSingleton - Download took 6.1220074 seconds to complete for BECM - Battery Energy Control Module (BECM) Software Update.
2022-04-02T07:24:11,109 INFO host.moduletoolbox.RunToolRunner - A tool is already running
2022-04-02T07:24:11,115 INFO host.moduletoolbox.RunToolRunner - Attempting to run tool
2022-04-02T07:24:11,115 INFO dflt.baton.DefaultApplicationBatonManager - Request baton for application G2232623
2022-04-02T07:24:11,115 INFO dflt.baton.DefaultApplicationBatonManager - Baton has been acquired for application G2232623. Current baton status ApplicationBaton{state=LOCKED, batonOwner=BatonOwner{name='FDRS', application=G2232621}, listener=null}
2022-04-02T07:24:11,134 INFO application.bootstrap.FdtApplicationLauncher - Searching for bootstrap id : "FDT_OTX_WEB_APP"
2022-04-02T07:24:11,134 INFO application.bootstrap.FdtApplicationLauncher - Found application bootstrap ID
2022-04-02T07:24:11,149 INFO hmi.otx.OtxHmiApplicationView - Creating OtxHmiApplication view singleton...
2022-04-02T07:24:11,154 INFO application.swt.TabbedSwtApplicationView - Updating view OtxHmiApplicationView {} for ONLINE mode!
2022-04-02T07:24:11,176 INFO hmi.otx.OtxHmiApplicationView - Showing vehicle selection tab.
2022-04-02T07:24:11,441 INFO hmi.otx.GetScreenHistoryFunction - JS Function "__fdtOtxGetScreenHistory" registered.
2022-04-02T07:24:13,226 INFO hmi.otxImpl.GetProcedureInformationFunctionImpl - {
"title" : "Battery Energy Control Module (BECM) Software Update",
"gNumber" : "G2232623",
"version" : "1.000"
}
2022-04-02T07:24:13,288 INFO hmi.otxImpl.LaunchBundleFunctionImpl - Launching bundle "Battery Energy Control Module (BECM) Software Update"
2022-04-02T07:24:13,449 INFO otx.core.BaseApplication - Adding runtime logs appender to COMMS channel logger
2022-04-02T07:24:15,440 ERROR j2534.win32.InstalledDeviceImpl - Not supported on non-Bosch device.
2022-04-02T07:24:15,456 WARN dflt.sources.VciConnectionSource - Failed to clear last used device: Error 1 clear last used device = Not supported on non-Bosch device. [J2534_ERROR:ERR_NOT_SUPPORTED]
2022-04-02T07:24:15,464 INFO j2534.win32.InstalledDeviceImpl - Thread-88
java.lang.Thread.getStackTrace(Thread.java:1559)
com.ford.etis.runtime.j2534.win32.InstalledDeviceImpl.logStackTrace(InstalledDeviceImpl.java:1075)
com.ford.etis.runtime.j2534.win32.InstalledDeviceImpl.passThruClose(InstalledDeviceImpl.java:504)
com.ford.etis.runtime.j2534.win32.DeviceConnectionImpl.closeDeviceConnection(DeviceConnectionImpl.java:446)
com.ford.etis.runtime.j2534.win32.DeviceConnectionImpl.close(DeviceConnectionImpl.java:414)
com.ford.otx.services.deviceconnection.dflt.sources.VciConnectionSource.closeConnection(VciConnectionSource.java:190)
com.ford.otx.services.deviceconnection.dflt.DefaultDeviceConnectionProvider.closeAllConnections(DefaultDeviceConnectionProvider.java:160)
com.ford.otx.services.deviceconnection.dflt.DefaultVehicleConnectionManager.cleanVehicleConnection(DefaultVehicleConnectionManager.java:343)
com.ford.otx.services.deviceconnection.dflt.DefaultVehicleConnectionManager.handleDisconnectedVehicleConnection(DefaultVehicleConnectionManager.java:243)
com.ford.otx.services.deviceconnection.dflt.DefaultVehicleConnectionManager.closeVehicleConnection(DefaultVehicleConnectionManager.java:202)
com.ford.otx.services.deviceconnection.command.CloseVehicleConnection.execute(CloseVehicleConnection.java:36)
com.ford.otx.services.deviceconnection.command.CloseVehicleConnection.execute(CloseVehicleConnection.java:10)
com.ford.otx.command.invoker.osgi.OSGICommandInvoker.invoke(OSGICommandInvoker.java:126)
com.ford.etis.runtime.apps.otx.core.BaseLibrary.closeDeviceConnection(BaseLibrary.java:174)
com.ford.etis.runtime.apps.otx.G1818205.orchestrateFlow(G1818205.java:386)
com.ford.etis.runtime.apps.otx.G1818205.main(G1818205.java:111)
com.ford.etis.runtime.apps.otx.core.BaseApplication.startApp(BaseApplication.java:319)
com.ford.etis.runtime.apps.otx.core.BaseApplication.access$000(BaseApplication.java:106)
com.ford.etis.runtime.apps.otx.core.BaseApplication$1.run(BaseApplication.java:254)
java.lang.Thread.run(Thread.java:748)

2022-04-02T07:24:15,534 INFO j2534.win32.InstalledDeviceImpl - Thread-88
java.lang.Thread.getStackTrace(Thread.java:1559)
com.ford.etis.runtime.j2534.win32.InstalledDeviceImpl.logStackTrace(InstalledDeviceImpl.java:1075)
com.ford.etis.runtime.j2534.win32.InstalledDeviceImpl.passThruOpen(InstalledDeviceImpl.java:467)
com.ford.etis.runtime.j2534.win32.InstalledDeviceImpl.open(InstalledDeviceImpl.java:211)
com.ford.otx.services.deviceconnection.dflt.sources.VciConnectionSource.createVciDeviceConnection(VciConnectionSource.java:270)
com.ford.otx.services.deviceconnection.dflt.sources.VciConnectionSource.connectToPreferredVci(VciConnectionSource.java:228)
com.ford.otx.services.deviceconnection.dflt.sources.VciConnectionSource.getDeviceConnection(VciConnectionSource.java:87)
com.ford.otx.services.deviceconnection.dflt.sources.VciConnectionSource.getDeviceConnection(VciConnectionSource.java:29)
com.ford.otx.services.deviceconnection.dflt.DefaultDeviceConnectionProvider.getConnection(DefaultDeviceConnectionProvider.java:77)
com.ford.otx.services.deviceconnection.dflt.DefaultVehicleConnectionManager.init(DefaultVehicleConnectionManager.java:292)
com.ford.otx.services.deviceconnection.dflt.DefaultVehicleConnectionManager.getVehicleConnection(DefaultVehicleConnectionManager.java:123)
com.ford.otx.services.deviceconnection.dflt.DefaultVehicleConnectionManager.reconnectVehicleConnection(DefaultVehicleConnectionManager.java:365)
com.ford.otx.services.deviceconnection.dflt.DefaultVehicleConnectionManager.handleDisconnectedVehicleConnection(DefaultVehicleConnectionManager.java:244)
com.ford.otx.services.deviceconnection.dflt.DefaultVehicleConnectionManager.closeVehicleConnection(DefaultVehicleConnectionManager.java:202)
com.ford.otx.services.deviceconnection.command.CloseVehicleConnection.execute(CloseVehicleConnection.java:36)
com.ford.otx.services.deviceconnection.command.CloseVehicleConnection.execute(CloseVehicleConnection.java:10)
com.ford.otx.command.invoker.osgi.OSGICommandInvoker.invoke(OSGICommandInvoker.java:126)
com.ford.etis.runtime.apps.otx.core.BaseLibrary.closeDeviceConnection(BaseLibrary.java:174)
com.ford.etis.runtime.apps.otx.G1818205.orchestrateFlow(G1818205.java:386)
com.ford.etis.runtime.apps.otx.G1818205.main(G1818205.java:111)
com.ford.etis.runtime.apps.otx.core.BaseApplication.startApp(BaseApplication.java:319)
com.ford.etis.runtime.apps.otx.core.BaseApplication.access$000(BaseApplication.java:106)
com.ford.etis.runtime.apps.otx.core.BaseApplication$1.run(BaseApplication.java:254)
java.lang.Thread.run(Thread.java:748)

2022-04-02T07:24:15,617 INFO apps.readvin.ReadVehicleIdentificationNumber - Attempting to read VIN from vehicle
2022-04-02T07:24:15,624 DEBUG api.service.Channel - PassThruMsg: ISO15765 TX -> 0,000,000,000 - [00,00,07,DF,09,02]
2022-04-02T07:24:15,721 DEBUG api.service.Channel - PassThruMsg: ISO15765 TX -> 0,000,000,000 - [00,00,07,26,22,F1,90]
2022-04-02T07:24:15,839 DEBUG api.service.Channel - PassThruMsg: ISO15765 RX <- 2,051,488,447 - [00,00,07,E8]
2022-04-02T07:24:15,839 DEBUG api.service.Channel - PassThruMsg: ISO15765 RX <- 2,051,507,725 - [00,00,07,E8,49,02,01,31,46,54,46,57,31,45,44,38,4D,46,41,39,31,30,32,39]
2022-04-02T07:24:15,841 DEBUG api.service.Channel - PassThruMsg: ISO15765 RX <- 2,051,579,370 - [00,00,07,2E]
2022-04-02T07:24:15,841 DEBUG api.service.Channel - PassThruMsg: ISO15765 RX <- 2,051,609,650 - [00,00,07,2E,62,F1,90,31,46,54,46,57,31,45,44,38,4D,46,41,39,31,30,32,39,00,00,00,00,00,00,00]
2022-04-02T07:24:15,842 INFO readvin.utils.SubmitReadVinUtils - Number of vins has found 1
2022-04-02T07:24:15,843 INFO deviceconnection.dflt.DefaultVehicleConnectionManager - Successfully obtain vehicle connection.
2022-04-02T07:24:16,897 INFO otx.core.BaseApplication - Adding runtime logs appender to COMMS channel logger
2022-04-02T07:24:17,058 INFO class otxcontainer.G2232623.authorLogs -

BEGIN ~~ main
2022-04-02T07:24:17,058 INFO class otxcontainer.G2232623.authorLogs -

BEGIN ~~ OTXAppFlowControl
2022-04-02T07:24:17,062 INFO class otxcontainer.G2232623.authorLogs -

BEGIN ~~ GetVehicleNodeInfoProcess
2022-04-02T07:24:17,062 INFO class otxcontainer.G2232623.authorLogs -

BEGIN ~~ BargraphDisplay
2022-04-02T07:24:17,062 INFO class otxcontainer.G2232623.authorLogs -

BEGIN ~~ GetVehicleNodeInfo
2022-04-02T07:24:17,080 INFO class otxcontainer.G2232623.authorLogs - node count 0
2022-04-02T07:24:17,080 INFO class otxcontainer.G2232623.authorLogs - node address 7E4
2022-04-02T07:24:17,080 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F166 = 19092510
2022-04-02T07:24:17,080 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F188 = ML38-14C197-AD
2022-04-02T07:24:17,095 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F110 = DSML38-10B687-AD
2022-04-02T07:24:17,095 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F162 = 06
2022-04-02T07:24:17,106 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID D03F = 40888D0148537F811B10ECF471FEEAA5167D615EEDDF4DC6F62A5AFDD7E8FBC5
2022-04-02T07:24:17,114 ERROR otxcontainer.G2232623 - Error in application, message was: No response found for DID DE00
com.ford.etis.runtime.apps.otx.utils.exceptions.NoDidResponseException: No response found for DID DE00
at com.ford.etis.runtime.apps.otx.utils.types.ford.VehicleDidWrapper.getGivisVehicleDidResponse(VehicleDidWrapper.java:79) ~[com.ford.otx.common.apps.utils-40.8.21.jar:?]
at com.ford.etis.runtime.apps.otx.utils.types.ford.VehicleDidVariable.getGivisVehicleDidResponse(VehicleDidVariable.java:54) ~[com.ford.otx.common.apps.utils-40.8.21.jar:?]
at otxcontainer.G2232623.GetVehicleNodeInfo(G2232623.java:7321) [G2232623:?]
at otxcontainer.G2232623.access$1600(G2232623.java:90) [G2232623:?]
at otxcontainer.G2232623$10.run(G2232623.java:17770) [G2232623:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_171]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_171]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
2022-04-02T07:24:17,140 INFO class otxcontainer.G2232623.authorLogs - No GIVIS response for: DE00
2022-04-02T07:24:17,141 INFO class otxcontainer.G2232623.authorLogs - Missing backup config data!! -- DE00
2022-04-02T07:24:17,141 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F18C = H388E21008000784
2022-04-02T07:24:17,141 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F113 = ML38-10B687-AD
2022-04-02T07:24:17,141 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F111 = ML38-14F092-AA
2022-04-02T07:24:17,141 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F163 = 04
2022-04-02T07:24:17,157 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F15F = 08080001500444020000
2022-04-02T07:24:17,158 INFO class otxcontainer.G2232623.authorLogs - Number of config DIDs = 0
2022-04-02T07:24:17,158 ERROR otxcontainer.G2232623 - Error in application, message was: Index: 0, Size: 0
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:657) ~[?:1.8.0_171]
at java.util.ArrayList.get(ArrayList.java:433) ~[?:1.8.0_171]
at com.ford.etis.runtime.apps.otx.utils.types.core.ListWrapper.get(ListWrapper.java:146) ~[com.ford.otx.common.apps.utils-40.8.21.jar:?]
at com.ford.etis.runtime.apps.otx.utils.types.core.ListVariable.getListItem(ListVariable.java:136) ~[com.ford.otx.common.apps.utils-40.8.21.jar:?]
at otxcontainer.G2232623.GetVehicleNodeInfo(G2232623.java:7838) [G2232623:?]
at otxcontainer.G2232623.access$1600(G2232623.java:90) [G2232623:?]
at otxcontainer.G2232623$10.run(G2232623.java:17770) [G2232623:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_171]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_171]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
2022-04-02T07:24:17,175 INFO class otxcontainer.G2232623.authorLogs - ****EXCEPTIONHANDLER****
2022-04-02T07:24:17,175 WARN types.core.GuardedFordEtisRuntimeException - GetExceptionQualifier on for Exception class that is not child of OTXExceptionTerm. Returning empty string.
2022-04-02T07:24:17,190 WARN types.core.GuardedFordEtisRuntimeException - GetExceptionText called on Exception class that is not child of OTXExceptionTerm. Returning empty string.
2022-04-02T07:24:17,191 INFO class otxcontainer.G2232623.authorLogs - Procedure name = GetVehicleNodeInfo - Exception qualifier = GetVehicleNodeInfo - Exception text = Unknown Error
2022-04-02T07:24:17,233 ERROR otxcontainer.G2232623 - Error in application, message was: java.lang.RuntimeException: java.lang.IllegalStateException: Unknown protocol: fordetis
com.ford.otx.command.exception.FdrsRuntimeException: java.lang.RuntimeException: java.lang.IllegalStateException: Unknown protocol: fordetis
at com.ford.etis.runtime.apps.otx.utils.ParallelExecutor.waitForAllToComplete(ParallelExecutor.java:119) ~[com.ford.otx.common.apps.utils-40.8.21.jar:?]
at com.ford.etis.runtime.apps.otx.utils.ParallelExecutor.waitForAllToComplete(ParallelExecutor.java:85) ~[com.ford.otx.common.apps.utils-40.8.21.jar:?]
at otxcontainer.G2232623.GetVehicleNodeInfoProcess(G2232623.java:17823) [G2232623:?]
at otxcontainer.G2232623.OTXAppFlowControl(G2232623.java:25235) [G2232623:?]
at otxcontainer.G2232623.main(G2232623.java:881) [G2232623:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication.startApp(BaseApplication.java:319) [com.ford.otx.apps.otx-72.16.33.jar:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication.access$000(BaseApplication.java:106) [com.ford.otx.apps.otx-72.16.33.jar:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication$1.run(BaseApplication.java:254) [com.ford.otx.apps.otx-72.16.33.jar:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: Unknown protocol: fordetis
at otxcontainer.G2232623$9.run(G2232623.java:17723) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_171]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_171]
... 1 more
Caused by: java.lang.IllegalStateException: Unknown protocol: fordetis
at org.apache.felix.framework.URLHandlersStreamHandlerProxy.toExternalForm(URLHandlersStreamHandlerProxy.java:482) ~[?:?]
at org.apache.felix.framework.URLHandlersStreamHandlerProxy.toExternalForm(URLHandlersStreamHandlerProxy.java:474) ~[?:?]
at java.net.URL.toExternalForm(URL.java:929) ~[?:1.8.0_171]
at java.net.URL.toString(URL.java:915) ~[?:1.8.0_171]
at java.lang.ClassLoader.defineClassSourceLocation(ClassLoader.java:678) ~[?:1.8.0_171]
at java.lang.ClassLoader.defineClass(ClassLoader.java:762) ~[?:1.8.0_171]
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClass(BundleWiringImpl.java:2370) ~[?:?]
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2154) ~[?:?]
at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1542) ~[?:?]
at org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:79) ~[?:?]
at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2018) ~[?:?]
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_171]
at otxcontainer.G2232623.BargraphDisplay(G2232623.java:12252) ~[?:?]
at otxcontainer.G2232623.access$400(G2232623.java:90) ~[?:?]
at otxcontainer.G2232623$9.run(G2232623.java:17695) ~[?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_171]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_171]
... 1 more
2022-04-02T07:24:17,243 INFO class otxcontainer.G2232623.authorLogs - ****EXCEPTIONHANDLER****
2022-04-02T07:24:17,243 WARN types.core.GuardedFordEtisRuntimeException - GetExceptionQualifier on for Exception class that is not child of OTXExceptionTerm. Returning empty string.
2022-04-02T07:24:17,257 WARN types.core.GuardedFordEtisRuntimeException - GetExceptionText called on Exception class that is not child of OTXExceptionTerm. Returning empty string.
2022-04-02T07:24:17,259 INFO class otxcontainer.G2232623.authorLogs - Procedure name = GetVehicleNodeInfoProcess - Exception qualifier = GetVehicleNodeInfoProcess - Exception text = Unknown Error
2022-04-02T07:24:17,259 ERROR otxcontainer.G2232623 - Error in application, message was: Qualifier: GetVehicleNodeInfoProcess text: Unknown Error
com.ford.etis.runtime.apps.otx.utils.exceptions.UserExceptionLiteral: Qualifier: GetVehicleNodeInfoProcess text: Unknown Error
at otxcontainer.G2232623.ExceptionHandler(G2232623.java:25716) ~[G2232623:?]
at otxcontainer.G2232623.GetVehicleNodeInfoProcess(G2232623.java:17845) ~[G2232623:?]
at otxcontainer.G2232623.OTXAppFlowControl(G2232623.java:25235) [G2232623:?]
at otxcontainer.G2232623.main(G2232623.java:881) [G2232623:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication.startApp(BaseApplication.java:319) [com.ford.otx.apps.otx-72.16.33.jar:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication.access$000(BaseApplication.java:106) [com.ford.otx.apps.otx-72.16.33.jar:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication$1.run(BaseApplication.java:254) [com.ford.otx.apps.otx-72.16.33.jar:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
2022-04-02T07:24:17,276 INFO class otxcontainer.G2232623.authorLogs - ****EXCEPTIONHANDLER****
2022-04-02T07:24:17,276 INFO class otxcontainer.G2232623.authorLogs - Procedure name = OTXAppFlowControl - Exception qualifier = GetVehicleNodeInfoProcess - Exception text = Unknown Error
2022-04-02T07:24:17,276 ERROR otxcontainer.G2232623 - Error in application, message was: Qualifier: GetVehicleNodeInfoProcess text: Unknown Error
com.ford.etis.runtime.apps.otx.utils.exceptions.UserExceptionLiteral: Qualifier: GetVehicleNodeInfoProcess text: Unknown Error
at otxcontainer.G2232623.ExceptionHandler(G2232623.java:25627) ~[G2232623:?]
at otxcontainer.G2232623.OTXAppFlowControl(G2232623.java:25366) ~[G2232623:?]
at otxcontainer.G2232623.main(G2232623.java:881) [G2232623:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication.startApp(BaseApplication.java:319) [com.ford.otx.apps.otx-72.16.33.jar:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication.access$000(BaseApplication.java:106) [com.ford.otx.apps.otx-72.16.33.jar:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication$1.run(BaseApplication.java:254) [com.ford.otx.apps.otx-72.16.33.jar:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
2022-04-02T07:24:17,292 INFO class otxcontainer.G2232623.authorLogs - ****EXCEPTIONHANDLER****
2022-04-02T07:24:17,292 INFO class otxcontainer.G2232623.authorLogs - Procedure name = main - Exception qualifier = GetVehicleNodeInfoProcess - Exception text = Unknown Error
2022-04-02T07:24:17,308 INFO class otxcontainer.G2232623.authorLogs -

BEGIN ~~ ApplicationExitAndCleanUp
2022-04-02T07:24:19,644 INFO class otxcontainer.G2232623.authorLogs -

DSP DEBUG > Exit - Fail
2022-04-02T07:24:19,647 ERROR otxcontainer.G2232623 - Error in application, message was: null
java.lang.NullPointerException: null
at otxcontainer.G2232623.ApplicationExitAndCleanUp(G2232623.java:16851) [G2232623:?]
at otxcontainer.G2232623.ExceptionHandler(G2232623.java:25547) [G2232623:?]
at otxcontainer.G2232623.main(G2232623.java:957) [G2232623:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication.startApp(BaseApplication.java:319) [com.ford.otx.apps.otx-72.16.33.jar:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication.access$000(BaseApplication.java:106) [com.ford.otx.apps.otx-72.16.33.jar:?]
at com.ford.etis.runtime.apps.otx.core.BaseApplication$1.run(BaseApplication.java:254) [com.ford.otx.apps.otx-72.16.33.jar:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_171]
2022-04-02T07:24:19,677 INFO class otxcontainer.G2232623.authorLogs - Closing comms exception in procedure
2022-04-02T07:24:19,681 INFO class otxcontainer.G2232623.authorLogs -

***** DEBUG LOG RESULTS *****
BECM software update
Based on template version: 26
Exit - Fail
2022-04-02T07:24:19,681 INFO class otxcontainer.G2232623.authorLogs -
 

Shoebox72069

Well-known member
Joined
Dec 3, 2021
Threads
4
Messages
138
Reaction score
64
Location
MN
Vehicles
2021 F150 Powerboost Lariat
This is by far the most interesting part of this hot mess:

2022-04-02T07:24:17,140 INFO class otxcontainer.G2232623.authorLogs - No GIVIS response for: DE00
2022-04-02T07:24:17,141 INFO class otxcontainer.G2232623.authorLogs - Missing backup config data!! -- DE00
2022-04-02T07:24:17,141 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F18C = H388E21008000784
2022-04-02T07:24:17,141 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F113 = ML38-10B687-AD
2022-04-02T07:24:17,141 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F111 = ML38-14F092-AA
2022-04-02T07:24:17,141 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F163 = 04
2022-04-02T07:24:17,157 INFO class otxcontainer.G2232623.authorLogs - GIVIS CDL DID F15F = 08080001500444020000
2022-04-02T07:24:17,158 INFO class otxcontainer.G2232623.authorLogs - Number of config DIDs = 0
2022-04-02T07:24:17,158 ERROR otxcontainer.G2232623 - Error in application, message was: Index: 0, Size: 0

I've never PMI'ed or anything with this module. I've left it alone aside from trying to update. I'm not quite sure it's even safe to PMI.
 

JaHoova

Well-known member
Joined
Apr 13, 2021
Threads
0
Messages
80
Reaction score
63
Location
USA
Vehicles
2021 F-150 Supercrew XLT Powerboost
got past this, figured out i needed to click the little redownload button in FDRS.
… but then kept getting stopped at this…any ideas? Looks the the APIM. Tried resetting the module a bunch of times already.
F363FFE5-FBC2-4D39-BA08-25D05192778D.jpeg
When did you get this? Before you had to plug in USB to the APIM connector?
 

Sponsored


nicholsbradley

Well-known member
First Name
Bradley
Joined
Jan 1, 2021
Threads
5
Messages
220
Reaction score
109
Location
Louisiana
Vehicles
2021 Ford F150 Platinum
Occupation
Analyst
This truck and this process has been fighting me every inch of the way ?. Ill try the reinstall, in a few days when my Mongoose gets here. Amazon updated my delivery date from April 14th to April 6th! My FDRS 2 day license already expired. I’ll probably spring for the 1 month again. At this rate it probably would have been more cost effective to just buy the whole year, ill already be about $450 into license fees. ??? Ford should reimburse us all for this.
@Ford Motor Company
You can always take to a dealership now and save some money.
 

travbz24

Member
First Name
Travis
Joined
Mar 2, 2021
Threads
1
Messages
16
Reaction score
3
Location
Iowa
Vehicles
21 F150 Platinum Powerboost
Did the driver side module this morning. This APIM update was available but haven’t started. Maybe later today or this afternoon. I was updated all the way through BC and this is the first day this has popped up.

0DA94692-43B5-4E6D-BBA7-EBE8575F34F7.jpeg
What sync version/revision are you on?

What does the software update show when you hover over?
 

Whoskyle

Well-known member
First Name
Kyle
Joined
Jun 29, 2021
Threads
18
Messages
274
Reaction score
269
Location
AZ
Vehicles
2021 F-150 XLT
This truck and this process has been fighting me every inch of the way ?. Ill try the reinstall, in a few days when my Mongoose gets here. Amazon updated my delivery date from April 14th to April 6th! My FDRS 2 day license already expired. I’ll probably spring for the 1 month again. At this rate it probably would have been more cost effective to just buy the whole year, ill already be about $450 into license fees. ??? Ford should reimburse us all for this.
@Ford Motor Company
Someone posted a guy on another forum that has 30 day licenses for $50. Idk how reputable, but he swore by them
 

Ajzride

Well-known member
First Name
Alan
Joined
Jun 6, 2021
Threads
15
Messages
856
Reaction score
1,077
Location
Houston
Vehicles
21Mach-E / 65Mustang / 21PB 502A 157"
Occupation
C&A
Someone posted a guy on another forum that has 30 day licenses for $50. Idk how reputable, but he swore by them
I did get a 30 day from them after spending so much on the helm licenses. They work, but you have to give them remote control of your computer for about 3 minutes for them to install it. If you are like me and your laptop only does FDRS and nothing else, probably not a concern. If you are running FDRS on your primary laptop, probably be pretty wary of doing it that way.
Sponsored

 
 




Top