Datasheet

Flyport Wi-Fi and Ethernet Programmer's guide framework 2.3 (rev 1.0) www.openpicus.com

QUESTION: What are the profiles?

The profiles are structures which store basic Ethernet/Wi-Fi information, necessary for

Flyport to know how to connect to the network. The basic information are:

– IP of the Flyport

– DNS servers

– Default GATEWAY

– DHCP enable / disable

– NETBIOS name

– SSID name (Wi-Fi only)

–

Network type (ad-hoc or infrastructure) (Wi-Fi only)

–

Security configuration parameters ( type and password) (Wi-Fi only)

QUESTION: How can the profiles be used?

Flyport Wi-Fi

The profiles can be used inside the function that starts a Wi-Fi connection. This connection

function is

WFConnect( connection profile);

and can be used with “WFConnect(WF_DEFAULT);” or with “WFConnect(WF_CUSTOM);”

Flyport Ethernet

The profiles can be used with the function that restarts the connection.

ETHRestart( connection profile);

and can be used with “ETHRestart(ETH_DEFAULT);” or with “ETHRestart(ETH_CUSTOM);”

QUESTION: How can I customize the profiles?

There are two ways to customize a connection profile.

The WF_DEFAULT/ETH_DEFAULT is the standard profile, and this type of connection is used

by the Framework in the standard template. Its parameters can be changed with the Wizard

tool of the IDE. Those values are fixed in PIC memory and can't be changed at runtime. Every

time you change some parameters in the Wizard you must compile the firmware again, and

download it inside the Flyport.

The WF_CUSTOM/ETH_CUSTOM is the runtime configurable profile template. Its

parameters can be updated in the Flyport tasks, but all the changes will be erased after a

Flyport reboot! In fact, WF_CUSTOM/ETH_CUSTOM are the same of

WF_DEFAULT/ETH_DEFAULT at startup, so every change should be reloaded by user

application. Every time Flyport is restarted, the CUSTOM profile should be loaded from

memory, and before a restart the values should be saved in memory by the user.