2 am - Given up now - Can't figure out the problem. Using DT_Int. PLEASE help


Closed Thread
Results 1 to 5 of 5
  1. #1

    Exclamation 2 am - Given up now - Can't figure out the problem. Using DT_Int. PLEASE help

    Am I going crazy or is there something really dumb I am doing here. I have a 16F72 sending few serout commands, 16F877A should accept it and make it's port pins high/low accordingly.

    I am using DT_Int to get a momentary function on 6 pins. Two should be latching. No other pin should go high if any other of the 8 pins is high.

    My dear 877A is not happy with me. It works sometimes, sometimes only 4 pins work, ( Yes I have MCLR tied to 5V).

    I have to do everything manually and don't have any simulation software. But after making changes, trying new ways and reprogramming nearly 1 billion times now, I am so close to give up as I can't figure our what is wrong with what!

    Please have a look to my code and show me the light.
    Your help is greatly appreciated.Tx.txtrX.txt
    ___________________
    WHY things get boring when they work just fine?

  2. #2
    Join Date
    Sep 2005
    Location
    Campbell, CA
    Posts
    1,107


    Did you find this post helpful? Yes | No

    Default Re: 2 am - Given up now - Can't figure out the problem. Using DT_Int. PLEASE help

    I see no trace of your ISR.
    Charles Linquist

  3. #3


    Did you find this post helpful? Yes | No

    Default Re: 2 am - Given up now - Can't figure out the problem. Using DT_Int. PLEASE help

    Hi Charles, I am using DT_Int s, the label Togglefast is an ISR in the Rx code.
    ___________________
    WHY things get boring when they work just fine?

  4. #4
    Join Date
    May 2008
    Location
    Italy
    Posts
    825


    Did you find this post helpful? Yes | No

    Default Re: 2 am - Given up now - Can't figure out the problem. Using DT_Int. PLEASE help

    You Are sending twice the same code and then you compare code1 with code to see if same value. This is wise but is giving you problem with the synchronism since you have no handshaking.

    Suggestion: remove the compare feature and work with a single byte sent. If your code works has you expect then re-install the double sending feature and try with a higher baud rate (9600) and with a delay between the first byte and the second one (this on the device that Tx the byte)

    Cheers

    Al.
    All progress began with an idea

  5. #5


    Did you find this post helpful? Yes | No

    Default Re: 2 am - Given up now - Can't figure out the problem. Using DT_Int. PLEASE help

    Quote Originally Posted by aratti View Post
    You Are sending twice the same code and then you compare code1 with code to see if same value. This is wise but is giving you problem with the synchronism since you have no handshaking.

    Suggestion: remove the compare feature and work with a single byte sent. If your code works has you expect then re-install the double sending feature and try with a higher baud rate (9600) and with a delay between the first byte and the second one (this on the device that Tx the byte)

    Cheers

    Al.
    Thanks Al. My baud cannot increase to beyond 2400 because of other hardware limitations. I use the same format in every other PIC I use, and it works. But this combination of 676 & 72 has made me crazy. Currently everything is on my breadboard. Rx is fully responding to the first few signals on the Tx but not ALL.
    ___________________
    WHY things get boring when they work just fine?

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