New software 3.056 available!

The black supports only PMU analog inputs 9-16, and they are mapped to CAN analog inputs 1-8.

This behaviour is the same as in V2. I try to make it more flexible for next version.

Okay but must the cam sensor level be constant during the whole missing tooth?
My scope shows a rising edge more or less exactly (but slightly too late) at 117thooth. So i was expecting it to be read as sensor level high during the gap.

Edit: It must be that slightly too late….when i initially tried it, it worked….but my engine was cold….probably there the timing was this 1 degree earlier and the function was working.

The state must be proper at the first tooth after the gap (where the dot is drawn)

In the next build there is solution for general settings window

I found the bug in crankcase pressure sensor proecudure. It will be fixed in the next build

The black supports only PMU analog inputs 9-16, and they are mapped to CAN analog inputs 1-8.

This behaviour is the same as in V2. I try to make it more flexible for next version.

That’s strange because I can manually assign PMU analogs 1-8 from 66A to black CANanalogs fine.

I would be great if the were more CANanalogs available on the black as I’ve currently used all 12 and would like to send more.

Then the function must be buggy somehow.
In my case i have a rising edge on the thooth befor the gap.

The next falling edge is far beyond the gap:

So the EMU says it is lvl low although it is defenitly lvl high at the first tooth after the gap.

Did you ssigned can analog inputs via user defined CAN?

The emu automatically reads 0x66b and assigned the values to can analog inputs. So I think it overrides yours values.

I’ve already add an option to disable rhis fearure, map pmu analog 1-8 to emu can analogs 1-8 or map pmu 9-16 to black 1-8

Still same bug v3 55 ok only 56c

Did you ssigned can analog inputs via user defined CAN?

Yes i have them manually assigned, i have some from PMU, some from ADU and some from switchboard so the more freedom there is the better.

It is possible that dark mode is not compatible with windows 7. The next build is planned on Monday/ Tuesday I will add a diagnostic to check.

What are your settings. I’ve tested it on the bench and works correctly. It is very simple algorithm that just read the signal level when the missing tooth is detected.

I’ve added signal edge ā€œBothā€ to make diagnostic easier.

Also the dots shows the level only when Sync with cam level is different than Disable

Please try to replace My Documents\EMU_BLACK_V3\config.xml wiht the config file attached. It disables dark mode.

Windows 7 doesn’t support dark mode so it is probably the reason it crashes.

config.xml (14.3 KB)

It will be tricky to fix. It is already on the list

The log time seems to show incorrectly when set to system time.

Viewing on the latest software 3.056c. Log was from 3.056b.

v3 log.emublog3 (434.1 KB)

Is there a channel that can be used in functions that corresponds to deltaRPM (RPM rate)?
I would like to implement the action of disengaging the A/C clutch when the RPM drops at a certain rate or more.

it seemds those spikes are on datalogger logs only…i will get the SD card next week

no problem with ecu beep sound, pc beep sound missing sometimes

I’m also seeing spikes in PW in my logs.
I’d like to know where this is coming from.

20250925_2309.emublog3 (4.0 MB)

Is this EDL log ? It looks like logging problem as no other parametrs indicate injectors PW spikes.