Innovate Wideband working, but not logging correctly
Jul 2, 2008, 05:19 PM
#1
Innovate Wideband working, but not logging correctly
Alright so i have an innovate lc-1 that is acting a little funny. I finally figured out how to change the com ports and other stuff like that and got evoscan .99 to recognize the wideband and log it. For some reason when it logs the wideband the numbers are ranging from 4-3 on evoscan, but reading perfectly on the wideband itself. I tried changing to different ports and things like that, even which usb i was putting it into the computer on. I then decided to make sure everything was working right with lm programmer and logworks. Luckily when i decided to log the wideband with lm prorammer and logworks it was logging and reading it spot on. I need to be able to log my afrs properly in order to get a good tune, but im unable to do this with evoscan. Any suggestions. Should i try mitsulogger? Is it possible to use both evoscan and the logworks simultaneously so that i can send them both to my tuner, or will that slow the loggers down to much and cause a problem, or will having the logworks file not really do anything for me even though it is showing what my actual afrs are. Im using a keyspan serial to usb just incase anyone was wondering. alright thanks for the help.
Jul 4, 2008, 09:41 AM
#7
what he said above and i was wondering if you hooked it up in logworks to see how it is working. It might need calibration as well. I used logworks then Evoscan.
Trending Topics
Jul 4, 2008, 09:46 AM
#8
I had the LC-1 working with 2.3 even though it is set up via the mts chain. this is a bonus as mitsulogger won't work it at all in that configuration.
edit: no, I had disconnected the chain.
Still, as mentioned above, try logworks/openport it is really a nice logging feature. In many ways vastly superior to evoscan at least in graphing. Since you have the innovate product its already there.
edit: no, I had disconnected the chain.
Still, as mentioned above, try logworks/openport it is really a nice logging feature. In many ways vastly superior to evoscan at least in graphing. Since you have the innovate product its already there.
Last edited by nothere; Jul 5, 2008 at 03:28 PM.
Jul 5, 2008, 03:54 PM
#9
Account Disabled
iTrader: (38)
Join Date: Aug 2005
Location: Virginia Beach, Virginia
Posts: 9,319
Likes: 0
Received 1 Like
on
1 Post
if it's reading correctly in logworks then you know the problem is with evoscan. if it's reading incorrectly in logworks you probably have a bad sensor or just haven't calibrated the sensor correctly.
Jul 5, 2008, 06:59 PM
#10
alright well i recalibrated it but havn't tried to log since. Im not really trying to use a new version of evoscan because my tuner prefers to use version .99 but also because i can't really figure out how to download the new version without paying for it again. Thanks for your help
Jul 8, 2008, 10:15 PM
#11
alright im pretty pissed. ive been trying everything and nothing is working right. I was just trying to get logworks working and it was reading everything fine but it wasn't reading other things like rpm and throttle position and other awesome stuff that it has on the box and the website. Anyway besides that not working i still can't get evoscan do pickup my wideband correctly and i must be a noob or something because i can't for the life of me download evoscan 2.4 without paying for it again. well i dunno what to do, i really don't wanna give up but im running out of options any more advice???
Jul 8, 2008, 10:21 PM
#12
Did you ever try logworks? did it work? Leave evo4mad a message and the link to download was actuallyl posted here. If you paid for evoscan then email them to get the newer version.
Evoscan help link
http://www.evoscan.org/helpdesk/
Evoscan help link
http://www.evoscan.org/helpdesk/
Last edited by oldevodude; Jul 8, 2008 at 10:25 PM.
Jul 9, 2008, 06:21 AM
#14
Account Disabled
iTrader: (38)
Join Date: Aug 2005
Location: Virginia Beach, Virginia
Posts: 9,319
Likes: 0
Received 1 Like
on
1 Post
the point of the logworks suggestion was to verify that the wb02 is working properly (not everything else)...if it is then you know it's an evoscan problem. Some people simply choose the wrong com port.