We appreciate the valuable contributions from everyone who helped improve this version.
We’re proud to announce the new EMU PRO 214.0 beta software update. This update brings multiple improvements:
Improvements:
Simplified configuration of the second high-pressure pump
Enhanced scope graph visualization for high-pressure pump events
Fixes:
DSG (PQ35) is working correctly again (fixed issue introduced in FW 212.0)
GDI support is compatible with all EMU PRO units; however, an external GDI Driver is required to control the injectors. The Ecumaster GDI Driver will be available for purchase starting January 17th.
Tuning a GDI engine is a complex process that requires advanced tools and significant effort. To assist you, we’ve prepared detailed documentation, including a “How-to” guide, GDI Driver pinout, and a comprehensive manual covering wiring, installation, Light Client settings, and SENT communication:
Regarding the dq500 PQ35 issue
I’ve done another 50km of daily tests and the DSG part is fine now.
But every new USB log is flagged as having “corrupted data” after the update.
I noticed that logs still open if you load the GDI log example first. It throws an error but the log is there and valid (VE tuner works and all that).
If I open any of my new logs first - I get no data.
Not much of a blocker with the workaround but still.
Opening any old logs (pre-2.xx) is ok.
Same USB flash, same wiring - no changes.
I can attach any data if needed.
also. EMU PRO client hangs every time I reconnect to my ECU without clearing the log. It has always been like that for me. Please have a look. Both of my laptops are affected
also also Could you enable negative numbers in short term trim → engine coolant temperature min?. It’s my daily swapped car and negative temperature is very much expected in the future
One more Question regarding the DSG part. Do you send all wheel speeds to the TCU (abs emulation enabled)?
My DSG is in the RWD configuration and I’m not sure how it’s going to handle the wheel speed difference (driven/undriven). I’m routing wheel speed sensors backwards just in case but it’s probably going to be an issue with traction control in the future
regarding the Crashes.
It’s more of a hang - it gets completely unresponsive so I have to force close the app. So It’s not caught by the bugtrap.
As if it tries to add the lost time to the timeline or something.
And maybe there’s some P\N of PULS oil level sensor I can use?
I have 2 Hella level/temp sensors from 2 different Honda vehicles (k20c1 and j35a8) and one random VAG Hella sensor that don’t work. Different protocol apparently
Please send us additional logs and share them via a Dropbox or Google Drive link. The log you previously sent appear to be broken in an unusual way. We need to review more logs to verify whether the issue is consistent across all of them.
Possible to add an input for cold junction thermocouple correction? I’m aware there’s a sensor for that internal to the Pro’s but I prefer to make the cold junction at a bulkhead connector and use an analog input for an rtd sensor to compensate.
I typically use CAN based thermocouple amps for this reason and locate them in the engine bay, as its cheaper then maintaining the thermocouple all the way to the ECU when using a bulkhead connector.
We were not able to reproduce your issue. Please record a video demonstrating the problem. You can also try resetting your project to the default settings via “File / Reset to Default” to check if the issue occurs in a blank project or if it is related to your settings.
(Remember to save a backup of your project before resetting to default.)
Sure, we can include such a correction in the future. For now, we are focused on the launch of GDI support on January 17th, prioritizing modifications to GDI features and bug fixes only.
