Hello eTech and the ETO forum,
Response to post #18:
The PC layout software is Dip Trace by Novarm
Link to Dip Trace home page
It does have a Schematic Capture module.
An attempt to master the Schematic Capture
feature was attempted but was abandoned in the face of a steep
learning curve. But now that a comfort level
has been achieved with the PCB Layout domain
will look at using the Schematic Capture.
I can see, not only would it save time, but solve
issues at several levels in going from schematic to PCB.
Will repost all three module schematics and
PCBs.
I recommend that you DO NOT post any more schematics, boards or order PCB's at this time. It is becoming difficult to keep track of them.
I suggest you take time to learn the schematic capture and capture the schematics first.
Then we can review the captured schematics, check they are up to date and correct before proceeding to PCB layout. This is what I was alluding to when suggesting to make ONE schematic and keep it up to date. Let the schematic drive the board layout. Also, the parts used on the boards posted seem to be of random package type/size. For example, the sensor module should have all 1/4 resistors and Q1 should be a TO-92 case. A list of parts should be on hand to use for laying out the board and ordering parts.
I make these suggestions because I want you to succeed with your project (It is a cool project) .
Have had some years of element versioning
working with software. It may be noticed
that the drawings are always dated and some have
revision notes like POCADAL Sensor Module
View attachment 127694
dated 200725 revised in Aug and Oct.
Although it is admitted sometimes revisions
are not always noted and will double down
on that.
Your post above has not been updated.
Response to post #19:
Will post separate LED, Sensor and
Shield schematic and PCBs as soon as able.
I believe this is the latest over all schematic.
View attachment 127695
Was there another schematic of the complete
system posted? It was thought that this
is the latest.
It looks close but I cannot vouch for the above schematic. I can only post the schematic I have and I know to be correct. The only thing that has changed in mine is the annotations we discussed in post #10.
The bread board was
examined and there is a red/red/orange
resistor. But i guess it was eliminated
and the elimination was missed.
It was never there and must have gotten added by mistake.
Oh, wait a minute. Separate 22k resistors
are shown for each of the sensor inputs
on schematic marked 'REF: 202026 Rev 2020/1028'.
They are marked R1, R2, R3, R4, R5, R6, R15, R25.
So in preparation for refactoring the
Shield Main Board would just run through
some of the ideas about how the Sensors
connect to the Main Board Shield and the
Arduino underneath. (It is realized that
pins from the shield penetrate down from the shield
to the Arduino for inputs on the left and
for outputs from the Arduino to the
DMOS array IC on the right. Right?)
I took your FTB designator to be whatever you are using to make a connection from the arduino pins to the shield. The terminal shown as a box with an "X" inside is a typical symbol for an arduino terminal and represents an "FTB" connection. I called it a "Feed Thru Terminal". I can see now that that is probably not a good designator as you meant FTB to mean "Fixed Terminal Block". TB1 through TB12 are Fixed Terminal Blocks.
1. The wires (some of them several feet long)
go from the two position fixed terminal blocks
(FTBs) on the Sensor modules and are received by
two position FTBs on the Shield marked
'IN S1 RTN' thru 'IN S8 RTN' on schematic
marked 'REF: 202026 Rev 2020/1028'.
Correct.
2. The 'IN S1 RTN' FTBs go to sixteen 430 ohm
resistors and to the anode and cathode of the
optocouplers. The emitters of the optocouplers
go to ground. The optocoupler collectors
go first, via traces on the shield, to the
Arduino input pins, and second to a 22k
resistor and then to the plus five volt
pin of the Uno.
This is the only part that made me scratch my
head. 'REF: 202026 Rev 2020/1028' shows what
is designed on the shield to be header pins
going thru shield down to the Arduino as
FTB1 and FTB2 (FTBs?)
Beginning to think this just how the headers
are marked based on the mistake I made in the PCB
marked 'POCADAL Arduino Shield Maon(sic) 201024
in post #17. That is, an extra set of FTBs were
shown because I forgot to remove
the FTBs from the shield when the optocouplers
were moved to the shield.
This is probably the same reason why the six input pins
sticking down thru the shield to pins A0-A5
on the Arduino are marked FTB3. My bad.
Review schematic post #19,
I took your FTB designator to be whatever you are using to make a connection from the arduino pins to the shield. The terminal shown as a box with an "X" inside is a typical symbol for an arduino terminal and represents an "FTB" connection. I called it a "Feed Thru Terminal". I can see now that that is probably not a good designator as you meant FTB to mean "Fixed Terminal Block". TB1 through TB12 are Fixed Terminal Blocks.
Ok I get it. The big difference between
'REF: 202026 Rev 2020/1028' and the two
drawings in post #17 ('POCADAL...201024'
and 'POCADAL...201026) is my drawing
shows one 22k resistor and eTech's shows
eight 22k resistors.
Will
1. Post the latest schematics and PCB
drawing of the LED and Sensor modules.
2. Redraw the shield PCB drawing based on
'REF: 202026 Rev 2020/1028' and post.
Glad I got your input before I ordered
the shield PCB.
Thanks.
Allen in Dallas
PS Sorry about the length of this post
but I think it got us on the same path.
I suggest, once more, to take some time to learn the schematic capture program and practice passing changes between the schematic and board layout so you get a feel of what is required for updates to work. You can create a simple one LED board to try this on. Practice this until you are comfortable with it. Then capture the sensor module schematic and we'll start from there.
Last edited: