 | | Re: Surveying MTBF of Edu NXTs
|
|
First, let me repeat the request for specifics. I *have* had some reports of indivdual sensors failing (and being replaced by LEGO), as well as the rare motor that seems a little bit to high in internal friction (and, again, at least addressed by (...) (18 years ago, 23-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Surveying MTBF of Edu NXTs
|
|
(...) Hi Fly, I suspect that your NXTs are fine. On the other hand, I suspect your rechargeables are toast; there is a big difference between those two things. An underpowered NXT will behave erratically, and therefore, as the battery looses its (...) (18 years ago, 23-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Surveying MTBF of Edu NXTs
|
|
(...) You should be able to estimate time-to-failure in the presence of your censored data; people do this all the time in engineering and cancer and many other fields. Steve H seems surprised at the fact that any NXT died and I must say that I am (...) (18 years ago, 23-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Surveying MTBF of Edu NXTs
|
|
(...) What exactly do you mean by "Dead"? I've never seen any NXTs die. I've been told it's possible to reprogram the flash memory enough to wear it out, but that required someone writing a PC program that did nothing but reprogram the flash, and (...) (18 years ago, 23-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Surveying MTBF of Edu NXTs
|
|
I have 11 commercial (C) and 25 educational (E) NXT sets. The 11Cs are doing fine after about 4 battery changes. They have been in use since July 2006 for about 60 class hours. I'm sure there's a more empirical way to calculate how much run-time 4 (...) (18 years ago, 23-Feb-07, to lugnet.robotics.nxt)
|
| |
| | NXC Counters
|
|
From the NXC Guide: ---...--- TachoCount: Return the internal position counter value for the specified output. BlockTachoCount: Return the block-relative position counter value for the specified port. RotationCount: Return the program-relative (...) (18 years ago, 23-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Extending the firmware through DrawGraphic()
|
|
(...) Hmm, this is interesting. The capabilities that aren't used by the current firmware are very curious. I can see the purpose of multiple sprites and draw modes though. With that, you could do masked graphics. A mask sprite would be drawn first (...) (18 years ago, 22-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Extending the firmware through DrawGraphic()
|
|
(...) Thanks John. I find it a problem that NXTasy posts are not signed - I didn't know you were the author... Philo (18 years ago, 22-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Extending the firmware through DrawGraphic()
|
|
(...) Unfortunately, I made several factual errors in my post on NXTasy the other day. I have attempted to correct those errors today by editing the existing post. Please make sure you read it again if you read it yesterday or earlier this morning. (...) (18 years ago, 21-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Extending the firmware through DrawGraphic()
|
|
(...) Yikes - I had no idea it was that convoluted! I want to put on some new graphics functions but I think I'll devise my own file format for those. I'll see if it's possible to hijack DrawGraphic to test it at least, but supporting new opcodes (...) (18 years ago, 21-Feb-07, to lugnet.robotics.nxt)
|
