I got an elechouse TLG10UA03 kit which I have up and working now, but can't get ARC to connect to my EZ-B board yet.
I have verified that I can send and recieve characters thru the wifi TLG10UA03 link using the kits USB to Serial TTL converter with realterm on one computer and telnet to it over wifi on a second computer. Ascii text goes back and forth just fine. So my serial link is up.
I connected it to my robot with a 3.3V regulator as the power source (the ez-b 3.3V supply didn't seem to have enough current to make it work correctly) and I can see the wifi modules web page and get a connect with telnet to it. On telnet I never see anything come from the ez-b board and when I put in the ip address and port in the ARC connect box, ARC seems to indicate that it is connected but my robot does not appear to be recieving any commands. It does take a long time for ARC to come back with the connect which makes me think I am just getting a timeout. Not sure what piece of the puzzle I am missing. I have tried swapping the TX and RX pins between the EZ-B and the wifi TLG10UA03 link but the results are the same both ways. No feedback in a telnet session and ARC just says connected but no real connection is made.
So I am kind of stuck at the moment with that part of my project.
Also I have been looking for a wifi camera that can replace the current wireless one that is part of the ez-b kit.
I was wondering if something link the AI Ball Mini Wifi Spy Camera IP Wireless Camera would work with the ARC software to provide a true wifi robot. ( http://www.thumbdrive.com/aiball/ )
Any suggestion for the camera would be appreciated. I noticed someone had a camera working with X-Bee. Could that approach work with a wifi module? Not sure about interference with two wifi sources on the same frequencies on the robot.
I am trying to get a robot that can roam throughout my whole house and yard.
Upgrade to ARC Pro
Harnessing the power of ARC Pro, your robot can be more than just a simple automated machine.
I think it was in the Elechouse thread where several of us were trying to get it working. I even reported that I could get ARC to see it that way, but I couldn't get it to talk, it kept disconnecting. I don't know if I posted my analysis of why it didn't work, but I did finally determine it is because it is giving its own greeting before opening the port tot he EZ-B, and ARC is reading something in that greeting as the firmware version being wrong, so it disconnects.
Also, I don't recall if it is the Elechouse WiFi or the USB TTL that came with mine, but one of them the TX and RX are mis-labeled or mis-wired and you don't do a crossover to make it work.
I am almost done with my home office renovation and will be able to get back to working on my robot and will have it on the bench so I can more accurately answer these questions.
I wish there was something I could type into realterm to get the EZ-B board to respond with its firmware version or something as a debug tool. This would allow me to at least see if I had baud rate issues or if it is a link reliability issue. As I could see if I am really getting data back and forth between my laptop and the ez-b board. There are laptop setting, Wifi router settings, elechouse wifi board settings, and wiring all involved in getting this to work. I think I am having a settings or wiring problem to the elechouse wifi board. I will be going back over my setting and wiring again. It may be a grounding issue. There really needs to be a tutorial done on getting wifi to work. At least with the recommended elechouse board.
Any thoughts on a simple (inexpensive hopefully) wifi camera that would work with ARC? I am starting to dabble with the motion tracking.
I thought about looking for a serial to ethernet adapter instead of the elechouse wifi board and putting a wifi game adapter or router on the robot. This would allow a standard ethernet camera and the ez-b to share the wifi link, but I would rather the robot be smaller and not have all the weight with the extra hardware.
Unfortunately, I am again away from my computer, but I'll post a link tomorrow to a unit that some have had better luck with, and a post about configuring it. My replacement is still in its box on my workbench, but I hope to get to hooking it up soon. All my other parts are tested and ready for final assembly, just need a few hours free from other obligations to upgrade my box bot to my tread bot. Then I can get started on the real project (Steampunk K9).
Elechouse WiFi thread has a ton of information about the Elechouse device. I'ss post again as soon as I find the thread that has the other device I was mentioning.
I also tried this device: Roving Networks WiFi and it does a lot of very cool things, but TTL Uart is not one of them
Better WiFi UART
The idea would be to use the wifi in infrastructure mode while the robot is at home and if he goes to visit someone he could connect to a laptop with blue tooth.
Anyone know of any wire length limitations on the EZ-B communication port?
Realterm was a nice test program to verify connectivity. I used it to verify I had the TX and RX wired up correctly and once I got the EZ-B to answer in realterm; it worked fine in EZ-Builider.
Thanks to all who helped be get this working. The EZ-B community is great.
Any thoughts on a wifi camera and making the EZ-B communcation switchable between bluetooth and wifi?
When you say "switchable between Bluetooth and wifi" can you expand on your idea?
If you want both on the same default I/o lines on the EZ-B board you'll need some sort of electronic controls to switch between the two, or manual controls at least. Then you'd probably need to refresh your connection the ARC software for the new communication method.
More on the settings that worked for me. Based on one of the Posts that I was pointed toward with the excellent help, I set the the Elechouse board to 9600 baud, 8 data bits, 1 stop bit. (This is not the factory default). Before I attempted any wifi setup.
Same schematic just upload it twice by accident since the EZ-robot said told me it had an error. I have been getting it every time lately.
Here is the more important part. Baud Rate Settings under advanced. Remember once the baud rate setting are saved to the elechouse you have to change your com port to match.
The setting to turn it into a pass thru uart are next. The are done using the wifi uarts web server.
The settings should look something like this with of course the appropriate changes to match the wifi network.
and the advance setting will look like this.
The next step is the Virtual Com software.
The setting on the virtual com port software should look like this:
Note the port number is 6666 to match up with the basic setting in the wifi uart web page.
The other important setting on the virtual com port are:
Be sure to save your setting using the save to ini button.
The next step for me was a test with realterm software to make sure the wifi uart was a true pass thru device.