User Tools

Site Tools


doc:tools_kadaver

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
doc:tools_kadaver [2014/12/28 12:16] admindoc:tools_kadaver [2015/06/10 11:55] (current) – [The Google Chrome Browser Kadaver App] admin
Line 1: Line 1:
 ====== OOBD Kadaver ====== ====== OOBD Kadaver ======
 +
 +===== Kadaver Clients =====
 +
 +==== The Google Chrome Browser Kadaver App ====
  
  
Line 9: Line 13:
   * make sure your computer has internet connection   * make sure your computer has internet connection
   * power up your [[http://caninvader.com|OOBD dongle]] inside the receiving range of your bluetooth   * power up your [[http://caninvader.com|OOBD dongle]] inside the receiving range of your bluetooth
 +  * go to the [[https://oobd.luxen.de|Kadaver Server Page]] first and accept the unknown certificate, **otherways the app would not work!**
   * start the Kadaver App   * start the Kadaver App
  
  
-The rest should work automatically: The app scans the surrounding for any bluetooth device having a name starting with "OOBD". When one ((in the actual ready-for-testing version you must have exactly **ONE** OOBD dongle around and/or in the list of known and paired devices. Later we'll add a selection box for the case that more as one is found)) is found, the app tries to connect to it. It also tries to connect to the OOBD remote Connect Server.+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. 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.
  
 That's all.. That's all..
 +
 +===== OOBD Settings =====
 +
 +FIXME This is just the description of the actual development version and might change again later again without further notice
 +
 +==== Setup OOBDesk to run with Java Portable 1.8 (JPortable) ====
 +  * Go to the [[https://drive.google.com/folderview?id=0B795A63vSunRbk1jc3U5VFFJbkU&usp=sharing|OOBD Google Drive Software Folder]]
 +  * Download and Install [[startup_windows|OODBDesk]](The remote Control version is only available for the developers and not public yet)
 +  * Download and Install Java18_portable_unlimited_policy.exe
 +
 +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.
 +
 +
 +==== OOBDesk (Windows) ====
 +
 +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).
 +
 +{{:doc:remoteconnect_menucheckmark.png?200|}}
 +
 +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.
 +
 +{{:doc:remoteconnect_connectionnumber.png?200|}}
 +
 +Settings: Please make sure that the Server URL is <nowiki>wss://oobd.luxen.de/websockssl</nowiki>
 +
 +
 +==== Android ====
 +
 +
 +
 +
  
  
-FIXME more to write... 
doc/tools_kadaver.1419765385.txt.gz · Last modified: 2014/12/28 12:16 by admin