@TractMec, AndyFocus, Victor, Narly1, et al,
What a BuzzKill....well the PC/ED manual arrived today and...within those austere pages it is clearly stated that only certain 2003 Ford cars have the HS-CAN comm bus, and the 2003 Ford Escape aint one of'm
( You were dead nuts on!! I had to buy three Ford manuals to acquire that info.
All the parts cost around $10. As for finding an interface that does the auto HS/MS CAN switching for $30, I was unaware of any that may be available. If you know of any vendor that offer an auto-relay switching version, please share that info. I do know of manual toggle switch vendor offerings. My point wasn't to make a super inexpensive auto-mode switching adapter, as I've already expended $150 for services manuals and $100 for a used laptop and $54 for an OBDLink-SX USB to OBD-II interface adapter. So $10 in my effort to remedy my car problem is well within my strategy scope. I'm attempting to save thousands of Dollars in dealer service fees. Not save $30 bucks. My car has been to the dealer service four times, they are quite willing to replace every sensor, actuator, solenoid in the car...guessing because they have no clues as to what is causing the malfunction. Ford, hah! Crappy diagnostics, else their service personnel would be able to diagnose and effect remedy. Myself being an engineer, I'd be embarassed to have people know that I designed crap like that. Everything I've ever engineered and I've made some really complicated gadgets, all were serviceable because I designed'm to be serviceable.
So without making any changes to the OBDLink-SX OBD-II bus interface adapter, I fired up my quad Intel CPU HP car LapTop, instantiated ForScan, plugged in the SX USB cable and plugged the SX OBD-II conn into the diag port and voilet, it fired right up. I ran all the tests, no codes and nothing is pending. However, upon setting up the live-stream configuration and running the 'oscilloscope'; the running traces, paint smoothly, then periodically jerks along and when driving, frequently, crashes the program, meaning that ForScan, apparently stops communicating with the SX adapter. The message that's emitted 'not connected to vehicle'. The anomaly behaves similarly to a buffer over-run. But I can't discern whether its the SX or the phukn Ford bus that's misbehaving? And to add to that, it only happens when driving!! To restart comm, the USB cable needs to be unplugged/replugged and then maybe it'll reconnect, while other times, I was forced to unplug/replug the USB AND deinstantiate/reinstantiate ForScan to restart comm.
But its a kewl program. A little twitchy but kewl. I really like the table view. Although I am confused about how the logging system works.
My plan is to enable live-stream data logging while driving and to continue logging until the engine is turned off. And then restart logging when the engine is cranked, so that I have the before and after engine states stored into the log file. However, it seems that logging only happens when the diskette icon is depressed. The question is, does ForScan start real-time logging when live-streaming is enabled or does ForScan only store previously RAM buffered data up until the icon is depressed? Another issue is that when the engine is turned off, the OBD-II interface stops communicating. Need I externally power the interface to keep the OBD-II data port alive?
An annoyance is the fact that the program ALWAYS puts the log files under the user directory. God I hate that. I put files where I want them for my convenience not McNazi$oft's. Too much fiddle diddle to get to files and often aren't moveable simply because of the M$ 'security' crap. So, please, ForScan, in the future allow users to put log files where we wanna put'm, and have the ForScan program remember where the files are placed, so that users aren't forced to vector all over to get to the logs!!
I'm gonna do some more testing. I have to discover whether or not the SX is malfunctioning. If it is, I need to RMA it. Maybe that's the reason ScanTools doesn't have a tech-support telephone number? However, I do feel that the SX is a good quality interface adapter. Gadgets fail, its the complexity of the components. So if it crapping out, I gotta fix it to move forward with my car diagnosis strategy.