TOBD2 Application
From Tallus LLC Wiki
Contents |
About
TOBD2 is an application that supports integration of MainLobby or CQC into your post 1996 vehicle.
MainLobby and CQC can then be used to create a "digital dashboard".
All of the typical core vehicle data is accessible including:
Tachometer
Speedometer
Ignition state
Coolant temperature
Battery Voltage
Ambient temperature
etc.
There is also means on many vehicles to control vehicle functions like lights, and even HVAC controls.
TOBD2 is currently in Beta development phase.
About Beta Testing
System Requirements
MainLobby3 Server v 3.75.14 (and newer)
MainLobby 3 Client v 3.0.85 (and newer)
TOBD2 Vehicle Gateway Application v 0.0.9 (and newer)
TOBD2 compliant vehicle interface hardware:
Coming soon: Vehicle device info at [Vehicle Interfaces]
Installation
Download and run the TOBD2_Plugin_Setup.exe on the PC that will be physically connected to the vehicle interface hardware (if USB or Serial based hardware interface). The software can run on any network connected PC if using an Ethernet (wired or wireless) hardware interface.
Connection path:
Vehicle Interface Serial device (DB9 or USB):
Vehicle Diagnostic port <> Vehicle Interface cable for that type vehicle <> Vehicle Interface hardware <> serial cable <> PC serial port <> TOBD2 application <> TCP (wired or wireless) <> MLComDevice or CQC FieldGenerator <> MainLobby Server or CQC Server <> MainLobby client or CQC user interface
Vehicle Interface wireless ethernet device:
Vehicle Diagnostic port <> Vehicle Interface cable for that type vehicle <> Vehicle Interface hardware <> WiFI wireless <> WiFi router or PC card <> wired ethernet <> PC ethernet port <> TOBD2 application <> TCP (wired or wireless) <> MLComDevice or CQC FieldGenerator <> MainLobby Server or CQC Server <> MainLobby client or CQC user interface
The vehicle diagnostic port is a standard connection on 1996 and newer US certified passenger vehicles. It is physically located within one foot of the steering wheel column. Each vehicle has it located in it's own unique spot, typically just under the dashboard. It looks like a 3 inch by 1 inch "parallelogram" shaped connector. It's original purpose was to support repair shop diagnostics scan tool connection.
Configuration
MLComDevice Configuration
Start by installing MLComDevice (if not already). You should see a TOBD2 family in the "Known" devices listing.
Add TOBD2 Family as a new device and call it : TOBD2 (for documentation naming consistency). Click TCP checkbox and add the PC's IP address where TOBD2.exe will be installed. Port 9850 should be used unless there is a known port conflict on either the MLServer PC, or the TOBD2 PC (if different PCs). Encoding should be UTF8 choice.
Click Save as New button to create the new TOBD2 device. You can now Enable it by deselecting the Disable checkbox and clicking Save button. In the Events tab, you should see that the new TOBD2 device is live on the network awaiting connection to TOBD.exe application (on port 9850).
Install Ease Configuration Software
Install the Device Configuration Utility software. Plug the Vehicle hardware's USB or DB9 serial cable into that PC. Run the application and choose the appropriate comport (if serial) or the appropriate ethernet / WiFi settings. Send these settings to the Device hardware. The hardware can now be unplugged and replugged into the vehicle. If Wifi, the WiFi LAN also needs to be configured to properly connect to the device.
Configure TOBD2 to connect to the Vehicle Interface hardware
Start the TOBD2 application. In the Profiles tab, select what type of Vehicle Interface hardware interface to be used. These settings were established and managed by the Vehicle Interface Configuration Software (not TOBD2). You should see the corresponding comport: port and / or ethernet / WiFi settings for the hardware. Make sure these are the same settings that the Vehicle Interface hardware interface is using. You may also need to configure the firewall and antivirus settings to allow connection to that device on the chosen port. The default port for Vehicle Interface devices is 4000 and should be used unless there is a conflict.
Click the Populate button. You should see information on the Interface Info tab that it is connected and hardware information that is extracted from the Vehicle Interface hardware.
Configure TOBD2 to connect to MLComDevice
Click on TOBD2's Polling tab. Select MainLobby Enable and port 9850 should be preset. You can also change the default vehicle polling settings and to initiate polling from the vehicle when TOBD2 is first launched. Click Save once you are done with your choices. Once you save your choices, TOBD2 should connect to MLComDevice if all your network settings are correct. You should see the connection in both TOBD2's Events Tab, as well as in MLComDevice's Events tab. The initial extracted data from the vehicle (extracted when you clicked the Get Data button) should have been sent to MLServer which should have created new variables in MLServer.
Tuning Polling in TOBD2
To achieve a balance of getting good responsiveness on vehicle data that changes quickly and is important to see those changes (typically: RPM, MPH, O2 feedback) and getting too much data that reduces overall performance, TOBD2 allows you to tailer how often vehicle data elements get updated. To configure this feature, connect to a vehicle and click the Get Data button. The Vehicle data tab should now populate. If there is an entry in the Last value column, then that data element is likely supported by the connected vehicle. If you right click on a data element that has a value, you can choose: Fast / Medium / Slow / Initial / No Polling / Cancel.
For important data that changes quickly, choose Fast. For data that doesn't change quickly (like ambient temperarture) choose Slow. For data that you only want to grab on initial vehicle connection, and do want to create a MLServer variable with that value (like OBD Type), choose Initial. For data that you don't care to ever receive (like data not supported by your vehicle), choose No Polling.
Note that there are limits to how much data the vehicle can send in any given time frame. Selecting all atributes as "Fast", will ultimately get all data "Slow" as there will be a bottleneck. MLServer can also get tied up with too many data elements. You can also tailer the polling by selecting how fast is Fast in the Polling tab. Fast by default is provided every 500 milliseconds (half a second). Medium every 5 seconds and Slow every 1 minute.
Using Vehicle data in MainLobby
With TOBD2, you can create a digital dashboard for your vehicle. With MainLobby's extensive library of graphics, you can create a retro / modern / or totally custom look to your dashboard. Just view the variable list in MLServer and you can see the naming convention for each element.
Supported MLServeCmds
Clear DTCs
MLComDevice|TOBD2~Send~FieldChanged|ClearDTCs
Unlock_Door
Syntax is:
MLComDevice|TOBD2~Unlock_Door:FrontLeft
Supported MLServer Variables
tobd2_jeep1_a/csystemrefrigerantmonitor = Not Supported
tobd2_jeep1_a/csystemrefrigerantmonitorcycleenabled = Disabled
tobd2_jeep1_a/csystemrefrigerantmonitorcyclestatus = Complete
tobd2_jeep1_absoluteloadvalue = 15.29
tobd2_jeep1_absolutethrottleposition = 13.3
tobd2_jeep1_absolutethrottlepositionb = 12.9
tobd2_jeep1_absolutethrottlepositiond = 8.6
tobd2_jeep1_absolutethrottlepositione = 4.3
tobd2_jeep1_ambientairtemperature = 108
tobd2_jeep1_barometricpressure = 14
tobd2_jeep1_calculatedload = 24.7
tobd2_jeep1_catalystmonitor = Complete
tobd2_jeep1_catalystmonitorcycleenabled = Enabled
tobd2_jeep1_catalystmonitorcyclestatus = Not Complete
tobd2_jeep1_catalysttemperaturebank1,sensor1 = 878.0
tobd2_jeep1_catalysttemperaturebank2,sensor1 = 878.0
tobd2_jeep1_commandedegr = 0.8
tobd2_jeep1_commandedequivalenceratio = 0.999
tobd2_jeep1_commandedevaporativepurge = 26.7
tobd2_jeep1_commandedthrottleactuatorcontrol = 2.4
tobd2_jeep1_comprehensivecomponentmonitor = Complete
tobd2_jeep1_comprehensivecomponentmonitorcycleenabled = Enabled
tobd2_jeep1_comprehensivecomponentmonitorcyclestatus = Complete
tobd2_jeep1_controlmodulevoltage = 14.28
tobd2_jeep1_distancesincedtcscleared = 13208
tobd2_jeep1_distancetravelledwhilemilisactivated = 0
tobd2_jeep1_egrerror = 63.84
tobd2_jeep1_egrsystemmonitor = Complete
tobd2_jeep1_egrsystemmonitorcycleenabled = Enabled
tobd2_jeep1_egrsystemmonitorcyclestatus = Not Complete
tobd2_jeep1_emissionrelateddtccount = 0
tobd2_jeep1_enginecoolanttemperature = 203
tobd2_jeep1_enginerpm = 594
tobd2_jeep1_evaporativesystemmonitor = Complete
tobd2_jeep1_evaporativesystemmonitorcycleenabled = Enabled
tobd2_jeep1_evaporativesystemmonitorcyclestatus = Not Complete
tobd2_jeep1_ffpidcapabilities = 7FBE8003
tobd2_jeep1_fuellevelinput = 18.8
tobd2_jeep1_fuelsystem1 = Closed loop - using oxygen sensor(s) as feedback for fuel control
tobd2_jeep1_fuelsystem1status = Closed loop - using oxygen sensor(s) as feedback for fuel control
tobd2_jeep1_fuelsystem2 = Closed loop - using oxygen sensor(s) as feedback for fuel control
tobd2_jeep1_fuelsystem2status = Closed loop - using oxygen sensor(s) as feedback for fuel control
tobd2_jeep1_fuelsystemmonitor = Complete
tobd2_jeep1_fuelsystemmonitorcycleenabled = Disabled
tobd2_jeep1_fuelsystemmonitorcyclestatus = Complete
tobd2_jeep1_heatedcatalystmonitor = Not Supported
tobd2_jeep1_heatedcatalystmonitorcycleenabled = Disabled
tobd2_jeep1_heatedcatalystmonitorcyclestatus = Complete
tobd2_jeep1_ignitiontimingadv.cyl.1 = 13.0
tobd2_jeep1_intakeairtemperature = 124
tobd2_jeep1_intakemap = 9.74
tobd2_jeep1_longtermfueltrimb1 = 5.47
tobd2_jeep1_longtermfueltrimb2 = 5.47
tobd2_jeep1_milstatus = OFF
tobd2_jeep1_misfiremonitor = Complete
tobd2_jeep1_misfiremonitorcycleenabled = Disabled
tobd2_jeep1_misfiremonitorcyclestatus = Complete
tobd2_jeep1_numberofwarm-upssincedtcscleared = 255
tobd2_jeep1_o2b1/s1outputvoltage = 0.565
tobd2_jeep1_o2b1/s2outputvoltage = 0.545
tobd2_jeep1_o2b2/s1outputvoltage = 0.665
tobd2_jeep1_o2b2/s2outputvoltage = 0.270
tobd2_jeep1_o2location = 33
tobd2_jeep1_obdtype = OBD (Federal EPA)
tobd2_jeep1_oxygensensorheatermonitor = Complete
tobd2_jeep1_oxygensensorheatermonitorcycleenabled = Enabled
tobd2_jeep1_oxygensensorheatermonitorcyclestatus = Not Complete
tobd2_jeep1_oxygensensormonitor = Complete
tobd2_jeep1_oxygensensormonitorcycleenabled = Enabled
tobd2_jeep1_oxygensensormonitorcyclestatus = Not Complete
tobd2_jeep1_relativethrottleposition = 2.4
tobd2_jeep1_rtpidcapabilities = BFBEB993
tobd2_jeep1_secondaryairmonitor = Not Supported
tobd2_jeep1_secondaryairmonitorcycleenabled = Disabled
tobd2_jeep1_secondaryairmonitorcyclestatus = Complete
tobd2_jeep1_shorttermfueltrimb1 = -3.13
tobd2_jeep1_shorttermfueltrimb1/s1 = -3.91
tobd2_jeep1_shorttermfueltrimb1/s2 =
tobd2_jeep1_shorttermfueltrimb2 = -3.91
tobd2_jeep1_shorttermfueltrimb2/s1 = -3.91
tobd2_jeep1_shorttermfueltrimb2/s2 =
tobd2_jeep1_timesinceenginestart = 771
tobd2_jeep1_vehiclespeed = 0