Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
web:features [2014/12/30 18:51] – adminweb:features [2016/06/05 09:40] – admin
Line 2: Line 2:
  
 The OOBD tool set contains a wide range of features and functionality. Some of it is part of the main applications, some others are done with additional software. All these functions are in permanent development, so some of them are still in beta state. The OOBD tool set contains a wide range of features and functionality. Some of it is part of the main applications, some others are done with additional software. All these functions are in permanent development, so some of them are still in beta state.
 +
 +===== Web based User Interface =====
 +
 +With the upcoming 1.0 release OOBD is controlled through the web browser. This gives nearly unlimited flexibly in the look & feel of the user interface
 +
 +You can create your own theme and choose between. 
 +
 +
 +The default theme already includes the standard functions, so you can write simple scripts without the need of writing any HTML colde
 +
 +{{  :web:webui_defaulttheme.png?400  }}
 +
 +
 +By including other popular libraries like e.g. jQuery, you can make simple responsive UIs like this
 +
 +{{  :web:webui_dtcs.png?400  }}
 +
 +or use pretty graphical elements like gauges and meters
 +
 +{{  :web:jqwidgets.png?400  }}
 +
 +Or you can create your own custom style like this 3D three.js sample
 +
 +{{  :web:3d_fiesta.png?400  }}
 +
 +===== Remote Connect =====
 +{{:doc:kadaver.png?200 |}}Just with a Google Chrome Browser + the [[:doc:tools_kadaver|OOBD Chrome Add-on]] or the Kadaver Android App you can connect to a dongle  everywhere in the world via internet and do the diagnostics comfortable from your home desk.
 +
 +
 +
  
  
Line 12: Line 42:
  
  
 +===== UDS compatible Telegram Support =====
  
-=== Full programmable with loadable, precompiled lua scripts ===+In opposite to many other dongles, OOBD support the full module address range and the full 4095 Byte data length. All the protocol handshake is done by the dongle itself, only the final answer of the communication with the module is reported back to the application. 
 + 
 +===== No Real Time Requirements ===== 
 +The dongle does all the real time data handling by itself. The finished result can be then picked also by e.g. slow mobile devices without the hassle of strong real time requirements. 
 + 
 + 
 + 
 +===== Full Programmable With Loadable Lua Scripts =====
  
  
Line 44: Line 82:
 For easy integration into other projects the [[:doc:rfc_firmware_syntax|dongle command syntax]] is powerful, but simple and easy to parse For easy integration into other projects the [[:doc:rfc_firmware_syntax|dongle command syntax]] is powerful, but simple and easy to parse
  
-===== No Real Time Requirements ===== + 
-The dongle does all the real time data handling like the complete UDS telegram transfer. The finished result can be then picked also by e.g. slow mobile devices without the hassle of strong real time requirements.+===== Graphical Programming Interface ===== 
 + 
 +{{:doc:qs_screenshot.png?200 |}} 
 + 
 + 
 + 
 +Simple Diagnostic programs and command sequences can be generated just in minutes with [[doc:tools_quickscript|OOBD QuickScript]] and it's graphical programming Interface, fully running in a Web Browser 
 + 
 + 
 +===== openXC Data Source ===== 
 + 
 +{{:doc:openxc_enabler.png?200 |}}{{:doc:openxc_oobd.png?200 |}} OOBD can also act as Data Source for [[http://openxcplatform.com/|openXC]] and so for any application which uses the openXC interface.
  
  
Line 55: Line 104:
  
  
-===== Remote Connect ===== 
-{{:doc:kadaver.png?200 |}}Just with a Google Chrome Browser + the [[:doc:tools_kadaver|OOBD Chrome Add-on]] you can connect to a dongle in a car everywhere in the world via internet. 
  
 +===== ODX Translator =====
  
  
 +{{:doc:opendiagx-screenshot.png?200 |}}Some ODX dialects can be automatically translated into lua scripts, ready to use - helpful when transforming module specifications. If your input format is different, just adapt the xslt transformation
 +<code xml>
 +<?xml version="1.0" encoding="ISO-8859-1"?>
 +<xsl:stylesheet version="1.0"
 +xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  
 +<xsl:template name="trim4">
 +<xsl:param name="string" select="'left'" />
 +<xsl:value-of select="substring(concat('0000',normalize-space($string)), (string-length(normalize-space($string))+1))"/>
 +</xsl:template>
  
-===== ODX Translator ===== 
  
 +<xsl:template match="/">
 +  <xsl:apply-templates/>
  
-{{:doc:opendiagx-screenshot.png?200 |}}Some ODX dialects can be automatically translated into lua scripts ready to use - helpful when transforming module specifications. If your input format is different, just apapt the xslt transformation+dofile("../../tools/lib_lua/serial_dxm.lua") 
 +dofile("../../tools/lib_lua/lua_utils.lua") 
 +dofile("../../tools/lib_lua/luabit/bit.lua") 
 +dofile("../lib_protocol/standard-uds.lua") 
 +dofile("../lib_protocol/secaccess.lua") 
 +dofile("../lib_protocol/module-uds.lua") 
 + 
 +</xsl:template> 
 +<xsl:template match="oobdobx"> 
 +moduleName = '<xsl:value-of select="./Name"/>' 
 +shortName = '<xsl:value-of select="./ShortName"/>' 
 +</code>