The time interval of position reports varies from 60 to 80 seconds (the band fair use policy requirement). Be aware that, unlike other SoftRF Editions, the Ham one is not designed for collision avoidance. It is best suited for:
--
You received this message because you are subscribed to the Google Groups "SoftRF_community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to softrf_communi...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/softrf_community/31b72686-643e-41bf-95a0-839753be734dn%40googlegroups.com.
Hey,
I was maybe a bit short on explaining why “just boost it and use a 1 W transceiver” isn’t a great idea — thanks to the person on Discord who called me out on that.
The reason I’m nervous about people using 1 W transceivers (and possibly hacking the software to actually reach that power, if that’s even feasible on that T-Beam) is that we don’t gain much from misbehaving transmitters. As Moshe also rightly said: it’s not legal — but beyond that, it actively disrupts how the system is supposed to work.
If all transceivers agree on something like 22 dBm, then the transmit and receive sides are balanced. With a 1 W T-Beam, that balance is likely broken: the receive path often doesn’t match the transmit capability. Most of these radio protocols rely on time-multiplexing and mechanisms like Listen Before Talk. If no signal is detected, the device assumes the channel is free and transmits.
Now imagine a node transmitting at 1 W, but with a receive path or antenna that can’t properly hear traffic from farther away. It may conclude the channel is idle, transmit at high power, and unintentionally suppress other transmissions that it simply can’t hear — even though they are very real for everyone else.
We see the same kind of problem with Wi-Fi. Some routers don’t adhere to the specs and just blast at excessive power. The result isn’t better throughput — it’s congestion. Other devices see higher error rates and start retransmitting, which makes everything worse.
So yeah, that’s why I’m worried about this. It’s not about being conservative — it’s about not breaking the shared radio environment.
On 30 Jan 2026, at 13:47, Adam Mościcki <adam68....@gmail.com> wrote: