Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

[SOLVED] problem with 74LS85 comparator

Status
Not open for further replies.
M

maark6000

Member level 5
Joined
Jan 15, 2013
Messages
92
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,288
Activity points
2,270
having a strange problem with a 74LS85 comparator. I'm running a binary clock on the A inputs, 0000 thru 1111, and on the B inputs I just have a fixed number. A=B goes high at the appropriate time... but also 2 before. So if I have my B input number at let's say 13... the A=B output goes high at 11 and 13. if I move the B number to be 14, then A=B goes high at 12 and 14. I tried swapping out the chip, the next chip did the same thing. It's driving me bananas... I've quadruple checked everything. Anybody ever encounter that problem?

Mark
 

For the specific example you've given with 11 and 13, A1 and A2 or B1 and B2 could be swapped.

Oops, didn't read the whole post. Are you allowing some time for the output to settle?
 
If this "clock" is a ripple counter, there could be enough
timing skew in the different bits' outputs that transient,
invalid codes are presented to the magnitude comparator.
This would not be the case with a synchronous counter.
 
the "clock" is a 74LS193 counter, which is synchronous. it is clocked by my BK precision signal generator, set to a square wave, about 10 Hz, from the TTL/CMOS output. What's funny about the fact that the A=B output goes high 2 before is it isn't a transient... it's not some little spike, it goes high for the entire time the clock is outputting that number. I'm going to isolate the clock and the comparator tonight and see if somehow other ICs in the circuit are causing the strange behavior (other ICs being a 7485, an OR gate, and a hex inverter).
 

well, i'll never know what I was doing wrong. tonight I ripped out all my jumpers and started over. I did do something I think was smart... I set up my clock and my comparator, and applied power to make sure it was working without any other parts of the schematic attached. I had the A>B, A=B, and A<B outputs lighting up LEDs. Then I kept the power on while I continued to connect up the rest of the ICs. That way, if something squirrelly started happening, I'd know exactly the moment it happened and with which connection. Don't know if that would have been a smart move with CMOS chips, but with rugged ol' TTL, it worked great. Circuit runs as designed. Thank you to all for your help. Cheers!
 
  • Like
Reactions: j33pn

    J

    j33pn

    Points: 2
    Helpful Answer Positive Rating
Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top