wiki:connect_ibts
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
wiki:connect_ibts [2019/09/25 15:27] ghi removed |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Wirnet™ iBTS: Connect to the gateway ====== | ||
| - | <note tip>Any questions on the product or accessories: please read the [[resources#documentations|Installation and Maintenance manual]].</note> | ||
| - | |||
| - | To connect to the Wirnet™ iBTS gateway, the following accessories are needed: | ||
| - | * **Ethernet cable:** To access/use the gateway. | ||
| - | |||
| - | * **PoE injector or DC power supply (11V to 56V):** To power the gateway. | ||
| - | |||
| - | * //Optional//: **Wirma2 debug tool:** Debug probe to access to linux console, with **USB wire (A type < --- > B type):** to connect it to the PC. | ||
| - | |||
| - | <note>**Note for PoE** | ||
| - | |||
| - | 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). | ||
| - | </note> | ||
| - | |||
| - | {{ :images:accesories_wl.jpg?600 |}} | ||
| - | |||
| - | ===== Power supply the gateway ===== | ||
| - | For the following points, detailed instructions are available in the Wirnet™ iBTS "Installation and Maintenance manual" of the [[resources|resources]] page.\\ There are two ways to power on the Wirnet™ iBTS: | ||
| - | |||
| - | * **Connect** the PoE output connector to the LAN port located on the bottom side of the CPU module. The RJ45 connector can be inserted directly to the gateway using a specific cable gland. | ||
| - | |||
| - | * **Connect** the DC power supply to the Aux Power connector identified by the 11-56V indication, respect the +/- indications. | ||
| - | |||
| - | {{ :images:pow_suppl_modes.jpg |}} | ||
| - | |||
| - | |||
| - | - **Plug** a RJ45 cable from the network in the DATA IN socket of PoE. PoE injector LED orange is ON. | ||
| - | - **Plug** the PoE (DATAOUT socket) to the Wirnet™ iBTS using a RJ45 cable. PoE injector LED green is ON. | ||
| - | - **Check** the following status once the gateway is well powered : | ||
| - | * green LED DEBUG socket is ON. | ||
| - | * orange LED DEBUG socket blinks every 5 seconds. | ||
| - | |||
| - | {{ :images:power_start.jpg |}} | ||
| - | |||
| - | |||
| - | |||
| - | ===== Connect through the network ===== | ||
| - | |||
| - | Please see the [[wiki:connection_credentials|connection, login and credentials page]] for more information on how to connect to your iBTS. | ||
| - | |||
| - | ===== Local connection ===== | ||
| - | |||
| - | If you do not use yet backhaul Ethernet port, you can connect a PC directly to the iBTS with a cable to its LOCAL Ethernet port. | ||
| - | |||
| - | - **You have a DHCP server**: Start an ssh client (typically Putty on Windows) on port 22 and using the gateway’s IP address obtained from the DHCP server. \\ \\ | ||
| - | - **You don't have a DHCP server**: Configure your PC Ethernet card to use 192.168.1.100 (netmask: 255.255.255.0) and start a ssh client (typically Putty on Windows) on port 22 and using the gateway default LOCAL IP address which is 192.168.1.1 ([[wiki:backhaul#local_ethernet|More information on the LOCAL Ethernet]]). | ||
| - | |||
| - | * After getting prompt: Enter login/password (“''root''/''pdmk-**$serialno**''”). ''pdmk-**$serialno**'' is the default password on the gateway. See [[wiki:connection_credentials#default_password|here for more information]]. In case of failure, request password to Kerlink support team. | ||
| - | |||
| - | ===== Debug probe ===== | ||
| - | |||
| - | To use the debug probe, it is necessary to download FTDI drivers on [[http://www.ftdichip.com/Drivers/VCP.htm | this website]]. | ||
| - | |||
| - | ==== Windows installation ==== | ||
| - | |||
| - | - **Download** ftdi drivers. | ||
| - | - **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 | | ||
| - | |||
| - | |||
| - | It is necessary 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. To check the FTDI kernel module is loaded, the following command can be used: | ||
| - | |||
| - | <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 necessary, the device in ''/dev'' could be renamed. To do so, add '', SYMLINK+="debug_probe"'' to the 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> | ||
| - | |||
| - | ++++ | ||
| - | |||
| - | ==== Using the debug probe ==== | ||
| - | |||
| - | - **Connect** the debug tool (WIRMA2_DEBUG_TOOL) with a standard ethernet cable to the “DEBUG” port and with an USB cable to the PC. | ||
| - | - **Open** an **//hyperterminal like//** tool on the com port with the following standard parameters: | ||
| - | |||
| - | <code> | ||
| - | baudrate : 115200 | ||
| - | data length : 8 | ||
| - | parity : none | ||
| - | stop bit : 1 | ||
| - | flow control : none | ||
| - | </code> | ||
| - | {{ :wiki:probe.jpg |}} | ||
| - | |||
| - | * After getting prompt, enter login/password (“''root'' / ''pdmk-**$serialno**''”). ''pdmk-**$serialno**'' is the default password on the gateway. See [[wiki:connection_credentials#default_password|here for more information]]. In case of failure, request password to Kerlink support team. | ||
wiki/connect_ibts.1569418042.txt.gz · Last modified: 2019/09/25 15:27 by ghi
