The RN-XV module by Roving Networks is a certified Wi-Fi solution especially designed for customer who want to migrate their existing 802.15.4 architecture to a standard TCP/IP based platform without having to redesign their existing hardware. In other words, if your project is set up for XBee and you want to move it to a standard WiFi network, you can drop this in the same socket without any other new hardware.
The RN-XV module is based upon Roving Networks' robust RN-171 Wi-Fi module and incorporates 802.11 b/g radio, 32 bit processor, TCP/IP stack, real-time clock, crypto accelerator, power management unit and analog sensor interface.The module is pre-loaded with Roving firmware to simplify integration and minimize development time of your application. In the simplest configuration, the hardware only requires four connections (PWR, TX, RX and GND) to create a wireless data connection.
The problem: Microchip bought Roving networks and the FTP server your modules firmware is trying to reach no longer exists. We have a procedure to fix this this though. First, reset your module to the factory defaults:
Now connect to your Wlan:
set wlan ssid *your SSID* set wlan passphrase *your WiFi password* save reboot
Now re-connect to your wlan and configure the new FTP settings: (We had to try the update twice to get it to work)
set ftp address 0 set dns backup rn.microchip.com save ftp update
You should see something like this:
<2.31> ftp update <2.31> FTP connecting to 126.96.36.199 FTP file=34 ………………………………………………………….. FTP OK. UPDATE OK
save factory RESET reboot
At this point you will need to re-enter your SSID and pass phrase and re connect to your wlan. After you’ve done that, try pinging google to make sure you’re live.
ping dgoogle.com 4
(you have to add the “d” to the beginning of the hostname in order for the module to do a DNS lookup.) You should see something like this:
Ping try (len=32) 188.8.131.52 <4.41> PING reply from 184.108.40.206 PING reply from 220.127.116.11 PING reply from 18.104.22.168 PING reply from 22.214.171.124
That should get you going!
If it requires power, you need to know how much, what all the pins do, and how to hook it up. You may need to reference datasheets, schematics, and know the ins and outs of electronics.
Skill Level: Rookie - You may be required to know a bit more about the component, such as orientation, or how to hook it up, in addition to power requirements. You will need to understand polarized components.
See all skill levels
Based on 8 ratings:
1 of 1 found this helpful:
If you're trying to replace an XBee-based solution - or you already have all of the XBee support hardware you want - this is a pretty solid option.
It is not 5V tolerant, and the sensor lines are only rated for 1.5V, so it's not necessarily trivial to add this in to an existing project.
The onboard configuration options are great - the v4 firmware is possibly useful without another microcontroller for certain logging applications. Getting it on to local WiFi is pretty easy.
There's no SSL/HTTPS support and I can't find a firmware SDK.
Client mode worked really well, but using it as a server suffered from a few issues - sockets had to time out to close, drastically lowering throughput.
I was astounded at the quality of this module for how cheap it is. The documentation is flawless, and I had no issues setting this up for my exact needs. It also performed incredibly well, even in a noisy PLC lab at my school where I was doing an industry project my robot was able to drive out the door, down the hallway, and into the grounds. If you need a cheap easy to use wifi module that will perform well, you can't do much better than this
I got a regulator for it so I can run 5 volts on the Io. Im amazed how much it can do. I.e. Build in web configuration. If u like to tinker like me, u will love this.
If this device is used through an existing WIFI router, it works very well. Communications is fast and reliable. On the other hand, if this device is used as an access point it generally does not work. Windows 7 PCs can connect to it, but the firmware will report CRASH and then reboot as soon as an attempt to send data occurs. Numerous reports of this are posted on the Internet, so this is not a problem that only I have observed. Microchip bought out Roving Networks, and does not actually seem interested in fixing this problem.
Sorry to hear about this issue. I wish there was more we could do to help.
I'm using this with the LPC1768 mbed on the application board. I'll suggest increasing the LEDs' resistors from 220 Ohms to 1.5k or even 2.2k.
I have a few of these, mostly used as an alternative to Xbee devices on a sensor network when it's more convenient to use Wifi. They mostly work as advertised, but about half of them fail to "sleep" which makes them not that useful for battery operated applications. In theory you set up a configuration allowing "set sys sleep N" and the module should go into low power mode drawing <100uA until an event wakes it up (a character interrupt or a pin signal). Normally this works but a few of the modules I've tried draw 3-10mA in this state vs <100uA, and they're too expensive to keep buying new ones until I get one that works. Probably ESP8266 is a better direction to go in now unless you need the specific command set and pinout.
0 of 1 found this helpful:
Best WI FI they cover all my needs thanks