Of course Peter.
But I mean about to solve the original member problem...why not to try with "short wires", some code, 3.3Vcc, and then going ahead with the own needs.
My board is this.
That's sort of what I meant by "it's not rocket science" in that it's fairly easy through elimination to find out what's going on as obviously there is nothing wrong with the software as the scope timing shows.
While we are trading pics here's the bottom part of the one I have been working on, the 74HC595s are in the TSSOP pack arranged as a 32-bit register which also drives optos on each pin driver module. It's all smd stuff packed in fairly tight as it fits into a sealed and rugged case that's designed to operate with extreme vibration and even under water if it has to.
I probably should have mentioned that part of the reason I went to using the 74LS245 drivers is that I'll be running very long Cat 5 wires between the Prop and the 74HC595 chips. I've attached photos of the Proto Board and one of my custom driver boards that is fully populated with LED's that I use for debugging. The Proto Board photo shows how easy it is to wire the outputs through the 74LS245 chip. I have a much uglier Proto Board where I used a 74LS244...
Comments
But I mean about to solve the original member problem...why not to try with "short wires", some code, 3.3Vcc, and then going ahead with the own needs.
My board is this.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Regards.
Alberto.
That's sort of what I meant by "it's not rocket science" in that it's fairly easy through elimination to find out what's going on as obviously there is nothing wrong with the software as the scope timing shows.
While we are trading pics here's the bottom part of the one I have been working on, the 74HC595s are in the TSSOP pack arranged as a 32-bit register which also drives optos on each pin driver module. It's all smd stuff packed in fairly tight as it fits into a sealed and rugged case that's designed to operate with extreme vibration and even under water if it has to.
*Peter*