WiShield problem is persistent
by Nerudin
on Sunday, 10 January 2010,
Till now I have been unable to get the WiShield to work with my Servo code and the WiShield code merged. I haven't really even tried to modify the page that the WiShield serves up to the computer. By now I wanted to be working on that, modifying the GET (though it looks more difficult than I had expected) to trigger the functions within the Servo code. I decided there was no point wasting time on that seeing as the two codes aren't even working together.
I have been conversing with a forum helper at the official WiShield support forum, who suspects that the WiShield + the Servo codes might be too big in size. This is very bad news as it's impossible shrink the WiShield code without breaking it. I suppose I will try to cut down my Servo code to see if that does the trick.
9 July 2012 at 15:17
Hi Farah, what became of your project? Have you graduated now? Are you looking for a job?
I am trying to do something like you as a personal project in my spare time. My plan is to simply pipe all data from Arduino digital and analogue pins over TCP/IP, both inputs and outputs. That will allow the robot control to be online, whether it's a user interface or an AI brain. I have the Roboduino motor shield and the AsyncLabs WiShield v1.0. I hope I don't meet the same problems as you with pin conflicts! If so then I'll look into using a custom motor circuit.
I've recently got a Raspberry Pi computer but it has no wifi and no analogue inputs so I will be using the Arduino.
Anyway please let me know how you are doing and if you could share your work with me.