RX TX modules - intermitent communication


Closed Thread
Results 1 to 14 of 14

Hybrid View

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


    Did you find this post helpful? Yes | No

  2. #2


    Did you find this post helpful? Yes | No

    Default

    Greetings dhouston,

    thanks for the help!

    I read your article and the Demo code.
    To be honest i didn't understood some of the lines in the code and a bit of the article( being English as NOT my native language and just starting to learn comm/protocols and stuff...doesn't help ).

    In your demo code you use Pulsin instead of Debugin or Serin and this makes me get confused.

    I was looking for a simple approach where i could use the debugin/HSerin instructions.

    Is there any other way for this to work ?

    Thanks

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


    Did you find this post helpful? Yes | No

    Default

    @ruijc

    I have added examples that use SerOut2 and SerIn2 but I have not tested these as I'm rather busy with a project of my own right now. They should be easier to follow.

    The problem with using $55 or $AA (or a string of several) is that the receiver has difficulty distinguishing them from the normal noise it sees in the absence of a signal. Using a long pulse followed by a space (about half the length of the pulse) sets the receiver AGC and gives the receiver an easy to distinguish marker for the start of a transmission. Keeping communications packets short will help maintain DC balance

  4. #4


    Did you find this post helpful? Yes | No

    Default

    Thanks dhouston,

    The Serin/Serout version looks good thanks

    I understand your explanation for the Pulsout.

    If i understood correctly... the problem is for the RX module distinguish the Data from noise, correct ?

    Since the RX module will "see" the data transmition with the pulsout trick and grab it, after processing internally, it should give the message correctly to the pic.

    Then why the Receiver pic needs to "Pulsin" the RX module?

    I'm looking forward to test the SerIn version tonight

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


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by ruijc View Post
    Then why the Receiver pic needs to "Pulsin" the RX module?
    In effect, the receiver code waits for a pulse of sufficient length then calls SerIn2 to catch the message that follows the intervening space. IOW, the pulse is seen as a "start of transmission" marker by the receiver
    Last edited by dhouston; - 9th June 2009 at 20:12.

  6. #6


    Did you find this post helpful? Yes | No

    Default

    Thanks for your time dhouston.

    I've tryed the Serin2/Serout2 version but i couldn't receive any message

    Since my modules work at 19200 i changed the code like ( the rest is the same as you posted ):

    TX
    Code:
    SerOut2 tx,16416,["HELLO",10]
    RX
    Code:
    SerIn2 rx,16416,[STR msg\5\10]
    lcdout cl,row4, "received - ",STR msg\5

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


    Did you find this post helpful? Yes | No

    Default

    I guess I should have looked at the datasheet for your modules but, based on your code in the first post, assumed they are ASK - they are FSK which changes things a bit. See Data Reception on p5 of the link you gave.

Similar Threads

  1. Replies: 67
    Last Post: - 8th December 2009, 02:27
  2. RX - TX timming
    By ruijc in forum mel PIC BASIC Pro
    Replies: 5
    Last Post: - 12th February 2009, 00:06
  3. RX / TX duo
    By mbw123 in forum General
    Replies: 19
    Last Post: - 30th July 2006, 16:07
  4. TX RX Buffer Question
    By shawn in forum mel PIC BASIC Pro
    Replies: 3
    Last Post: - 14th January 2005, 01:49
  5. Tx and Rx of Single Pin PIC's
    By Dwayne in forum Code Examples
    Replies: 0
    Last Post: - 26th May 2004, 14:55

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