|
 | | Re: NXT Reset
|
| (...) Glory, glory! OOBER is alive! It took a couple of tries of the above procedure. It never registered as an Unknown Device. In fact, it never registered at all. Finally it came up as a Lego Device. At that point, I downloaded firmware and Ouala, (...) (18 years ago, 25-Feb-07, to lugnet.robotics.nxt)
| |
|  
firmware
(score: 0.713)
|
|
| | ROBOLAB 2.9.3 Patch
|
| The ROBOLAB 2.9.3 Patch is available from at LEGOEngineering.com (URL) highlighted fixes include: 1. RCX Firmware 7.08: This firmware is substantially smaller than the last one, giving a lot more space for programs. 2. NXT Firmware 7.07: This (...) (18 years ago, 6-Feb-07, to lugnet.robotics.rcx.robolab)
| |
|
firmware
(score: 0.713)
|
|
| | Re: Rejected mac ad's
|
| (...) Hey I learned 6502 assembler on mine, remember the Big Mac macro assembler? And I used it to write a program that could squeeze about 5 times as much data on tapes as the standard firmware (yes, I said tapes). And I did my first paid computer (...) (18 years ago, 21-Feb-07, to lugnet.org.ca.rtltoronto)
| |
|
firmware
(score: 0.712)
|
|
| | Re: Spawning threads in NBC
|
| (...) Just to clarify, NXT-G doesn't have a thread scheduler. NXT-G is a just a graphical programming language, not a firmware or a virtual machine. The standard NXT firwmare implements a virtual machine which has a thread scheduler. The name of the (...) (18 years ago, 31-Jan-07, to lugnet.robotics.nxt)
| |
|
firmware
(score: 0.712)
|
|
| | Re: Rejected mac ad's
|
| (...) And thus his future life in a technical field was born... (...) Strangly, I never did have an asembler for the Apple ][. Somehow, my HS friends and I missed that and did everything on graph paper and raw hex code. The best part was when we (...) (18 years ago, 21-Feb-07, to lugnet.org.ca.rtltoronto)
| |
|
firmware
(score: 0.712)
|
|
| | RE: Bluetooth Comm Problem
|
| The NXT-G firmware implementation for mailbox messaging is extremely funky. I don't think your code is working properly for this implementation. You need to be continuously calling "ReadMessage" and only check for "a message was found" error code. (...) (18 years ago, 14-Feb-07, to lugnet.robotics.nxt)
| |
|
firmware
(score: 0.712)
|
|
| | Re: NXC/NBC release news
|
| (...) I am inclined to agree with you. The NXT firmware system calls provide the flexibility for choosing whether to clear the screen before any screen drawing operation but generally this option is not needed every time. Since I have a ClearScreen (...) (18 years ago, 15-Feb-07, to lugnet.robotics.nxt)
| |
|
firmware
(score: 0.712)
|
|
| | RE: NXC/NBC release news
|
| (...) In addition to the explicit flag on the opcodes, the NXT-G firmware also does an implicit clear of the screen the first time a user application program writes to the screen. So the macros could be hard-coded with 'false' and this parameter (...) (18 years ago, 15-Feb-07, to lugnet.robotics.nxt)
| |
|
firmware
(score: 0.712)
|
|
| | Re: BricxCC release 3.3.7.16
|
| (...) In the soon to be available new test release, BricxCC (3.3.7.17) now properly assumes NXC when a file has no extension if you switch your Preferred language for the standard firmware (on the Compiler|Common tab of the Preferences dialog) to be (...) (18 years ago, 15-Feb-07, to lugnet.robotics, lugnet.robotics.nxt)
| |
|
firmware
(score: 0.711)
|
|
| | Re: NXC/NBC release news
|
| (...) I would agree. I would prefer versions of the graphics commands that didn't include the clear screen flag. The fact that LEGO designed the firmware to require the flag with each of these doesn't mean it's needed in a high level language. Of (...) (18 years ago, 15-Feb-07, to lugnet.robotics.nxt)
| |
|
firmware
(score: 0.711)
|
|
| | Re: Bluetooth Comm Problem
|
| (...) Dick and David, Thanks for posting this conversation here. Even though I'm not participating directly, I am reading it and as I'm touching up the Bluetooth support for pbLua right now, this has given me invaluable insight into how the (...) (18 years ago, 16-Feb-07, to lugnet.robotics.nxt)
| |
|
firmware
(score: 0.711)
|
|
| | Re: Wireless RCX Communication.
|
| (...) "little odd" ? This is totally odd. 1. Possible wireless channels are : infrared or visible light, modulated ultrasonic/sound or radio 2. You don't want to compromise infrared sensors, so there only remains modulated acoustics/ultrasonics or (...) (18 years ago, 11-Feb-07, to lugnet.robotics)
| |
|
firmware
(score: 0.710)
|
|
| |
|
mindstorms, firmware
(score: 0.710)
|
|
| | Wireless RCX Communication.
|
| Hello, This may seem a little odd, but I want to get the RCX talking to the PC wirelessly without compromising the infrared sensors! This may seem a little odd, but it is because I need line of sight between the two robots, but communication from (...) (18 years ago, 11-Feb-07, to lugnet.robotics)
| |
|
firmware
(score: 0.710)
|
|
| | Re: Spawning threads in NBC
|
| (...) I'm sure someone with some firmware knowledge will have a better answer for this, but my belief is that there are no smarts in the firmware for swapping threads during a wait - i.e. I bet it uses a full timeslice. I have done some BT logging (...) (18 years ago, 31-Jan-07, to lugnet.robotics.nxt)
| |
|
firmware
(score: 0.710)
|
|
| |
|
firmware
(score: 0.709)
|
|
| |
|
firmware
(score: 0.709)
|
|
| |
|
firmware
(score: 0.709)
|
|
| | Re: Improving the firmware?
|
| (...) Dick, I was thinking more in the direction of adding a new Module, with a IOMap that has room to set a command and several parameters, and use the ReadIOMap and WriteIOMap to set them. This may not be the fastest solution, since as you (I (...) (18 years ago, 27-Jan-07, to lugnet.robotics.nxt)
| |
|
firmware
(score: 0.709)
|
|
| | Re: Drive types
|
| (...) Rosco is correct. The standard NXT firmware uses a completely different execution model than the old RCX firmware uses. The NXT firmware does not provide any mechanism at all for starting and stopping threads. The only mechanism is to define (...) (18 years ago, 14-Jan-07, to lugnet.robotics)
| |
|
firmware
(score: 0.709)
|
