Via a special link on the control page, the operator can see statistics about how many visitors connected, and which files were downloaded on a particular day. These statistics include dates which come from a running clock. However, because there is no battery to keep a clock running when it is not powered, the MicroPi starts up with the date and time of its previous shutdown. On the control page, the date can be set so that connection counts and contact data show accurate dates.
This is entirely optional. All other functions will operate correctly with an inaccurate clock. If the MicroPi is connected in network mode with captive portal disabled, the system clock will automatically be set.
Users will find it much easier to find the MicroPi's website if the Captive Portal is enabled. This causes web requests for any HTTP site to be redirected to the MicroPi's home page.
Go http://mpi.local/controls/net.php
Find the tool shown at left and click "On". The setting will be maintained through reboots.
When this is set, the unit may be accessed through the HTTPS URL: https://micropi.local if the accessing device is not connected to the internet.
This is important becasue there will be no error shown by the browser of the user's device as long as the SSL certificate is valid. The certificate must be updated every 90 days by connecting the MicroPi to the internet and clicking "Renew" on the Network Admministration page.
The MicroPi can be powered by any filtered 5V source. USB based mobile phone chargers supplying 5V at at least 750ma should work well. A computer's USB port works as well.
Note that there exists a much greater risk of system corruption when using an inadequate power supply. This includes a poorly filtered or underpowered charger or a weak battery. If the system fails to boot after running in such a case, get a better power supply and reprogram the SD card.
Autonomy can be achieved via the use of rechargeable power bank devices designed for off-line mobile phone charging. A 2500ma/hr device can keep the Raspberry Pi Zero W based MicroPi running for 8-10 hours. Larger capacity power banks will provide proportionally longer runtimes. Note that other Raspberry Pi models consume more power and correspondingly shorter runtimes.
It is best to get a power bank unit which includes a power gauge. Corruption of the MicroPi's SD card can easily occur when running with a dying battery. Shutdown the MicroPi before the battery dies.
The MicroPi can serve users from an automobile using a cigarette lighter USB power adapter as a power supply.
The MicroPi can be used in a standalone mode where other networks may or may not exist. This is the classic use of this type of device. Users connect their device to the signal emanating from the MicroPi and then can download materials stored on it.
As built, the MicroPi is by default a standalone server. It can be customized for a particular use, by changing the site language, logo, host name and SSID string. See the Status and Control Page.
To use this mode, connect the remote device to the WiFi network generated by the MicroPi and connect to the home page, this defaults to http://mpi.local, but can be changed on the Network Page.
The MicroPi is connected to an external WiFi network where it functions as a peer and becomes available as a server on that network. Other network users can download materials stored on the MicroPi.
To connect the MicroPi to an external network, see the Network Control Page. Once connected, the MicroPi's IP address appears in the network status tool. Some devices can access it at its URL, but others will need to use it's IP address to access it. The MicroPi's IP address is shown on the network administration page. There is a QR code to help users link to this alternate address on the About page.
A strong external signal is required for reliable operation. If it is intended to operate in network mode, install the MicroPi as closely as possible to the access point supplying the external LAN.
The MicroPi's printed circuit WiFi antenna is not well suited to network environments where there exist several sources of the same SSID (mesh networks). It works best with a strong signal from a single source.
Note that SAB integration is not possible in this mode.