Finnish ST-Line X owner

[geno]

First try at updating the sound settings was unsuccessful. A few reasons i noticed later.
- Was a bit too eager on the changes so a bit too much at once
- Some settings i tried are not available on the 2020 but only later on like the ambient lighting, newer b&o, some of the climate menu options, the dab l-bands compatibility toward the dab+ multiplex block configuration.
- Seems like different modules activate differently? Have to read up on the forscan tutorial more in detail what is the case. If PCM needs to activcate it or not.

But yeah, i'll try once again with more modest changes once i get the license renewed to forscan, so more study, tutorialcheck, update and i'll give it another go. Also did a DTC check if any serious errors but should be fine and i have backup of original and know the latest working code so it's easy to revert back.

EDIT: Reading the ForScan tutorial through i realised one of my mistakes, in addition to trying to update too much and some wrong unavailable features. And that was that i only reset one of two modules. But, i'll charge the laptop, update the license, look more carefully through the codes and try again in the weekend. Taking it a small step by step approach instead of being in too much of a rush.

[geno]

Update on this.

So.. today i did a new check on my as built codes and updated them + this time also resboot those modules i changed.

apim:
- the surround sound hexcode
- the climate setting to show on screen

bcm:
- the rear light DRLs to be on as default

acm:
- the surround speaker setting to go with apim change

result: i see the stereo/surround option in the sound menu but with fader to rear it is still very faint in the rear so speakers not working as they are supposed to. i tried also to reboot the DSP and unplug/replug amp but it didn't help.

climate visible in menu but i don't have dual climate and it's showing in menu.

bcm update worked and have rear drls like i wanted.

questions:
am i missing something? do i need to reboot something else also than the 3 modules i modified as built data on?
i still have faint rear speakers and as if the amp is not working. does this indicate that it is broken, are there other settings in forscan that activate it, i checked the fuses but they seem fine and sound does go to the 5 rear ones but very faint?
Is it now a sign that the amp is broken and should be replaced?

Feels unprecedented that you pay for and have a 10 speaker system and can hear only half and it's driving me nuts.

i hear a pop from the rear speakers after 5 mins from the car shutting down. ground error?

anyone had similar and got it fixed? pretty much out of ideas atm and think it could be a broken amp but not sure since of the pop and faint sound from them. so maybe still a as built code setting that can be set that i don't know of yet?

EDIT: Is it possible to update firmware with extended license on ForScan? Or could there be a wiring issue, like the subwoofer plug or similar that causes my rear speaker issue? Or can it be simply broken from the start and hence hasn't worked. I also did the diagnostic for the sound and it's clearly not giving as strong signal from rear as from front.

[geno]

found this on the F150 forum:
"SSM 51663 2021-2023 F-150/Expedition - Pop Noise And/Or Static In Speakers At Start Up
2021-2023 F-150/Expedition may exhibit a pop noise and/or static in the speakers at start up that cannot be turned down or off using the audio system controls. To correct the condition, reprogram the audio digital signal processing module (DSP) to the latest software level using the Ford Diagnosis and Repair System (FDRS) diagnostic scan tool. For claiming, use causal part 18B849 and applicable labor operations in Section 10 of the Service Labor Time Standards (SLTS) Manual."

is there some similar DSP update for the Puma?

[robgee]

Problem is without access to to Ford ETIS anymore you cannot tell . With Forscan extended license you can apply firmware updates to modules and check if there are any updates.

[geno]

Yeah. I'm starting to think it's a DSP update issue. I saw someone used the OTA to get ford powerup updatepackages, but had to submit a couple times feedback through the screen on the wireless connection to speed it up.
I tried to look once again in ForScan for module versions and any update option but couldn't find any on the 2.3.63 version of ForScan. The diagnostics doesn't show it either.
How do you check for module updates in ForScan?
I'll see tomorrow or sunday if any systemupdates are available over sync wifi.

Meanwhile i don't really know what to do about the issue.

[geno]

Problem is without access to to Ford ETIS anymore you cannot tell . With Forscan extended license you can apply firmware updates to modules and check if there are any updates.

Checked some info on Cyanlabs. I have the extended license trial version but do i need the paid extended to be able to use the 2.4.15 beta ForScan for updating the DSP module? Or is it possible to use with any extended license? Could give it a try tomorrow. See if i could find an update for the module since the DSP seems to be between the speakers and everything else. And considering other vehicles got a DSP update toward the popping sound.

EDIT: issue being i have 2.3.63 free extended trial which doesn't seem to allow checking the modules for updates. Didn't know there was a beta for that parallell to the free versions.

[robgee]

If I remember correctly you need the beta version, usually if you ask someone at Cyanlabs they will point you to a link

[geno]

Almost there now, it seems. I saw again a forum post about how somebody had the same issue with the B&O and only solution was to get the DSP module updated.
Today i had the F13 maps on the usbstick so i had to get that out of the way first.

I installed the ForScan 2.4.15 beta to my laptops Forscan extended license trial version, then i just now checked the modules and yes, it does now show the module firmware upgrade options. I took a backup of PCM, APIM, BodyCM, ACM and DSP as built modules. But when i tried after that to check the DSP module update it did not get anything on "download". Then in the Log it says updates "Not available under extended license trial"

So i'll get the 1-year extended license (12€ or £10 for a year?) so i can unlock the updates.

The DSP version i have atm is FA1T-14C591-AA, but more when i have a chance to try the update. Must be a newer version that fixes this issue and itching to find out.

EDIT: I got the 1-year license, then went to try the DSP update but didn't have the nerve to complete it. On download it found only 2/3 IDs for the DSP and no newer versions. But on choosing "Test SBL" (between download and program buttons) it gave me a warning my OBD 2 ELM327 500k usb cableplug wouldn't be efficient enough and 50/50 chance of breaking module if i tried to update the DSP. I'll have to see if i can get a better one somewhere. Just to make sure, since idk if this message is one of those "oh i get them all the time and still works" or "you did the James May lighter on the Nuke but this time it wasn't damp".

EDIT 2: Yeah, not risking it. I'll get a proper OBDLink EX instead of risking using my cheap obd2 usb cable with manual switch. I don't want to hurt the Pumas Brains. :\

[robgee]

I would go from something from the links from the forscan page .

I have a OBDLink EX USb and have never had any issues with it

[geno]

Yeah, exactly. Learning on the go as i get closer to getting the update done. But i'm also relieved since i now know i can do it myself with the software.
My doubt of using the cheap elm327 speed switch cable was good because i should definately not use a bad cable for updates. Plus when i get more familiar with the software i can rely on a good one and i guess Vlinker and OBDLink EX are the ones that works.
I saw a local reseller has it for 80€ (around £66) but i happen to be more or less broke atm so i'll see when i get to order it. But there's hope now to get the needed updates done.