====== Wirnet™ iFemtoCell: Connect to the gateway ======

<note tip>Any questions on the product or accessories: please read the [[wiki:quickstart:quickstart_ifemto#documentation|Installation and maintenance manual]].</note>

===== Powering the iFemtoCell =====

Connect the AC/DC power supply to the barrel jack power connector.

Technical specifications for power supply:
{{ :images:polarity.png? |}}
  * Polarity: positive tip
  * Voltage: DC 12V
  * Current: 500mA
  * PCB connector - barrel jack (5.5mm sleeve, 2.5mm pin/tip)

{{ :images:wire_connection.jpg?500 |}}

<note warning>Take care to switch-off the gateway properly to avoid data loss (use the ''halt'' command).\\
The power supply is intended for indoor use only.</note>
===== Connect through the network =====

You can connect you iFemtoCell through its Ethernet port to your network, or use the [[#wifi_ap_connection|local WiFi Access Point connection described below]]. Once done, please see the [[wiki:systeme_mana:connection_credentials|connection, login and credentials page]] for more information on how to connect to your iFemtoCell.

===== WiFi AP connection =====

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. ''7076FF**YYYYYY**''.

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. It is not possible to upgrade the gateway firmware when you are connected with the WiFi access point.


Once connected, please follow the instructions in the [[wiki:systeme_mana:connection_credentials|connection, login and credentials page]].
===== Debug probe =====

<note warning>
The Wirnet™ iFemtocell embeds a proprietary serial debug interface within its enclosure.// 
The Wirnet™ iFemtocell is not warranted by KERLINK in case the enclosure is opened by customer.// 
Therefore, the debug interface is only for specific customer needs, it is intended to be used by authorized and qualified personnel only.
</note>

<note important>
When the switch is positioned on the left, the CPU is in reset mode.

When the switch is positioned again to the right, the reset is released and the Wirnet™ iFemtocell starts booting.

  * Reference document: [[wiki:quickstart:quickstart_ifemto#documentation|Wirnet™ iFemtoCell Installation and Maintenance guide]].
</note>

==== Windows installation ====

  - Download the [[http://www.ftdichip.com/Drivers/VCP.htm|ftdi drivers]] for the debug probe 
  - Install the drivers

==== Linux installation ====

On Linux, everything should work out of the box. The serial port will be located in ''/dev/ttyUSB*''.

++++ If it didn't work |

You may need to tell the Kernel to load the proper [[http://www.ftdichip.com/Support/Documents/AppNotes/AN_220_FTDI_Drivers_Installation_Guide_for_Linux.pdf|FTDI driver]] when the debug probe is plugged.

To do so, list the USB devices and see the product and vendor IDs:

<code text>
$ 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
</code>

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:

<code>
$ lsmod | grep ftdi
ftdi_sio               53248  1
usbserial              53248  3 ftdi_sio
</code>

Next, create a udev rule matching this, and place it in a file called ''/etc/udev/rules.d/99-usbftdi.rules'' (for example):

<code>
# 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"
</code>

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:

<code>
$ ls -l /dev/debug_probe
lrwxrwxrwx 1 root root 15 04-06 16:05 /dev/debug_probe -> ttyUSB0
</code>

++++

{{ :images:hw_probe_wiring.jpg|}}

==== Connection to the Wirnet™ iFemtocell ====
  - Open a serial terminal (HyperTerminal, PuTTY, GNU screen, minicom, etc.)
  - Select the serial port created by the FTDI driver (usually: ''COM3'' on Windows, ''/dev/ttyUSB0'' on Linux)
  - Apply the following parameters to use your serial connection:
     * baud rate : ''115200''
     * data length : ''8''
     * parity : ''none''
     * stop bit : ''1''
     * flow control : ''none''
  - Connect with the prompt :
     * login: ''root''
     * password: ''pdmk-$serialno''
''pdmk-**$serialno**'' is the default password on the gateway. See [[wiki:systeme_mana:connection_credentials#default_password|here for more information]]. In case of failure, request password to Kerlink support team.