Connect to kwikwai
Put kwikwai on your network using the ethernet port while using a usb cable to power up the device. (If you connect kwikwai's usb port to a Windows PC or laptop, automatically an appropriate FTDI driver should be proposed and installed by the OS, see #Serial (DB9 or USB).)
Connect using your favorite browser and you'll find kwikwai on the network without knowing its IP address by using its name. By default, the name is "kwikwai", so type
and you should get a page like that.
If it does not work, check out IP address.
Connect using telnet on port 9090.
unix$ telnet kwikwai.local 9090 Trying 192.168.1.51... Connected to kwikwai.local. Escape character is '^]'. ! Kwikwai command shell ! Password required
Provide the password
password kwikwai OK password
Serial (DB9 or USB)
The serial connection allow the same level of control as the Telnet connection but some cases (home automation) or some people (geeks) may require to have RS232 access.
This is made possible using a USB cable via a Virtual COM port. The chip used on kwikwai to do this is the FTDI chip which will necessitate the installation of the corresponding driver on your machine.
FTDI drivers can be found here.
Once the driver is installed, instructions can be found on the Serial How To page.
Control the device
- The human readable approach : Web interface
- The geek approach (telnet or serial) : Command Line Interface
The kwikwai default configuration is the following:
Network configuration and device access
The IP / gateway / DNS addresses and mask are dynamically defined through DHCP.
- NetBIOS name: KWIKWAI
- Bonjour name: kwikwai.local
- Password is not activated
Without DHCP server (for example when connecting kwikwai directly to a PC with an Ethernet cable), kwikwai will first try to use a (random) link local address.
With bootloader 1.5.2 and firmware > 1.0r700, kwikwai first tries to use link local address 169.254.12.91 (if already in use, it will use a completely random address). Also, the IP LED only glows once kwikwai has an address. It's very quick for DHCP but can take 10s for link local.
Time is automatically set through SNTP (needs a few minutes after start up).
- SNTP server: time.windows.com
- Timezone offset: 0
- CEC message listening is off
- Verbose: 0
This default configuration is restored by pressing the reset button.