Mindboards

-10000000000000000000000000000000000000 is of type integer, maybe try -10000000000000000000000000000000000000.0 or -10000000000000000000000000000000000000.0f

Oh, and btw.: Doing this primes-thingy on an NXT is a very good exercise. You learn a lot about the endless possibilities of optimization. It's an advantage, that the NXT is so slow, as you feel a greater impact of slow vs. fast code. With all the peculiarities of NXC... Also, everyone has the EXACT...

There are possible performance improvements with this setbitarr and readbitarr code: 1.) Shift operations are slow in NXC (if anybody is interested, have a look at my NXC profiler and try for yourself, the results should be around here somewhere (or on nxtasy :/) ). You can pre-calc the 8 possible b...

Anyhow, according to statements made by "experts who should know" it is actually at present not possible to write a program in NXC, which could solve the problem of a multi-threading-safe multiplexer via BT network reliably. I'm pretty sure it's possible, I think there are people out ther...

no, you're wrong, my wish always was to have multi-threading-safe BT access, your advice was to avoid multi-threaded access. IIRC, the guidance by John and others was to avoid calling BT functions from across different threads at all times. Having done a lot of socket, serial and BT programming, th...

hippicurean, have you done some basic benchmarking to get a feeling for your algorithm? How many iterations per second you can expect on "bare metal" NXT? I'd suggest something like this: measure start time repeat N times { one iteration of your algorithm WITHOUT reading sensor/motor data ...

Half a year ago I posted in this thread that I was going to start my first job (as PhD student, actually), and my institute finally has a Youtube-channel. So if you're interested in what we do, check it out: http://www.youtube.com/user/VEROSIMSimulations A video of interest for robot navigation migh...

Just for the record, there's a direct command to change the NXT's name -- maybe one can inspect the underlying firmware code?

Appendix 1-LEGO MINDSTORMS NXT Communication protocol.pdf wrote: SET BRICK NAME COMMAND
Byte 0: 0x01
Byte 1: 0x98
Byte 2-17: New name of brick (15 characters + null terminator)

Edit: Never mind, I just saw that that's what you did

Yep, the additional Bluetooth latency will be horrible :-( -- NXT-to-NXT messages are not exactly fast anyway. Have you thought about the simple way of debugging this with acousting tones? You could beep on every lost message, or beep on every sent/received message, maybe with a different frequency ...

Another thing, more on the point of what you actually want to do (I've always been a big fan of NXT performance and stress tests, especially for Bluetooth performance): - Can you just protect all the Bluetooth operations from different tasks with a single "BT-access-mutex" to see if the pa...