Datasheet

Flyport Wi-Fi and Ethernet Programmer's guide framework 2.3 (rev 1.0) www.openpicus.com
Using the TCP/IP Stack
Flyport TCP/IP management is based on the Microchip TCP/IP stack. On that basis, the openPicus framework
integrates the stack with the operating system FreeRTOS, to ease the management of any TCP/IP operation.
Even if all the communication issues have been simplified to make everything easier, the TCP/IP is a very
complex stack with many functionalities, so a minimum knowledge of the TCP/IP is needed. (If you are not
able to make a basic configuration of an access point, of a wireless router, you may experience problems in
the integration of Wi-Fi with your application).
Managing the Network
Flyport Wi-Fi
IMPORTANT: Flyport Wi-Fi cannot work as access point. In ad-hoc mode, DHCP server of Flyport
assigns the IP address only to one device. Ad-hoc networks are peer-to-peer networks. In
infrastructure mode, Flyport Wi-Fi connects to already existing networks.
How to manage all the aspects of the network, how to monitor the status of the connections and
how to modify all the parameters of the Ethernet and Wi-Fi.
The Connection Profiles
Flyport allows the user to freely set any parameter for a Network connection (like IP and MAC
address, Subnet mask, Gateway, DNS, Host Name, DHCP...) but also for Wi-Fi connection (SSID,
encryption and so on). All the configuration parameters can be set using the IDE TCP/IP wizard and
that configuration will be stored in the “ETH_DEFAULT” connection profile for Flyport Ethernet, or
“WF_DEFAULT” connection profile for Flyport Wi-Fi.
In the openPicus Framework there are two Connection Profiles, the default profile named
ETH_DEFAULT/WF_DEFAULT and the customizable one named ETH_CUSTOM/WF_CUSTOM.
30