EDT setup

From EMIT Controls

The EDT does not have many settings, but a details can found on this page.

On the EIM, the EDT setup is on the EDT home page followed by "Setup". On the DCT, the setup is found under "Settings" - "Data Translator".

Mode

Edt setup adem4.png EDT Setup page in ADEM mode

The top box of the EDT setup page is the "Mode". This defines what type of engine the EDT is talking to, and how it will communicate.

  • ADEM 3/4: The EDT will snoop (read) data from both the CAN and CDL busses and report any value it can find. There are not any other settings when in this mode since the EDT reads any data it can find.
  • ADEM (Send CAN Requests): The EDT will snoop (read) data from both CAN and CDL busses. Additionally, the EDT will write out requests for certain data values via the CAN bus. I.e., the EDT will ask the engine via CAN to send some data that isn't already being sent.
  • ADEM (Send CDL Requests): The EDT will snoop (read) data from both CAN and CDL busses. Additionally, the EDT will write out requests for certain data values via the CDL bus. I.e., the EDT will ask the engine via CDL to send some data that isn't already being sent. The EDT will ask for specific values that are commonly needed (such as manifold pressure), and any data that has been requested via the slave modbus port(s).
  • Wauk. ESM: The EDT will use the Modbus master port to request expected data from the Waueksha ESM engine controller
  • Wauk. ESM2: The EDT will use the Modbus master port to request expected data from the Waueksha ESM2 engine controller
  • ATV71 VFD: The EDT will use the Modbus master port to request expected data from the ATV71 VFD
  • Motertech Detcon: The EDT will request detonation information from the Motortech Detcon via CAN and report the results to the ignition for timing adjustment
  • MV1000 VFD Ethernet: The EDT will use the ethernet port to request data from an MV1000 motor drive
  • EICS: The EDT will use the Modbus master port to request expected data from a Murphy EICS controller
  • ASC RS-485: The EDT will use the Modbus master port to request expected data from an Ariel Smart Compressor. Note: if ethernet is used instead with the ASC the setup will be under system settings - ASC Setup
  • Modbus Slave Only / Off: This will disable the EDT and hide the EDT tab on the home page.

Additional Settings

Modbus

If using a modbus mode (ESM, ESM2, EICS, etc.) some additional settings will appear.

Edt esm2.png

  • Target Modbus ID: This specifies the modbus ID or slave address of the engine controller. This needs to match the setup on the engine controller. This is usually adjustable on the controller via a service tool or through the OEM screen.
  • Baud rate: This specifies the modbus baud rate for the engine controller. This needs to match the setup on the engine controller.
  • Line Control Mode: This specifies the control mode / bit format for the modbus line. This needs to match the setup on the engine controller.

Other Mode-Specific Settings

  • Number of Cylinders (ESM and ESM2 only): This specifies the number of engine cylinders. Since the ESM has registers for all possible cylinders, this setting will hide cylinders that are not present.
  • Rated power (ESM2 only): This specifies the current rated power of the engine, from EngCalc. The EDT uses this to calculate the displayed percent load.
  • Transmit bit delay (CDL request mode only): This specifies the amount of time the bus should be clear before the EDT should attempt a transmit. Higher numbers will lead to less comm issues but slower updates.
  • TCP settings (MV1000 only): This specifies the IP address, port, and slave ID of the vfd drive. These need to match the settings on the VFD controller.