err thats what i meant. Must get them both working together!! lol
Yeah. Just looks like it's not a priority at Greddy, like the whole emu thing. I think the v2 beta long time ago was even better that this "release". Hard to image it would any time soon be fixed...
at least they made most of the features now available without going stage 3. I almost picked up the maftpro just becuase i wanted afr tracking but didn't wanna deal with idc and duration settings. Now I can use map ecu maps to start from if i undertsand correctly? If they get that bug fixed with the rpm signal then the emanage would def be top piggyback imo. maybe its as simple as some kind of electronic signal buffer just as the boost readings were fixed.
I just got my emanage in the mail today, still dont have the wiring harness yet though. I was wondering if there was anything i could be doing in the software to get it prepared for when i hook it up in a couple days? Also is there anybody or place i could get a base map from? Thanks
__________________
USED ROSS High Compression PISTONS FOR SALE CHEAP $180 PM ME FOR DETAILS...
at least they made most of the features now available without going stage 3. I almost picked up the maftpro just becuase i wanted afr tracking but didn't wanna deal with idc and duration settings. Now I can use map ecu maps to start from if i undertsand correctly? If they get that bug fixed with the rpm signal then the emanage would def be top piggyback imo. maybe its as simple as some kind of electronic signal buffer just as the boost readings were fixed.
It should be a quick fix, looking the logged signal closely suggests that they use raw angle signal instead of calculating the average for a revolution or something. It shouldn't be too hard to apply an own low-pass filter to the raw signal, but then it might confuse ecu.
It shouldn't be more than just a line of code in emu, which makes me wonder why they haven't fixed it?? I hope they know about the problem??
anyone know where the emanage wiring diragram is for our cars? i cant seem to find it. i know they posted it here before. OH ya i only have the blue not ultimate.
If they get that bug fixed with the rpm signal then the emanage would def be top piggyback imo.
I don't have any rpm signal bugs. The ultimate lets you choose two different ways to input rpms. One method is better at tuning, and the other method is better at 2-step launch control. It's only the people doing 2-step launch control that are unsatisfied as they want both which is understandable.
For the people that tried out the beta 2.0 firmware when you switched to 2.00 non-beta did your emanage firmware get updated? You may be running non-beta software on your notebook and beta firmware on your emanage which undoubtedly will cause problems. If you don't know then I'd suggest going back down to 1.14 firmware and software and then apply the 2.00 non-beta version.
also can you pull timing without a boost pressure sensor? im working on a new beetle and the timing is going up to 38-40 sometimes. atleast thats what the scanner is telling me at wot. i know thats to much id like to keep it at 30 when wot.
I don't have any rpm signal bugs. The ultimate lets you choose two different ways to input rpms. One method is better at tuning, and the other method is better at 2-step launch control. It's only the people doing 2-step launch control that are unsatisfied as they want both which is understandable.
For the people that tried out the beta 2.0 firmware when you switched to 2.00 non-beta did your emanage firmware get updated? You may be running non-beta software on your notebook and beta firmware on your emanage which undoubtedly will cause problems. If you don't know then I'd suggest going back down to 1.14 firmware and software and then apply the 2.00 non-beta version.
I upgraded directly from v1.14 to v2.00, no betas ever in my laptop/emu. And the emu was upgraded as well. Don't you have these problems?
About the rpm signal, I think it's a clear bug that the emu shows rpm's jumping around when they in fact are not. Another bug is that using the rpm signal for rpm, the rev limiter in the lauch control doesn't work correctly. When some features works incorrectly or give false information, there's a bug in that feature.
I upgraded directly from v1.14 to v2.00, no betas ever in my laptop/emu. And the emu was upgraded as well. Don't you have these problems?
I'm still at v1.14 and I installed v2.00 on my desktop computer to browse around in the software.
Quote:
Originally Posted by Elina75
About the rpm signal, I think it's a clear bug that the emu shows rpm's jumping around when they in fact are not. Another bug is that using the rpm signal for rpm, the rev limiter in the lauch control doesn't work correctly. When some features works incorrectly or give false information, there's a bug in that feature.
My rpm signal is running perfectly for me. Did your problems start with v2.00 firmware? Launch control has been quirky since day one if you use the rpm_signal for rpms.
The AutoGuide.com network consists of the largest network of enthusiast-owned enthusiast-operated automotive communities.
AutoGuide.com provides the latest car reviews, auto show coverage, new car prices, and automotive news. The AutoGuide network operates more than 100 automotive forums where our users consult peers for shopping information and advice, and share opinions as a community.
Re: -= Ultimate Emanage Thread =-
Re: -= Ultimate Emanage Thread =-
atleast thats what the scanner is telling me at wot. i know thats to much id like to keep it at 30 when wot.
