elfege
Hello,
After unsuccessfully trying the UART WIFI suggested by this website, mainly because of power issues though I could have it to work and run for a little while, I tried another UART WIFI which seems much, much, much more reliable and user friendly since it has its own AP mode which allows you to configure it through web interface directly (you do not need to connect it to USB TTL module) and a quite efficient factory restoration process in case you input the wrong settings.
The model hardware name on Amazon is "Embedded Wifi To Serial Module RS232UART WIFI Board Module External Antenna"
I can get a connexion to EZB using both methods : typing directly the IP address + port into ARC's connection or through serial emulation.
However, when I use serial emulation (HW virtual serial port) I get a repeating message such as : "Disgard incoming buffer (This should never happen)"
And if I connect through IP address directly I get something really weird : it says that I have to upgrade the EZBoard firmware and, most of all, it shows different versions numbers : 24.x , 14, 17...
Here is the full debug report in cas God (DJ) took a look at it. I remember someone had ordered the same device so I'm posting this in case he found the proper settings. I set the module to 9600 bauds, TCP server mode. Let me know if you need more details.
Here is the debug report.
EZB 0: TCP Server stopped Camera Disabled
EZB 1: TCP Server stopped
EZB 2: TCP Server stopped
EZB 3: TCP Server stopped
EZB 4: TCP Server stopped
Attempting connection on 192.168.0.10:8086 Connection Failed: System.Exception: Controller Not Responding at EZ_B.EZB.Connect(String hostname, String tcpPassword, Int32 baudRate) Disconnected Attempting connection on 192.168.0.10:8086 Connection Failed: System.Exception: Controller Not Responding at EZ_B.EZB.Connect(String hostname, String tcpPassword, Int32 baudRate) Disconnected Attempting connection on 192.168.0.10:8086 Connected to 192.168.0.10:8086 EZ-B reports EZ-B Firmware V14.5 Connection Failed: System.Exception: Invalid Firmware Version. Please Upgrade. EZ-B Reports v14.5. This copy of ARC requires v16
Would you like to view the help tutorial with instructions on how to upgrade the firmware? at EZ_B.EZB.Connect(String hostname, String tcpPassword, Int32 baudRate) Disconnected Attempting connection on COM8 Connected to COM8 at 9600 EZ-B reports EZ-B Firmware V24.5 Connected Disgard incoming buffer (This should never happen) (...) Disgard incoming buffer (This should never happen) Disconnected [by user]
Hope this helps.
It's ok, it works on my side too now ! Thanks a lot.
The WiFi board seems to handle a few screens that are real time hogs.
I just received my Roving Networks WiFi device, and I hope to have time to test it tonight. I'll update here with results.
Alan
Looking forward to seeing the result! Thank u for sharing
Grrr. Frustration number one is that the headers on the board are for RS-232. For TTL I am going to need to solder wires to through holes on the board. Not a big deal, but means I probably can't return it if it doesn't work for me.
Alan
I guess i need some soldering practice. I soldered the necessary wires on, and I got the board hooked up to my USB Uart and was able to communicate with it and get it configured for my network.
Moved it to the EZ-B, and I could telnet in, but could not see the EZ-B from ARC either direct or with HW virtual port. After wasting a couple of hours I went back to the USB Uart, and I could receive data, but not send any serial data. After again spending way too much time, I realized that the transmit wire was much more flexible than the other... Just before it broke off the board. (once again teaching me to always always always break out the multi-meter at the first sign of trouble, and maybe to stop trying to work on my robot late at night).
Too late to mess with it more tonight. Maybe tomorrow night, but I am getting frustrated with trying to wifi enable my EZ-B. Spent too much money for too many problems.
Alan
With the Roving Networks device, I am having the same kinds of issues (EZ-B reporting the wrong firmware, not connecting with direct TCP connection and needing the virtual comm port). I believe I know what may be causing the wrong firmware errors. When I make a Telnet connection to the device, whether or not it is connected to the EZ-B through the TTL connection, it gives its own greeting "HELLO" before connecting. I believe ARC is seeing this and mis-interpreting it. On the Roving Networks device, this greeting can be changed, but it can not be removed.
Unfortunately, despite replacing the RX wire and having good continuity, the board no longer seems to be able to receive data over TTL. It still sends, and I can connect via Telnet and interact, but neither the EZ-B serial terminal, or another serial app I have can connect through my USB UART and it seems the EZ-B is no longer able to send it data either.
I am putting this project aside for a while until I get the rest of the robot functional, and then will call the vendor to see if I broke the board or if I accidentally turned off receive or something (although I did a factory reset and it still can't receive, so I suspect another $80 down the drain, and Bluetooth is actually good enough for this bot. I only started playing with WiFi to try and help you all, and because I did want it in my second bot).
I don't think this is a total waste though because the Roving Networks device has a lot of other capabilities as a remote sensor device that I may put to use (and those functions don't need TTL).
Alan