General > General Technical Chat
Sharing some project planning phase: A (digital) ELECTRO-MECHANICAL Network
<< < (14/39) > >>
RJSV:
Photo shows:
   It seemed pretty inconvenient, to have 3 shafts from the other switch segments, penetrating the 'C' segment volume (rectangular compartment).
But, seen in upper left, both the 'A' local output (to do reset), and the 'B' input, are needed, and used right there. Extremely convenient.
RJSV:
   Photo is to show, generally, the path of that reset, to the 'C' segment of switch, going against the grain, so to speak; The reset coming from the 'A' local output takes the path usually reserved for input, as there isn't any input process. That is the other side (local). The main side is for chaining signal, input to chain output (via the toggle switch with tip wheel).

   This view is from front, towards the back. Altogether, there are 18 layers: 6 for each segment of the ABC 3 section contactor.
RJSV:
   Jumping ahead, for a second: Here is some outline for a Base controller.
   Currently, have identified 2 key issues, details for implementing the basic path switch, or commutation switch assembly.  One issue, involves mixing mechanical (rotary) signal 'data', inadvertantly causing 'backwards direction signal, into other components.
Other current issue involves how to actually turn off or reset all channels in a given switch box,  meanwhile the preceding boxes have all gone to 'transparent' mode, and so cannot effectively send out local controls.

   For controller aspects, photo showing toy 'robot dog's for wired control, where a clever switch setup helps for sending dual polarity to motors, for doing both directions, CW and CCW (that's counter-clockwise.)
   The toy hand controls will issue approx 3.4 volts DC of either polarity direction, to each Base motor / gear drive. For the Base controller  outputs, there are 3 'chained' signals (channels 'A', 'B', 'C'), with an additional 'local' output, using 'B' to send 'Select' to next station switch box.
   Various other Base Station features mostly manual controls, but with plans towards eventual controller, (Arduino likely).  The rotary switches seen are 2 pole, and 6 positions, for various options while testing / experimenting with series networks of switches.
RJSV:
Those TOY DOGS, well, they provide some function examples that I could use in my project
   The motor has a two directional separator that puts any clockwise rotation to one output, in this case the dog wags tail, and barks, via small audio chip with little 1 inch speaker. The little PC board and connected motor respond to one POLARITY direction, diode isolated.  The other polarity output direction, of the two cell battery pack gets isolated, mechanically, and provides the 'walking' motions of that dog.

   Anyhow, being more software experienced I need that kind of fairly simple TOY mechanism, for implementing actual progress, towards a working 3Pole - 2 throw switch (3PDT).

   (It's been couple years since I've open one, but have forgotten how that toy doggy does the separation of the two motor directions, into 2 destinations, according to motor polarity.
RJSV:
   Here is a view, I've been wanting to show: This diagram view, included, shows how there is a sort-of 'DUALITY' in the mechanical commutation switch.  In the view, simplified disks pressed together act as switch, for selecting one or the other. That would be the chain output, or the 'local' output.
   Now, any switch is going to have a TOPOLOGY (no expert; I can barely spell that), where it's a 1 in and 2 (signals) out.  When the topology, or connection layout is extended, as in my series connected, the layout, itself, suggests a 'fourth' terminal, rather than just the 3 used in one stage.
   The match, of the 'B' segment, of 3PDT switch, going out to the next station 'B' switch segment, suggests that a fourth location be assigned as 'B local input'.
This creates a nice, common sense result, putting each local output to be sent into next station's local input.  Formally, that doesn't show much meaning, but in the (series) network, in the bigger view that 'local' input makes sense, and preserves the need, to avoid any spatial offsets, from each station box to the next.
(Otherwise, there would be a 'drift', misaligning each next box, that either needs correction, or simply doing station box placements that aren't in a straight line.
   ...Confusing, YES I know. (Thanks).
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod