If you experience communication issues with the device, please restart your computer. We have noticed that these problems are caused by the Windows USB driver. We are working on reproducing and resolving this issue.
Change log:
TC: Rotary switch disable adj. pos bug fixed
CC: Improved and fixed
GEARSHIFT: Blip level table changed to 3D (gear vs RPM)
ACCENRICH: 3D acc enrich correction table added
ACCENRICH: Acc enrich async bug fixed (extremely long injection times)
IDLE: Idle RPM increase table Y axis range increased
FF: Sensor status added (disabled, error, ok)
PADDLESHIFT: Paddle shift status Rejected - gear unknown added
FUEL: Fuel rail models modified. New log channels added Effective fuel pressure, Fuel pressure error. See Help for more details
FUEL: Fuel pressure protection strategy adjusted to new fuel pressure conepction
FREQOUT: Frequency output support fixed
SENSOR: Turboshaft speed configuration modified (Num blades and divider)
USER FN: Support for Imperial units in user functions
USERCAN: Improved math precision of exported channels
USERCAN: Possible buffer overrun bug fixed
CAN: Unification of E46 and Mini Cooper CAN, CAN Switches assignment changed (see Help for CAN setup)
BOOST: Engine oil temperature limit indication on X axis corrected from IAT to OILT
LOG: IAT F. correction flag fixed
LOG: CAM1/2 Signal Present bug
LOG: Log group windows sorted and its behaviour modified
LOG: Merging EDL-1 files fixed
LOG: Fixed different frequency channels time offset
LOG: CAM1 input level channel fixed
LOG: kPa g is converted to psi g if imperial units selected
LOG: PIT limiter Inj cut source flag added
HELP: CAN BUS help work in progress
HELP: Feul rail types
Just to clarify - Using a fixed 4 bar fuel pressure regulator, and a fuel pressure sensor at the rail - Ideally I should set my base pressure to 400 kPa g, and type to BARO Referenced + Fuel Pressure Sensor, correct?
Exactly. Check the log for fuel pressure error. It should be near 0 as the pressure should be constant 4 bar (small fluctuations will be on the sensor for sure)
I try to add new channel ‘Effective Fuel Pressure’ to User CAN Stream, but it somehow changes ‘Analog 3’ when you press OK: The other new channels are fine. I will log with laptop for now
This channel has index 514. The data structure for user CAN allows to use 512 channels.
It will be fixed for next build. Now there is no possibility to CAN export the following channels:
Effective fuel pressure
Paddle hold switches
Paddle shift status
I can’t connect to Black after upgrading client from 3.0.32. Every time I connect USB, client (3.033) crashes with bug report (already sent to v3@ecumaster.com).
Try to go to General options and uncheck Load ECU desktops.
Then try to connect.
If you will be able to connect without loading desktops please send me the following files:
desktops.xml
desktops.emublayout
from My Documents/EMU BLACK V3/YOUR ECU NAME/ directory
In 3.033 version there is a new code for log groups windows management.
That could possible make an issue.
Having issues with Rev Matching. Spent the day today trying to get it working but suffering with multiple blips from the throttle. In some places it’s opening the throttle again once the gear is selected and bringing the clutch up causing the car to launch forward.
Addtionally one of the time it’s rev’ed the engine to 8350rpm when the limit is 7000rpm and the max match is 6970.
I have attached a screen shot of on of the instances including the settings but I’ve tried all sort of combinations of delays.
I have noticed the rev match target only appears on the graph part way through the sequence.
Screenshot of my old set up on V2 which worked flawlessly. I did start by copying these values over but get the same multiple blips.
I have double checked the gear ratios and tried a ratio tolerance between 2% and 8%.
When you are connected the EMU Client uses file definitions from 3.028 version.
There was a bug in Short term trim correction channel definition. That causes the Autotune issues.
Any updates on the Rev matching issue or the Map compensation for the ACC correction posted above? Have these been corrected in the latest version released?
