09-26-2013 03:09 PM
I took a RobotC brick and plugged it into a compute with Labview on it. When I started Labview I pulled up an NXT terminal. the firmware was incorrect of course so I started an update. The update got through the first section, locating NXT, and then stopped and the brick just beeps now. Any suggestions of how to fix it? Two bricks have done this to me.
09-27-2013 09:34 AM
This is a new issue relating to the NXT Driver unable to detect bricks in firmware update mode. I have seen it on one other computer and the best workaround was just updating the brick from another computer.
What kind of computer and OS version are you using? Do you have any other NI software installed, in particular something that might have included/updated NI-VISA?
12-29-2013 09:04 AM
This also hapenned to me with two bricks in a row (just doing a firmware upgrade using LabVIEW).
I was using a Windows 8 Machine.
I also had mindstorms 2.1 software loaded. This also could not find the brick.
Both bricks updated fine on another PC.
My logical assumption was dubious drivers.
Phil.
12-29-2013 12:23 PM
I have successfully updated a RobotC brick to LabVIEW on my Windows 8 machine.
NOTE: I had downloaded NXT-G 2.1 on that same machine, and many things NI went awry. I chose to uninstall all things NI, and performed a fresh install of LabVIEW 2012/MCT. It is now the only NI software I have installed. (A fresh install is how I've had to handle .dll errors too. 'Repairs' were not successful.)