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

Problem in 4094 IC

Hello all, I am using tm4c129 controller. I have interfaced dot matrix printer (LX-310) with it. For this i am using HEF4094B IC and it is working fine but when i replace it with CD4094BE then printing is not working. I dont know why? i have checked data sheet of both ICs. There is no difference in them.

Regards,
Sagar

Parents
  • Besides comparing the datasheet - have you spent some quality time with an oscilloscope and verified all signals similarly to what you would do if one of the chips is damaged?

    It shouldn't take many minutes to verify if the chip accepts the input signals - and if it produces the expected output signals. And suddenly you have your answer without having to wait for someone on the other side of the world guessing what might be wrong but without access to your hardware.

Reply
  • Besides comparing the datasheet - have you spent some quality time with an oscilloscope and verified all signals similarly to what you would do if one of the chips is damaged?

    It shouldn't take many minutes to verify if the chip accepts the input signals - and if it produces the expected output signals. And suddenly you have your answer without having to wait for someone on the other side of the world guessing what might be wrong but without access to your hardware.

Children
  • Yes sir, I have already observed both IC's waveform with CRO ,but i have not found any difference in both waveform.

    Regards,
    Sagar

  • If identical signals in give identical signals out (voltage levels and rise/fall times), then the problem isn't with the brand of 4094 but somewhere else. Just note that since the 4094 has internal state, it isn't enough to compare with static input data. You need to verify that the same sequence of dynamic input produces the expected output - a noisy input to a clock signal can count as one or multiple clocks depending on hysterese, input-high/input-low limits, rise/fall times etc.

    The goal with debugging is to evaluate the problem until you find where expectation and reality differs - and then verify if it was the expectation that was wrong or if you need to continue to search.