RN-XV Wifly

Warning

Page is depreciated. All notes added to the Wifly components page and future updates will go there. https://mbed.org/components/Roving-Networks-WiFly-RN-171-XV

Command Sheet

Tips

  • do a scan and look for the same network as the user is trying to connect to - otherwise connection will always fail
    • seen funny things where a network was visible to everything but the RN-XV - fix = scan??
  • firmware update
    • connect to WiFi
    • ftp update
    • boot image
    • factory R
    • power cycle

Device Wont connect to WiFi but you're sure the settings are correct

for me this fixed the problem being that I was 1000% certain that the ssid and phrase were correct and I always got:

<4.00> join
Auto-Assoc McGroves chan=0 mode=NONE FAILED

or

Auto-Assoc McGroves chan=1 mode=MIXED SCAN OK
<4.00> Joining McGroves now..
Disconn from McGroves,AUTH-ERR
AP mode as McGroves on chan 1
DCHP Server Init

From either of these states you can see the result from scan:

<4.00> scan
<4.00>
SCAN:Found 0
END:
scan
<4.00>
SCAN:Found 6
01,01,-85,04,3104,1c,00,c0:83:0a:41:99:e1,2WIRE819
02,01,-40,04,1104,1c,00,14:5b:d1:ec:6e:00,McGroves
03,02,-73,04,3104,28,c0,00:26:f2:fa:de:f5,JANOV2
04,06,-70,04,3104,28,40,28:c6:8e:16:89:b8,NETGEAR50
05,11,-84,04,1104,28,40,f8:7b:8c:0b:18:e9,JANOV
06,11,-82,04,1104,1c,40,58:6d:8f:6c:83:38,Gpatrick
END:

Try this

  1. power cycle the device
  2. send $$$
  3. send factory RESET
  4. send scan (if your device isn't here or if all 000000's are returned, there's your problem)
    • if 0 networks are returned or all the info is 0's keep sending scan until you get multiple valid networks. Then send factory RESET
    • I think the critical step is that you get valid networks upon sending the first scan. Otherwise reset the device and start again
  5. send set wlan ssid network_name
  6. send set wlan phrase password (spaces don't seem to be supported - I didn't test this but read about other peoples problems while looking for a solution here)
  7. send join
  8. send ftp update
  9. send boot image _ _ (the number of file returned from ftp update)
  10. send factory R
  11. power cycle the board

Not sure if this problem is fixed with 4.0.0.1. Every device I had was 4.0.0 (problems) and once connected to a network I updated the firmware.


Please log in to post comments.