RF Transmitter Receiver Recommendation?


Closed Thread
Results 1 to 22 of 22

Hybrid View

  1. #1
    Join Date
    Nov 2003
    Location
    Wellton, U.S.A.
    Posts
    5,924


    Did you find this post helpful? Yes | No

    Default Re: RF Transmitter Receiver Recommendation?

    I would recommend anything from here.
    http://www.rentron.com/PicBasic/RemoteControl.htm
    The TWS-434A and RWS-434 is what I would try from your project description.

    To receive data from different transmitters into one receiver, each transmitter could have a unique value in the checksum. Then the receiver MCU will know where the data came from. Lots of possibilities here.
    Dave
    Always wear safety glasses while programming.

  2. #2
    Join Date
    Jun 2005
    Posts
    53


    Did you find this post helpful? Yes | No

    Default Re: RF Transmitter Receiver Recommendation?

    Thanks Dave for the recomendation. The Rentron parts look perfect. I'm not sure how to deal with multiple remote transmitters trying to send data at the same time. I'm thinking transceivers might be easier, I can request data from the selected remote.

    Mark

  3. #3
    Join Date
    Nov 2003
    Location
    Wellton, U.S.A.
    Posts
    5,924


    Did you find this post helpful? Yes | No

    Default Re: RF Transmitter Receiver Recommendation?

    I'm not sure how to deal with multiple remote transmitters trying to send data at the same time
    If the remotes are constantly sending data then you should be good with sending an ID.
    What you basically do is treat the ID like a checksum. If the checksum is correct the data is saved/used. Same with an ID. If ID=r1 then data is from remote #1.
    Dave
    Always wear safety glasses while programming.

  4. #4
    Join Date
    Oct 2004
    Posts
    448


    Did you find this post helpful? Yes | No

    Default Re: RF Transmitter Receiver Recommendation?

    Quote Originally Posted by mackrackit View Post
    If the remotes are constantly sending data then you should be good with sending an ID.
    What you basically do is treat the ID like a checksum. If the checksum is correct the data is saved/used. Same with an ID. If ID=r1 then data is from remote #1.
    Dave, in that case wouldnt there be constant collisions in the incoming packets, affecting the validity of the actual data seen by the receiver?

    Anand

  5. #5
    Join Date
    Nov 2003
    Location
    Wellton, U.S.A.
    Posts
    5,924


    Did you find this post helpful? Yes | No

    Default Re: RF Transmitter Receiver Recommendation?

    Quote Originally Posted by ardhuru View Post
    Dave, in that case wouldnt there be constant collisions in the incoming packets, affecting the validity of the actual data seen by the receiver?

    Anand
    Receivers are constantly being flooded with noise from everywhere. That is why the checksum or some other way of knowing if the signal being received is good or data we are after. If the ID is part of that then we know the data is good and where it came from.
    Dave
    Always wear safety glasses while programming.

  6. #6
    Join Date
    Oct 2004
    Posts
    448


    Did you find this post helpful? Yes | No

    Default Re: RF Transmitter Receiver Recommendation?

    No, thats not what I meant; if all transmitters are transmitting together, wont the receiver ALWAYS see a 'composite' signal thats actually a mix of more than one signal?

    Anand

  7. #7
    Join Date
    Dec 2005
    Posts
    1,073


    Did you find this post helpful? Yes | No

    Default Re: RF Transmitter Receiver Recommendation?

    It's not likely that all transmitters are transmitting all the time. Most jurisdictions have rules limiting such transmissions to intermittent transmissions spaced well apart.

    In that scenario, building in both an ID byte and error checking is sufficient. The NEC protocol (used by X10 for ~40 years) works quite well. There's a PBP example at http://davehouston.org/PIC-RX-TX.TXT. If you need to send more than 2 payload bytes, you can extend this.

    Transceivers that transmit only when queried also work quite well but at large increase in cost. The simple transmitter and receiver like those Bruce sells are inexpensive and available from many sources worldwide. http://davehouston.org/modules.htm

Members who have read this thread : 0

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts