# DIY Kerlink Wirgrid debug probe **URL:** \ **Category:** Kerlink Gateways\ **Created:** [March 16, 2019, 12:20pm UTC](https://www.thethingsnetwork.org/forum/t/diy-kerlink-wirgrid-debug-probe/24001 "2019-03-16T12:20:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jpmeijers](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jpmeijers/32/44875_2.png) [@jpmeijers](https://www.thethingsnetwork.org/forum/u/jpmeijers)\ **Post date:** [March 16, 2019, 12:20pm UTC](https://www.thethingsnetwork.org/forum/t/diy-kerlink-wirgrid-debug-probe/24001/1 "2019-03-16T12:20:56Z")
(repost of [https://forum.loraserver.io/t/schematic-kerlink-wirgrid-debug-board/3837/2](https://forum.loraserver.io/t/schematic-kerlink-wirgrid-debug-board/3837/2)) If you happen to mess up the network or firewall config on your Kerlink gateway, the only way to get back into it is using a Wirgrid Debug probe. These things are really expensive and/or difficult to get your hands on. Looking at the [photos](https://www.thethingsnetwork.org/docs/gateways/kerlink/config.html#wirgrid) of this debug probe one will see that it uses an FTDI FT232BL. This is a USB to serial chip which is very often used in USB to Serial/UART modules. This confirms that there must be a serial interface on the Kerlink’s debug port. From experimentation I got a working terminal via the debug port using a Sparkfun FTDI basic breakout for 3.3V: [https://www.sparkfun.com/products/9873](https://www.sparkfun.com/products/9873) The pinouts of the debug header on the Kerlink itself I used are as follows: ```nohighlight # 1 2 # O TEST # 3 4 # # 5 6 # # 7 8 # O RESET ``` 1. Vcc?? - unsure about this 2. Looks like Reset 3. TX (connect to dongle RX) - reads as 3.3V on a multimeter, indicating 3.3V TTL logic - so use a 3.3V FTDI breakout. 4. RX (connect to dongle TX) 5. Looks like Boot 6. Ground (connect to dongle ground) 7. ?? 8. ?? ![46](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/e/5/e52de812148478bbe7f947ae0c18fab6d0ab6f39.jpeg) ![54](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/8/e/8ed05f456f6173cc459ed62e133ac6660d6f5656.jpeg) ---
**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\ **Post date:** [June 30, 2019, 12:31pm UTC](https://www.thethingsnetwork.org/forum/t/diy-kerlink-wirgrid-debug-probe/24001/2 "2019-06-30T12:31:43Z")
> [@jpmeijers](#): > > From experimentation I got a working terminal via the debug port Do you remember if you needed to log in? Version 2.7 (August 2016) of “[Installation and Maintenance Manual Long Range IoT Station (Lora Station)](https://www.google.com/search?q=type:pdf+%22Installation+and+Maintenance+Manual+LoRa+IoT+Station+Wirnet+Station%22)” says: > It is also possible to access to the debug interface by Ethernet connection by connecting directly to the POE injector or the Ethernet switch (depending on the installation topology). That makes me wonder if connecting directly to the ethernet connector behaves differently than connecting through a network. > [@jpmeijers](#): > > 1. Vcc?? - unsure about this Indeed; some more details from that document: > The Wirgrid Debug Board is intended to be connected to the debug interface. It is mainly a simple UART to USB converter. > > … > > The main characteristics of the Wirgrid debug board are: > > | Characteristics | Specification | > | --- | --- | > | UART Interface | Micromatch 8 contacts connector | > | | External power supply on pin 1 | > | | Up to 1Mb/s | > | USB2.0 interface | USB 2.0 A type | > | | USB Self Bus Powered at 5V | > | | Full Speed (12Mb/s) | > | Operating temperature range | 0°C to +60°C | > | Chipset | FT232BL (FTDI) | > > ![debug probe](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/2/9/29cf13d5cfa287041f0ab325d52898d21ef836f2.png)