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
Last revisionBoth sides next revision
start [2013/11/17 12:36] – wsauerstart [2020/03/15 12:46] – [Own Hardware - The CAN-Invader] admin
Line 1: Line 1:
-{{  :oobd_3d_white_320.jpg  |}}+{{  :oobd_3d_white_320.jpg  }}
  
  
- +====== Welcome to OOBD ======
- +
-====== Welcome to OOBD  ====== +
- +
- +
-<php> +
-$hostname = gethostbyaddr($_SERVER['REMOTE_ADDR']); +
-#echo $hostname; +
-if (preg_match('/ford\.com$/i', $hostname)>0){ +
-   #echo "I'm inside Ford:"; +
-   #echo $hostname; +
-   } +
- +
-</php>+
  
  
 ===== What is OOBD? ===== ===== 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. 
  
 +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.
  
-To get out of this hell of tools, the target of OOBD is to provide an open framework as one single program, which is able to handle all kinds of diagnostic problems by having a flexible plug-in interface for all type of requests, visualizations and hardware. 
  
 +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.
  
-===== Several Platforms =====+{{  :web:webui.png?800  }}
  
  
-^  On Java-ME:  ^  On Android:   ^ +===== Quickstart =====
-|  {{  :pics:oobdme-window.png?150  |}}  | {{  :pics:diagnose.png?150  |}} | +
-^  On Windows (and Linux & Mac((No installation pack available yet, needs to be compiled manually out of the repository)))  ^^ +
-|{{  :swing_screenshot.png?437  |}}||+
  
  
-===== Flexibility =====+To download, install, setup and run the software, please follow the instructions for [[:doc:startup_android|Android]] or [[:doc:startup_windows|Windows]].
  
  
-This is realized by not to have hardcoded functionality, but to control the functions by loadable (Lua) scripts.+For all documents, please use the links [[:start?do=index|Sitemap]] and [[:doc:start|Manual]] provided in the header of each page.
  
-Building the main menu: 
-<code lua> 
  
-function Start(oldvalue,id) +===== Features =====
- 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>+As the feature list became to long for the main page, we moved it to the separate [[:web:features|Feature page]].
  
  
-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 =====
  
-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. 
  
 +Although the build plans are available in the OOBD repository, we did recommend to better buy a completely build & tested CAN invader device at our partner
  
-===== Own Hardware ===== 
  
-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.diamex.de/dxshop/BTM222-Bluetooth-Modul-class1-mit-100m-Reichweite|DXM Bluetooth BTM222]], [[interface:busswitch|modify]] it and install our own [[interface:bootloader|firmware]]+[[caninvader|{{  :jatra_logo_mittel.jpeg?nolink&300  }}]].
  
  
- {{:doc:cimg2479.jpg?256|}}{{:house1.jpg?256|}}+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.
  
-===== About us ===== 
  
-We are a small group of mainly automotive engineers who wanted to have some simple and handy equipment for our daily work.+{{  :house1.jpg?100  }}
  
 +===== Our Partners & Sponsors =====
  
-==== Join the OOBD- Community.. ==== 
  
 +Jatra as our partner in produce and distribute the [[http://caninvader.de|CAN Invader]]
  
  
-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+<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>
  
-But..+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}}]] 
  
-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...+{{  :oobd_logo_tooling.png?229  }}
  
  
-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. 
- 
- 
-{{  :oobd_logo_tooling.png?229  |}} 
- 
----- 
- 
-===== Our Sponsors ===== 
  
-We 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|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>