Tweet
Hi,
I was able to install the Samantha module with our team and get the FCS software running. As they had still been working on DriveMain.c, the controller worked first time during the teleop portion of the game.
We hoped the Wifi would be a more robust connection than bluetooth, but were unable to make it work with RobotC.
After a LOT of effort, I disabled Avast, and the RobotC Wifi Connection worked without a hitch.
Windows 7, RobotC 3.62, FW 9.68. Linksys WRT54G running DD-wrt. During the RobotC connection step of scanning for devices, the symptoms are you get a "not Avaliable" message under the brick name even though it shows up in the address list. A popup window also says it it not communicating and you may need to press the red button etc... in the Message window of RobotC there are "NXT FW Err: WiFi Firmware is out of date "
the Samatha module web interface shows the 2.02 sept 9 2011 firmware.
Anyway, if you go to avast, disable the web shields, everything works without a hitch.
There are several posts around the web with similar problems. Seems like a RobotC / Avast incompatibility.
I was able to install the Samantha module with our team and get the FCS software running. As they had still been working on DriveMain.c, the controller worked first time during the teleop portion of the game.
We hoped the Wifi would be a more robust connection than bluetooth, but were unable to make it work with RobotC.
After a LOT of effort, I disabled Avast, and the RobotC Wifi Connection worked without a hitch.
Windows 7, RobotC 3.62, FW 9.68. Linksys WRT54G running DD-wrt. During the RobotC connection step of scanning for devices, the symptoms are you get a "not Avaliable" message under the brick name even though it shows up in the address list. A popup window also says it it not communicating and you may need to press the red button etc... in the Message window of RobotC there are "NXT FW Err: WiFi Firmware is out of date "
the Samatha module web interface shows the 2.02 sept 9 2011 firmware.
Anyway, if you go to avast, disable the web shields, everything works without a hitch.
There are several posts around the web with similar problems. Seems like a RobotC / Avast incompatibility.
Comment