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 [2013/02/14 21:11] – old revision restored adminstart [2014/12/30 15:29] admin
Line 1: Line 1:
-{{  :oobd_3d_white_320.jpg  |}}+{{  :oobd_3d_white_320.jpg  }}
  
  
 +====== Welcome to OOBD ======
  
  
-====== Welcome to OOBD  ======+===== What is OOBD=====
  
  
-<php> +OOBD (Open On Board Diagnosticsis a collection of open Source software and hardware for OBD Vehicle Diagnostics.
-$hostname = gethostbyaddr($_SERVER['REMOTE_ADDR'])+
-#echo $hostname; +
-if (preg_match('/ford\.com$/i', $hostname)>0){ +
-   #echo "I'm inside Ford:"; +
-   #echo $hostname; +
-   }+
  
-</php> 
  
 +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..
  
-===== What is OOBD? ===== 
  
-When you are familiar with Vehicle Diagnostics, you know: You have 100 problems, and for each problem you've your own software, an own dedicated hardware and some dedicated hardware drivers to deal with that particular task.+===== Quickstart =====
  
  
-To get out of this hell of tools, the target of OOBD is to provide an open framework as one single programwhich is able to handle all kinds of diagnostic problems by having a flexible plug-in interface for all type of requests, visualizations and hardware.+To downloadinstall, setup and run the softwareplease follow the instructions for [[:doc:startup_android|Android]] or [[:doc:startup_windows|Windows]]. 
 + 
 + 
 +For all documents, please use the links [[:start?do=index|Sitemap]] and [[:doc:start|Manual]] provided in the header of each page. 
 + 
 + 
 +===== Features ===== 
 + 
 + 
 +    * 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
  
  
Line 29: Line 41:
  
  
-^  On Java-ME ^  On Android:   +^  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  |}} +|  {{  :pics:oobdme-window.png?150  }}  |{{  :pics:diagnose.png?150  }} |{{  :swing_screenshot.png?437  }} |
-^  On Windows (and Linux & Mac((No installation pack available yet, needs to be compiled manually out of the repository)))  ^^ +
-|{{  :swing_screenshot.png?437  |}}||+
  
  
Line 38: Line 48:
  
  
-This is realized by not to have hardcoded functionality, but to control the functions by loadable (Lua) scripts.+This is realized by control the functions by loadable (Lua) scripts. 
 + 
 + 
 +==== Examples ==== 
  
 Building the main menu: Building the main menu:
-<code lua> 
  
-function Start(oldvalue,id)+ 
 +<code lua>function Start(oldvalue,id)
  identifyOOBDInterface()  identifyOOBDInterface()
  setSendID("$7E8") -- set not UDS compatible sender (=answer) address for OOBD firmware  setSendID("$7E8") -- set not UDS compatible sender (=answer) address for OOBD firmware
  openPage("OOBD-ME Main")  openPage("OOBD-ME Main")
  addElement("Sensor Data >", "createCMD01Menu",">>>",0x1, "")  addElement("Sensor Data >", "createCMD01Menu",">>>",0x1, "")
-        addElement("Snapshot Data >", "createCMD02Menu",">>>",0x1, ""+        addElement("Snapshot Data >", "createCMD02Menu",">;;;>;;;>;;;",0x1, ""
-        addElement("Dynamic Menu3 >", "createCMD03Menu",">>>",0x1, "")+        addElement("Dynamic Menu3 >", "createCMD03Menu",">;;;>;;;>;;;",0x1, "")
  addElement("Trouble Codes", "showdtcs","-",0x1, "")  addElement("Trouble Codes", "showdtcs","-",0x1, "")
  addElement("VIN Number", "vin","-",0x2, "")  addElement("VIN Number", "vin","-",0x2, "")
  addElement("Clear Trouble Codes", "clearDTC","-",0x0, "")  addElement("Clear Trouble Codes", "clearDTC","-",0x0, "")
- addElement("System Info >>>", "SysInfo_Menu",">>>",0x1, "")+ addElement("System Info >>;;;>;;;", "SysInfo_Menu",">;;;>;;;>;;;",0x1, "")
  addElement("Greetings", "greet","",0x1, "")  addElement("Greetings", "greet","",0x1, "")
  pageDone()  pageDone()
  return oldvalue  return oldvalue
 end end
- 
 </code> </code>
  
  
 Reading the VIN number: Reading the VIN number:
-<code lua> + 
-function vin(oldvalue,id)+ 
 +<code lua>function vin(oldvalue,id)
  echoWrite("0902\r\n")  echoWrite("0902\r\n")
  udsLen=receive()  udsLen=receive()
Line 88: Line 102:
  
  
-OOBD itself stands for Open On Board Diagnostics, where OnBoardDiagnostics stands for the diagnostics connector in each modern car, where OOBD is coming from, but it can also be adapted to all other scenarios, where a request is send by a tester and a system sends an answer back.+===== Own Hardware - The CAN-Invader =====
  
  
-===== Own Hardware =====+Although the build plans are available in the OOBD repository, we do recommend to better buy a finished CAN invader device at our partner
  
-To be able to support the full telegram length of the [[http://de.wikipedia.org/wiki/Unified_Diagnostic_Services|UDS protocol]] and to have two CAN busses available, we are using the existing [[http://www.obd-shop.com/danila/product_details.php?id=373&lang=de|DXM Bluetooth BTM222]], [[interface:busswitch|modify]] it and install our own [[interface:bootloader|firmware]] 
  
 +[[http://caninvader.de|{{  :jatra_logo_mittel.jpeg?nolink&300  }}]].
 +
 +
 +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  }}
  
- {{:doc:cimg2479.jpg?256|}}{{:house1.jpg?256|}} 
  
 ===== About us ===== ===== About us =====
  
-We are a small group of mainly automotive engineers who wanted to have some simple and handy equipment for our daily work. 
  
 +We started as a small group of mainly automotive engineers who wanted to have some simple and handy equipment for our daily work.
  
-==== Join the OOBD- Community.. ==== 
  
 +==== Join the OOBD- Community.. ====
  
  
 If you like the concept of a flexible, configurable diagnostic software so much as we do, you might want to take the advantage of Open Source and take the base to implement your own ideas, wishes and needs - which is, of course, a good idea If you like the concept of a flexible, configurable diagnostic software so much as we do, you might want to take the advantage of Open Source and take the base to implement your own ideas, wishes and needs - which is, of course, a good idea
 +
  
 But.. But..
 +
  
 As you certainly know, there are hundreds of diagnostic programs around, solving hundreds single problems, each one for its own. We have set up the OOBD project to generate a generic framework  to have just one single program instead which can be adapted to every possible topic. As you certainly know, there are hundreds of diagnostic programs around, solving hundreds single problems, each one for its own. We have set up the OOBD project to generate a generic framework  to have just one single program instead which can be adapted to every possible topic.
  
-We are now just worried that you probably like this idea of this all-in-one-design, and you start your own all-in-one project - so that in the end we end up with hundred all-in-one concepts... 
  
 +We are now just worried that you probably like this idea of this all-in-one-design, and you start your own all-in-one project - so that in the end we end up with hundred all-in-one concepts…
  
-So please before you start your own thing, have a thought about to [[dev:join|join us]]. We are wide open to every new idea, and as you see, we are also just at the beginning, but we really would like to end up with just one program for everything. 
  
 +So please before you start your own thing, have a thought about to join our team. We are open to every new idea, and as you see, we are also just at the beginning, but we really would like to end up with just one program for everything.
 +
 +
 +{{  :oobd_logo_tooling.png?229  }}
  
-{{  :oobd_logo_tooling.png?229  |}} 
  
 ---- ----
  
-===== Our Sponsors ===== 
  
-We would like to thank our sponsors to support the OOBD idea:+===== Our Partners & Sponsors ===== 
 + 
 + 
 +Jatra as our partner in produce and distribute the [[http://caninvader.de|CAN Invader]] 
 + 
 + 
 +<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&}}]]  
 + 
 + 
 +\\ 
 +===== Chat with the Developers (experimental) ===== 
 +<html> 
 +<iframe src="http://webchat.freenode.net?channels=%23oobd&uio=ND10cnVlb4" width="647" height="400"></iframe> 
 +</html>
  
-[[http://www.hellermanntyton.de/|{{http://upload.wikimedia.org/wikipedia/de/thumb/7/70/HellermannTyton-Logo.svg/200px-HellermannTyton-Logo.svg.png|Hellermann Tyton}}]]+<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>