Changes between Version 49 and Version 50 of Development

Timestamp:

12/07/09 15:56:24 (3 years ago)

Author:

atorf

Comment:

—

Development

@@ +1 @@
+[[BR]]
+[[BR]]
+<!> '''Totally outdated page''' <!>
+[[BR]]
+[[BR]]
+----
+
 = Brainstorming & Further Concepts =
 
 == Firmware ==
- * Try using a different firmware than official standard NXT, like LeJOS / NXC / RobotC? There are hints to more precise motor control (!TachoLimit problem potentially fixed in LeJOS) or better performance of direct commands / bluetooth transmission!
+ * ./ Try using a different firmware than official standard NXT, like LeJOS / NXC / RobotC? There are hints to more precise motor control (!TachoLimit problem potentially fixed in LeJOS) or better performance of direct commands / bluetooth transmission!
 
 
 == Communication ==
- * Check the MATLAB-Help for the command `readasync`. Can it help to reduce timeouts and lags? Can it be used for the above mentioned non-blocking functions?
+ * (!) Check the MATLAB-Help for the command `readasync`. Can it help to reduce timeouts and lags? Can it be used for the above mentioned non-blocking functions?
 
 
 === USB ===
- * /!\ Add USB-Support, try to use as many existing BT-functions as possible (by using wrappers if necessary). Some code snippets, hints etc are collected on this temporary page: [wiki:USBStuff]
+ * ./ Add USB-Support, try to use as many existing BT-functions as possible (by using wrappers if necessary). Some code snippets, hints etc are collected on this temporary page: [wiki:USBStuff]
 
 
 === Bluetooth ===
- * Consider Bluetooth / serial port code from !MathWorks' NXT toolbox to reduce Bluetooth timeouts (try using option ''!NumRetries''?)
+ * {*} (!) {*} Consider Bluetooth / serial port code from !MathWorks' NXT toolbox to reduce Bluetooth timeouts (try using option ''!NumRetries''?)
 
- * The (sometimes optionally) passed Bluetooth-Handle (to functions) gets checked/validated far too often inside these functions. Checking/validating is only necessary at the lowest level, the other checks are a waste of performance...
+ * ./ The (sometimes optionally) passed Bluetooth-Handle (to functions) gets checked/validated far too often inside these functions. Checking/validating is only necessary at the lowest level, the other checks are a waste of performance...
 
- * Compatibility for multiple bluetooth handles / NXT connections at one time is not perfectly implemented: The settings !SendSendPause etc. are unique and global, and should be defined PER connection, not only once. Workaround: Disable those pauses by setting to 0.
+ * ./ Compatibility for multiple bluetooth handles / NXT connections at one time is not perfectly implemented: The settings !SendSendPause etc. are unique and global, and should be defined PER connection, not only once. Workaround: Disable those pauses by setting to 0.
 
 
 == Motor Control ==
- * Note: Apparently we CAN access the PID regulation directly, as this post suggests (http://forums.nxtasy.org/index.php?showtopic=2054&view=findpost&p=16463). Code-Sample: 
+ * ./ Note: Apparently we CAN access the PID regulation directly, as this post suggests (http://forums.nxtasy.org/index.php?showtopic=2054&view=findpost&p=16463). Code-Sample: 
 {{{
 def set_PID(motor,P,I,D):
@@ -33 +40 @@
 }}}
 
- * Note: John Hansen supported the module ids at http://news.lugnet.com/robotics/nxt/nxthacking/?n=14 to access the module directly, without request sequentially the modules[[BR]]
+ * ./ Note: John Hansen supported the module ids at http://news.lugnet.com/robotics/nxt/nxthacking/?n=14 to access the module directly, without request sequentially the modules[[BR]]
    The interpretation should be ''MSB'' '''PP TT CC FF''' ''LSB'' --> 0xPPTTCCFF[[BR]]
    PP: identify programmer
@@ -54 +61 @@
   /!\ As long as a new firmware update doesn't change this IDs, we are fine to use constants.
 
- * Own tests and example programs "!DriveAlong" using the NXT-G software showed no different behaviour of the driving robot. The motors also switch into the coast mode after the defined rotation angle is set.
+ * ./ Own tests and example programs "!DriveAlong" using the NXT-G software showed no different behaviour of the driving robot. The motors also switch into the coast mode after the defined rotation angle is set.
 
 
 == Software Design ==
- * Split GET-Functions into REQUEST and COLLECT parts again, making it possible to do calculations inbetween. I.e. add possibility for non-blocking (asynchronous) functions, as known from many sockets implementations.
+ * {X} Split GET-Functions into REQUEST and COLLECT parts again, making it possible to do calculations inbetween. I.e. add possibility for non-blocking (asynchronous) functions, as known from many sockets implementations.
 
- * textOut and dec2hex are slow. String-handling is slow. What can be done? Consider various performance improvements, use the Profiler.
+ * {x} textOut and ./ dec2hex are slow. String-handling is slow. What can be done? Consider various performance improvements, use the Profiler.
 
 
 == Version Discussions ==
- * Proposal for new toolbox commands with USB support, discussion about changes for toolbox version 2.00, see here: [wiki:DiscussionRelease2.00] ''(16.5.2008)''
+ * ./ Proposal for new toolbox commands with USB support, discussion about changes for toolbox version 2.00, see here: [wiki:DiscussionRelease2.00] ''(16.5.2008)''
 
 
 == Miscellaneous ==
- * Overview and comments about comparison between other solutions for MATLAB: Toolboxes from Chikamasa, The !MathWorks
+ * (!) Overview and comments about comparison between other solutions for MATLAB: Toolboxes from Chikamasa, The !MathWorks
 
  * This page provides a developer's notepad to discuss further concepts -> '''[wiki:FurtherConcepts Further Concepts (German)]'''