Multiecuscan 1.8 'latency too high' errors
Posted: 16 Mar 2014, 11:01
I recently got a 'new' laptop, a Lenovo X121e, AMD E-300, 128Gb SSD, 4Gb RAM, with Windows 7 Professional 64 bit OS. I installed Multiecuscan 1.8 and set it up according to the Multiecuscan User Guide. The program worked fine except for the graphs which had a lot of dips down to zero along with frequent red 'latency too high' error messages; seeing as I was looking for an intermittent idling problem on my Alfa Romeo GTV 2.0 JTS this was useless.
Previously I had run FiatECUScan 3.3 on my old laptop, an Asus Eee PC 1008HA, Intel Atom N280, 160Gb HD, 1Gb RAM, with Windows 7 Starter 32 bit with never any error messages or graph problems.
I searched on the internet for FiatECUScan 3.3 which I found and installed on my Lenovo, and set it up the same as I had for Multiecuscan 1.8. It worked perfectly.
I tried FiatECUScan 3.3 for 5 full screens of 4 data graphs - no data drop out, no reported error.
I tried Multiecuscan 1.8 at least 10 times with the same graphs - within a quarter of the graph page each time there was data drop out.
I am sticking with the old FiatECUScan 3.3.
Previously I had run FiatECUScan 3.3 on my old laptop, an Asus Eee PC 1008HA, Intel Atom N280, 160Gb HD, 1Gb RAM, with Windows 7 Starter 32 bit with never any error messages or graph problems.
I searched on the internet for FiatECUScan 3.3 which I found and installed on my Lenovo, and set it up the same as I had for Multiecuscan 1.8. It worked perfectly.
I tried FiatECUScan 3.3 for 5 full screens of 4 data graphs - no data drop out, no reported error.
I tried Multiecuscan 1.8 at least 10 times with the same graphs - within a quarter of the graph page each time there was data drop out.
I am sticking with the old FiatECUScan 3.3.