This dialog configures how the application tries to establish a connection with the ECU.
Select the "first" port the ECMLink application should use when trying to connect with the ECU. If Remember last good port is checked, then the last good port (if any) will override the Initial port selection. If Scan ports for ECU is unchecked, then the Initial port is the only port the application will try to use.
If checked, the application will search through all configured ports to find an ECU connection. If unchecked, then the Initial port is the only port the application will try to use. For more details on how to configure which ports the application is going to scan, see the Port Configuration page (accessible via the Configure port... link on this dialog).
If checked, the application will override the Initial port selection with the last known good port, once one is identified. Basically, once a connection is established with the ECU, the application will remember which COM port was used to establish that connection and then always try to start with that port in future attempts.
Causes the application to aggressively try to establish a connection the ECU at all times. If this is selected, you may want to deselect the Show background status in status bar option on the preferences dialog. Doing so will hide the reconnection attempts from the status bar (which can be annoying if you're just trying to look at log files offline). Status text will still appear in the Device Status box on the main tab, however.
Configures the application to constantly poll the ECU connection in the background. This isn't generally useful and can cause some slightly annoying side effects (like getting an occasional Port Owned error when trying to connect the ECU because the background thread has the port momentarily). But if you like know when you have a good connection and when you don't, check this box.
This adjusts the bit rate at which the application will attempt to communicate with the ECU. This MUST agree with what the ECU is coded for. Stock 1G DSM MUT-II rate is 1952. If you have modified this to be 15625, then you'll need to enter 15625 into this field. Stock 97+ MUT-II rate is 15625. If you have selected MUT - 1997+ as your device type, then you need to set the bitrate field to 15625.
The stock MUT-II protocol requires that the initiating application indicate its desire to communicate with the ECU by pulling the diagnostic pin low. This triggers the ECU to configure the UART for communication and enables a few other conditions. ECMLink does this actively. That is to say, the application will only pull this pin low when it really needs to (just before sending a new command or while logging). The value in the Diag hold field is used to indicate how long you would like the application to hold the diag pin low before sending commands to the ECU. Unless you have a specific reason to adjust this behavior, it's probably best to leave this field alone.
Adjusts the time between bytes sent to the ECU and the time to wait for a command time out. In the standard MUT-II protocol, there is no inter-byte delay, so this field doesn't actually change much yet. The "hybrid" OBD2/MUT mode introduced in '95/'96 ECUs will make this field a little more useful. The timeout field is simply how long the application will wait for a reply from the ECU before giving up. There's really little reason to adjust either of these fields.
© 2002 - 2023 ECMTuning, Inc. All rights reserved.