Hi, updated to the new version but could not log my JDM STi Forester via SSM thereafter. Says ecu connected and no data shows for the selected parameters. I have since reverted back to the previous version just by copying over the executable and I can log again.

ckibue wrote:Hi, updated to the new version but could not log my JDM STi Forester via SSM thereafter. Says ecu connected and no data shows for the selected parameters. I have since reverted back to the previous version just by copying over the executable and I can log again.

I've test again version using fast query mode and standard mode, and all works fine on 16bit & 32bit ECUs. May be you have too many gauges for updating - check your CPU usage after connect

epifan wrote:

ckibue wrote:Hi, updated to the new version but could not log my JDM STi Forester via SSM thereafter. Says ecu connected and no data shows for the selected parameters. I have since reverted back to the previous version just by copying over the executable and I can log again.

I've test again version using fast query mode and standard mode, and all works fine on 16bit & 32bit ECUs. May be you have too many gauges for updating - check your CPU usage after connect

Hi, just tried version 515 again and no luck at all, no data on min, current and max value boxes and soon thereafter a dialog box comes up saying connection to ecu has been interrupted. 502 works though has random disconnections with the same dialog box and sometimes rendering my usb port un-usable until after a hard reboot.
My setup is Windows 7 Pro 64 bit and using openport 2.0 with firmware from ecuflash 3252 beta.

Hi again, completely stumped here, tried this version with Openport 1.3U again and no data shows on the datalist window, and soon thereafter, the logger disconnects from the ecu, and again 3.5.1.502 works flawlessly Any help appreciated as I would benefit greatly from the fast logging feature, or a link to the freshest binary other than the installation file.

Test again on several subarus - all works fine with logging (fast & normal). I know about some issues with DTC reading thru SSM and I've create fix build of executable
try it

epifan wrote:Test again on several subarus - all works fine with logging (fast & normal). I know about some issues with DTC reading thru SSM and I've create fix build of executable
try it

Thanks, tried 517 again today, car is a 2004 JDM Forester STi, connects and logs for a couple of seconds then disconnects with ecu disconnected error. It however worked on a 2004 JDM STi even in fast logging.....

ckibue wrote:

epifan wrote:Test again on several subarus - all works fine with logging (fast & normal). I know about some issues with DTC reading thru SSM and I've create fix build of executable
try it

Thanks, tried 517 again today, car is a 2004 JDM Forester STi, connects and logs for a couple of seconds then disconnects with ecu disconnected error. It however worked on a 2004 JDM STi even in fast logging.....

Sorry. I don't understand how it can be. Normal mode is total the same as before. I didn't change anything!
Try to minimize params count, try to change logging speed in Normal mode. Please, give me more information, because currenty you are only the one who have any problems with logging thru SSM in new version

Try to change "Custom Port settings" - Read Constant to 100-200

epifan wrote:Try to change "Custom Port settings" - Read Constant to 100-200

Thanks, tried today and still no luck, I can log though by keeping the logged items less than 20 unlike in the 16 bit ecus which so far have not had any restriction. Thanks for the help and support; the fast logging has very good resolution

Same here Epifan, tried today with my 2011 EDM STi and no chance to log via SSM at all. It connects, try to read parameters, then I got a popup windows saying ECU has been disconnected. Tried to log 1 parameter only and display rate to 200ms and read rate to 200ms, but still the same problem.
Switch back to previous Ecuedit version and it worked fine !

I had the same problem and I came back to the old version

This "problem" was solved today for one customer via remote desktop by changing Port settings. Here is recommended settings:

Will try and let you know

Thanks, tried 517 again today, car is a 2004 JDM Forester STi, connects and logs for a couple of seconds then disconnects with ecu disconnected error. It however worked on a 2004 JDM STi even in fast logging.....

Ganapoes wrote:Thanks, tried 517 again today, car is a 2004 JDM Forester STi, connects and logs for a couple of seconds then disconnects with ecu disconnected error. It however worked on a 2004 JDM STi even in fast logging.....

Try latest 550, this version ignore old port settings