Problem with manchester code for RF


Closed Thread
Results 1 to 12 of 12
  1. #1
    Join Date
    Jul 2007
    Posts
    3

    Red face Problem with manchester code for RF

    Hi everybody,
    I want to use manchester encode for RF data communication. Coz I heard it will not affected by noises when using such modules. My RF module is 315MHz module its data sheet tells that its range 80m. But it works poperly for 2m for data transmission. Beyond that it works with large noise.

    please tell me weather it is advantageous or not.

  2. #2


    Did you find this post helpful? Yes | No

    Default

    Hi,

    Every RF Module need a good Ground and a good Antenna! did you have near your RF Module other Transmitter ?
    RF Phone,RF Headsset....

    Regard Pesti

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


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by Dhanushka View Post
    Hi everybody,
    I want to use manchester encode for RF data communication. Coz I heard it will not affected by noises when using such modules. My RF module is 315MHz module its data sheet tells that its range 80m. But it works poperly for 2m for data transmission. Beyond that it works with large noise.

    please tell me weather it is advantageous or not.
    Manchester encoding is not immune from noise but does have built-in error detection.

    You haven't indicated just which RF modules you are using but most of the low cost modules use OOK (On-Off Keying) and a superregenerative receiver. The range spec given is usually based on free air line-of-sight. Typical range indoors will be about 20-25% of that if you are using an efficient antenna on the receiving end.

    In the absence of a strong signal it is the nature of superregenerative receivers to output continuous noise.

    For small amounts of data, I prefer to use the NEC protocol which has a fairly long initial pulse to set the receiver AGC and then transmits two payload bytes with built-in error checking.

    I have posted example code for transmitting and receiving in the Code Examples forum http://www.picbasic.co.uk/forum/showthread.php?t=6261

  4. #4
    Join Date
    Jul 2007
    Posts
    3


    Did you find this post helpful? Yes | No

    Default manchester encoding

    Hi dhouston and all,
    I'm using ASK RF module, which is similar to dhouston's "http://davehouston.net/modules.htm" list. its antenna 18cm long
    wire for both transmitter and receiver. No any other transmitter or some thing operate nearby.

    Thanks for your example thread, I'll try using that NEC protocol.

    Dhanushka

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


    Did you find this post helpful? Yes | No

    Default

    The distance problem is most likely from the wrong antenna length.

    315 MHz requires a 22.619 cm antenna. 1/4 wave length. And yes, a couple of cm will make a very big difference.

    The 1/4 wave antenna needs to be worked against a ground plane.
    Dave
    Always wear safety glasses while programming.

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


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by Dhanushka View Post
    Hi dhouston and all,
    I'm using ASK RF module, which is similar to dhouston's "http://davehouston.net/modules.htm" list. its antenna 18cm long
    wire for both transmitter and receiver. No any other transmitter or some thing operate nearby.
    ASK and OOK are essentially the same. The noise issue is illustrated here...It's easy to use your PC soundcard as a storage oscilloscope to view the receiver output. See...As mackrackit has noted, something around 22-23cm antenna length will work best for 315MHz. The exact length is more critical for the transmitter than the receiver but cutting both to the appropriate length works best.

  7. #7
    Join Date
    Mar 2003
    Location
    Commerce Michigan USA
    Posts
    1,166


    Did you find this post helpful? Yes | No

    Default

    dhouston, How can you say: Manchester encoding is not immune from noise but does have built-in error detection. What is the "built-in error detection"? This is news to me as I write software for Tire Pressure Monitoring equipment which uses Manchester coding. Please explain.....

    Dave Purola,
    N8NTA

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


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by Dave View Post
    dhouston, How can you say: Manchester encoding is not immune from noise but does have built-in error detection. What is the "built-in error detection"? This is news to me as I write software for Tire Pressure Monitoring equipment which uses Manchester coding. Please explain.....
    If you don't see a change of state at the middle of a bit period, you've detected an error which is usually the result of noise if you are using it over a wireless link or a collision if you're using it over a wired link (e.g. 802.3, X-10). See the last paragraph at http://www.wildpackets.com/support/c...ignal_encoding.
    Last edited by dhouston; - 5th August 2007 at 23:39. Reason: added X-10 reference

  9. #9
    Join Date
    Mar 2003
    Location
    Commerce Michigan USA
    Posts
    1,166


    Did you find this post helpful? Yes | No

    Default

    dhouston, I call that type if "error detection" signal integrity, not error detection. You could have a noise source producing edge changes at the same rate as the baud rate you are trying to detect. Where is the error detection then?

    Dave Purola,
    N8NTA

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


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by Dave View Post
    dhouston, I call that type if "error detection" signal integrity, not error detection. You could have a noise source producing edge changes at the same rate as the baud rate you are trying to detect. Where is the error detection then?
    Call it what you like. I'll call it what it is.

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


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by Dave View Post
    You could have a noise source producing edge changes at the same rate as the baud rate you are trying to detect. Where is the error detection then?
    And where is the error if no low state gets changed to a high state?

  12. #12
    Join Date
    Mar 2003
    Location
    Commerce Michigan USA
    Posts
    1,166


    Did you find this post helpful? Yes | No

    Default

    dhouston, Try deciphering 1 individual transmission of 128 data bits (256 states) with 4 or more transmitters being keyed at the same time.... The data states at the receiver might look good but what about the actual data..... Like I said... Signal integrity

    Dave Purola,
    N8NTA

Similar Threads

  1. My first DT_INT code has a problem.....
    By E Kizer in forum mel PIC BASIC Pro
    Replies: 2
    Last Post: - 13th April 2009, 13:37
  2. Weird code problem
    By Navaidstech in forum mel PIC BASIC Pro
    Replies: 5
    Last Post: - 16th March 2009, 11:16
  3. Making Program Code Space your playground...
    By Melanie in forum Code Examples
    Replies: 15
    Last Post: - 19th July 2008, 08:26
  4. Help with serin, serout, Manchester encoding
    By oneohthree in forum mel PIC BASIC Pro
    Replies: 30
    Last Post: - 5th April 2007, 13:31
  5. Code problem
    By chai98a in forum mel PIC BASIC Pro
    Replies: 0
    Last Post: - 20th May 2006, 04:43

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