scan tool input.
These scanners would then miss most of the important functions since the scanner does not understand GM codes and so you would be able to see all car functions and you would not be able to scan or record those of GM parameters.
As to transfer rates, 10.4K, that is only true for generic OBD-II as per SAE but a decent scanner like the one from Ease functions either at SAE rate or at VPW baud rate which is much faster (4x) then other laptop PCM scanners that support some of GM parameters but not all PCM and body/chassis parameters.
Trending Topics
Please enlighten.....
The Best V8 Stories One Small Block at Time
Please enlighten.....
This allows as an example water temps only be polled lets say once a second but O2s polled every 25 mSec while the CAN interface to CAN network function at VPW speed.
Being Ease allows like 50 plus PIDs to concurrently be polled I would not set all of them to 4x mode with fast polling for then as you mention your flooding the CAN network with OBD-II data while engine is under high load but at lower speeds or idle its not a issue so maybe using 2 or 3x mode would be better for that engine condition.
Scanning lets say 25 PIDs concurrently at 4x is not a issue for its the way Ease packages the requests.
Ease has already designed and now comes with its scanner the new CAN interface required for the new next gen PCMs GM is already using and be required for OBD-III and its speed is like 500 Kb/s on GMLAN network and 83K at the ADLC path so having done that Ease could use some of that logic to speed up its OBD-II traffic.
I have used the 4x mode for several months with no ill issues with other nodes on CAN network so when its needed you can set each PID for 1 to 40 frames per second.
With the new Ease interface already supporting the new GMLAN the interface can be used directly to car where older interfaces only supporting OBD-II would require a CANdi interface be installed between the car and scanner.



