Scope Utility

Emtron features a built in Scope for all ECU types except the Shadow 8. Depending on the ECU (or if a plug in model – the type it is based off of), the number of channels that can be scoped is variable:

The scope function records the channels assigned to internal memory when started/stopped.

The memory can be subsequently downloaded, erased, saved, and loaded by the other buttons in the scope tools.

Utilities > Scope

When you select Scope, it opens a new window with the Scope.

Configuration details are as follows:

Purple:

Select what channel to display, and whether you want the trace to be visible or not

Red:

Change the volts per division for each channel

The chart is divided in blocks up and down. Each block equals 2 volts in the above example.

Orange:

The traces can be offset so they do not overlay on top of each other. The default value is 0.00V, meaning the voltage will trace from the centre (so it will read +/- 0V). It is useful to offset the traces, so they can be all visible at the same time on the chart as in the above example.

Green:

Sec Offset moves the trace to a specific position

Blue:

Time Sec Per Div changes the zoom level of the scope by adjusting the time per division horizontally. Like voltage per division vertically. After starting and stopping the scope, this will need to be adjusted until a trace draws an appropriate picture as in the example above.

Light Blue:

Sample Rate should be adjusted to set the scope recording rate. In most cases the default value of 10ksps should be enough, but if scope traces are requested for troubleshooting purposes (on running engines for example – not just for trigger decoding requests), then a higher speed may be requested.

** Note a higher sampling rate will use up the Emtron internal memory much faster. A shorter period of recording should be anticipated (a few seconds generally).

Scope Voltage Clipping

The scope can only read +/- 25v. Anything over 25v (regardless of input specifications) will display signals that can be misconstrued as error.

Above is an example of the scope “clipping” over its 25v limit.

This is normal and should not be considered an error in signal.

Troubleshooting Trigger Errors

There are several runtimes the ECU generates to diagnose/validate triggers the ECU is using. You can see these runtimes live under:

F3 Runtimes > Triggers/Limits, Engine Decoding/Engine Decoding Status

Green runtimes simply are notifications that there is a “signal” present on these inputs. They do not signify if the signals are valid.