Let me repeat, I do NOT think this is the case. I suspect this is a case of a new piece of software suddenly being testing by several hundred folks on radically different machines with all sorts of odd install histories Windows users: ever really browed your drivers?
The list can be scary. Suggestion for the "ticked off": remove the batteries, and count to 5. Now put them in. Still clicking? Try pushing it in and holding it, fully pushed, for 5 seconds. Now, try running the environment, and then attach the clicking NXT to the computer via USB; make sure there are no BT dongles on the computer at the time, and you migbht want to try different USB ports.
Ask the environment politely to update the firmware, and see what happens. As to what the difference in functionality between the two firmware version is, I don't remember if indeed I ever knew. But in general, the MDP has been running on 1. Some of the blocks may have odd or reduced functionality under earlier non-supported versions of the firmware.
On a personal note, I'm sorry some of you are having these troubles. All I can say is even a bunch of dedicated fans can't identify problems that we didn't find, and this sounds like one of them. We may not work for LEGO, folks, but we're trying to figure out how to help.
The topic name contains 28th june , but 28th is wednesday and there it says: ''Some videos of the RoboCenter challenges'' Am I missing something?
Nice long post, Brian. There's another post for Wed June I get the message, but above the ''NXT Problems? Hope I helped. I gotta go to bed Hey, it's PM here and I'm 11 years old boy, so I'll check again tomorrow. May be there is a defect in some distribution CD and for what ever reason that file is corrupted.
Feel free to do not post this if you think it is not worth the try. Back from work and I see much has been discussed. Tried all suggestions so far in both Posts with no luck. Glad Todd was able to call them directly. I would like to thank all the MDPers for their suggestions on this issue.
With LEGO still ramping up their support, your experience is all we have to go on for now. I wanted to post and shre my experience with the NXT firmware. Hopefully it will help. I use a dual core intel MacBook. I have the bluetooth capability turned OFF. I have never had a need for bluetooth until receiving my NXT kit, so it has been off to help battery life.
I installed the Mindstorms NXT application and proceeded to update to the 1. The firmware updated without incident and the new rcx is working perfectly with no clicks. I have cycled the unit on and off repeatedly, and have also downloaded a test program. I could not get my rcx to click like so many have experienced.
I have been lurking on the board throughout the day and would have to agree that problem seems to be related to the bluetooth functionality. You might try disabling your computer's bluetooth cpability, resetting your rcx, and trying updating the firmware again. Hopefully this may help some, if not, hang in there I am sure that Lego or a bright NXT user will help us get through this very soon. I was just trying to get somthing straight.
For what it's worth, here's an excerpt from an email, sent to me today from Lego Customer Support: "We are aware of the issue with the firmware update and our developers are currently investigating the issue We are Very Sorry For the inconvenience LOL Rick, Well, at least you got a nice email.
My tech support agent was quite rude to me at first telling me that he couldn't take my word that others were having the issue and it was most likely something I was doing because he had never heard of this issue.
After checking with another agent he came back and said that others had indeed reported the issue. He also questioned their ability to support the mac. At that point in the conversation it was all "blah blah blah, you're screwed for a while.. I'll understand and wait the time it takes to get out a fix. I was just expecting a better experience from Lego tech support. It should be noted that a stomach ache can be caused by many things food poisoning, stress, coffee etc Hence the same principle applies HERE.
Their maybe multiple problems not saying that likely but when diagnosing I think we should look at BT for sure, but also keep an eye out for other commonalities from the MANY different computer configurations.
I also had a problem updating the firmware, but I did eventually get it to work. My first attempt with my PowerBook found the NXT and claimed to have downloaded it successfully, but the screen was blank on the NXT and it was clicking.
I unplugged the NXT from the Mac and even tried to manually power cycle by pulling a battery. That didn't work. For my second attempt, I reconnected the USB cable and tried again. This time the program on the MAC froze and I had to force it to quit. I then rebooted the Mac. I then plugged in the USB and tried to download the update. This time it worked! Except the motors didn't work! I tried running the demo program it just sat there.
I then power cycled the NXT and then the motors finally worked again. Jun 29, , PM. Since it works for some most? So I suggest trying to update the firmware on a different machine. For how many non-MDP people is the firmware update working well? It is hard to really diagnose a problem if you mostly have the cases where it didn't work.
I thought that I would try to download it and see what happened. Well, their program said "successfully downloaded firmware" but then gave me an error saying "NXT failed to reboot after download. Juergen, Sorry if this sounds stupid Im dont know that much about computers but what did you mean by downloading the firmware from a different machine? Jun 30, , AM. He probably meant a different computer. Here's another datapoint for contrast-- my firmware update went fine on a Dell laptop.
I felt a bit nervous though- I've "bricked" a few wireless routers in the past through botched firmware upgrades. However, based on Brian's comments it seems that any damage can someday be reversed.
I'm one of the folks whose brick "died" when installing firmware v. So, maybe this will help some folks I hope. Brian or anyone : should I refrain from enabling Bluetooth, on the theory that Bluetooth may be part of the problem? Here is the rundown. After the update - just ticks. Reset the brick 5 seconds without any cables. Plugged in the USB cable into the back of the computer and into the brick.
No why? Blind luck? I was also thinking that there might be a difference in the USB between my monitor and the back of the computer Powered vs no power or high power vs low power. Somebody else give it a try and let us know! Rick, Todd I never even thought of someone using anything other than the "normal" USB ports, but you are completely correct - the ones on a monitor or keyboard are almost certainly not the best bet.
Regarding turning BT on If you really want to have fun, join the elite NXTbusters: now that you've got your NXT working again, try to see if you can reproduce "braking" it again, to figure out exactly how it happens. Hey, now you know part of what beta-testing is about ;-. I still wonder why it wasn't working on my powerbook G4. Perhaps I was running on battery and I needed to be plugged in. I don't know if that has anything to do with the power sent by the USB jack. Concerning bluetooth.
It was working great on my powerbook. I used it to download all of my programs to the brick. I swapped USB ports on my laptop. I reset the brick for 5 seconds. Got into the clicking mode. Then I plugged the brick into the cable and did my firmware upgrade again. Brian--You were right about Bluetooth.
It works fine on XP, anyway. BT doesn't work on the Mac. I'll try it on another Mac later. I'm not complaining, 'cause I'm up and running! It has been great to commiserate about NXT issues. SO is this a solution? Or ar people still having trouble once they tried the above? Thanks to you guys. Tried a different USB port, in my case the one on the back of the monitor worked as opposed to the one on the front of my PowerMac G5 tower.
I knew I came to the right blog. Just wondering, have most people fixed their problems with the advice given here? I have a hardware problem. I just opened the NXT box today and put together the starter kit. The A port on the brick is not responding to "try me" and just sounds a continous beep.
Not to be obvious, but have you connected a motor to the A port when trying the "Try Me" for that? I don't have my NXT handy, so I don't remember if it prompts you to do that. Alex, I would try skipping the "Try Me" parts of the in-box instruction booklet.
I tried some of those "Try Me" prompts, too, and they didn't work. Don't get the new firmware if that's not the case. Since there are countless models and manufacturers, as well as different methods for updating the speaker unit, it would be best if you read and understand the installation steps before initiating the update process.
In addition to that, we recommend you perform the installation in a steady power environment, such as the one ensured by a UPS unit so that the device doesn't encounter any malfunctions. This easy-to-use app allows you to interact with your very own EV3 robots without even connecting to a computer! That means you can play instantly with your own robots! EV3 Home App system requirements Windows. Android tablets only. Apple Macintosh with macOS By proceeding to downloading the Content, you agree to be bound by the above as well as all laws and regulations applicable to your download and use of the Content.
Provide your booking code and email address you used for the registration, we will re-send the confirmation email to you.
Consumer Business ENG. Consumer Switch to: Business. Consumer Business. Support Search Download. Contact Us. Outline Standard This is a driver that will provide full functionality for your selected model. Update History [Ver. System requirements Windows 11 Windows 10 32bit Windows 10 64bit Windows 8. Caution Printer Driver: 1. Was this helpful? Thank you!
0コメント