News:

LATEST RELEASE:  FPP 8.5.1 - Download from here - https://github.com/FalconChristmas/fpp/releases/tag/8.5

+-+-

+-User

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?

+-Site Stats

Members
Total Members: 16898
Latest: Kap10G
New This Month: 14
New This Week: 0
New Today: 0
Stats
Total Posts: 135496
Total Topics: 16990
Most Online Today: 104
Most Online Ever: 7634
(January 21, 2020, 02:14:03 AM)
Users Online
Members: 0
Guests: 94
Total: 94

Is my k4-PB nuked?

Started by Kensington Graves, December 17, 2023, 09:53:41 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Kensington Graves

I've had this issue for the last two years but didn't get around to fixing it.  This isn't a mission-critical controller, but I'd like to get it sorted while I'm thinking about it.

The K4-PB was purchased from kulplights in October 2021.  I'm pretty sure that I attempted to set it up via USB tethering the first time with the WiFi dongle attached to the cape's USB port (as I did with all PB-based items from kulplights).  I know that I hadn't read about the "don't use USB tethering" at the time, and I don't know whether my generation of K4-PB was affected by that directive.

Symptoms:

1. No separate PSU.  When not connected to the K4 cape, and a powered USB hub with an ethernet jack is connected to the Pocket Beagle's micro USB port, and a WiFi dongle is plugged into the hub, FPP boots and finds both eth0 and wlan0.

2. No separate PSU.  When the Pocket Beagle is connected to the K4 board, powered through the microUSB port using the powered USB/Ethernet hub with the WiFi dongle attached to the hub and the ethernet cable plugged into the ethernet port, FPP boots normally and finds both network interfaces.

3. No separate PSU.  When the Pocket Beagle is connected to the K4 board and powered through microUSB port using the powered USB/Ethernet hub with the ethernet cable connected to the ethernet plug, and the WiFi dongle is plugged into the USB port on the K4 cape, FPP boots and finds eth0 only (no WiFi).

4. When the assembled K4 board is powered by a 12v PSU (with jumper properly set), with the ethernet cable connected to the USB hub and the WiFi dongle is connected to the USB hub (hub NOT powered up), FPP boots, but no network is found.

5.  When the Pocket Beagle is connected to the K4 board and powered with a 12v PSU (jumper correctly set), the ethernet cable connected to the ethernet plug on the hub, and the WiFi dongle is plugged into the USB port on the K4 cape, FPP boots but does not find any network.

Sounds like I broke something, right?

Kensington Graves

Follow up on the story.  I ordered a new K4-PB and had the same problem.  I found another pocket beagle in my spare parts box and swapped it in place of the original pocket beagle.  It worked without a hitch.  So I must have fried something on the first pocket beagle, apparently.

Support FPP

+- Recent Topics

Light Elf Bluetooth IP65 Laser by Kap10G
March 22, 2025, 12:45:02 PM

HA MQTT plugin for single model by s1godfrey
March 20, 2025, 08:21:46 PM

Virtual Display not working? by dkulp
March 19, 2025, 11:45:01 AM

PixelOverlay-Clock - Revisited Again by jnealand
March 18, 2025, 06:00:53 PM

PixelOverlay-Clock.php works but I have questions... by datajack
March 18, 2025, 04:38:32 AM

Backup Feature not functional by efamlights
March 16, 2025, 11:58:28 AM

WS2811, Raspberry Pi 5, GPIO, could not initialize. by Ulysse-srfc24
March 16, 2025, 05:07:48 AM

K16A-B Issue by nolatron
March 15, 2025, 01:52:26 PM

F16V5 and SRx1 v5 by jkp
March 15, 2025, 07:19:44 AM

Differential Board: PSU & Enclosure by hakko808
March 14, 2025, 09:17:01 AM

Powered by EzPortal
Powered by SMFPacks Menu Editor Mod