# Issue with XM preset slider

**URL:** <https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034>\
**Category:** CyanLabs Update Support\
**Tags:** oem, nav, na, APIM, SYNC3, Syn3Updater, pre-my20\
**Created:** [11 February 2025 13:51 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034 "2025-02-11T13:51:14Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![jon.nielsen](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/jon.nielsen/32/15458_2.png) [@jon.nielsen](https://community.cyanlabs.net/u/jon.nielsen)\
**Post date:** [22 March 2025 12:54 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/21 "2025-03-22T12:54:10Z")

</div>

Thanks but just tried that, still not aligned

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [22 March 2025 17:35 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/22 "2025-03-22T17:35:51Z")

</div>

Could you post a pic of what you are seeing?

---

<div class="post-metadata">

**Author:** ![jon.nielsen](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/jon.nielsen/32/15458_2.png) [@jon.nielsen](https://community.cyanlabs.net/u/jon.nielsen)\
**Post date:** [22 March 2025 18:26 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/23 "2025-03-22T18:26:57Z")

</div>

Do you want Forscan data or pictures of the radio, like in addition to the original post picture?

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [22 March 2025 18:28 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/24 "2025-03-22T18:28:13Z")

</div>

Does it still look like the original post pic? If not, can you post a new pic?

---

<div class="post-metadata">

**Author:** ![jon.nielsen](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/jon.nielsen/32/15458_2.png) [@jon.nielsen](https://community.cyanlabs.net/u/jon.nielsen)\
**Post date:** [22 March 2025 19:11 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/25 "2025-03-22T19:11:44Z")

</div>

Yup, same as the first pic. Thinking the answer is no, but can the number of presets per page or number of preset pages be changed in forscan?

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [22 March 2025 19:34 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/26 "2025-03-22T19:34:38Z")

</div>

Yes, it can in both the ACM and APIM.

Check the setting for NOP.  
727-01-01 xxxx \*xxx xxxx  
A2B, Reserved, Alternative Frequency (AF), Number of Presets (NOP)  
0=A2B Disabled, Reserved, AF On, NOP 10  
1=A2B Disabled, Reserved, AF On, NOP 6  
2=A2B Disabled, Reserved, AF Off, NOP 10  
3=A2B Disabled, Reserved, AF Off, NOP 6  
8=A2B Enabled, Reserved, AF On, NOP 10  
9=A2B Enabled, Reserved, AF On, NOP 6  
A=A2B Enabled, Reserved, AF Off, NOP 10  
B=A2B Enabled, Reserved, AF Off, NOP 6

Check to see what the setting is for Mixed Mode Presets.  
7D0-02-02 xxxx xx\*x xx–  
Autostore/Mixed Mode Presets (A), Electronic Horizon Type (EHT), Integrated Control Panel (ICP) (EFP) Type, Integrated Control Panel (ICP) (Electronic Feature Panel - EFP) Branding  
0=Autostore Enabled (Normal Presets), EH: MPP + Stubs, ICP (EFP) Type: EFP, ICP(EFP) Brand: Non-Branded  
1=Autostore Enabled (Normal Presets), EH: MPP + Stubs, ICP (EFP) Type: EFP, ICP(EFP) Brand: Branded  
2=Autostore Enabled (Normal Presets), EH: MPP + Stubs, ICP (EFP) Type: ICP, ICP(EFP) Brand: Non-Branded  
3=Autostore Enabled (Normal Presets), EH: MPP + Stubs, ICP (EFP) Type: ICP, ICP(EFP) Brand: Branded  
4=Autostore Enabled (Normal Presets), EH: MPP + Stub+Exp, ICP (EFP) Type: EFP, ICP(EFP) Brand: Non-Branded  
5=Autostore Enabled (Normal Presets), EH: MPP + Stub+Exp, ICP (EFP) Type: EFP, ICP(EFP) Brand: Branded  
6=Autostore Enabled (Normal Presets), EH: MPP + Stub+Exp, ICP (EFP) Type: ICP, ICP(EFP) Brand: Non-Branded  
7=Autostore Enabled (Normal Presets), EH: MPP + Stub+Exp, ICP (EFP) Type: ICP, ICP(EFP) Brand: Branded  
8=Autostore Disabled (Mixed Mode Presets), EH: MPP + Stubs, ICP (EFP) Type: EFP, ICP(EFP) Brand: Non-Branded  
9=Autostore Disabled (Mixed Mode Presets), EH: MPP + Stubs, ICP (EFP) Type: EFP, ICP(EFP) Brand: Branded  
A=Autostore Disabled (Mixed Mode Presets), EH: MPP + Stubs, ICP (EFP) Type: ICP, ICP(EFP) Brand: Non-Branded  
B=Autostore Disabled (Mixed Mode Presets), EH: MPP + Stubs, ICP (EFP) Type: ICP, ICP(EFP) Brand: Branded  
C=Autostore Disabled (Mixed Mode Presets), EH: MPP + Stub+Exp, ICP (EFP) Type: EFP, ICP(EFP) Brand: Non-Branded  
D=Autostore Disabled (Mixed Mode Presets), EH: MPP + Stub+Exp, ICP (EFP) Type: EFP, ICP(EFP) Brand: Branded  
E=Autostore Disabled (Mixed Mode Presets), EH: MPP + Stub+Exp, ICP (EFP) Type: ICP, ICP(EFP) Brand: Non-Branded  
F=Autostore Disabled (Mixed Mode Presets), EH: MPP + Stub+Exp, ICP (EFP) Type: ICP, ICP(EFP) Brand: Branded  
Note:  
Mixed Mode Presets Turns Off Autostore.  
Autostore is normal presets with discreete banks for each source such as AM or FM radio, SiriusXM, DAB, etc.  
Mixed Mode presets does not utilize the discrete banks, rather you can store any source in any position.  
To utilize Mixed Mode Presets, you must have a compatible ACM and turn off Autostore.

---

<div class="post-metadata">

**Author:** ![jon.nielsen](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/jon.nielsen/32/15458_2.png) [@jon.nielsen](https://community.cyanlabs.net/u/jon.nielsen)\
**Post date:** [23 March 2025 01:49 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/27 "2025-03-23T01:49:00Z")

</div>

So I tried to make changes to both:  
1 to 0  
0 to 8  
That didn’t show any changes though after writing and restarting the truck. Also tried restarting the modules.

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [23 March 2025 03:05 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/28 "2025-03-23T03:05:21Z")

</div>

You should have 1 and 0 respectively, which it appears you did.  
Do you have APIM profiles enabled by chance?

Maybe an idea, maybe a shot in the dark. This really looks like you have a corrupted asbuilt or something is not communicating properly. Let’s rule out the asbuilt…  
Backup your ACM asbuilt.  
Edit your ACM asbuilt and replace the data from block 5 onward with the data below. You can do this in notepad, make sure to save as an ABT file.  
Write this to the ACM and then reset the ACM.

;Block 5  
727050100072F575B1C  
7270502765B572F0793  
;Block 6  
7270601040004013E7C  
7270602003E025F00D5  
72706035F015C003528  
72706040033000A0075  
;Block 7  
727070100000A003373  
72707020035005C00C8  
727070364005C00352D  
72707040033000A0076  
;Block 8  
72708011717171717AA  
7270802173646557A9A  
72708030F0F0F0F0F84  
72708040F274C7C5B93  
72708051717171717AE  
7270806172946515D70

---

<div class="post-metadata">

**Author:** ![jon.nielsen](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/jon.nielsen/32/15458_2.png) [@jon.nielsen](https://community.cyanlabs.net/u/jon.nielsen)\
**Post date:** [25 March 2025 00:55 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/29 "2025-03-25T00:55:38Z")

</div>

So I wrote the above blocks but I didn’t notice any changes. What was the desired result?

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [25 March 2025 17:58 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/30 "2025-03-25T17:58:05Z")

</div>

Overwrite the presets to see if there was corruption in the ACM asbuilt. Post your asbuilts for the ACM and APIM…

---

<div class="post-metadata">

**Author:** ![jon.nielsen](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/jon.nielsen/32/15458_2.png) [@jon.nielsen](https://community.cyanlabs.net/u/jon.nielsen)\
**Post date:** [25 March 2025 18:34 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/31 "2025-03-25T18:34:22Z")

</div>

Sure, here you go:

 ![acm1](https://community.cyanlabs.net/uploads/default/original/3X/7/3/7328280e895a5b7a3a756b6261e805a449a2d2db.png)  
 ![acm2](https://community.cyanlabs.net/uploads/default/original/3X/b/6/b637d064e40acbc7c0dc383cf1d0a45c2e3992f2.png)  
 ![apim1](https://community.cyanlabs.net/uploads/default/original/3X/f/7/f7bd9a962e1b7287863c2591d684a5c063591e5a.png)  
 ![apim2](https://community.cyanlabs.net/uploads/default/original/3X/f/d/fd3ec657cc6792a63b316f33de3ba6d7317f9ac1.png)

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [26 March 2025 03:21 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/32 "2025-03-26T03:21:46Z")

</div>

Did you restore your ACM asbuilt after you tested the one I gave you? They do not match…otherwise the ACM looks fine.

In the APIM, I do not see anything that would cause this issue, however…  
7D0-08-02 xxxx xxxx \*x-- LIN12-Y (count).  
Number of Times for LIN Scheduler 12.  
Your value is ‘0’, should be a ‘1’.  
This should not have anything to do with the issue but it needs to be corrected.

Could you run the Interrogator Utility and post the XML here…

---

<div class="post-metadata">

**Author:** ![jon.nielsen](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/jon.nielsen/32/15458_2.png) [@jon.nielsen](https://community.cyanlabs.net/u/jon.nielsen)\
**Post date:** [26 March 2025 15:10 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/33 "2025-03-26T15:10:37Z")

</div>

Yes I did revert it back after testing with your AB changes. I will also change this value you recommended. Attached is the XML. I removed vin info from the file. Thank you!  
[Sync\_VX6P086E\_XXXXXXXXXXXX.xml](https://community.cyanlabs.net/uploads/short-url/4z5VR8C7b4WR2RPKGxo9WUrvydT.xml) (11.0 KB)

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [27 March 2025 01:58 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/34 "2025-03-27T01:58:11Z")

</div>

All of the tests and the data like asbuilts and interrogator log info look fine, and the original issue still persists.

> [@jon.nielsen](#):
>
> The upgrade went fine, but had an issue where the XM slider for the presets not aligning properly. If I slightly move the slider, it does correct itself. This problem occurs everytime I start the truck or leave and return to the radio view.

At this point I would try reformatting the APIM and reloading the asbuilt. That seems to be the only option left. Unknown if it will clear the issue.

---

<div class="post-metadata">

**Author:** ![Scrubboy](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/s/e47774/32.png) [@Scrubboy](https://community.cyanlabs.net/u/Scrubboy)\
**Post date:** [2 April 2025 17:10 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/35 "2025-04-02T17:10:36Z")

</div>

Yes, I have the same issue on my 18 F250, recently updated from 3.0 to 3.4.23188.  
Did you keep your Sirius XM logos?

---

<div class="post-metadata">

**Author:** ![jon.nielsen](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/jon.nielsen/32/15458_2.png) [@jon.nielsen](https://community.cyanlabs.net/u/jon.nielsen)\
**Post date:** [2 April 2025 19:26 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/36 "2025-04-02T19:26:33Z")

</div>

I retained maybe 70% of the logos. When I started losing hope a couple months ago, I purchased a used APIM from eBay. I may just install that. These issues aren’t huge, but my OCD is getting the better of me lol. I do appreciate the assistance that was provided by the people in the community.

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [2 April 2025 19:37 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/37 "2025-04-02T19:37:30Z")

</div>

If you install that let us know if it helps…

---

<div class="post-metadata">

**Author:** ![warlock12118](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/w/e95f7d/32.png) [@warlock12118](https://community.cyanlabs.net/u/warlock12118)\
**Post date:** [2 April 2025 22:18 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/38 "2025-04-02T22:18:46Z")

</div>

Personal experience here…  
If the logos don’t come back after a 3.0 to 3.4 reformat or after a 3.4 to 3.4 reformat to load maps dropping in a different APIM, hitting the XM channels after it boots and then putting the original back in will cause the logos to update on the original APIM.

The replacement APIM channel buttons when you hit them will come up as invalid for about 10 minutes and show the little blue SIRIUSXM text, then they work and the logos update.  
Drop the original back in and the logos update.

Don’t ask me why, but it works, my gut is that the ACM sees the new ESN of the APIM and it causes the ACM to resync the logos.

---

<div class="post-metadata">

**Author:** ![Scrubboy](https://community.cyanlabs.net/letter_avatar_proxy/v4/letter/s/e47774/32.png) [@Scrubboy](https://community.cyanlabs.net/u/Scrubboy)\
**Post date:** [14 April 2025 22:48 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/39 "2025-04-14T22:48:05Z")

</div>

@warlock12118.

Sir, is this the refresh button you are referring to? I am thinking of buying another APIM with the same part number off of ebay and giving this a try…

 ![20250414_184041](https://community.cyanlabs.net/uploads/default/original/3X/1/d/1d2def2ee310bde740eb29a68f07a24673c003bb.jpeg)

---

<div class="post-metadata">

**Author:** ![F150Chief](https://community.cyanlabs.net/user_avatar/community.cyanlabs.net/f150chief/32/14712_2.png) [@F150Chief](https://community.cyanlabs.net/u/F150Chief)\
**Post date:** [15 April 2025 20:09 UTC](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034/40 "2025-04-15T20:09:18Z")

</div>

Here’s an idea: run the RWData Cleaner (and maybe a Master Reset) then try the XM refresh with that menu. If it works it’s a bonus, if not nothing lost.

[Previous page](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034.md?page=1)

[Next page](https://community.cyanlabs.net/t/issue-with-xm-preset-slider/17034.md?page=3)
