Migrating From the WA1000

 Top  Previous  Next

This topic details the differences between the previous and current incarnation of the wln object. This difference is related to switching to the new GA1000 hardware. The old WA1000 Wi-Fi add-on module has been replaced with the new GA1000 device. The wln object has been affected, but the changes are minimal. Here is what's different:

•Wln Tasks: two new tasks -- wln.networkstart and wln.networkstop.
•Wln State Transitions: now includes creating and terminating own ad-hoc network.
•Applying Reset: you can't turn the power on/off anymore, you can just reset the Wi-Fi;
•Configuring Interface Lines: all interface lines can now be remapped, not just the CS line. Any 5 I/O lines (including RST) of your programmable module can be used to control the Wi-Fi add-on. See wln.clkmap, wln.dimap, wln.domap.
•Setting MAC address (wln.mac): it is now optional. The Wi-Fi add-on has a factory-assigned MAC. Leave the wln.mac uninitialized ("0.0.0.0.0.0"), boot up (wln.boot) and the pre-assigned MAC will be used.
•Selecting Domain: domain list has changed -- see wln.domain.
•Booting Up the Hardware: the firmware file for the Wi-Fi add-on is now called "ga1000fw.bin".
•Setting TX Power: power selection is in the 4-15 range now (see wln.settxpower).
•Setting WEP Mode and Key: no more wln.wepkey1...wln.wepkey4, wln.wepmode deleted too. The wln.setwep method now accepts the mode and the key directly. Keys 2-4 are not used, so there is only one key to set.
•Associating With Selected Network: wln.associate now accepts bssmode and ssid as arguments, so wln.bssmode and wln.ssid have been deleted. Also, the wln.associate won't cause the Wi-Fi interface to start its own ad-hoc network. This is now done using wln.networkstart.
•Creating Own Ad-hoc Network (wln.networkstart), Terminating Own Ad-hoc Network (wln.networkstop) are completely new topics. wln.associationstate now  has a new state: 2- PL_WLN_OWN_NETWORK. Wln.defaultibsschannel is gone -- wln.networkstart takes this as argument.