This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

lcd display repeats the same digit twice

hi i am using at89c51 controller along with jhd162a while printing the number like 1234
it prints as 1133,this error does not happens always, only few times it prints correctly as 1234 ,but most of the time it prints with error as like 1133,even i ve changed the circuit board still it prints with the same error
please guide me to solve the problem
thanks in advance

Parents
  • "so i think there may not be nothing wrong with my code is there any common error with AT89s52 or jhd162a? is these device are temperature Dependant?"

    The general conclusion when something works should be:

    "There must be something wrong with my stuff."

    You really think a simulator can prove correctness? It can detect some errors so a simulator is a valuable tool. But it isn't a reference that can be fully trusted to give results that are matching the real world.

    Whenever you look at a datasheet for a component you are using, there are a large number of statements about limitations and requirements. They are basically a contract between you and the component supplier. It is up to you to fulfill all the requirements in the datasheet, or the component can't be trusted to behave as intended.

    So every timing value you see in a datasheet has to be verified by you. Do you fulfill all setup times? All hold times? All rise times? All fall times? All min/max voltages? All currents? Capacitive loads? ...

    There is a reason why logic analyzers, digital oscilloscopes etc are quite common tools when doing embedded development. You need real hardware tools to prove much of the parameters specified in the datasheets.

Reply
  • "so i think there may not be nothing wrong with my code is there any common error with AT89s52 or jhd162a? is these device are temperature Dependant?"

    The general conclusion when something works should be:

    "There must be something wrong with my stuff."

    You really think a simulator can prove correctness? It can detect some errors so a simulator is a valuable tool. But it isn't a reference that can be fully trusted to give results that are matching the real world.

    Whenever you look at a datasheet for a component you are using, there are a large number of statements about limitations and requirements. They are basically a contract between you and the component supplier. It is up to you to fulfill all the requirements in the datasheet, or the component can't be trusted to behave as intended.

    So every timing value you see in a datasheet has to be verified by you. Do you fulfill all setup times? All hold times? All rise times? All fall times? All min/max voltages? All currents? Capacitive loads? ...

    There is a reason why logic analyzers, digital oscilloscopes etc are quite common tools when doing embedded development. You need real hardware tools to prove much of the parameters specified in the datasheets.

Children
No data