The OOBD Book
- Web UI
- Setup your Developer Environment
The OOBD Book
This is an old revision of the document!
The rest should work automatically: The app scans the surrounding for any bluetooth device having a name starting with “OOBD”. When one or more dongles are found, the app tries to connect to it. It also tries to connect to the OOBD remote Connect Server.
If everything goes right, all symbols will go green and the connection number is shown. This number you'll need to tell then to the remote operator who is trying to access from outside.
This is just the description of the actual development version and might change again later again without further notice
After doing that, you'll find the additional Start command “OOBDesk (Java Portable)” in the Windows Start menu. When choosing that, OOBDesk is started with the portable Java version.
Use OOBDesk as normal, but before press the “Start” button on the main screen, select “Remote Connect” in the Settings- Menu (the “?” item in the menu bar).
When then the “Start” Button is pressed, a dialog pops up where OOBDesk asks for the connection number. This number is the number which is shown in the Google Chrome App, when the client starts the Chrome app (“the other side” from the OOBDesk user perspective). After entering this number, the system will try to connect the user through to the client.
Settings: Please make sure that the Server URL is wss://oobd.luxen.de/websockssl