X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2015-09-22_02:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 kscore.is_bulkscore=2.33092989354589e-11 compositescore=0.99972376455583 phishscore=0 kscore.is_spamscore=0 rbsscore=0.99972376455583 recipient_to_sender_totalscore=0 spamscore=0 urlsuspectscore=0.99972376455583 adultscore=0 kscore.compositescore=0 circleOfTrustscore=0 suspectscore=3 recipient_domain_to_sender_totalscore=0 bulkscore=0 recipient_domain_to_sender_domain_totalscore=0 recipient_to_sender_domain_totalscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1412110000 definitions=main-1509220122 From: "Chris Smith (space DOT dandy AT icloud DOT com) [via geda-user AT delorie DOT com]" Content-type: text/plain; charset=utf-8 Subject: [geda-user] Wireless communication 101 Message-id: <70C4A238-D361-4A6C-A81D-CBF019CADC4F@icloud.com> Date: Tue, 22 Sep 2015 07:51:07 +0100 To: gEDA User Mailing List MIME-version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t8M6pH9J000828 Reply-To: geda-user AT delorie DOT com Hi all, Can anyone recommend any good texts or online resources dealing with the practical considerations of wireless communication, particularly discussion of techniques to improve performance in non-optimal environments? I have a project using an off-the-shelf 433 MHz transmitter and receiver, which works well at home but fails in other environments. I obviously can’t change the transmitter/receiver hardware, but I’m interested in anything I can change, such as antenna choice, encoding algorithms, transmission strategy, which would help produce a robust system. I’m also interested in methods of measuring what’s happening in the environment, to figure out what’s causing the problem. Thanks, Chris — Chris Smith