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
start [2014/03/02 08:52] – adminstart [2016/06/05 09:58] – [What is OOBD?] admin
Line 8: Line 8:
  
  
-OOBD (Open On Board Diagnostics) is a collection of open Source software and hardware for OBD Vehicle Diagnostics.+OOBD (Open On Board Diagnostics) is not a single hardcoded diagnostic application, its a runtime environment instead which gives you the flexibility to implement your own ideas, needs and wants. By supporting the hardware connectivity, diagnostic software library and a powerful User interface, you can fully focus on your problem without re-inventing the wheel again and again.
  
-Our target is to provide a flexible platform to do the most diagnostic tasks quick, handy and reliable. To do so, we've developed a whole set of applications, hardware and tools - and we still continue.. 
  
 +All your results (diagnostic functionality and user interface layout) can be packed into one single container file and shared and distributed and executed on both Desktop machines and Android mobiles.
 +
 +{{  :web:webui.png?800  }}
  
  
Line 20: Line 22:
  
  
-For all documents, please use the links [[:menu|Content]] and [[:doc:start|Manual]] provided in the header of each page.+For all documents, please use the links [[:start?do=index|Sitemap]] and [[:doc:start|Manual]] provided in the header of each page.
  
  
 ===== Features ===== ===== Features =====
  
 +As the feature list became to long for the main page, we moved it to the separate [[:web:features|Feature page]].
  
-    * Runs on Windows, Linux, MacOS, Android and JavaMe 
-    * The Application Menu lists and functions are not hardcoded, they are programmable by lua scripts, who do the menus and the whole data handling 
-    * some ODX dialects can be automatically translated into lua scripts ready to use - helpful when transforming module specifications 
-    * Own dongle with own firmware supports 
-      * full length UDS messages (4095Bytes) 
-      * selective buffering of real time can messages directly in the dongle to de-couple the mobile app from real time requirements 
-      * can inject mode to send whole frame sequences for data simulation 
-      * raw can mode 
-      * readout for rx/tx CAN error counter to measure bus quality 
-      * in field updateable via bluetooth 
  
  
-===== Several Platforms =====+===== Own Hardware - The CAN-Invader =====
  
  
-^  Java-ME ((partly)) </sup>  ^  Android  ^  Windows (and Linux & Mac((No installation pack available yet, needs to be compiled manually out of the repository)) ) | +Although the build plans are available in the OOBD repository, we do recommend to better buy a completely build & tested CAN invader device at our partner
-|  {{  :pics:oobdme-window.png?150  }}  |{{  :pics:diagnose.png?150  }} |{{  :swing_screenshot.png?437  }} |+
  
  
-===== Flexibility =====+[[http://caninvader.de|{{  :jatra_logo_mittel.jpeg?nolink&300  }}]].
  
  
-This is realized by control the functions by loadable (Lua) scripts.+It was found that there's a lot of experience and time needed to collect all parts and to solder the dongle by yourself. Especially for commercial applications it's more effective to directly order the complete units.
  
  
-==== Examples ====+{{  :house1.jpg?100  }}
  
- 
-Building the main menu: 
- 
- 
-<code lua>function Start(oldvalue,id) 
- identifyOOBDInterface() 
- setSendID("$7E8") -- set not UDS compatible sender (=answer) address for OOBD firmware 
- openPage("OOBD-ME Main") 
- addElement("Sensor Data >", "createCMD01Menu",">>>",0x1, "") 
-        addElement("Snapshot Data >", "createCMD02Menu",">;;>;;>;;",0x1, "") 
-        addElement("Dynamic Menu3 >", "createCMD03Menu",">;;>;;>;;",0x1, "") 
- addElement("Trouble Codes", "showdtcs","-",0x1, "") 
- addElement("VIN Number", "vin","-",0x2, "") 
- addElement("Clear Trouble Codes", "clearDTC","-",0x0, "") 
- addElement("System Info >>;;>;;", "SysInfo_Menu",">;;>;;>;;",0x1, "") 
- addElement("Greetings", "greet","",0x1, "") 
- pageDone() 
- return oldvalue 
-end 
-</code> 
- 
- 
-Reading the VIN number: 
- 
- 
-<code lua>function vin(oldvalue,id) 
- echoWrite("0902\r\n") 
- udsLen=receive() 
- if udsLen>0 then 
- if udsBuffer[1]==73 then 
- local pos=4 
- local res="" 
- while pos <= udsLen and pos < 36 do 
- if udsBuffer[pos]>31 then 
- res=res..string.char(udsBuffer[pos]) 
- end 
- pos= pos +1 
- end 
- return res 
- else 
- return "Error" 
- end 
- else 
- return "NO DATA" 
- end 
-end 
-</code> 
- 
- 
-===== Own Hardware - The CAN-Invader===== 
- 
- 
-Although the build plans are available in the OOBD repository, we do recommend to better buy a finished CAN invader device at our partner  
- 
-[[http://caninvader.de|{{  :jatra_logo_mittel.jpeg?300   |CANInvader.de}}]]. 
- 
-It was found that there's a lot of experience and time needed to collect all parts and to solder the dongle by yourself. Especially for commercial applications it's more effective to directly order the complete units. 
- 
- 
-{{ :house1.jpg?100 |}} 
  
 ===== About us ===== ===== About us =====
Line 152: Line 84:
 <html><!– Place this tag where you want the widget to render. –> <div class="g-post" data-href="https://plus.google.com/103009956802601954261/posts/18QqdLZKY6p"></div></html> <html><!– Place this tag where you want the widget to render. –> <div class="g-post" data-href="https://plus.google.com/103009956802601954261/posts/18QqdLZKY6p"></div></html>
  
-We also would like to thank our sponsors to support the OOBD idea:  [[http://www.hellermanntyton.de/|{{http://upload.wikimedia.org/wikipedia/de/thumb/7/70/HellermannTyton-Logo.svg/200px-HellermannTyton-Logo.svg.png?nolink&}}]]+We also would like to thank our sponsors to support the OOBD idea:  [[http://www.hellermanntyton.de/|{{https://de.wikipedia.org/wiki/HellermannTyton#/media/File:HellermannTyton-Logo.svg}}]]  
  
  
-<html><!– Place this tag in your head or just before your close body tag. –> <script type="text/javascript" src="https://  apis.google.com/js/plusone.js"></script></html>+<html><!– Place this tag in your head or just before your close body tag. –> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script></html>