Setups
General information
Wirnet™ iBTS information
Wirnet™ iFemtoCell information
Wirnet™ iFemtoCell-evolution information
Wirnet™ iStation information
System management
Network management
LoRa Features
KerOS customization
Support and resources
Setups
General information
Wirnet™ iBTS information
Wirnet™ iFemtoCell information
Wirnet™ iFemtoCell-evolution information
Wirnet™ iStation information
System management
Network management
LoRa Features
KerOS customization
Support and resources
This is an old revision of the document!
Connect the AC/DC power supply to the barrel jack power connector.
Technical specifications for power supply:
halt command).You can connect you iFemtoCell through its Ethernet port to your network, or use the local WiFi Access Point connection described below. Once done, please see the connection, login and credentials page for more information on how to connect to your iFemtoCell.
A WiFi access point is available at boot time on each Wirnet™ iFemtoCell for one hour, broadcasting an SSID named after its serial number (klk-wifc-XXXXXX). It can only be used to access the Wirnet™ iFemtoCell itself, as it does not route traffic to anywhere and does not serve as an Internet wireless access point.
The passphrase to connect to this WiFi network is the Ethernet MAC address (it can be found on the Wirnet™ iFemtoCell label), in uppercase, without spaces between the digits, e.g. 7076FFYYYYYY.
Note that this interface does not come with a DHCP server, it is only meant to be used for the Wirnet™ iFemtoCell configuration. Your computer may take some time to get the “connected” status, and the interface will have a “limited connectivity”, which is normal.
Once connected, please follow the instructions in the connection, login and credentials page.
When the switch is positioned again to the right, the reset is released and the Wirnet™ iFemtocell starts booting.
On Linux, everything should work out of the box. The serial port will be located in /dev/ttyUSB*.
You may need to tell the Kernel to load the proper FTDI driver when the debug probe is plugged.
To do so, list the USB devices and see the product and vendor IDs:
$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 039: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 001 Device 005: ID 0461:0010 Primax Electronics, Ltd HP PR1101U / Primax PMX-KPR1101U Keyboard Bus 001 Device 045: ID 18d1:4ee7 Google Inc. Bus 001 Device 003: ID 0424:2512 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
Here the debug probe is located on the 1st bus, device 039. The device should be automatically recognized, provided you have the FTDI kernel module loaded. To check this, you can run the following command:
$ lsmod | grep ftdi ftdi_sio 53248 1 usbserial 53248 3 ftdi_sio
Next, create a udev rule matching this, and place it in a file called /etc/udev/rules.d/99-usbftdi.rules (for example):
# Added on xx/yy/zzzz for Kerlink debug probe by foobar
# For FTDI FT232 & FT245 USB devices with Vendor ID = 0x0403, Product ID = 0x6001
ATTR{idProduct}=="6001", ATTR{idVendor}=="0403", RUN+="/sbin/modprobe ftdi_sio product=0x6001 vendor=0x0403"
Be sure to replace the product/vendor IDs if they need to be changed. This will have the FTDI Kernel module loaded when the debug probe is plugged.
Next, reload the device tree: udevadm control –reload-rules && udevadm trigger (run as root).
If you will, you could rename the device in /dev. To do so, add , SYMLINK+=“debug_probe” to your udev rule.
Here's the result:
$ ls -l /dev/debug_probe lrwxrwxrwx 1 root root 15 04-06 16:05 /dev/debug_probe -> ttyUSB0
COM3 on Windows, /dev/ttyUSB0 on Linux)1152008none1nonerootpdmk-$serialno
pdmk-$serialno is the default password on the gateway. See here for more information. In case of failure, request password to Kerlink support team.