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!
To connect to the Wirnet iBTS gateway, the following accessories are needed:
PoE class is depending on the configuration of the Wirnet iBTS as power consumption becomes higher accordingly to the number and the type of RF modem (consult Kerlink to choose correct PoE device).
For the following points, detailed instructions are available in the Wirnet iBTS “Installation and Maintenance manual” of the resources page.
There are two ways to power on the Wirnet iBTS:
Login/Password information are available in the dedicated credential chapter.
To use the debug probe, it is necessary to download FTDI drivers on this website.
On Linux, everything should work out of the box. The serial port will be located in /dev/ttyUSB*.
It is necessary 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. To check the FTDI kernel module is loaded, the following command can be used:
$ 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 necessary, the device in /dev could be renamed. To do so, add , SYMLINK+=“debug_probe” to the udev rule.
Here's the result:
$ ls -l /dev/debug_probe lrwxrwxrwx 1 root root 15 04-06 16:05 /dev/debug_probe -> ttyUSB0
baudrate : 115200 data length : 8 parity : none stop bit : 1 flow control : none
pdmk-$serialno is the default password on the gateway, to recover the $serialno, please refer to the credentials page. In case of failure, request password to Kerlink support team.pdmk-$serialno is the default password on the gateway, to recover the $serialno, please refer to the credentials page. In case of failure, request password to Kerlink support team.pdmk-$serialno is the default password on the gateway, to recover the $serialno, please refer to the credentials page. In case of failure, request password to Kerlink support team.pdmk-$serialno is the default password on the gateway, to recover the $serialno, please refer to the credentials page. In case of failure, request password to Kerlink support team.
To retrieve files easily with a graphical interface, WinSCP can be used: Download link.
WinSCP acts as the Linux scp command, allowing to retrieve file with a copy/paste or drag'n'drop from a distant server to a computer.
Install WinSCP as a classic Windows program and run it.
1 - Configure file protocol. Here, Secured File Transfert Protocol is required.
2 - Configure iBTS' IP address.
3 - Enter username : default is root.
4 - Enter password : default is the following pattern pdmk-XXXXXX where XXXXXX are hexadecimal units of iBTS hostname. More informations here.
5 - Click to login.