Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
web:features [2014/12/30 18:58] – admin | web:features [2017/07/26 20:42] (current) – admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Features ====== | ====== Features ====== | ||
+ | |||
The OOBD tool set contains a wide range of features and functionality. Some of it is part of the main applications, | The OOBD tool set contains a wide range of features and functionality. Some of it is part of the main applications, | ||
+ | |||
+ | ===== 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 | ||
+ | |||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | By including other popular libraries like e.g. jQuery, you can make simple responsive UIs like this | ||
+ | |||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | or use pretty graphical elements like gauges and meters | ||
+ | |||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | Or you can create your own custom style like this 3D three.js sample | ||
+ | |||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | ===== Remote Connect ===== | ||
+ | |||
+ | |||
+ | {{: | ||
Line 8: | Line 47: | ||
- | ^ Java-ME ((not maintained anymore, so only old, reduced command set available)) | + | ^ Java-ME ((not maintained anymore, so only old, reduced command set available)) |
| {{ : | | {{ : | ||
===== UDS compatible Telegram Support ===== | ===== 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. | 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 ===== | ===== 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. | ||
+ | |||
+ | 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 25: | Line 67: | ||
Reading the VIN number: | Reading the VIN number: | ||
+ | |||
<code lua> | <code lua> | ||
Line 48: | Line 91: | ||
end | end | ||
</ | </ | ||
+ | |||
===== Simple Syntax ===== | ===== Simple Syntax ===== | ||
+ | |||
+ | |||
For easy integration into other projects the [[: | For easy integration into other projects the [[: | ||
- | ===== PGP Script Protection | + | ===== Graphical Programming Interface |
- | {{: | + | |
- | OOBD supports this with optional strong PGP encryption, where through its unique [[https:// | ||
+ | {{: | ||
- | ===== Remote Connect | + | Simple Diagnostic programs and command sequences can be generated just in minutes with [[: |
- | {{:doc:kadaver.png? | + | |
+ | |||
+ | ===== openXC Data Source | ||
+ | |||
+ | |||
+ | {{:doc:openxc_enabler.png? | ||
+ | |||
+ | |||
+ | ===== PGP Script Protection ===== | ||
+ | {{: | ||
+ | OOBD supports this with optional strong PGP encryption, where through its unique [[https:// | ||
Line 70: | Line 126: | ||
- | {{: | + | {{: |
- | ===== Monitoring Real Time Data ===== | + | <code xml> |
+ | <?xml version=" | ||
+ | < | ||
+ | xmlns:xsl=" | ||
+ | |||
+ | < | ||
+ | < | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | |||
+ | < | ||
+ | < | ||
+ | |||
+ | dofile(" | ||
+ | dofile(" | ||
+ | dofile(" | ||
+ | dofile(" | ||
+ | dofile(" | ||
+ | dofile(" | ||
+ | |||
+ | </ | ||
+ | < | ||
+ | moduleName = '< | ||
+ | shortName = '< | ||
+ | </ | ||
- | {{http:// | ||
+ | ===== Monitoring Real Time Data ===== | ||
+ | {{: | ||
+ | |||
+ | OOBD offers several possibilities to monitor the CAN real time data. In the RTD mode the received data is stored in the dongle to be picked up later, while in the CAN raw mode the data is directly dumped on the serial line. This, together with the socketCANd emulator, allows to view the data in real time e.g. in [[http:// | ||
===== Bus Quality ===== | ===== Bus Quality ===== | ||
+ | |||
+ | |||
During bus transfer the dongle also monitor the occurrence of error frames, so it can be used also to measure the error rate, means the bus quality. | During bus transfer the dongle also monitor the occurrence of error frames, so it can be used also to measure the error rate, means the bus quality. | ||
+ | |||
===== CAN Injection ===== | ===== CAN Injection ===== | ||
+ | |||
+ | |||
If needed, the dongle can send long can data sequences to inject simulation data onto the CAN bus. | If needed, the dongle can send long can data sequences to inject simulation data onto the CAN bus. | ||
Line 89: | Line 178: | ||
===== Field Programmable ===== | ===== Field Programmable ===== | ||
- | {{: | + | |
+ | {{: | ||
===== Python Library for automated task ===== | ===== Python Library for automated task ===== | ||
+ | |||
+ | |||
To use the dongle also for automatic testing, a python library exist to send command sequences from a dos shell or within a batch file | To use the dongle also for automatic testing, a python library exist to send command sequences from a dos shell or within a batch file | ||
+ | |||
+ | |||
+ | \\ | ||
+ |