Shop OBEX P1 Docs P2 Docs Learn Events
433MHz Transceiver Problem — Parallax Forums

433MHz Transceiver Problem

eacastroeacastro Posts: 2
edited 2012-11-20 08:27 in Accessories
Hi all

I'm student and working with a small project which involves wireless transmission. I'm using the Parallax 433MHz Transceiver (OOK modulation, 2500 feet sight line) and have a problem during the transmission.

I'm using the UART from PIC16F876A with a baud rate of 2400 .Initially the MCU is only in TX mode, while my laptop is in RX mode (using Hyperterminal).
The MCU sends numbers as characters (0,1,2...).
I could receive succesfully this data in my laptop, but only if the distance between TX and RX is around 20cms. If I exceed distance, the RX receives the characters but mixed with garbage characters.

I'vet tried different baud rates (9600, 4800) but the problem is still the same, only works fine if the distance is 20cms or less, no more.
Datasheet says it works with 2500 feet.

I have no idea why I'm getting garbage characters over my strings.
This link is for the wireless transceiver:

http://www.parallax.com/Portals/0/Do...eiver-v1.1.pdf

My configuration is:

TX:
MCU (pin TX)----> RF Transmitter (pin Data, "TX/RX Sel" = High, this is TX mode).

RX:
RF Transmitter (pin Data, "TX/RX Sel" = Low, this is RX mode) --> MAX232---->RS232 PC


Using +5V for Vcc.


Thanks for your help/comments/suggestions.

Comments

  • Kevin CookKevin Cook Posts: 159
    edited 2011-04-04 08:54
    Line of site is 250 feet not 2500.

    Depending on what is around you, there could be other 433 interference. The 433 MHz is really susceptible to radio noise. Try relocating the setup to see if that helps with the erroneous data.
  • kuismakuisma Posts: 134
    edited 2011-04-05 01:08
    You can really not expect anything feeding the transceiver directly using the RS232/V.24 protocol. It is not built nor suited for wireless at all. You need to implement a better encoding, take care of start synchronization, handle noise, determine end of transmission etc.
  • eacastroeacastro Posts: 2
    edited 2011-04-05 15:32
    Hi

    First, by mistake I wrote 2500 feet, and datasheet states 250 feet. But at the very beggining my problem was transmission problem in more than 20cms.

    I was sending numbers (0,1,2) from MCU UART to the PC. The MCU had a while loop with a delay of 300mS in every loop. I think with this delay, the RX had enough chance to capture noise and mix it with my signal.

    I reduced the delay from 300mS to 40mS. In this case, the communication was good, even 6 meters away with a wall as obstacle. It seems with this delay, the receiver is not able to capture de noise but my signal.
    The strings were received perfectly on Hyper-terminal.

    Now I'm trying in build a "protocol" for TX/RX.
  • micro_engineermicro_engineer Posts: 7
    edited 2011-04-15 09:57
    Using RS232 is not the issue at all. I used the UART from a PIC16F689 for bi-directional communications with the 433MHz transceiver modules. Other "protocols" could be even better, but are not really needed.

    The notes about receiving noise are correct. For reliable data transmission you have to do a little extra work.

    The following can be done for more reliable communication:

    1) Pick up the LINX IC datasheet and check out the notes regarding "squelch". The module is very susceptible to noise and squelching (done by adding resistor(s) to the appropriate pin) is helpful. For example, I used 2M Ohms. It is a compromise between noise sensitivity and reception sensitivity. Easy fix on the PCB.

    2) You need to make a simple 'protocol' in which you transmit data in a formal structure with a start byte, data, and a checksum of some sort. This will allow the receiving device to know when a valid message has started and/or been received. Bad messages can be ignored or discarded

    I would suggest making a little TX message buffer, filling it, then transmitting as fast as possible (via polling or interrupts) from the UART.

    3) Don't forget about the "sync" bytes the LINX IC needs. (See datasheet)

    4) Adding a long delay between transmissions will become irrelevant if you use a good protocol, but will not really be necessary. Also you should be able to transmit at the maximum rate (10,000bps) using your UART's 9600 rate.

    I'm thinking about posting a schematic and related notes here in the forum.

    Give these things a try and see how it works out.
  • shaunakshaunak Posts: 8
    edited 2011-05-16 22:56
    I used these modules successfully some time ago. I used:

    1. 1200 baud
    2. A simple checksum
    3. Redundant transmission
    4. 2 Radio antennae - extracted from old radio sets and mounted onto a badminton shuttle, with a AL foil ground plane - This seemed to help a lot.
  • w0byw0by Posts: 1
    edited 2012-11-19 08:39
    I know this is late, but my remote start/keyeless entry for my car stopped working when it's next to my house. I shut the power off at the house and still nothing. If I move 10 feet south, everything works again. I can stand next to the car with the remote pretty much on top of the antenna and sometimes it will work. I found out it's 433mhz. Horrible! I have a $500 paperweight. Right now I'm going to the installer for a 900mhz SS remote.
  • Mike GreenMike Green Posts: 23,101
    edited 2012-11-20 08:27
    There's nothing magic about 433MHz except that it's a commonly used band of frequencies used for many purposes including remote control and short distance data communications. Remote controls particularly tend to be cheaply made with marginal power levels, filtering, and gain since they're intended for use at very close range. 900MHz is another similar band. Whether it works any better will depend more on the quality of the units used and on the amount of other usage of the same frequencies in the neighborhood than anything else.
Sign In or Register to comment.