isobianin
commented
5 years ago Hi! So I addressed this issue later and came with a plan of solving it. Nothing special but it will help with keeping this issue transparent to those who are interested in it and it just keeps everything organized. Additionally, it may help with estimating time needed to achieve desired result.
Plan of work:
- Look into schematics and PCB layout.
- Examine analogous systems.
- Work on modularity. 3.1. Design new PCB layout. 3.2. Check PCB signal integrity and electromagnetic compatibility (Verify PCB's ability to function in general).
In order to accomplish set goals I would like to know the following: 1) This issue was posted a long (relatively) time ago. Are there any time restrictions? 2) How is PCB assembled and manufactured? I suppose that you order it in assembled state from somewhere. 3) What components are available? There should be a little database where one can find required connectors and other components. 4) Even so I had looked through the folder "PCB", I got confused a little bit because there are so much files. Can you please explain what are the files that I can work with? I mean, what are the files for latest PCB schematic, layout and bill of materials?
amchagas
Figure 1 - FlyPi structure
It consists of:
a) power 1 - 12v to 5v converter dedicated to power the Raspberry Pi
b) power 2 - 12v to 5v converter to power LEDs, LED ring, Thermistor and devices on the I2C port
c) High power LED / 5V general module 1
d) High power LED / 5V general module 2
e) LED ring module
f) servo motor module
g) Peltier element module
*) also there is SD card (I2C port)
Figure 2 - Perpendicular
pros: approach uses Z-axis and allows for more things to placed
cons: PCB enclosure is very tight and PCB may have problems with dimensions (for now, I have checked that LEDs can be implemented that way but more research is needed)
Figure 3 - On top
Pros: straightforward, relatively easy design
Cons: approach creates a lot of unused space below modular PCBs
Figure 4 - Parallel
Pros: relatively easy design
Cons: PCB will be cut, best used only on border modules (power, peltier), LEDs – not so much
Figure 5 - Enclosure
Figure 6 - Design
What are your thoughts on amount of modules, design approaches and schematics?
Figure 1 - Discrepancy in components
2 - Got it, very informative. I knew that there was something with the pins' specification.
3 - Totally agree with the first part of the paragraph. I was about to propose something like that because it is practical to design universal module that can be easily programmed. It just need to have enough pins. However, I did not quite understand the other part of the message. So are you referring to the second design where the main board consists of plastic connectors (or pin headers) which are connected to anything with the corresponding pins? In this case, what about driving circuits (transistors)? I mean there are examples without drivers on the same main board.
Figure 2 - Drivers
I came up with the idea of implementation of small PCBs based on an assumption that all the stuff on the main board is essential for its connection to the desired object (led, servo motor, led ring etc.). If the desired object resembles complete module (with all necessary driving elements), it is possible to replace small PCBs with connectors. Nevertheless, peltier will still remain as the one big module that, in all likelihood, will be turned in to the PCB.
Here I drew general concepts (fig. 3).
Figure 3 - Concepts
The A concept is what I was going for. The main issue of the B concept is the driving circuit. If it can be omitted, then it is settled and general-purpose connectors will be inserted on the main PCB. 
Figure 1 - The concept of designated modules
Here, the main objective is to determine specific modules and modules that are to be implemented in the future. I mean the current version of FlyPi have a lot of things for research purposes. However, there should be some ideas that were omitted due to the lack of manpower or time (maybe both).
Currently the system has 1 PCB containing all hardware modules. Optimally, each module would be implemented in a small PCB, as a piece of a puzzle. Seeed has implemented something like this with their grove system.
The advantage of this modularity would be to reduce costs (as users only need to source parts for the modules they need and each PCB will be smaller). Also it will allow bigger customization as users might want 3 LED modules and no Peltier module (as opposed to the stock 2 LEDs and 1 Peltier).