New EMU PRO software version 261.2.1 release candidate (RC2)

New EMU PRO software version 261.2.1 (RC2) is now available.

— 261.2.1 (RC2) —

  • Fixed a UI bug introduced in Client 261.2 (RC1) that caused the menu below Idle / Air flow / Enable to disappear after upgrading the ECU firmware from an older version.
  • Note: Firmware version 261.2 included with Client 261.2.1 is exactly the same as the firmware included with Client 261.2. If you are already using 261.2 (RC1), only the Client needs to be updated - no firmware flashing is required.

— 261.2 (RC1) —

This update adds a couple of small client features and fixes several minor issues.

New features:

  • Added a menu command: Devices / Disconnect
  • Added a “Save DBC File…” button to the Project Tree / CANbus Transmit Frame

Fixes:

  • Fixed EMU PRO-8 compatibility with EGTtoCAN – all 8 channels now work correctly
  • Fixed a rare bug causing VE Tuner to show large negative numbers in the Proposed VE table
  • Fixed an issue where the Vehicle / Speed Limiter / Activation Custom Channel was not working correctly
  • Fixed a bug that prevented saving a password-protected project in offline mode (issue introduced in version 261.0)
  • Fixed an issue where the frequency of the “Engine Cylinders cut” channel was not loaded from a project file

Download the latest software update: https://www.ecumaster.com/testVersions.html

This is a release candidate — if no major issues are found, it will be promoted to a public release. We’d appreciate it if you could give it a try and let us know if you run into anything.

Sincerely,
The Ecumaster Team

I’m not sure if this is exclusive to 261.2.1

assigned colors for channels don’t stick when switching to different PCs

same SW version on both

PC 1
assign colors → Save Project + Save Log + Save desktop template

PC 2
Open Project + Open Log + Open desktop template → colors set to default

If PC 1 gets a full reboot, the colors do return as saved in the template

Also, not specific to this version, and probably not mission critical

Coolant Fans → vehicle speed max
and
Coolant Fans → temperature target error minimum

This should probably have some kind of hysteresis. When cruising around at that speed, the fan cycles quickly or at least often (depending on the delay time). Especially a problem with a PWM fan because there isn’t a “delay” time. It just picks up right where it left off unless it’s below the temperature target error minimum

for speed should probably be two parameters
vehicle speed to disable
vehicle speed to enable

For the temperature target error minimum with PWM control, I haven’t had any real world issues with that since that’s usually below the running temperature. The engine temperature passes that value quickly and then the PWM takes over at slow speed. For very powerful fans or very cold ambient temperature I could see that being a problem when even the minimum duty cycle is just too much airflow. It could theoretically bring the temperature down to that set value and hover there. Some hysteresis on that value would be more “generally good practice” than really required.

Want to avoid unnecessary relay/MOSFET load cycles if at all possible, especially when switching 30-60A

Hi, the colors aren’t saved in the project, log, or desktop template.

Instead, they’re stored in the logChannels.xml file under Documents\EMU_PRO. So when you switch PCs, the colors don’t transfer automatically. We may add a mechanism for that in the future — in the meantime, you can transfer this XML file manually.

Let me know if this solves your issue.

I’ll need to do some more testing in the car, but volume data from cylinder 7 and 8 seem to be missing. Engine is a v8 and runs normally, just reviewing logs this evening and noticed.


Bug reproduced. Thank you for reporting it.

Re: colors

This makes sense, yes, copying that file does the trick. It’s easy enough.

It begs the question, should channel colors follow the project, layout, or computer?

It was most surprising to me when it didn’t follow the layout, that seems to be the most intuitive.

We fixed this bug today. The fix will be included in the public release planned for next week.

The good news is that it’s a client-side bug - your log data was recorded correctly and will be available once you install the fixed release.