My experience is J2534 support is sketchy and if you want to do the things you actually want to do you need a manufacturer approved device with an insane markup. Also the subscriptions are insanely expensive, not even close to reasonable and you need to be a company (at least you used to be with Ford last time I checked, but they accept the UK or Dutch royal residence as a valid company location so there is that...)
I agree that J2534 is sketchy. The standard isn't very good to start with, there's usually no matrix (ie x systems * y devices) conformance testing but instead just a brief QA step done at some compliance stage in a release process, and most manufacturers don't really want to support it (preferring their in-house dongles). So, a lot of dealer tools do non-standard stuff and a "conforming" J2534 cable doesn't actually work.
Many subscriptions are painful, yes - VW brands / ODIS for example are awful to try to get as an individual and annoying as an independent shop; I'm sure the fraction of independent shops who pirate it are quite high. It's funny you mention Ford though, as they are incredibly easy to buy from in my experience, although the login/licensing backend is frequently broken.
However, there's a good cottage industry of companies reverse engineering the compatibility issues back out, and for better or worse these companies are cloned almost immediately too. I recently did key programming on a newer Ford (where Forscan can't) using a $125 VXDiag cable which I could have bought cloned for $30 and a short-term FDRS subscription that cost $50.
What about using ForSCAN? It allows anyone with the software and a dongle to monitor and to update modules in the ECU AFAIK. I paid under $100 (can't remember) for a dongle and downloaded the free software and it is extremely handy working on one of my vehicles. The other two Fords I own are both pre-OBDII so there is less bullshit on them to begin with. Ford forums are full of owners who use ForSCAN to modify their vehicle's operation. Lots of hacks available.
Just do as /u/bigfatkitten suggests and get the service manuals when you purchase the vehicle.
ForSCAN is awesome but it's an orthogonal conversation since it's a reverse engineered diagnostic tool rather than a first-party one. If we expand the conversation to that space there are tons of options with varying capabilities depending on manufacturer, including also pirating the OEM tools directly. Also worth noting that ForSCAN also doesn't _quite_ support all common operations, for example Remote Keyless Entry enrollment on newer BCMs with push-to-start needs FDRS still.
Thanks for this explanation. I knew that ForSCAN was a RE tool (Russian guy?) and that there were others out there for multiple purposes on various product lines. I also knew that ForSCAN did not support customizing all OEM functions. I just wasn't bright enough to make the connection between this being a first party versus anybody's tool type of mods that one might make. I do most of my own auto maintenance so I use the tools that best facilitate the process and since I am only mechanically experienced and not an accredited tech I lean towards using third party tools, custom tools I cobble together, OEM manuals, etc. to guide all the work I do here in my driveway or shop.
Ah the infamous "no I wrote it myself" submission in university coursework. Usually gets you a free visit to the guidance counsel and a bonus free mark (on your three strikes and you are out plagiarism form).
Reminds me a bit about installing one of my 128MB 72 pin SIMM modules in a 486, it has the same caching issues. Most board will not accept them anyway (I have both FP and Edo ones) but if you put a lower capacity one in the first slot they will happily boot and accept the full ram amount if all lanes are occupied (which is not a given on all 486 motherboards). Also remember to enable quick ram check or you will be getting more coffee.
> And yet it failed in the common user's perspective
In Germany, the situation was different: there, at that time OS/2 (in particular OS/2 3.0 Warp) had quite a bit of popularity among common users because Escom and in particular Vobis (the latter was an at that time ultra-successful chain for selling computers in Germany) decided they want to challenge Microsoft's de-facto monopoly on operating systems of that time by also selling PCs that had OS/2 pre-installed (you only got DOS/Windows installed for an upcharge):
"Als die deutschen Computerhändler Vobis und Escom ankündigten, auf ihren PCs zukünftig OS/2 vorzuinstallieren und Windows nur noch gegen Aufpreis anzubieten, übte Microsoft massiven Druck auf die beiden Computerhändler aus. So schloss Microsoft Vobis vom Beta-Programm von Windows 95 aus, bot für die Zukunft Windows-Lizenzen nur zu wesentlich schlechteren Bedingungen an und versuchte, Vobis dazu zu zwingen, eine Verschwiegenheitserklärung zu unterzeichnen."
DeepL translation:
"When the German computer retailers Vobis and Escom announced that they would pre-install OS/2 on their PCs in the future and offer Windows only at an additional cost, Microsoft exerted massive pressure on the two retailers. For instance, Microsoft excluded Vobis from the Windows 95 beta program, offered Windows licenses in the future only under significantly worse terms, and attempted to force Vobis to sign a non-disclosure agreement."
"1995 setzte Vobis wegen Lieferterminverschiebungen der 32-Bit-Plattform Windows 95 darauf, Kunden standardmäßig das bereits erschienene 32-Bit-Betriebssystem OS/2 von IBM auf PCs vorzuinstallieren, wodurch OS/2 auf dem deutschen Markt einen größeren Bekanntheitsgrad als anderswo erreichte. Microsoft soll in der Folge versucht haben, Vobis die Lizenz für Windows 95 zu entziehen, was einen schweren wirtschaftlichen Nachteil für Vobis bedeutet hätte."
DeepL translation:
"In 1995, due to delays in the release of the 32-bit Windows 95 platform, Vobis decided to pre-install IBM’s 32-bit OS/2 operating system—which was already available—on PCs as standard, resulting in OS/2 achieving greater recognition on the German market than elsewhere. Microsoft is said to have subsequently attempted to revoke Vobis’s license for Windows 95, which would have caused Vobis serious financial harm."
Vobis also produced its own computer magazine named "Highscreen" (named after Vobis' brand name for their PCs) that also contained lots of beginner tips for OS/2 to get PC buyers accustomed to OS/2.
There’s a lot of framing in how questions are asked. I’m going to bet asking the community “Would you like more features if they’re made using AI assistance?” is going to get wildly different results.
How many years of experience with git do you have? How much of git do you use? I bet you use 5 commands and 10 flags at most. Take a look at git's docs
Overly verbose and "glitter" readme.md files is a good indicator of bad projects or at least projects which need more attention to be used. It's too often pre-rugpull or look-at-me repos where better solutions are one click away.
Finding any curse words in hidden comments in the commit history is for me a good indication of a human working on a passion project, though ymmv.
And there are always exceptions to the exception of the exceptions.
reply