ShadowsPapa
Well-Known Member
- First Name
- Bill
- Joined
- Oct 12, 2019
- Threads
- 247
- Messages
- 40,442
- Reaction score
- 53,860
- Location
- Runnells, Iowa
- Vehicle(s)
- '25 JTMX, '23 JLU 4xe, '82 SX4, '73 Javelin
- Occupation
- Retired auto mechanic, frmr gov't ntwrk security admin
- Vehicle Showcase
- 3
- Thread starter
- #76
Great explanation and example.Ok- Jscan and AlfaOBD name the settings differently (a little more user friendly for Jscan), but they are changing the exact same message IDs in the BCM. Jscan doesn’t use the real setting names, such as VehConfig 1, ECUConfig 1, CustSetMenu 1, etc.
The equivalent for AlfaOBD CustSetMenu 1,2,3 in Jscan would be “Radio User Settings”, and the equivalent for AlfaOBD CustSetMenu 1: Auto High Beam CSM Present in Jscan would be Radio User Settings > Auto High Beam On/Off. They both do the exact same thing.![]()
![]()
Yes, for the non-programmers "radio user settings" is easier for the average person to see in the list and the jscan explanation of "allows you to turn ON or OFF this feature............." is extremely user friendly.
In other words, it's THERE - per your screenshot.
I found that jscan was faster and more user friendly even for tire size changes. Both do it and do it fine, but you can find it and change it super-fast in jscan.
That's one reason I have both - one is a bit more "I don't feel like digging into my C++ books to find the library for this" and the other is "I worked for FCA and created these things" types LOL
Sponsored