What do you exactly mean ? Actualy table DBW characteristic has pedal position on X axis and throttle position as a value
thank you, i didnt realise that.
Im more familiar with haltech terminology
V2 Importer،
Can’t import dbw settings and output assignments are you guys going to fix that?
Importer is not finished yet as stated in the first window after running this tool.
For next build it will import more data.
Right now you can look at the text log that appears after importing, to see what was imported and what you need to check (in red)
Oh ok sir,
Bless your efforts waiting to be completed then.
Cheers
Does the IgnitionAngle in the Ignition log window include the knock retard?
Thank you for your reply.
I thought it only worked that way when set to “PerCylinder”.
I dont like this solution as it is not intuitive. However to make it logical, there should be 8 ignition angle channels, 1 per cylinder.
Any one can tell me why idle hangs up at approx.. 1200rpm at 3% dbw and its not entering idle state?
its hapening 70% off times.
idleprob.emub3 (72.6 KB)
idleprob.emublog3 (31.9 KB)
At 3% it keeps at 1200 so it is too much.
Adjust the Armed state airflow table
Also your ramp down max offset is very low, Typicaly it is 300-500 or more RPM.
1 Like
whell i tried lower air flow table it still was rock solid at 1200rpm and 3%, tomorrow will test again and make log.
i can brake with clutch engine and get lower rpm then it will idle normally.
cranking ignition angle parameter is hidden again
1 Like
“Porsche997.1” can be selected in the CAN-Bus stream in the EmublackV3 software. Is there any information on what is being sent?
0x242 - RPM
EMU also receives wheel speeds from the standard ABS via 0x24A.
The issue with sending any other data (CLT, etc) is some of the other IDs contain MUX messages which the EMU cannot replicate as they are vehicle model/specification specific.
Is it still not possible to replace the original ECU like with the G4X?
I really hope that in the future I’ll be able to run the 987/997 with Ecumaster (or just EmuPro).
Yes, of course, I have ran 987 on EMUBv3 for over a year now. You just have to find another way (hardware) of replicating the missing messages the standard ECU broadcasts specific to your vehicle, otherwise you’ll have an ‘Electrical System Fault’ on the dashboard all the time. By messages specific to the vehicle, it contains the VIN, engine type, transmission type, and so on.
I don’t know anything about the G4X, or of anyone using it and the CAN confirmed working, would be interested to hear that though, and if the rest of the car is 100% functional.
I know what is required to be on the CAN, and have a fully functional cluster with no faults 
Sorry to talk about other manufacturers.
When I heard that the G4X supported 987/997 at the time, I inquired immediately.
It will probably be some time before I install it in my vehicle, but at that point I will choose the ECU to use.
I can provide @Jadzwin_ECUMASTER with all the above CAN information to add into the EMUBv3 9x7 stream, however they are simply status flags, no actual data other than wheel speeds and two pressures. There is also no RPM listed?
Also notice how there is no coolant temperature listed? That’s because it has the encoded chassis data in the same message. Your ABS will not work without that message being present and correct. I know this from first hand experience.
There is also no oil temperature listed - this is used in the calculation of the oil level by the instrument cluster. Strange, because that value is sent alongside oil pressure, which they do list. I’d be interested to know about someone actually using the above stream, as from my own experience the bottom statement is incorrect
Sorry, I’m not an expert on this at all.
When I looked at Aim’s documentation, I thought that ME7.8 sent other data via OBD.