Differences

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

--- web:features [2014/12/30 18:53] – admin
+++ web:features [2015/02/15 06:27] – admin
@@ Line 10: / Line 10: @@
 ^  Java-ME ((not maintained anymore, so only old, reduced command set available))  ^  Android  ^  Windows (and Linux & Mac((No installation pack available yet, needs to be compiled manually out of the repository)) ) |
 |  {{  :pics:oobdme-window.png?150  }}  |{{  :pics:diagnose.png?150  }} |{{  :swing_screenshot.png?437  }} |
+===== UDS compatible Telegram Support =====
+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.
@@ Line 44: / Line 52: @@
 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 65: / Line 84: @@
-{{: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
+{{: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>
+<xsl:template match="/">
+  <xsl:apply-templates/>
+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>