Tws 434/ Rws 434


Closed Thread
Results 1 to 11 of 11

Hybrid View

  1. #1
    Join Date
    Nov 2005
    Location
    Bombay, India
    Posts
    971

    Default

    Try baud rate 1200 instead of 2400. Most of these modules are good at this frequency.

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

    Default

    Two things:
    First, the junk data transmitted has to be a certain type of junk. The receiver has to be put into a “middle” state in order to work. Think of a capacitor that is charged to its maximum of 25 volts. Adding a 25 volt signal to it will not have a change on its state. The same goes for one that is zero charged, 0 volts will not change its state. In order for either 0 or 25 volts to have the same effect the capacitor has to have an initial charge of 12.5 volts.

    To put the receiver in a “middle” state send $55 five times. Then send the synch then your data all on one line.

    Code:
    'transmitted
    junk = $55
    synch = a
    SEROUT PIN,N2400,[junk,junk,junk,junk,junk,synch, data]
    Code:
    'received
    SERIN PIN, N2400,[“a”],data
    Notice I used the SERIN/SEROUT , not SERIN2/SEROUT2.
    Dave
    Always wear safety glasses while programming.

  3. #3
    Join Date
    Jan 2006
    Location
    Toronto
    Posts
    109

    Default

    These modules require all data to be encoded using the Manchester code. Search this forum for it and you will find lots of examples.

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

    Default

    Quote Originally Posted by PJALM View Post
    These modules require all data to be encoded using the Manchester code. Search this forum for it and you will find lots of examples.
    Manchester encoding is not a requirement. They are used extensively without it.

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

    Default

    Quote Originally Posted by dhouston View Post
    Manchester encoding is not a requirement. They are used extensively without it.
    Agreed. When I was having my problems with SERIAL, tested RF by simply sending a high bit.

    Kind of like Morse code. Instead of "..._ _ _..." it was "... ..."
    DOTS = HIGH
    Dave
    Always wear safety glasses while programming.

  6. #6

    Default

    sorry for the late reply, i have not had time to work on this till now.


    so it tried what you said and sent %10101010 to stabalize the oscillators, (put it in the neutral zone). and now i am able to get something on the other end of the pic. however i can't seem to get it continously. in my sample program i am counting numbers continously in my transmitter side and sending it to my reciever to display it. it sends numbers but it does not send it continously.

    i.e i send 1,2,3,4,5,6,7,8,9,10 and will recieve 1, 4, 6,9

    how do i make my program more stable.

    '=====transmitter=====
    junk = $55
    synch = "a"
    dat = 0
    loopa:
    pause 1000
    serout tx, N2400, [junk, junk, junk, junk, junk, synch, dat]
    dat = dat + 1
    if dat = 255 then dat = 0
    goto loopa

    '=====reciever======
    synch = "a"
    dat = 0
    begin:
    serin rx, 4, [synch], dat
    pause 5:serout2 LCD, baud, ["start", 1, DEC (dat), 0]
    goto begin

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

    Default

    For small amounts of data I prefer using the NEC protocol which has been around since the dawn of remote control and has been widely used by manufacturers of audio/visual gear.

    I posted a short example for sending/receiving in the Code Examples forum.

    http://www.picbasic.co.uk/forum/showthread.php?t=6261

Similar Threads

  1. Replies: 2
    Last Post: - 29th September 2007, 07:49

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