Last updated: 11 July 2025
With a heap of work from Michaela VK3FUR, we now have a more bandwidth-efficient version of Wenet - Wenet v2!
Key Differences
- Baud Rate: 96000 baud
- No RS232 Framing (so no more 20% framing overhead!)
- Per-packet scrambling
- Modulation using RPi I2S peripheral (Guide on how to set this up coming soon!)
- Narrower bandwidth
How to Receive
WebWenet
If using WebWenet, there is now a 'Wenet Configuration' section in the Configuration page, where you can select Wenet v2.
Docker Image
If receiving Wenet using the docker image, you will need to update, and download a new version of the startup_docker.sh file.
Assuming you already have a Wenet receive setup going, you can update by running:
cd ~/wenet/
docker pull ghcr.io/projecthorus/wenet:latest
curl -o start_docker.sh https://raw.githubusercontent.com/projecthorus/wenet/master/start_docker.sh
chmod +x start_docker.sh
Edit the start_docker.sh file with your callsign and receiver settings, and in particular look for the Wenet Mode Settings, where you will need to comment-out the 'Wenet Classic' settings and uncomment the 'Wenet v2' settings as follows:
# Wenet 'Classic' (v1, RS232 framing)
#BAUD_RATE=115177
#OVERSAMPLING=8
#FRAMING_MODE=drs232_ldpc
# Wenet v2 (96000 baud, no RS232 framing)
BAUD_RATE=96000
OVERSAMPLING=10
FRAMING_MODE=wenet_ldpc
If you are running more than one Wenet receiver on the same network, change the IMAGE_PORT setting on the second receiver to 7891, otherwise they can 'interfere' with each other.
From there, you can restart/startup Wenet by running the start_docker.sh script, and you should be good to go!