 | | Re: .NET Micro Framework released!
|
|
(...) The .NET Micro Framework documentations (URL) it requires at least 256K RAM and 512K Flash. The NXT processor has 64K RAM and 256K Flash.... Guy Ziv NXTasy.org (18 years ago, 15-Feb-07, to lugnet.robotics.nxt)
|
| |
| | 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)
|
| |
| | 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)
|
| |
| | Re: Bluetooth Comm Problem
|
|
Dick, Thanks for the research and all of the valuable information! It's Valentine's Day, so my wife won't allow me the time to try it tonight, but I'll try your suggestions tomorrow and see how it works. By the way, I actually saw a response come (...) (18 years ago, 15-Feb-07, to lugnet.robotics.nxt)
|
| |
| | .NET Micro Framework released!
|
|
Microsoft released a micro version of the .NET Framework SDK today! Could we be writing C# code for the NXT, and unlike the Microsoft Robotics Studio, actually have that code run natively on the brick itself? Quick summary article: (URL) download (...) (18 years ago, 14-Feb-07, to lugnet.robotics.nxt, lugnet.robotics, lugnet.technic)
|
| |
| | Re: NXC/NBC release news
|
|
Hi John! I think there is not an urgent need for a clear-screen flag in a bunch of NXT screen functions. That is, my sources are full of "false," flags :-) TextOut(...,true,...); TextOut(...,false,...); TextOut(...,false,...); LineOut(...,false); (...) (18 years ago, 14-Feb-07, to lugnet.robotics.nxt)
|
| |
| | 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)
|
| |
| | Re: Programming for NXT
|
|
(...) Would it help to add a "Last Updated: mm/dd/yyyy" to this page? Thank you Andy (18 years ago, 13-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Bluetooth Comm Problem
|
|
(...) I was a little confused about how I was supposed to determine when the message had been received. I wasn't sure whether the ReceiveMessage should be called multiple times or not. Here is my code: // Connection = 1, Queue = 0 (...) (18 years ago, 13-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: BricxCC release 3.3.7.16
|
|
(...) Agreed, even if you select NXT target BricxCC insists to use .nqc as default extension. Misleading at best... Philo (18 years ago, 13-Feb-07, to lugnet.robotics, lugnet.robotics.nxt)
|
