 | | Re: NXT Reset
|
|
(...) It would be really cool if the girls could get OOBER back themselves. One way to do it is as follows: 1. Kill OOBER again. Not really, just hit the reset button for more than 10 seconds to force it into SAMBA mode again. 2. Let the girls do (...) (18 years ago, 25-Feb-07, to lugnet.robotics.nxt)
|
| |
| | 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)
|
| |
| | RE: NXT Reset
|
|
(...) If you're using Windows, confirm that it is recognized as a USB device by Windows but that the device driver cannot be found. You do this by opening up the Windows "Device Manager" window and looking for an "Unknown Device". Of course before (...) (18 years ago, 25-Feb-07, to lugnet.robotics.nxt)
|
| |
| | RE: legWay
|
|
(...) I can't speak for what actually got implemented. But Robolab's 2.9.2 firmware has almost all of the same features as the RobotC firmware. This includes the capability to customize the sensor scan rate from the default of 3 msec. The scan rate (...) (18 years ago, 25-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Reset
|
|
(...) I think my laptop has 1.02. I updated eveything when I needed the compass block. Although, I searched and couldn't confirm the NXT-G version number. Must not have looked hard enough. I've tried resetting another of the Educational NXT's and (...) (18 years ago, 25-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: NXT Reset
|
|
(...) It sounds like it's stuck in update mode (SAMBA boot mode). By any chance, have you downloaded and installed the 1.02 driver patch from LEGO? (URL) hoping you say you haven't, and installing it fixes this). (18 years ago, 24-Feb-07, to lugnet.robotics.nxt)
|
| |
| | NXT Reset
|
|
I've tried to resusitate OOBER several times. I have it plugged into the USB. NXT software is ready to download firmware. Following page 74 of the User Guide. I hit the reset, hold OOBER to my ear and hear it's "heartbeat". Downloading firmware (...) (18 years ago, 24-Feb-07, to lugnet.robotics.nxt)
|
| |
| | legWay
|
|
Steve H. 's legway, needless to say, is very cool. I wonder if I may obtain expertise ideas on the following: . I wonder if anyone has tried this with the regular RCX sensors + Robolab2.9.2 using the Optimizer feature. The Optimizer is supposed to (...) (18 years ago, 24-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Surveying MTBF of Edu NXTs
|
|
(...) Thanks Folks. I'm just finishing up a class for 9 & 10 year olds. When I get home, I'll try resetting and upgrading OOBER. Without the tears and emotions breaking around me, I should be able to isolate the bug. (18 years ago, 24-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Surveying MTBF of Edu NXTs
|
|
(...) Ouch, I understand quite well, actually*. But I agree with John, it sounds like the NXT might be in firmware update mode. If you *haven't* already done it, download the latest firmware (1.04), and a patch for the driver (1.02), from LEGO's (...) (18 years ago, 24-Feb-07, to lugnet.robotics.nxt)
|
| |
| | Re: Surveying MTBF of Edu NXTs
|
|
(...) It sounds to me like the NXT is simply in firmware download mode. There is no visible reaction on the NXT once it is in that mode but you should hear a faint clicking sound. That's what the reset button does - i.e., it puts the NXT into (...) (18 years ago, 24-Feb-07, to lugnet.robotics.nxt)
|
| |
| | BricxCC & NBC/NXC News
|
|
The Sourceforge shell service finally came back on line today so I was able to update my web pages again. The official links to beta 27 are up now. I have also uploaded a revision to Danny Benedettelli's fantastic NXC Tutorial (and sample code). And (...) (18 years ago, 24-Feb-07, to lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | Re: Surveying MTBF of Edu NXTs
|
|
(...) Two 6th grade girls at Ladd Acres Elementary in Hillsboro Oregon USA, named the NXT, "OOBER" out of the box. They used a rechargeable until that needed recharging. I replaced their original rechargeable with another one. Today, about 30 (...) (18 years ago, 24-Feb-07, to lugnet.robotics.nxt)
|
| |
| | RICScript
|
|
You may not find this terribly interesting, but I have implemented an RIC to Text converter (a decompiler, if you will) which generates source code for an RIC file in a text format. Soon BricxCC will have support for writing and (...) (18 years ago, 24-Feb-07, to lugnet.robotics, lugnet.robotics.nxt)
|
| |
| | 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)
|
