In March 2010 we wrote about openPICUS, the Italian project made to fill the gap between low-cost embedded hardware and wireless connectivity. In September 2010 the first video review of its first web server application arrived. Check it out below.
What openPICUS was
openPICUS was an Italian company and open project that built small Wi-Fi modules, called FlyPort, around Microchip microcontrollers, together with a free development environment. The aim was to let engineers and hobbyists who know C put a sensor or a controller on a Wi-Fi network and serve web pages from it, without writing a TCP/IP stack or a web server themselves.
A 2013 Digi-Key article, OpenPICUS Speeds Designs Based on Microchip Technology's MCUs and Connectivity Chips, describes the platform: a system-on-module built on a 16-bit PIC24 processor and a Microchip Wi-Fi transceiver, a free IDE and framework built on FreeRTOS, and a set of carrier boards called "Nests".
Why an embedded web server matters
A web server on the device means any phone or PC with a browser becomes its user interface. There is no app to install and no special software on the PC. The device serves a page showing its sensor readings, and buttons or forms on the page send commands back. For a first application, a web server is the natural demonstration: it proves the Wi-Fi link, the network stack and the application code all work together.
Deep dive: the numbers and details
This part holds the module details from the 2013 description. Skip it if the overview is all you need.
FlyPort Wi-Fi at a glance
From the Digi-Key article:
| Item | Detail |
|---|---|
| Processor | Microchip PIC24FJ256GA106, 16-bit |
| Wi-Fi | Microchip MRF24WB0MA/RM 802.11b transceiver |
| Module size | 35 x 48 mm (FlyPort Wi-Fi, TEIK001) |
| Protocols supported | HTTP, TCP, UDP, SNTP, FTP and SMTP |
| Software | Free openPICUS IDE and framework built on FreeRTOS, with a free C30 compiler |
| Other variant | FlyPort Ethernet with a Microchip ENC424J600 10/100 Ethernet controller |
How a small web server fits in a microcontroller
A microcontroller of this class has a few hundred kilobytes of flash and tens of kilobytes of RAM, far less than a PC. Embedded web servers fit by keeping pages small, storing them in flash, and filling in live values (a temperature, a switch state) at the moment a page is requested. The network stack handles one or a few connections at a time, which is enough for a device that a handful of people check now and then.
The flow when you open the device's page in a browser:
- The browser sends an HTTP request to the module's IP address over Wi-Fi.
- The TCP/IP stack on the module passes the request to the web server task.
- The server reads the page template from flash and inserts current sensor values.
- The page goes back to the browser; a button press on the page sends a new request that the application code acts on.
What happened next
In July 2011 openPICUS released new applications for FlyPort, including a hibernation mode for battery-powered use and integration with the ThingSpeak data logging service, as covered in our 2011 post. The 2013 Digi-Key article shows the platform had grown by then to Wi-Fi and Ethernet modules, nine expansion boards and examples such as a web-controlled Geiger counter with email alerts.
About the links
The original post linked to our March 2010 article on the project. That page no longer exists on this blog and no archived copy was found, so the link has been removed. The video is embedded as originally published.


Your comments will be moderated before it appears here.