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.
These parameters shouldn't be changed from "stock" unless you really know what you're doing. "Stock" values are a byte delay of 2ms and timeout of 500ms for a V3 connection and byte delay of 30ms and timeout of 500ms for a V2 connection.
© 2002 - 2023 ECMTuning, Inc. All rights reserved.