PixelRadio, a DiY FM Transmitter with RDS RadioText

I figured out what the issue was. I am using a USB hub via an HDBase-T extender (keyboard, mouse and monitor use the same extender). Most devices work without any problem and the TTGO board was properly recognized (after manually installing the drivers). However, I just wasn't able to write the firmware. After connecting it to the computer directly it worked on the first trial.
 
...but now I have another issue. I connected to the PixelRadio's AP. I then set the

* SSID (for a 2.4GHz radio)
* Password for that SSID
* Set IP address to 192.168.1.222 (in the static IP range)
* Setting the IP automatically set the gateway to 192.168.1.1, which is correct
* I disabled DHCP

I think that was all. I then power cycled the board. However, I can neither reach http://pixelradio.local nor 192.168.1.222. I also don't see PixelRadioAP anymore. Since I don't see PixelRadioAP anymore I suspect the board thinks it is connected to the WiFI network. I did power cycle the board a couple of times but got the same result.

I also did the "emergency wifi credentials" but still don't see the AP. I then did download the firmware again and then the image via SD card, just as I did before. But still no AP even after waiting for more than 5 minutes.
 
Sorry to hear that. From those symptoms my best guess is that the device is not successfully booting. But really hard to say without more investigation.

To troubleshoot the issue I recommend using the serial log feature. Connect PixelRadio to your PC, launch a serial terminal program (I use PuTTY), and monitor the log messages.
https://github.com/thomastech/Pixel...r_Manual/Controllers.md#usb-serial-controller

The posted log messages during boot (immediately after pressing ESP32's reset button) should provide information about the WiFi connection. Serial also has an "info" command that will echo the IP address upon request. See: https://github.com/thomastech/PixelRadio/blob/main/docs/User_Manual/Controllers.md#info-command

- Thomas
 
So I used putty to see the log. Below is what I got. It seems the ESP32 thinks it is connected to my network which explains why it doesn't go into AP mode. However, when I look at all the wireless devices listed in my router's GUI I can't find 192.168.1.222, hence the browser times out when I try to access that IP.

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DOUT, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:1044
load:0x40078000,len:10124
load:0x40080400,len:5828
entry 0x400806a8

00:00:00.035 {INFORM } PixelRadio FM Transmitter by Thomas Black
00:00:00.036 {INFORM } Version 1.1.2, Oct-18-2022
00:00:00.037 {INFORM } System is Starting ...
00:00:00.048 {INFORM } ADC eFuse provided Factory Stored Vref Calibration.
00:00:00.450 {INFORM } Initialized VBAT and RF_VDC ADCs.
00:00:00.455 {INFORM } LittleFS: Mounted File System, testing ...
<snip>
00:00:00.514 {INFORM } -> File System Testing Complete.
00:00:00.520 {VERBOSE} Found "/RadioLogo225x75_base64.gif" Logo Image in File System.
00:00:00.522 {INFORM } Restore Configuration From LittleFS ...
00:00:00.540 {VERBOSE} -> Located Configuration File (/backup.cfg)
00:00:00.564 {VERBOSE} -> Configuration JSON used 1931 Bytes.
00:00:00.565 {INFORM } -> Configuration Restore Complete.
00:00:01.568 {INFORM } Starting WiFi (Webserver Initialization):
00:00:01.703 {INFORM } -> Static IP Connection Enabled, IP Address: 192.168.1.222
00:00:01.804 {INFORM } -> Connecting to Guest2.4 ...
00:00:01.809 {INFORM } -> Connection Retry #1
00:00:02.810 {INFORM } -> Connection Retry #2
00:00:03.815 {INFORM } -> Server mDNS has started
00:00:03.816 {INFORM } -> Open http://PixelRadio.local in your browser
00:00:03.817 {INFORM } -> WiFi connected, IP address: 192.168.1.222, RSSI: -68dBm
00:00:03.841 {INFORM } WiFi Initialization Complete (Online).
00:00:03.842 {INFORM } -> WiFi Mode: Station
00:00:03.843 {INFORM } -> WiFi IP address: 192.168.1.222
00:00:03.867 {INFORM } Serial Controller CLI is Enabled.
00:00:03.868 {INFORM } Scanning i2c for Devices ...
00:00:03.902 {ERROR } -> No i2c Devices Found.
00:00:03.903 {INFORM } Initializing QN8027 FM Radio Chip ...
00:00:03.904 {ERROR } -> QN8027 is Missing
00:00:03.904 {INFORM } FM Radio RDS/RBDS Started.
00:00:03.915 {INFORM } Initializing Web UI ...
00:00:03.991 {INFORM } -> Image File /RadioLogo225x75_base64.gif Successfully Loaded (3988 bytes).
00:00:04.000 {INFORM } -> Web UI Loaded.
00:00:04.001 {FATAL } PixelRadio System Init Failed. Please Review Serial Log.
00:00:04.002 {INFORM } Changing Log Level to LOG_LEVEL_VERBOSE
00:00:04.018 {INFORM } Local Controller RDS Will Use: PI=0x6400, PTY=9.
00:00:04.020 {INFORM } Local Controller Sending RDS Station Name (PixeyFM).
00:00:27.172 {ERROR } -> Abort: waitForRDSSend() function time-out!
 
Yes, Guest2.4 is my guest network on 2.4GHz. I will give the other one a try but I never had any issue accessing a device on the guest network (the other way doesn't work). All my 6 or so Chromecast and some other devices are on the guest network which are mostly accessed from the non-guest WiFi. And even if access rights are the issue, the IP should still show up on my router but it doesn't.
 
I agree, the brower's failure to access PixelRadio could have something to do with the guest WiFi. As suggested by Mike, connect it to your other WiFi network and see if browser access is possible.

However, when I look at all the wireless devices listed in my router's GUI I can't find 192.168.1.222
Click to expand...
If you are sure you are looking at the Guest WiFi router's GUI then I suggest rebooting the guest router and see if the device shows up after the device list is re-populated.

BTW, the logs show that the QN8027 module needs your attention. This issue shouldn't affect WiFi operation. But as a precaution, fix this and then see if it helps the WiFi problem.

- Thomas
 
Last edited:
I tried to change the SSID with the credential file (just as I did for Guest2.4) but it wouldn't take it (based on the serial output). After multiple trials I ended up erasing the board before loading the firmware again. That did the trick. Now I am able to get to the web portal (if I just use the ESP32 connected via USB).

I then put the ESP32 on the PCB and gave it 12V (outer contact being ground/negative and inner contact being 12V). However, the ESP32 doesn't come on, i.e. obviously no power (USB cable is disconnected). I went through a few pages of this thread but didn't find anything. Is there some troubleshooting guide to bring up the board?

Btw, it would be great if the first post had some links to:

* Part list
* Troubleshooting guide (if it exists)
* Loading FW onto the board
* User manual
* etc.
 
I then put the ESP32 on the PCB and gave it 12V (outer contact being ground/negative and inner contact being 12V). However, the ESP32 doesn't come on, i.e. obviously no power
Click to expand...

The ESP32 gets 5V from the main PCB via the 2-pin cable labeled P1 5V (VBAT). See this photo for location:
https://github.com/thomastech/PixelRadio/blob/main/docs/Images/pcb_RevB1_1500.png

Troubleshooting suggestions:

1. Make sure the power switch on the ESP32 is in the ON position. See:
https://github.com/thomastech/PixelRadio/tree/main/docs/Hardware#esp32-installation

2. Confirm the P1 connector has 5V (4.8 to 5.2 VDC) and is plugged into the ESP32.

3. If P1 voltage is missing then inspect/re-solder connections at P3 (DC Power Jack), D1 (Diode), and U2 (7805 VReg). For details to these components and their relationship to the 12VDC & 5VDC power path please review the schematic:
https://github.com/thomastech/PixelRadio/blob/main/docs/Hardware/Schematic_RevB.pdf

- Thomas
 
Last edited:
I have a question to Thomas or the group.

If I just mount the PCB board in a case say along with a BBB16 controller would everything be OK or does the Board really need to be installed in the
Metal case for best performance?
 
If I just mount the PCB board in a case say along with a BBB16 controller would everything be OK
Click to expand...

PixelRadio's RF power is low, so should play nice with the pixel controller in the same enclosure. Your idea should be OK.

- Thomas
 
As FPP7 is getting ready for release, has anyone tested the FPP plugin for PixelRadio?
I ask as it has come out that other plugins had issues with the new Bootstrap included with FPP7.
 
I went through the last 4 pages of posts to see if anyone still had an extra couple PCB's, if not how hard it is to get JLCPCB to build them properly or any lessons learned if I go that route. I would likely make extras and distribute on here if I go that route.
 
reidage said:
I went through the last 4 pages of posts to see if anyone still had an extra couple PCB's, if not how hard it is to get JLCPCB to build them properly or any lessons learned if I go that route. I would likely make extras and distribute on here if I go that route.
Click to expand...

Hi Reidage, I do have some extra blank boards left over, either 4 or 5, would need to check. If you would like one or more just shoot me a PM. I think $2 per board plus shipping and PayPal fees if interested. Shipping will prob be between $6-$10. Just let me know and I can get them together tonight and in the mail tomm.
 
Did any of you change any setings? I hooked it up to a Soundblaster 3 and I hear the music,but the static is awful. With nothing playing I still hear static.

Update: Changed cable and all is good now.
 
Last edited:
Port usage is as follows:

Web Server: 80
HTTP Controller: 8080
MQTT Controller: 1883

Values are declared in PixelRadio.h file.

- Thomas
 
Last edited:
You must log in or register to reply here.
Back
Top