# Kv4p HT for use with hotspot node

**URL:** <https://community.allstarlink.org/t/kv4p-ht-for-use-with-hotspot-node/25034>\
**Category:** AllStarLink\
**Created:** [October 1, 2026, 9:21am UTC](https://community.allstarlink.org/t/kv4p-ht-for-use-with-hotspot-node/25034 "2026-10-01T09:21:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ZR1RF](https://community.allstarlink.org/user_avatar/community.allstarlink.org/zr1rf/32/5182_2.png) [@ZR1RF](https://community.allstarlink.org/u/ZR1RF)\
**Post date:** [October 1, 2026, 9:21am UTC](https://community.allstarlink.org/t/kv4p-ht-for-use-with-hotspot-node/25034/1 "2026-10-01T09:21:28Z")

</div>

For the last couple of months I have been using the[kv4p HT](https://www.kv4p.com/) as my primary radio interface and is very happy with how well it works and thought I would share my setup in case someone else would like to try it.

The kv4p was never intended for this purpose and was more aimed at turning you mobile phone into an HT with real RF.

The device contains an ESP32 and SA818 (mostly VHF) module and uses the ESP32s internal ADC.

You interface kv4p HT over serial using an extended KISS protocol.

To get it to work with ASL3 there is a [Python script](https://github.com/dadecoza/kv4p-usrp) that runs as a service on the Raspberry PI that translates between KISS and USRP.

 ![ASL3 with kv4p HT](https://community.allstarlink.org/uploads/default/original/2X/4/4a37031b9048f5f05e354d3b9dabc87ed3ef1837.jpeg)

---

<div class="post-metadata">

**Author:** ![ZS1GFL](https://community.allstarlink.org/user_avatar/community.allstarlink.org/zs1gfl/32/5226_2.png) [@ZS1GFL](https://community.allstarlink.org/u/ZS1GFL)\
**Post date:** [October 1, 2026, 9:37am UTC](https://community.allstarlink.org/t/kv4p-ht-for-use-with-hotspot-node/25034/2 "2026-10-01T09:37:40Z")

</div>

Awesome, MIne is running to, still need to package it properly etc.