SManager went crazy on me...

s300 and SManager software questions & answers
Locked
Dunc
Posts: 10
Joined: Tue Oct 04, 2005 11:34 am

SManager went crazy on me...

Post by Dunc »

This topic was originally posted here: http://www.honda-tech.com/zerothread?id=1890874
Background Info:
So on Friday I was inquiring about fuel trims just before I went to test the S300 on my car for the first time and drive home for a few hours. Well I uploaded the converted (S200) file to a S300 calibration and the ECU seemed to like it. I switched the key off momentarily like you would with the S200 and then started the car. That's when the fun happened....
The car was running fine and actually seemed to run better even though I didn't change the tune at all. Niether the CEL or Maintanence lights came on so I thought everything was good to go. I had my laptop datalogging and was going to fine tune the street tune a bit buuuuut that didn't work out.

The SManager was giving me like 10 different error codes. The ones I can remember are:
- MAP sensor
- TPS sensor
- Injector Error
- Unknown <--??? haha :shock:
- Fuel Supply Sytem
- Ignition System
- Cylinder Position Sensor
- VSS
- ...and a few more

Some of these would go away and then show back up. The SManager also seemed like it was lagging. It wasn't smooth with updating the data, it seemed as though it would sample every second instead of sampling in real time. After like a minute or two, I got the pop-up window error of "Access violation at address 0043CA5B in module 'SManager.exe'. Read of address 00F582B0". It just wigged out and cascaded that same pop-up like 8 times from what I counted on the screen haha. If I clicked on "OK" the popup would not go away. See picture below.

Question:
Has anyone ever had this problem? What might be the cause? I have yet to reconnect the laptop and see if would work because now I'm scared that it'll screw with the tune or soemthing haha. Oh and by the way, I know those error codes are not right because the car is in perfect working order. It was also socketed by Hondata since I had the S200 before and I just checked, and J12 is cut. Thanks for any input.

Image
User avatar
Hondata
Site Admin
Posts: 10615
Joined: Thu Aug 15, 2002 12:13 pm
Location: Torrance, CA
Contact:

Post by Hondata »

It is a mismatch between the s300 and SManager.

Make sure that you have the latest version of SManager.
Check (initially) that the onboard datalogging is switched off.
Re-upload the calibration.
Datalog and check that the speed seems OK.
Hondata
Dunc
Posts: 10
Joined: Tue Oct 04, 2005 11:34 am

Post by Dunc »

Will do. Thanks for the quick reply.
deafy
Posts: 191
Joined: Mon Jul 10, 2006 6:22 pm
Contact:

Post by deafy »

Maybe update USB drivers?
smracing
Posts: 107
Joined: Sat Sep 17, 2005 5:38 pm

Post by smracing »

I came out this morning and started my car up. The MIL was on and the engine seemed to be idling funny. I grabbed my laptop and plugged in to see what was going on. I had a similar line of Error Codes. I hit the Datalog button and really got some weird readings. No rpm, tps, etc. I cleared the codes and re-loaded my tune and it ran fine. Suggest to me some sort of software problem.

I have been running S300 since it came out. I think I loaded the latest update a couple of weeks ago. One thing I have noticed lately is the engine is slow to come back to idle when driving around town. The TPS reads zero but engine is still idling 1600-1800rpms. Finally it settles down to a normal idle.
deafy
Posts: 191
Joined: Mon Jul 10, 2006 6:22 pm
Contact:

Post by deafy »

Check the IACV duty cycle, that may fix your idle problem
smracing
Posts: 107
Joined: Sat Sep 17, 2005 5:38 pm

Post by smracing »

IAC duty cycle is set to "normal". Today it is much colder than it has been (mid 30s) and car is running much better. It seems to run great when cold out, (obviously), but things like idle seem normal and starting is not a problem.
Dunc
Posts: 10
Joined: Tue Oct 04, 2005 11:34 am

Post by Dunc »

Hondata wrote:It is a mismatch between the s300 and SManager.

Make sure that you have the latest version of SManager.
Check (initially) that the onboard datalogging is switched off.
Re-upload the calibration.
Datalog and check that the speed seems OK.
Just as an update for anyone searching the future:
The above suggestions listed fixed the problem. I believe my problem was that I had datalogging enabled the first time I tried it. I disable it and tried again....worked perfectly. Now I just need to figure out what settings work correctly for the GM 3Bar :/
El Verdugo
Posts: 47
Joined: Fri Dec 08, 2006 6:08 pm
Location: Port Allen
Contact:

Post by El Verdugo »

Thanks for the tip, always good to hear when things get resolved.
Locked