1. Home
  2. Electronics Down Under
  3. How to check 125 logic states...?
  4. Page 4

How to check 125 logic states...?

I guess I am fortunate enough to have come throught the ranks via asm.

Abstraction is a good thing when used wisely. I often think that poeple misunderstand PC programmers. You typically have GUI programmers who have no concept of hardware, then you have the rest of us that do the underlying work, such as device drivers and frameworks for the presentation layer.

AQs for 64 bytes of memory, are your tring to control a toaster? Hardware is cheap now, even the entry level micro's come with heaps of ram/flash etc.

I beleive that C is just an extension on assembler. When I used to write assembler, i thought C was rubbish. Now I write c++ and c# i think it is much more effective in reducing development time.

Lies. I have seen terrible assembler coding too. Its how you code that makes the difference

I agree.

Any one can do a 'hello world' in VB. However not many self taugh 'Hello VB world' programmers can actually cut real code. That is the big misconception.

Reply to
The Real Andy
Loading thread data ...

yeah, it gives you a really good understanding of whats really happening.

its the unwise use of it thats the problem, sure.

likewise generalisation vs specialisation.

I often think that

alas, the former greatly outweigh the latter, yet think they are programmers.

the DSP im using now has truckloads of memory, costs US$10, and has 2 x 12-bit 83ns flash ADCs, with a pair of 8:1 s/h + mux. but that goes into an exensive box of tricks.

shortly i need to find a *very* cheap micro to run a 300W smps; that will have far fewer features

I'm looking forward to trying out this DSPs toolset, as I have quite a bit of code to write that needs to run very fast. If i choose my data structures carefully, I shouldnt need to resort to asm at all

yeah, fair enough. but I think C can be seriously unintelligable (witness the obfuscating C competition).

eruditely put.

Cheers Terry

Reply to
Terry Given

Noticed this and wondered if it might help - ideas to borrow

formatting link

David

Reply to
quietguy

formatting link

Thanks David Unhappily I need to look at the logic states of 125 inputs, not the open/closed state of only one of a large number of switches. :-( My circuit board re-design/expansion's properly under way now. One thing's for sure, I ain't gunna be able to squeeze 16 x 74HC165 shift registers into one square inch (25mm^2) of board area as someone suggested!

Cheers Bob

Reply to
Bob Parker

formatting link

An SO package is about (from memory) 100sq mm (including clearances), so you might get say 6 of them in your square inch. Then if you use both sides of the board, you are almost there... If you build a daughter board like I suggested previously then that could use up very little practical space on your main board.

Dave :)

Reply to
David L. Jones

Howdy Dave, I think that in amongst all the discussion, most people got the impression that I'm trying to make a tiny board. Actually the board size isn't very important, as long as it's not outrageously huge. :-) I just didn't want to lay out 16 x 74HC165 if there was an easy, practical way of using a smaller number of other readily-available devices which have a lot more input pins on each package. But it looks like the original idea is the way to go after all. I'm using ordinary SO16 devices. With all the necessary tracks in place to connect them to the outside world and using only one side of the board, I can fit about 4 of them into a square inch of board area. That will work out reasonably well. Thanks to you and everyone for all the suggestions. Some good design ideas have surfaced from all this. :-)

Regards Bob

Reply to
Bob Parker

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.