Arduino Uno and DFRobot Wifi 2.1
patillac 2012-07-18 08:02:16 26077 Views29 Replies So I've been trying to get this thing working, and running into all the troubles everyone else seems to have with this setup. I didn't see all the horrors of AT command errors and blank putty screens until I ran into them and discovered everyone else goes through the same perils.
I had the thing connecting to my wireless router and appearing in the Connected Devices list, and I was able to open a connection to it on the right port and was seemingly able to send data, although my initial test of: Serial.println("Hello world!"); failed.
In the process of jumping through the v2.1 hoops I had to switch between USB and Wifi modes on the v2.1 board. Now that I've done that I think I may have broken something. As far as I can recall I could put the v2.1 board into USB mode and upload sketches to the Uno, but now it seems that no matter what the board is set to I can't upload sketches unless I remove the v2.1 board entirely.
This is what happens every time I try to upload when the v2.1 board is attached to the Uno:
Binary sketch size: 1,280 bytes (of a 32,256 byte maximum)
avrdude: stk500_getsync(): not in sync: resp=0xfc
the response code is apparently randomly generated and meaningless.
I'm thinking about returning this board and getting something else just because something else has to be less trouble than this thing, but if I can keep pushing and get it working I'll try a little more. Does anyone have any suggestions on how to fix this error? The documentation I've read about "avrdude: stk500_getsync(): not in sync:" errors is along the lines of "you're screwed."
I had the thing connecting to my wireless router and appearing in the Connected Devices list, and I was able to open a connection to it on the right port and was seemingly able to send data, although my initial test of: Serial.println("Hello world!"); failed.
In the process of jumping through the v2.1 hoops I had to switch between USB and Wifi modes on the v2.1 board. Now that I've done that I think I may have broken something. As far as I can recall I could put the v2.1 board into USB mode and upload sketches to the Uno, but now it seems that no matter what the board is set to I can't upload sketches unless I remove the v2.1 board entirely.
This is what happens every time I try to upload when the v2.1 board is attached to the Uno:
Binary sketch size: 1,280 bytes (of a 32,256 byte maximum)
avrdude: stk500_getsync(): not in sync: resp=0xfc
the response code is apparently randomly generated and meaningless.
I'm thinking about returning this board and getting something else just because something else has to be less trouble than this thing, but if I can keep pushing and get it working I'll try a little more. Does anyone have any suggestions on how to fix this error? The documentation I've read about "avrdude: stk500_getsync(): not in sync:" errors is along the lines of "you're screwed."
2012-07-24 01:49:18 I'll try reducing the voltage/heat when I get a chance and see how it works out.
My original goal was to have a means to communicate any and all data from my robot to my computer so that my computer could be the brain. I wanted it to be fed raw sensor data from the robot, and be able to produce a 3D world using modern software libraries.
Obviously I can't do this on Arduino, but I was hoping I'd be able to transfer all the data the Arduino receives over wifi. I'm starting to realize that my expectations likely wont be met by these boards. I think what I'm looking for is a processor in the 1Ghz+ range running linux.
I'm having some fun with the breadboard and the soldering and the LEDs, but my goal is really to produce a mobile brain that I can spend my time developing software and 'AI' for. I tried to cheap out on the mobile part by relaying all data to a more powerful desktop PC, but it's a limited solution using these components. I'm guessing the next thing I buy will look like the motherboard of a computer. patillac
My original goal was to have a means to communicate any and all data from my robot to my computer so that my computer could be the brain. I wanted it to be fed raw sensor data from the robot, and be able to produce a 3D world using modern software libraries.
Obviously I can't do this on Arduino, but I was hoping I'd be able to transfer all the data the Arduino receives over wifi. I'm starting to realize that my expectations likely wont be met by these boards. I think what I'm looking for is a processor in the 1Ghz+ range running linux.
I'm having some fun with the breadboard and the soldering and the LEDs, but my goal is really to produce a mobile brain that I can spend my time developing software and 'AI' for. I tried to cheap out on the mobile part by relaying all data to a more powerful desktop PC, but it's a limited solution using these components. I'm guessing the next thing I buy will look like the motherboard of a computer.
patillac 2012-07-24 01:49:18 I'll try reducing the voltage/heat when I get a chance and see how it works out.
My original goal was to have a means to communicate any and all data from my robot to my computer so that my computer could be the brain. I wanted it to be fed raw sensor data from the robot, and be able to produce a 3D world using modern software libraries.
Obviously I can't do this on Arduino, but I was hoping I'd be able to transfer all the data the Arduino receives over wifi. I'm starting to realize that my expectations likely wont be met by these boards. I think what I'm looking for is a processor in the 1Ghz+ range running linux.
I'm having some fun with the breadboard and the soldering and the LEDs, but my goal is really to produce a mobile brain that I can spend my time developing software and 'AI' for. I tried to cheap out on the mobile part by relaying all data to a more powerful desktop PC, but it's a limited solution using these components. I'm guessing the next thing I buy will look like the motherboard of a computer. patillac
My original goal was to have a means to communicate any and all data from my robot to my computer so that my computer could be the brain. I wanted it to be fed raw sensor data from the robot, and be able to produce a 3D world using modern software libraries.
Obviously I can't do this on Arduino, but I was hoping I'd be able to transfer all the data the Arduino receives over wifi. I'm starting to realize that my expectations likely wont be met by these boards. I think what I'm looking for is a processor in the 1Ghz+ range running linux.
I'm having some fun with the breadboard and the soldering and the LEDs, but my goal is really to produce a mobile brain that I can spend my time developing software and 'AI' for. I tried to cheap out on the mobile part by relaying all data to a more powerful desktop PC, but it's a limited solution using these components. I'm guessing the next thing I buy will look like the motherboard of a computer.
patillac 2012-07-24 01:49:18 I'll try reducing the voltage/heat when I get a chance and see how it works out.
My original goal was to have a means to communicate any and all data from my robot to my computer so that my computer could be the brain. I wanted it to be fed raw sensor data from the robot, and be able to produce a 3D world using modern software libraries.
Obviously I can't do this on Arduino, but I was hoping I'd be able to transfer all the data the Arduino receives over wifi. I'm starting to realize that my expectations likely wont be met by these boards. I think what I'm looking for is a processor in the 1Ghz+ range running linux.
I'm having some fun with the breadboard and the soldering and the LEDs, but my goal is really to produce a mobile brain that I can spend my time developing software and 'AI' for. I tried to cheap out on the mobile part by relaying all data to a more powerful desktop PC, but it's a limited solution using these components. I'm guessing the next thing I buy will look like the motherboard of a computer. patillac
My original goal was to have a means to communicate any and all data from my robot to my computer so that my computer could be the brain. I wanted it to be fed raw sensor data from the robot, and be able to produce a 3D world using modern software libraries.
Obviously I can't do this on Arduino, but I was hoping I'd be able to transfer all the data the Arduino receives over wifi. I'm starting to realize that my expectations likely wont be met by these boards. I think what I'm looking for is a processor in the 1Ghz+ range running linux.
I'm having some fun with the breadboard and the soldering and the LEDs, but my goal is really to produce a mobile brain that I can spend my time developing software and 'AI' for. I tried to cheap out on the mobile part by relaying all data to a more powerful desktop PC, but it's a limited solution using these components. I'm guessing the next thing I buy will look like the motherboard of a computer.
patillac 2012-07-23 10:54:14 Patillac,
The board might be overheating. You might want to feel it to see if its too toasty, a bit warm is normal. You might try to place a small PC fan on it to disipate some of the heat, or try a lower voltage something in the 7V range.
Also, do you think a constant stream of data is necessary? I think it might be overkill and unnecessary strain on your processing power.
Hector
The board might be overheating. You might want to feel it to see if its too toasty, a bit warm is normal. You might try to place a small PC fan on it to disipate some of the heat, or try a lower voltage something in the 7V range.
Also, do you think a constant stream of data is necessary? I think it might be overkill and unnecessary strain on your processing power.
Hector 2012-07-23 10:54:14 Patillac,
The board might be overheating. You might want to feel it to see if its too toasty, a bit warm is normal. You might try to place a small PC fan on it to disipate some of the heat, or try a lower voltage something in the 7V range.
Also, do you think a constant stream of data is necessary? I think it might be overkill and unnecessary strain on your processing power.
Hector
The board might be overheating. You might want to feel it to see if its too toasty, a bit warm is normal. You might try to place a small PC fan on it to disipate some of the heat, or try a lower voltage something in the 7V range.
Also, do you think a constant stream of data is necessary? I think it might be overkill and unnecessary strain on your processing power.
Hector 2012-07-23 10:54:14 Patillac,
The board might be overheating. You might want to feel it to see if its too toasty, a bit warm is normal. You might try to place a small PC fan on it to disipate some of the heat, or try a lower voltage something in the 7V range.
Also, do you think a constant stream of data is necessary? I think it might be overkill and unnecessary strain on your processing power.
Hector
The board might be overheating. You might want to feel it to see if its too toasty, a bit warm is normal. You might try to place a small PC fan on it to disipate some of the heat, or try a lower voltage something in the 7V range.
Also, do you think a constant stream of data is necessary? I think it might be overkill and unnecessary strain on your processing power.
Hector 2012-07-20 19:07:56 Hector,
My tests so far have been bandwidth tests. They send the maximum amount of data over the Serial connection without delay. I tried a sketch where I sent "Brightness: 0-255" strings corresponding to the read values of a photosensor (wireless light detector woohoo), and I tried a sketch that simply looped and write the integer value 217 over Serial repeatedly.
With the 'light detector' configuration it seemed to stall after about a minute, and when I reduced it to just flooding the Serial connection it lasted for 10 minutes before stalling, but I've yet to leave it alone while it was connected and come back a short time to find it still connected. It seems to be a guaranteed thing, but randomly timed. I'll try sending a few keep-alive bytes on a timer and see if it can stay connected.
I'm powering the arduino with a 9v wall adapter, and there is no USB cable plugged into it when I enable wifi.
Is there anything I can do to debug the disconnects? are there logs or something I can read through? patillac
My tests so far have been bandwidth tests. They send the maximum amount of data over the Serial connection without delay. I tried a sketch where I sent "Brightness: 0-255" strings corresponding to the read values of a photosensor (wireless light detector woohoo), and I tried a sketch that simply looped and write the integer value 217 over Serial repeatedly.
With the 'light detector' configuration it seemed to stall after about a minute, and when I reduced it to just flooding the Serial connection it lasted for 10 minutes before stalling, but I've yet to leave it alone while it was connected and come back a short time to find it still connected. It seems to be a guaranteed thing, but randomly timed. I'll try sending a few keep-alive bytes on a timer and see if it can stay connected.
I'm powering the arduino with a 9v wall adapter, and there is no USB cable plugged into it when I enable wifi.
Is there anything I can do to debug the disconnects? are there logs or something I can read through?
patillac 2012-07-20 19:07:56 Hector,
My tests so far have been bandwidth tests. They send the maximum amount of data over the Serial connection without delay. I tried a sketch where I sent "Brightness: 0-255" strings corresponding to the read values of a photosensor (wireless light detector woohoo), and I tried a sketch that simply looped and write the integer value 217 over Serial repeatedly.
With the 'light detector' configuration it seemed to stall after about a minute, and when I reduced it to just flooding the Serial connection it lasted for 10 minutes before stalling, but I've yet to leave it alone while it was connected and come back a short time to find it still connected. It seems to be a guaranteed thing, but randomly timed. I'll try sending a few keep-alive bytes on a timer and see if it can stay connected.
I'm powering the arduino with a 9v wall adapter, and there is no USB cable plugged into it when I enable wifi.
Is there anything I can do to debug the disconnects? are there logs or something I can read through? patillac
My tests so far have been bandwidth tests. They send the maximum amount of data over the Serial connection without delay. I tried a sketch where I sent "Brightness: 0-255" strings corresponding to the read values of a photosensor (wireless light detector woohoo), and I tried a sketch that simply looped and write the integer value 217 over Serial repeatedly.
With the 'light detector' configuration it seemed to stall after about a minute, and when I reduced it to just flooding the Serial connection it lasted for 10 minutes before stalling, but I've yet to leave it alone while it was connected and come back a short time to find it still connected. It seems to be a guaranteed thing, but randomly timed. I'll try sending a few keep-alive bytes on a timer and see if it can stay connected.
I'm powering the arduino with a 9v wall adapter, and there is no USB cable plugged into it when I enable wifi.
Is there anything I can do to debug the disconnects? are there logs or something I can read through?
patillac 2012-07-20 19:07:56 Hector,
My tests so far have been bandwidth tests. They send the maximum amount of data over the Serial connection without delay. I tried a sketch where I sent "Brightness: 0-255" strings corresponding to the read values of a photosensor (wireless light detector woohoo), and I tried a sketch that simply looped and write the integer value 217 over Serial repeatedly.
With the 'light detector' configuration it seemed to stall after about a minute, and when I reduced it to just flooding the Serial connection it lasted for 10 minutes before stalling, but I've yet to leave it alone while it was connected and come back a short time to find it still connected. It seems to be a guaranteed thing, but randomly timed. I'll try sending a few keep-alive bytes on a timer and see if it can stay connected.
I'm powering the arduino with a 9v wall adapter, and there is no USB cable plugged into it when I enable wifi.
Is there anything I can do to debug the disconnects? are there logs or something I can read through? patillac
My tests so far have been bandwidth tests. They send the maximum amount of data over the Serial connection without delay. I tried a sketch where I sent "Brightness: 0-255" strings corresponding to the read values of a photosensor (wireless light detector woohoo), and I tried a sketch that simply looped and write the integer value 217 over Serial repeatedly.
With the 'light detector' configuration it seemed to stall after about a minute, and when I reduced it to just flooding the Serial connection it lasted for 10 minutes before stalling, but I've yet to leave it alone while it was connected and come back a short time to find it still connected. It seems to be a guaranteed thing, but randomly timed. I'll try sending a few keep-alive bytes on a timer and see if it can stay connected.
I'm powering the arduino with a 9v wall adapter, and there is no USB cable plugged into it when I enable wifi.
Is there anything I can do to debug the disconnects? are there logs or something I can read through?
patillac 2012-07-20 11:23:43 Hi Patillac,
You mean the Wifi shield stalls after 10 minutes of operation?
how much power are you supplying for the wifi shield?
Have you tried running a smaller sketch which only sends a few bytes to keep the connection alive?
Thanks for the feedback on the wiki. The ZIP file tutorial was written by a colleague.
Hector
You mean the Wifi shield stalls after 10 minutes of operation?
how much power are you supplying for the wifi shield?
Have you tried running a smaller sketch which only sends a few bytes to keep the connection alive?
Thanks for the feedback on the wiki. The ZIP file tutorial was written by a colleague.
Hector 2012-07-20 11:23:43 Hi Patillac,
You mean the Wifi shield stalls after 10 minutes of operation?
how much power are you supplying for the wifi shield?
Have you tried running a smaller sketch which only sends a few bytes to keep the connection alive?
Thanks for the feedback on the wiki. The ZIP file tutorial was written by a colleague.
Hector
You mean the Wifi shield stalls after 10 minutes of operation?
how much power are you supplying for the wifi shield?
Have you tried running a smaller sketch which only sends a few bytes to keep the connection alive?
Thanks for the feedback on the wiki. The ZIP file tutorial was written by a colleague.
Hector 2012-07-20 11:23:43 Hi Patillac,
You mean the Wifi shield stalls after 10 minutes of operation?
how much power are you supplying for the wifi shield?
Have you tried running a smaller sketch which only sends a few bytes to keep the connection alive?
Thanks for the feedback on the wiki. The ZIP file tutorial was written by a colleague.
Hector
You mean the Wifi shield stalls after 10 minutes of operation?
how much power are you supplying for the wifi shield?
Have you tried running a smaller sketch which only sends a few bytes to keep the connection alive?
Thanks for the feedback on the wiki. The ZIP file tutorial was written by a colleague.
Hector 2012-07-19 19:07:14 Hey Hector,
I love wikis! I've only glanced at the new wifi wiki so far (I'll read it over a few times after work) but it's looking good. It resembles a couple tutorial PDFs I've followed (one I believe was by you - a .zip attached to a forum post detailing how to use AT commands instead of a GUI Wizard to configure the arduino wifi).
I think the two most helpful things I remember about the past couple days is that:
1) If something doesn't work in PuTTy, then type it into notepad.exe and copy/paste it into PuTTy.
2) Jumpers set to WIFI lets you talk to the wifi board via wifi; Jumpers set to USB lets you talk to the wifi board via usb; No jumpers lets you talk to the arduino via usb.
Perhaps your configuration of PuTTy fixes the need to use notepad, and I'm only 99% sure about the jumpers... not quite 100% yet. I need to do some trial and error, but so far that seems to be the way things are. EDIT: Okay, you covered both of these in the wiki
One thing I'd be interested in reading about is data transfer rates, and what affects them. I've heard of baud rate many times in my life, but I have no idea how it might affect bandwidth, nor do I know what else might affect it. I wrote a small program to try and send as much data as possible through the Serial object and the transfer rate seems to be a few kilobytes per second. Also, it seems to disconnect after about 10 minutes and remains powered but unresponsive until power is reset. After being reset it acts normally again for some time (1-10 minutes) and disconnects. It's as if it hits some upper limit somewhere and fails. I tried removing all code that might allocate memory or consume more resources over time, and it still eventually putters out. Perhaps it's a setting somewhere that isn't quite right. patillac
I love wikis! I've only glanced at the new wifi wiki so far (I'll read it over a few times after work) but it's looking good. It resembles a couple tutorial PDFs I've followed (one I believe was by you - a .zip attached to a forum post detailing how to use AT commands instead of a GUI Wizard to configure the arduino wifi).
I think the two most helpful things I remember about the past couple days is that:
1) If something doesn't work in PuTTy, then type it into notepad.exe and copy/paste it into PuTTy.
2) Jumpers set to WIFI lets you talk to the wifi board via wifi; Jumpers set to USB lets you talk to the wifi board via usb; No jumpers lets you talk to the arduino via usb.
Perhaps your configuration of PuTTy fixes the need to use notepad, and I'm only 99% sure about the jumpers... not quite 100% yet. I need to do some trial and error, but so far that seems to be the way things are. EDIT: Okay, you covered both of these in the wiki
One thing I'd be interested in reading about is data transfer rates, and what affects them. I've heard of baud rate many times in my life, but I have no idea how it might affect bandwidth, nor do I know what else might affect it. I wrote a small program to try and send as much data as possible through the Serial object and the transfer rate seems to be a few kilobytes per second. Also, it seems to disconnect after about 10 minutes and remains powered but unresponsive until power is reset. After being reset it acts normally again for some time (1-10 minutes) and disconnects. It's as if it hits some upper limit somewhere and fails. I tried removing all code that might allocate memory or consume more resources over time, and it still eventually putters out. Perhaps it's a setting somewhere that isn't quite right.
patillac 2012-07-19 19:07:14 Hey Hector,
I love wikis! I've only glanced at the new wifi wiki so far (I'll read it over a few times after work) but it's looking good. It resembles a couple tutorial PDFs I've followed (one I believe was by you - a .zip attached to a forum post detailing how to use AT commands instead of a GUI Wizard to configure the arduino wifi).
I think the two most helpful things I remember about the past couple days is that:
1) If something doesn't work in PuTTy, then type it into notepad.exe and copy/paste it into PuTTy.
2) Jumpers set to WIFI lets you talk to the wifi board via wifi; Jumpers set to USB lets you talk to the wifi board via usb; No jumpers lets you talk to the arduino via usb.
Perhaps your configuration of PuTTy fixes the need to use notepad, and I'm only 99% sure about the jumpers... not quite 100% yet. I need to do some trial and error, but so far that seems to be the way things are. EDIT: Okay, you covered both of these in the wiki
One thing I'd be interested in reading about is data transfer rates, and what affects them. I've heard of baud rate many times in my life, but I have no idea how it might affect bandwidth, nor do I know what else might affect it. I wrote a small program to try and send as much data as possible through the Serial object and the transfer rate seems to be a few kilobytes per second. Also, it seems to disconnect after about 10 minutes and remains powered but unresponsive until power is reset. After being reset it acts normally again for some time (1-10 minutes) and disconnects. It's as if it hits some upper limit somewhere and fails. I tried removing all code that might allocate memory or consume more resources over time, and it still eventually putters out. Perhaps it's a setting somewhere that isn't quite right. patillac
I love wikis! I've only glanced at the new wifi wiki so far (I'll read it over a few times after work) but it's looking good. It resembles a couple tutorial PDFs I've followed (one I believe was by you - a .zip attached to a forum post detailing how to use AT commands instead of a GUI Wizard to configure the arduino wifi).
I think the two most helpful things I remember about the past couple days is that:
1) If something doesn't work in PuTTy, then type it into notepad.exe and copy/paste it into PuTTy.
2) Jumpers set to WIFI lets you talk to the wifi board via wifi; Jumpers set to USB lets you talk to the wifi board via usb; No jumpers lets you talk to the arduino via usb.
Perhaps your configuration of PuTTy fixes the need to use notepad, and I'm only 99% sure about the jumpers... not quite 100% yet. I need to do some trial and error, but so far that seems to be the way things are. EDIT: Okay, you covered both of these in the wiki
One thing I'd be interested in reading about is data transfer rates, and what affects them. I've heard of baud rate many times in my life, but I have no idea how it might affect bandwidth, nor do I know what else might affect it. I wrote a small program to try and send as much data as possible through the Serial object and the transfer rate seems to be a few kilobytes per second. Also, it seems to disconnect after about 10 minutes and remains powered but unresponsive until power is reset. After being reset it acts normally again for some time (1-10 minutes) and disconnects. It's as if it hits some upper limit somewhere and fails. I tried removing all code that might allocate memory or consume more resources over time, and it still eventually putters out. Perhaps it's a setting somewhere that isn't quite right.
patillac 2012-07-19 19:07:14 Hey Hector,
I love wikis! I've only glanced at the new wifi wiki so far (I'll read it over a few times after work) but it's looking good. It resembles a couple tutorial PDFs I've followed (one I believe was by you - a .zip attached to a forum post detailing how to use AT commands instead of a GUI Wizard to configure the arduino wifi).
I think the two most helpful things I remember about the past couple days is that:
1) If something doesn't work in PuTTy, then type it into notepad.exe and copy/paste it into PuTTy.
2) Jumpers set to WIFI lets you talk to the wifi board via wifi; Jumpers set to USB lets you talk to the wifi board via usb; No jumpers lets you talk to the arduino via usb.
Perhaps your configuration of PuTTy fixes the need to use notepad, and I'm only 99% sure about the jumpers... not quite 100% yet. I need to do some trial and error, but so far that seems to be the way things are. EDIT: Okay, you covered both of these in the wiki
One thing I'd be interested in reading about is data transfer rates, and what affects them. I've heard of baud rate many times in my life, but I have no idea how it might affect bandwidth, nor do I know what else might affect it. I wrote a small program to try and send as much data as possible through the Serial object and the transfer rate seems to be a few kilobytes per second. Also, it seems to disconnect after about 10 minutes and remains powered but unresponsive until power is reset. After being reset it acts normally again for some time (1-10 minutes) and disconnects. It's as if it hits some upper limit somewhere and fails. I tried removing all code that might allocate memory or consume more resources over time, and it still eventually putters out. Perhaps it's a setting somewhere that isn't quite right. patillac
I love wikis! I've only glanced at the new wifi wiki so far (I'll read it over a few times after work) but it's looking good. It resembles a couple tutorial PDFs I've followed (one I believe was by you - a .zip attached to a forum post detailing how to use AT commands instead of a GUI Wizard to configure the arduino wifi).
I think the two most helpful things I remember about the past couple days is that:
1) If something doesn't work in PuTTy, then type it into notepad.exe and copy/paste it into PuTTy.
2) Jumpers set to WIFI lets you talk to the wifi board via wifi; Jumpers set to USB lets you talk to the wifi board via usb; No jumpers lets you talk to the arduino via usb.
Perhaps your configuration of PuTTy fixes the need to use notepad, and I'm only 99% sure about the jumpers... not quite 100% yet. I need to do some trial and error, but so far that seems to be the way things are. EDIT: Okay, you covered both of these in the wiki
One thing I'd be interested in reading about is data transfer rates, and what affects them. I've heard of baud rate many times in my life, but I have no idea how it might affect bandwidth, nor do I know what else might affect it. I wrote a small program to try and send as much data as possible through the Serial object and the transfer rate seems to be a few kilobytes per second. Also, it seems to disconnect after about 10 minutes and remains powered but unresponsive until power is reset. After being reset it acts normally again for some time (1-10 minutes) and disconnects. It's as if it hits some upper limit somewhere and fails. I tried removing all code that might allocate memory or consume more resources over time, and it still eventually putters out. Perhaps it's a setting somewhere that isn't quite right.
patillac 2012-07-19 13:41:17 OK,
The Wifi Shield Wiki is finally ready! Please let me know if I botched something up, or if I missed something. I will add it immediately. Hector
The Wifi Shield Wiki is finally ready! Please let me know if I botched something up, or if I missed something. I will add it immediately.
Hector 2012-07-19 13:41:17 OK,
The Wifi Shield Wiki is finally ready! Please let me know if I botched something up, or if I missed something. I will add it immediately. Hector
The Wifi Shield Wiki is finally ready! Please let me know if I botched something up, or if I missed something. I will add it immediately.
Hector 2012-07-19 13:41:17 OK,
The Wifi Shield Wiki is finally ready! Please let me know if I botched something up, or if I missed something. I will add it immediately. Hector
The Wifi Shield Wiki is finally ready! Please let me know if I botched something up, or if I missed something. I will add it immediately.
Hector 2012-07-19 11:06:35 Hi Patillac,
No worries, we've all been there and it can be a bit frustrating to no find good documentation or to understand what you are looking at the first time. Just keep at it, these things take time, but one day it just clicks...
Here is the Wifi shield Schem
it is listed in the wifi shield product page under "documents"
In our site there are 4 very important components to every product:
1. Product page.- Contains a brief description about the product, along with tech specs, and links to documentation.
2. Wiki.- Contains a more detailed explanation about the product along with connection diagrams and sample codes. This is the best place to check for ideas! It is chock full of sample codes and connection diagrams. So it will give you a good education about how to connect things. If you find some error please let us know so we can fix it!
3. Community(blog).- Contains projects, guides, news, etc... Mostly contributed by us, but if you feel inclined to do so, you may e-mail me for "author" access and you can write your own posts about your projects on our blog.
4. Forum.- Here you can vent your frustrations, ask for help, or look for others in a similar situation.
Lastly, there is also our twitter account "@dfrobotcn" Youtube: "DFRobotcn" and facebook: "DFRobot"
Where we post news and updates, along with notifications about new products. Hector
No worries, we've all been there and it can be a bit frustrating to no find good documentation or to understand what you are looking at the first time. Just keep at it, these things take time, but one day it just clicks...
Here is the Wifi shield Schem
it is listed in the wifi shield product page under "documents"
In our site there are 4 very important components to every product:
1. Product page.- Contains a brief description about the product, along with tech specs, and links to documentation.
2. Wiki.- Contains a more detailed explanation about the product along with connection diagrams and sample codes. This is the best place to check for ideas! It is chock full of sample codes and connection diagrams. So it will give you a good education about how to connect things. If you find some error please let us know so we can fix it!
3. Community(blog).- Contains projects, guides, news, etc... Mostly contributed by us, but if you feel inclined to do so, you may e-mail me for "author" access and you can write your own posts about your projects on our blog.
4. Forum.- Here you can vent your frustrations, ask for help, or look for others in a similar situation.
Lastly, there is also our twitter account "@dfrobotcn" Youtube: "DFRobotcn" and facebook: "DFRobot"
Where we post news and updates, along with notifications about new products.
Hector 2012-07-19 11:06:35 Hi Patillac,
No worries, we've all been there and it can be a bit frustrating to no find good documentation or to understand what you are looking at the first time. Just keep at it, these things take time, but one day it just clicks...
Here is the Wifi shield Schem
it is listed in the wifi shield product page under "documents"
In our site there are 4 very important components to every product:
1. Product page.- Contains a brief description about the product, along with tech specs, and links to documentation.
2. Wiki.- Contains a more detailed explanation about the product along with connection diagrams and sample codes. This is the best place to check for ideas! It is chock full of sample codes and connection diagrams. So it will give you a good education about how to connect things. If you find some error please let us know so we can fix it!
3. Community(blog).- Contains projects, guides, news, etc... Mostly contributed by us, but if you feel inclined to do so, you may e-mail me for "author" access and you can write your own posts about your projects on our blog.
4. Forum.- Here you can vent your frustrations, ask for help, or look for others in a similar situation.
Lastly, there is also our twitter account "@dfrobotcn" Youtube: "DFRobotcn" and facebook: "DFRobot"
Where we post news and updates, along with notifications about new products. Hector
No worries, we've all been there and it can be a bit frustrating to no find good documentation or to understand what you are looking at the first time. Just keep at it, these things take time, but one day it just clicks...
Here is the Wifi shield Schem
it is listed in the wifi shield product page under "documents"
In our site there are 4 very important components to every product:
1. Product page.- Contains a brief description about the product, along with tech specs, and links to documentation.
2. Wiki.- Contains a more detailed explanation about the product along with connection diagrams and sample codes. This is the best place to check for ideas! It is chock full of sample codes and connection diagrams. So it will give you a good education about how to connect things. If you find some error please let us know so we can fix it!
3. Community(blog).- Contains projects, guides, news, etc... Mostly contributed by us, but if you feel inclined to do so, you may e-mail me for "author" access and you can write your own posts about your projects on our blog.
4. Forum.- Here you can vent your frustrations, ask for help, or look for others in a similar situation.
Lastly, there is also our twitter account "@dfrobotcn" Youtube: "DFRobotcn" and facebook: "DFRobot"
Where we post news and updates, along with notifications about new products.
Hector 