![]() WinVer sez I'm still the more pedestrian 1803 (build 17134.472). Windows update has been paying visits and preforming updates between last SCR/ISTA+ run and new cable arriving. I hate to lead the witnesses, so just use this as intel. Now I'm like all the stories littering these pages, but my isn't a simple text fix and save the ini's. This is an installation, that has always started without error and connected the same way. ![]() Both get an Icon in systray from EDIABAS. 'Vehicle Could not be Identified'.Įach of their idiot lights shine on plug in. So now, both cables act exactly the same. ![]() Yes, shuffle obd.ini to match Cable plugged in. on it's still in Windows / DM available Com9. Sure enough, Win10 sees the new cable as different hardware and I need to change obd.ini to my newly assigned Com10, Latency 1. The providor teased me about the comport. ( I'm in the middle of a 200 mile shutdown threat and wanted the best possible result.) I decided to get what probably was a better Dcan cable to go forward with finishing an SCR evaluation. (There's a backstory post and query available.) It was doing fine when configed to use EDIABAS and my older ATMega 16 chipped white board cable. It's been used a little offline since the 2017 install. I have an older install of I think the standalone ISTA+.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |