Jump to content

JTEX

Hybrid Member
  • Posts

    23
  • Joined

  • Last visited

Posts posted by JTEX

  1. On 4/30/2022 at 10:06 AM, GeR2 said:

    I noticed yesterday that there was a new update for the FordPass app.  I didn't notice anything different.  Anyone else find something new?

    Same here.  Thankfully I have yet to find any regressions.   One minor improvement seems to be you do not have to pull down 5 times to get it to really refresh on charge state/range.  Now once or twice will do it.  Under the account icon you can now access via the app (versus logging in via a browser) “connected services,” but I believe that is for hot spot equipment vehicles and perhaps pure EVs.

  2. On 4/28/2022 at 1:49 PM, cr08 said:

     

    Not stock, no. I don't believe any of the C-Max model years came with the option for an LTE/cellular antenna integrated into the rooftop antenna combo. May even be the same with the Fusion. I don't think any of the 3G modem parts had the option for an external antenna. Mine didn't when I pulled it. Even the official upgrade instructions just has an separate antenna they have you attach with adhesive tape/velcro to the nearest trim piece.

     

    That said, other Ford models do have this option with the rooftop antenna including all the different options and they usually have an antenna splitter harness to break out the different feeds (AM/FM, Sirius, GPS, and LTE). It's something that is on the potential agenda to add to my 2013 at some point down the road.

    Whether using the official Ford “stick on” flat 4G antenna used in the official upgrade, the one available on Amazon (that yields a harmless DTC), or the one you can buy from Ford for $35ish (that is detailed in the F150 forum about this and must be screwed/grounded in) you will find the as a rule (at least I have found this to be the case) your 4G TCU reception and responsiveness is dramatically better even if the antenna is not on the roof, but rather hidden someplace under the back window ?.   Unlike cell phones that have to successfully manage lots of packets of data with sufficient reliability to assure normal sounding voices, the TCU communicates very simple encrypted data sets via 4G back and forth with “Fordpass central” in the cloud (your app talks to Fordpass in the cloud which then talks to your car . . .the smartphone Fordpass app doesn’t communicate directly with your vehicle).  Indeed 4G for this purpose is a huge improvement.

  3. On 4/26/2022 at 10:08 PM, cr08 said:

     

    You might want to try having ForScan re-scan the modules without using a saved profile if you haven't already. If that doesn't do it, you may want to see if you can track down the latest beta build. Mine still gives me the firmware update option after this.

    ForScan for me wasn't even aware that UN was available or a current version. It still assumes UM is the latest available. In reality I don't think it cares and should not be hiding the firmware update function even if you are current because these modules can usually be downgraded without issue.

    Thanks . . .good call.  I will try as you suggested over the weekend and report back.

  4. On 4/25/2022 at 10:36 AM, bookemdano said:

    Did the upgrade last night. Also seeing no change whatsoever in FordPass. I am not seeing anything missing in the JSON data either (although quite a bit of it is not applicable/incorrect). So that's sort of disappointing. But maybe Ford needs to make changes on their end before any improvement is seen on our side.

     

    Good news is that there is at least no regression from what I can tell. Everything that worked before is still working now.

    I am now also at “-UN” level on my FFE’s “H” series TCU.   Same functionality and thankfully no regressions.   Hopefully more improvements are still coming in the app and the backend over the summer.

     

    BTW interesting Forscan behavior (that you folks may already be aware of) in that after the update to the UN level the option to make any other firmware changes to the TCU disappeared, but the ability to edit the “754 . . “ remained (I made no changes).   On many of the other modules the firmware update option remains available . . . So apparently Forscan takes away the firmware update option (at least in the beta version I am using) once you are “current” per Ford and reverting to a prior version does not seem to be an available option.

  5.  

    On 4/15/2022 at 12:44 AM, oldbeyondmeasure said:

    @bookemdano's approach requires a laptop computer running Windows, a program called FORScan that you can use for free for some period of time, and a $70 or so piece of hardware that you use to connect the laptop to your car's OBD port (https://www.obdlink.com/products/obdlink-ex/?ref=forscan). I would start reading on page 14 of this topic with @bookemdano's post at Posted April 3, 2022 at 06:40 PM. There is a sequence of posts about modifying data stored in the car in a way that may fix your problem with lock/unlock/remote start. 

    When I had my 4G modem installed by a Ford dealer in January, it took five days before I could activate my car on FordPass and not all of the FordPass features worked right away. My sense is that things have improved since then. But FORScan can help diagnose the problem and potentially fix it. 

     

     

    As someone that has been successful with the DIY 3G -> 4G update (thanks to lots of help from folks on this and the related FFE forum) it seems worth sharing that:

     

    1) to be successful you need to follow all the steps/upgrades/configurations required using the proper tools/software  . . .(like having an “H” TCU, installing the “UM” update, and the revelation from one team member that having the correct data in each and every line of the TCU configuration mattered . . .which BTW was a huge turning point.)

     

    2) just as every step is important for DIY the same applies to the dealer techs and we all know that now and then a few don’t necessarily “sweat the details” so just because one had the upgrade done at the dealer is sadly not a guarantee you will have a successful upgrade (unfortunate recent example: I found that nearly all of the plastic insert “nuts” for the screws that hold my FFE’s air flow panel . . .that must be removed for oil changes. . .are stripped because the a few techs are using power drivers that are not properly torque limited for such a use)

     

    3) using the “connected car” web site helps to accelerate the toggle for authorization  . . .including making it easy and fast to go back and forth, re-enable after a SYNC reset, etc.

     

  6. On 4/8/2022 at 11:38 PM, cr08 said:

    Crossing fingers maybe we see something with the EV Driving data soon? It did originally have the wording about enabling the connected services in vehicle but now it just says there's no previous trip events to view. I did have a couple drives today but nothing recorded outside of the 'Journey' data.

     

    Seems like Ford may be finally getting on top of things. Excited to see all these functions start populating again.

     

    EDIT: And just as a reminder, this is on a 2013 that wasn't originally on the CSP, and DIY'd to boot. Really happy to see that it has basically been fully functioning to the extent that everyone else so far has had functionality show up, both in the 'supported' model years as well as the official dealer installed upgrades.

    What I just posted in the FFE forum may benefit the Cmax team regarding driving data:

     

    I tried Journeys a few weeks back and while it was interesting the value judgements it was making on my driving style was too much to handle so since then I have always had Journeys off, but I do get lots of fun facts after each drive under Driving Data/My Journeys/EV Data/My EV Driving . . .so I have been churning through the “what may be different?” for you folks.

     

    Each time I have reset SYNC for any reason once it comes back online I have a checklist of my prefs I set including: connect to my home wifi for SYNC updates, set Home and Work favorites, pair both cell phones, turn off CarPlay, turn off charge light, and then this is what you folks may want to check. . . .   under apps in SYNC I download the SYNC Fordpass app and once it becomes alive (sometimes it take a few minutes) in SYNC you are asked to give it permissions,  I give it all the permissions, then I give all permissions to “all apps” and the “app catalog”.  This is done all in SYNC.   Also on my iPhone I have given the iOS app Fordpass “always” location rights.  When driving my iPhone is also always connected to the car via USB and Bluetooth.

     

    I bring up all of the above because perhaps while I have Journeys off giving both the related SYNC Fordpass app all the rights and the iOS Fordpass app location services rights/permissions in some way allows the required data to get to the Fordpass back end database to then be reported in the smartphone Fordpass app inside “Driving Data.”   So you folks may want to mess with that if you don’t have it set the same way.

     

    For overall functionality of Fordpass now on my DIY FFE TCU swap I am “all good” for all functions.   Indeed I am now in better shape than with MFM and have the benefits of 4G speed. The key “must do’s” seem to be:

     

    1) “H” TCU

    2) “-UM” firmware, calibration, etc. for that H TCU using Forscan’s latest beta with a top quality USB OBE cable

    3) Configuring ALL the lines of your TCU to be absolutely identical to the known good dealer installed configuration (in my case for the FFE).

    4) being in a reasonably good AT&T cell reception area

    5) using the connected car app to enable the car

    6) doing at least one SYNC reset

    7) giving it a few days for the FordPass back end to update

     . . . .and having the lastest rev of the Fordpass app on your smart phone

     

    Perhaps to the above list the “permissions” on Fordpass in SYNC, etc. also matter, but we will need one or two other team members to validate.

  7. After nearly 24 hours AT&T fixed their regional outage so my FFE is now working on Fordpass again.   Even the charge notification now works (that’s how I knew the FFE was back online: I received a charge notification).   

     

    So the lesson is that if you have been successful updating your vehicle to 4G (so most Fordpass functions work for you including lock, unlock, start, charge scheduling, etc.) and suddenly the Fordpass interactive functions are no longer working then the first thing to check is to determine if your vehicle is for some reason no longer connected to the ATT 4G network.

     

    your vehicle functions<->your vehicle’sTCU & antenna<->AT&T 4G network<->Ford’s Fordpass “servers”<->Fordpass app on your device

  8. On 4/5/2022 at 7:03 AM, JTEX said:

    Good intel . . .thank you!  

     

    On the FFE 4G forum another user is having the same issue so perhaps this is just backend issues for iOS users.

    May have nothing to do with the platform . . .I just checked and AT&T 4G cell service is down (checked with 3 mobile devices) in my area so at least for now it appears the root cause is my FFE not being able to make contact with the Fordpass backend.

  9. On 4/5/2022 at 6:32 AM, cr08 said:

    Looking good on my Android phone this morning, no issues connectivity-wise.

     

    In fact, I got the charge complete notification which is the first time I've gotten that so far! No charge logs or anything I can find in the app just yet.

     

    I can also confirm the Departure Times worked as expected. Set for 6:30 this morning and somewhere around 5:30-5:45 it started doing stuff, my EVSE power usage started and held at the expected ~1200w til shortly after 6:30 and the HVAC blower was clearly going.

    Good intel . . .thank you!  

     

    On the FFE 4G forum another user is having the same issue so perhaps this is just backend issues for iOS users.

  10. Just in case other forum members are experiencing the same  . .. so you know it is not your setup . . .since last evening the Fordpass app (on iOS) is not getting any response from the backend for nearly all key actions including lock/unlock, charge state, charge schedule, etc.   Top of my app says it hasn’t been updated in 16 hours.  The bottom banner says “waiting to charge” with the time stamp for last night ?

     

    Things I have tried:

    -force close the app

    -reset the iPhone

    -delete Fordpass, reset the iPhone, download fresh Fordpass, and login

     

    Some historical stuff remains (like going into Journeys I can see EV data from a brief drive yesterday morning), but anything interactive to the backend is down (like going to charge settings/setup preferred . . . ./ you get a hard red error banner at the top after “begin setup”)

  11. On 4/2/2022 at 4:41 PM, JTEX said:

    i can now confirm those other blocks make a major difference as after just changing on my 2020 FFE to the identical blocks of ALL of the TCU blocks as shared from that was done by a Ford dealer I now have ability to set “Preferred Charge Times” (formerly called “Value Charge in MFM and still in SYNC).  So every bit matters ?

     

    Charge level notification is yet to work, but the banner now at the bottom seems sufficient.

     

    Note after making these changes to the TCU, I reset the TCU & and the APIM.  Then I did a SYNC reset.

     

    So now all good so far on my FFE as long as the 12V battery issue doesn’t come up again.

     

    I did not want to edit the above since it is all correct, BUT I learned the “preferred charge times” may be a bit buggy on the back end.  

     

    BACKGROUND: A key “ahah!” when I got this to work after fixing all those other blocks was that finally my home location appeared in previous locations so I was finally able to make the settings (name my location, pick two sets of times, etc.).  Once that was done it did supersede the ValueCharge settings in Sync (i know this because in SYNC I set the start time to 12:01am whereas in the app it does not allow minutes so 12:00am).   

     

    BUG APPEARS:  Later on I decided I wanted to change the second of the two preferred charge times, but it will not allow one to edit.   So I figured I would delete the location and start over.  Big mistake as then I could not get the location to return.   So next step was to figure out how I can prompt the system to get that location to return.

     

    SOLUTION: It is a bit wonky from a user experience perspective, but if you have lost your preferred charge location to get it to return you must complete a charge now (seemed obvious so I had already done that), BUT additionally disconnect from the EV charger, start the car, drive a foot forward and back, turn off car.   The location will now appear and you can redo your preferred charge settings and also toggle between a preferred time and charge now just like with MFM.

     

    BTW:  Charge logs now works too.

  12. On 4/2/2022 at 1:41 PM, cr08 said:

     

    This is 100% where mine is at as well. I just went through and compared notes on what I see with my app vs what you mentioned here and it's all identical. The assumption so far from multiple people is it is all on Ford's end and they still need to get FordPass fully functioning with these new features for us ( @bookemdano and I had a brief discussion on this stuff with F150chief over on the CyanLabs boards and that seems to be his thoughts as well. Did get some new and useful info on that front which I'll post below.). So it's largely a waiting game.

     

    Once again thanks goes out to F150chief over at CyanLabs for providing some more useful knowledge concerning these TCU's and the AsBuilt configs. You can read the whole thread as it is currently here: TCU HJ5T Asbuilt Discussion - Ford / AsBuilt Configuration - CyanLabs Official Community

    We had originally assumed the 754-03-xx blocks were just garbage or storage bits. But apparently these are additional configuration options to tell the TCU what various bits of data to pull from the vehicle and send back to Ford. 7D indicates the data should be pulled and sent back. 7C ignores that bit of data. Unfortunately there's no insight to what each individual bit corresponds to. Based on the discussion, it seems like it is harmless just to set everything to 7D to enable ALL THE THINGS and send it to Ford. It is still then up to them to populate and display this data on their end in the app. I have went ahead on mine and did just this and enabled all those bits. No new data just yet but as always I'll keep you posted if anything changes on this front.

     

    Just as a quick FYI on the AsBuilt stuff that I've briefly mentioned here previously: With ForScan, the last two bits in each individual block are checksum bits. So in the case of these changes to the 754-03-xx blocks, they won't show or even be able to be set to 7D. You can enter anything in these bits and ForScan will just recalculate what should be there when you go to write it to the module.

    i can now confirm those other blocks make a major difference as after just changing on my 2020 FFE to the identical blocks of ALL of the TCU blocks as shared from that was done by a Ford dealer I now have ability to set “Preferred Charge Times” (formerly called “Value Charge in MFM and still in SYNC).  So every bit matters ?

     

    Charge level notification is yet to work, but the banner now at the bottom seems sufficient.

     

    Note after making these changes to the TCU, I reset the TCU & and the APIM.  Then I did a SYNC reset.

     

    So now all good so far on my FFE as long as the 12V battery issue doesn’t come up again.

  13. On 4/2/2022 at 2:27 AM, cr08 said:

    A bit off topic, but this thread seemed apt to ask this considering a number of you have access and are comfortable with using ForScan.

     

    Those of you who have 2016+ models, especially with the full front/rear parking sensor and parallel park assist features equipped, I wonder if I could bother you to post the PAM (Parking Aid Module) part #'s as well as calibration levels? Also interested if ForScan provides an AsBuilt config option for the PAM for you.

     

    I've been digging back into the parking stuff with the Sync 3 retrofit on my '13. One feature I've been trying to add is the 'overhead sensor' display (example image below) but potentially a roadblock I may be dealing with is ForScan is not providing an option to modify the PAM AsBuilt which may have options that need to be changed. So far the parallel parking feature seems to work, although it's very rare for me to have the opportunity to use it here. I've only ever been able to mess with it once since my retrofit.

    image.jpg

    Had that complete feature set in my 2015 Ford Fusion Hybrid Titanium, but alas not on my 2020 FFE even though it is a fully loaded “Titanium” . .. sadly just another example of the “de-contenting” of the 2020 FFE..  I mention this because perhaps someone on the Fusion Hybrid forum may be able to provide what you need.

  14. On 4/1/2022 at 3:01 PM, cr08 said:

     

    I'll have to pay closer attention to mine and see if that's the same. I HAVE been fiddling with the app and refreshing it a lot and that also seems to trigger the vehicle to wake up and start pulling power briefly from the EVSE. Here's my power usage graph since Mar 27th:

     

    399444929_Screenshot2022-04-01155951.thumb.png.65d87bcf6539e627a5e04c99fb5722d1.png

     

    I'll try not to mess with the app and see what shows up going forward.

     

    EDIT: Probably a better link since the forum likes resizing these: https://imgur.com/zrHPqXR

     

    Great graph!

     

    This morning when I went to the car and opened the door coincidentally I found the dreaded “system off to save battery” message which is the second time that has happened since installing the 4G TCU.

     

    I took delivery of my 2020 FFE in late November of 2019 and I suspect it was likely built a few months before so to be fair I am getting reasonably close to the typical 3-4 year lead acid cell end of life.  I decided to replace the 12V battery.

     

    Scary bit of intel: all of the area Ford dealers that particular replacement battery back ordered.  IMHO not a good sign.  But the parts guy told me that AutoZone carries the identical battery in the “Duralast” brand and recommended I check around local stores.   So I ended up with the Duralast Gold version and indeed everything other than the label is identical to the Motorcraft unit including vent port, etc.

     

    It was priced a bit higher than the Motorcraft, but is rated about 100 CCA higher.  Standard 3 year warranty.

     

    Before installing it I put my tester on it and it read 100%

     

    Now I have a fresh start point so if the “system off to save battery”  happens again in the near future after a standard overnight Value Charge than (at least on my FFE) I have a 12V power drain issue post 4G TCU install.

  15. With regard to notifications, app status, etc. I just posted in the FFE forum on this 4G upgrade:

     

    My Fordpass app screens are identical (to those posted in the FFE forum) and I get a screen notification within the Fordpass app that is a banner within the app that appears on the bottom.   This morning for example it reads: “ Reached 100% charge” then shows the approximate time it was finished.  To the right in that banner it has a “Details” button.  When I click on Details the next screen usually has a “Fordpass timed out” at the top in red, shows the charge range, and then a bunch of empty rows for other aspects.

     

    I am hoping that when the “Charge Level Notification” button starts working (versus “Loading” circle running for many minutes without success” that it will give us an app push notification & an email (like MFM did) when charge is completed, but at least now know charge level via the app is progress.

     

    Tops on my list of function fixes will be the arrival of charge parameters/timing control via the app (what was called “Value Charge” in MFM).   Once that arrives and given the other progress my needs will be met.

     

    Some concerns:

    - ANNOYING -the current Fordpass app (or the backend) is very buggy (so hard to believe it passed thorough sufficient testing).   The best example is when you start the app in the morning on your phone after a charge was likely completed and click on “vehicle” then the screen (nor lower banner) will not show the car is charged.  Then you do the classic “update” pull down move at the top and the app will charge from “updated 7 hours ago” to “updated just now”, but will still not show the battery has been charged.  Then you pull down yet again for another update and it will show the actual fully charged info.   Yes, I do have background app refresh on in iOS for Fordpass and I am on a fast low latency network.   This is purely a buggy app thing or very sluggish backend at Ford.

    - VERY WORRIED ABOUT- Systems wise the app/Ford backend/car integration is likely very similar to typical IOT devices wherein the Fordpass app is never talking directly to the car, but rather the app is only talking with backend servers at Ford and those servers’ APIs  in turn talk to the car.   So the 4G modem TCU at steady state when nothing is happening should be just basically listening in a very low power mode and only pulling more power to transmit when either the backend tells it “hey wake up and send us the following data . . .. or do the following (as in unlock the door because the servers have picked up the app asking for such)“ or something happens with the car (as in battery fully charged event) so the car then proactively calls on the TCU to transmit to send data to the Ford servers.  For both cell data traffic management and power consumption this is the way it should work ?   But as shared in another post lately the dialogue between the TCU and the car seems very “chatty” as I can be doing chores in the garage and hear the relay clamp under the hood a few times each hour even though the car is fully charged, plugged in, and I am not asking the vehicle to do anything via the app.   So either the backend is frequently asking the car for info or the car is frequently on its own wanting to send the backend data.  The problem with this is potential major drain impact to the 12v battery.   So one parks your FFE or CMax plug in at the airport for a few days and do you come back to a dead 12volt battery?     Hopefully the “system off to save the battery” logic will have intervened, but???   There was chatter in one of the other forums about some dealers claiming the upgrade program was on hold . . . If that is true (perhaps was just particular dealer talk) it could be because the beyond the concern with the app not being quite ready yet there are unexpected adverse event issues ?.   Let’s hope not.

  16. On 3/29/2022 at 2:56 AM, SlaV77 said:

    Hello, I have a request, can anyone check with Forscan what software you have in TCU after updating on the Ford website from 3g to 4g?
    You need to connect the car to the computer, scan (1) Then switch to the Configuration tab (2) and read the configuration of the TCU module (3) I'm interested in calibration and strategy. If you could take a picture like I did and send it to me please.

    Bez tytułu.jpg

    I will likely not be able to get to pull the exact information until much later today (US time) or tomorrow, but from everything learned on this forum (and the FFE sister forum) what Ford dealers are installing (and I also purchased used that worked) in the 3G to 4G upgrades are TCUs that have part numbers beginning with “H” (so just have the one LTE antenna connection . . . Not also with the hotspot antenna connection).  I was unsuccessful trying it with a “K” TCU.   Additionally with such a “H” TCU the working calibration and strategy as installed by Ford dealers and successful DIYs on this forum ends in “UM.”   Perhaps other variants with later model TCUs, calibrations, etc. could be made to work, but I have yet to pick up both the “how to” and successful project results..

     

     

  17. BIG progress delivered via the latest release of FordPass for iOS today (v4.13.0):

     

    - banner now appears at bottom in either Home or Vehicle screen that summaries results of most recent charge.  It has a details button, but so far clicking on that presents a momentary “Fordpass is unavailable” at the top of the modal with only the estimated distance being available in that modal.

    - in Vehicle/Driving data even if you don’t have journeys turned on you do see an active link that takes you to a working driving monthly summary and

    - under EV data more detail on recent drives

     

    On the Vehicles screen the charge settings button no longer gives a red error but the setting routine for preferred charge times (I suspect this is what was called “value charge” in MFM) doesn’t do anything because the “locations” still does not work.

     

    Charge level notification still has the error after the long progress error.

     

    So awesome progress for the Fordpass development team.   It seems we are very close to getting back control via the Fordpass of what was called in MFM Value Charge (and still is called that in Sync)

  18. As of today the Fordpass app on iOS has gone back to its multiple minute “loading” spinning wheel if one attempts to turn on/save charge notifications via the app.  After the long time has passed it says at the top “something has gone wrong. Please try again”. When you try again to save the same things happens.

     

    Whatever the case . . . current accurate charge state remains shown in the app (a great thing!), but notifications are yet to come.

  19. Interesting change of behavior on the Fordpass iOS app today:  Previously when you would attempt to activate the charge level notification there were many seconds of waiting before it gave up and you had to “discard” your settings attempt.   As of today when you click on “Charge level notification” a “something’s not right, please try again” pops nearly instantly followed by (nearly instantly as well)  it jumping back to the prior screen.  Obviously stuff being changed in the background.   I am fine with waiting on anything beyond what have achieved together so far in that I have value charge back (via Sync) and I can remotely see charge status (the key 4G win).   Just hope we don’t experience any regressions in functionality as they work all of this out.   If/when the addition of app management of VC arrives may plan is to call this a full success.

  20. On 3/23/2022 at 3:17 PM, cr08 said:

    One weird and funny thing I noticed happening and totally expected given how Value Charge was a bit hit or miss on MFM:

     

    If I do a refresh in FordPass, even with VC set or even when the battery is full and has sat, it'll start trying to charge again. Got my EVSE plugged into a smart plug directly now and it's been fine (knock on wood) and I reliably see the power usage jump to ~1200w when I do this.

    I can confirm the same behavior on my 2020 FFE since doing the “H” TCU with UM profile DIY update.  

     

    Past behavior with the 3G MFM setup was that when I would plug in the car in the garage during mid day (even though VC was set to go at 12:01am the next morning) you would hear a relay clamping down under the hood and sometimes the amp meter on my level 2 charger would show a few amps being drawn for less than a minute.  If I changed by VC settings when MFM was still working I would also hear that noise as the profile would change.

     

    Since completing the 4G upgrade it appears that every time Fordpass has ANY dialogue with the car one hears that same relay (or at least one that sounds the same in the same area under the hood).   It is very easy to reproduce by standing in that area of the car when locking or unlocking the doors using the Fordpass app in that before the doors lock or unlock you hear that relay and then after that noise the doors lock or unlock.  I am also able to reproduce it just by pulling down to update on the Fordpass screen that shows charge level and gasoline fill level.

     

    Since my DIY upgrade this weekend I can set and toggle on/off VC via SYNC and the car will act accordingly.  The Fordpass app will show charging underway and a completed charge.   No notifications yet and as some have mentioned the set button gets rejected anyway.   Lock/unlock works as does start.   I can see oil life.

     

    No control via the app of value charge, but I am happy with the progress and plan to wait patiently for additional functions to appear as Ford does more homework on this.

×
×
  • Create New...