Changes for page Lego On-Line Testing System (KLOTS)
Last modified by Richard Kreissig on 2023/09/14 10:54
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,1 +1,1 @@ 1 -KIELER.SCCharts .SCCharts(DeprecatedHistorical Documentation).WebHome1 +KIELER.SCCharts (DeprecatedHistorical Documentation & Features).WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ybe1 +XWiki.stu230980 - Content
-
... ... @@ -1,11 +1,11 @@ 1 -{{panel borderStyle="dashed" title="Project Overview"}} 1 +== Project Overview == 2 + 2 2 Responsible: 3 3 4 4 * [[Christian Motika>>url:http://www.informatik.uni-kiel.de/rtsys/kontakt/cmot/||shape="rect"]] 5 5 * Yvan Benekov 6 -{{/panel}} 7 7 8 -= KLOTS - KIELER Lego On-line Testing System[[url:http://trac.rtsys.informatik.uni-kiel.de/trac/kieler/wiki/Projects/KLOTS#KLOTS-KIELERLegoOn-lineTestingSystem||title="Link to this section" shape="rect" class="anchor"]] =8 += KLOTS - KIELER Lego On-line Testing System[[url:http://trac.rtsys.informatik.uni-kiel.de/trac/kieler/wiki/Projects/KLOTS#KLOTS-KIELERLegoOn-lineTestingSystem||shape="rect" title="Link to this section" class="anchor"]] = 9 9 10 10 [[image:attach:klots_logo.png]] 11 11 ... ... @@ -23,7 +23,7 @@ 23 23 24 24 For more information about the leJOS NXJ project and especially the leJOS tutorial and NXT Programming API please visit the [[leJOS NXJ website>>url:http://lejos.sourceforge.net/||shape="rect" class="ext-link"]]. 25 25 26 -**Note that KLOTS currently uses leJOS NXJ v0.8.5, not the brand new v0.9.0.** You can download the v0.8.5 API from (% class="confluence-link" %) (% class="confluence-link confluence-link" %)[[here>>attach:leJOS_v0.8.5_API.zip]](% class="confluence-link" %) (% class="confluence-link noprintconfluence-link" %)[[image:attach:download.png]][[attach:leJOS_v0.8.5_API.zip]](% class="noprintconfluence-link" %) (%%).26 +**Note that KLOTS currently uses leJOS NXJ v0.8.5, not the brand new v0.9.0.** You can download the v0.8.5 API from (% class="confluence-link" %) (% class="confluence-link confluence-link" %)[[here>>attach:leJOS_v0.8.5_API.zip]](% class="confluence-link" %) (% class="confluence-link confluence-link noprint" %)[[image:attach:download.png]][[attach:leJOS_v0.8.5_API.zip]](% class="confluence-link noprint" %) (%%). 27 27 28 28 ---- 29 29 ... ... @@ -56,7 +56,7 @@ 56 56 * org.lejos.jtools 57 57 * org.lejos.pccomms 58 58 * org.lejos.pctools 59 -* If you want to be able to import KLOTS example programs using the KIELER Example Management (KEX), you will also need: \\59 +* If you want to be able to import KLOTS example programs using the KIELER Example Management (KEX), you will also need: 60 60 ** de.cau.cs.kieler.core.kgraph 61 61 ** de.cau.cs.kieler.kex 62 62 ** de.cau.cs.kieler.kex.ui ... ... @@ -78,7 +78,6 @@ 78 78 79 79 **Note: Currently there are some problems when using the 64-bit version of KLOTS. Since leJOS is using only the 32-bit Lego USB Fantom driver, you will not be able to connect the NXT brick via USB cable, i. e. you will also not be able to flash the leJOS firmware on the NXT. Bluetooth connection will work with most (but not all) bluetooth devices. So, if you want to be on the safe side, you will have to use the 32-bit version of KLOTS on your 64-bit machine.** 80 80 81 - 82 82 83 83 === USB set-up on Microsoft Windows systems === 84 84 ... ... @@ -88,9 +88,8 @@ 88 88 89 89 For the communication over Bluetooth, you will need a Bluetooth dongle or built-in support on your computer, and a Bluetooth software stack. The Microsoft and Widcomm stacks have been tested and proven to work, but other stacks should work as well. 90 90 91 -**Note: The (% style="color: rgb(0,0,0); color: rgb(0,0,0)" %)__BlueSoleil__(%%) stack has been reported as currently not working with KLOTS.**90 +**Note: The (% style="color:#000000" %)__BlueSoleil__(%%) stack has been reported as currently not working with KLOTS.** 92 92 93 - 94 94 95 95 === USB set-up on Linux systems === 96 96 ... ... @@ -118,7 +118,7 @@ 118 118 119 119 === (optional) Bluetooth set-up on Linux systems === 120 120 121 -If you want to communicate with the NXT over Bluetooth, you will need a Linux supported Bluetooth dongle or built-in support on your computer. KLOTS uses the Bluecove libraries which are included in the distribution. Note however, that not all Bluetooth adapters are compatible with Linux. A list of the supported hardware in several Linux distributions can be found on the web, for example [[Ubuntu Hardwaredatenbank (German)>>url:http://wiki.ubuntuusers.de/Hardwaredatenbank||shape="rect" class="ext-link"]] for the Ubuntu distribution. 119 +If you want to communicate with the NXT over Bluetooth, you will need a Linux supported Bluetooth dongle or built-in support on your computer. KLOTS uses the Bluecove libraries which are included in the distribution. Note however, that not all Bluetooth adapters are compatible with Linux. A list of the supported hardware in several Linux distributions can be found on the web, for example [[Ubuntu Hardwaredatenbank (German)>>url:http://wiki.ubuntuusers.de/Hardwaredatenbank||shape="rect" class="ext-link"]] for the Ubuntu distribution. 122 122 You may also need to install the **libbluetooth** and **libbluetooth-dev** libraries, however on most systems they are already pre-installed. 123 123 124 124 ---- ... ... @@ -193,7 +193,7 @@ 193 193 PC: 28087 194 194 ))) 195 195 196 -appears on the display. This indicates that an uncaught Java //Runtime Exception//, e.g. (% style="color: rgb(0,0,0); color: rgb(0,0,0)" %)//NullPointerException//(% style="color: rgb(0,0,0);" %),(%%) occurred somewhere in your program. The error message indicates the kind of the exception and the method where it was thrown. This information is produced by the program build procedure and you can see it by clicking on the //Details// button. It can be very helpful for debugging your programs.194 +appears on the display. This indicates that an uncaught Java //Runtime Exception//, e.g. (% style="color:#000000" %)//NullPointerException//,(%%) occurred somewhere in your program. The error message indicates the kind of the exception and the method where it was thrown. This information is produced by the program build procedure and you can see it by clicking on the //Details// button. It can be very helpful for debugging your programs. 197 197 198 198 (% class="confluence-link" %)[[image:url:http://trac.rtsys.informatik.uni-kiel.de/trac/kieler/raw-attachment/wiki/Projects/KLOTS/build_program_output.png]] 199 199