modular portable prototyping

[mpp2508]

I am developing a method for prototyping electronics that are resistant to transportation.
You can see what it looks like here
https://mpp2508.github.io/docs/03asmb/unsorted/

Here are modules that either already exist in their final form or are at the final stage.
https://mpp2508.github.io/docs/02m/00gal/

The photos of the assemblies show what it looks like and what advantages it has over a tangle of wires on the table.

Another use case is to assemble temporary devices that are needed temporarily. Assembled, used, disassembled.

The rules for developing modules will make it easier for everyone to develop their own compatible modules.
https://mpp2508.github.io/docs/01rul/
Which will contribute to the formation of an ecosystem of approaches to prototyping.

The project is open. But I publish the necessary materials upon request, to track real interest.

Developing working modules requires making at least one prototype, in the best case. In the worst case, several. And if the most expensive parts can be reused, then the boards need to be ordered again. And despite the cheapness of the boards, this negatively affects the family budget in the absence of income from the project. So here is a patreon, if anyone decides to support the development of the project.
https://www.patreon.com/c/mpp2508

I will not launch a crowdfunding campaign, due to unfavorable circumstances that may cause non-fulfillment of obligations.

In fact, the issue of financing is not in the first place. But it was raised so that it would not be too late. In the first place is the issue of feedback. I at least need to understand why my approach to prototyping is considered unsuitable for use.
I need a discussion to expand the range of modules.
Where can I look for potential users of my approach to prototyping?

[PlainName]

prototyping electronics that are resistant to transportation

I don't think you should use the word 'resistant', which means transportation is a no-go. Instead, try 'tolerant'.

Interesting project, but I think you should explain quite early one exactly what it is and how it works. It took me quite some time perusing the photos to work it out, and I'd almost given up before then. How does that 0.1" header fit to those big holes, for instance. So just say straight off that it's a base board with fixing holes, and each sub-module is designed to affix to that board via screwed pillars.

[shabaz]

In the first place is the issue of feedback. I at least need to understand why my approach to prototyping is considered unsuitable for use.

Interesting idea, but personally I would find it unsuitable because I think it is micro-managing prototyping too much..  The repository has even got detail down to placement of text, and prescribed connectors. The grid may be important for things that need more precise alignment (such as mating connectors, or assembling mechanisms, or optical work) but your design is using jumper wires, which do not need the boards aligned.

The defined 5.08 mm spacing and 2 mm hole diameter feels impractical, since many off-the-shelf existing boards may not fit. There's an Adafruit product which tries to address that, by having slots. I think at least making your base board have slots, or at least some slots, may improve it.

Personally I prefer to use a piece of plastic or wood, with holes drilled for board standoffs or spacers. That way works with almost all existing prototyping and breakout boards, using (usually) standard M3 screws. It works for plastic (often transparent or translucent) covers too.

I tend to keep a small amount of opaque, clear and translucent plastic sheets, 3 mm thick, and drill some holes in them, to act as a base and/or cover. The end result is as robust as drilled plastic is, and can look as neat as a regular-arranged grid if drilled accurately. But I appreciate not everyone might feel comfortable cutting/drilling plastic (although there are services for it, but chargeable).

[mpp2508]

I don't think you should use the word 'resistant', which means transportation is a no-go. Instead, try 'tolerant'.

I am not a native English speaker. I use Google Translate. So the wording that seems logical to me actually turns out strange and illogical.

I am developing a method for creating portable prototypes of electronics.
Maybe this phrase is more appropriate? Which says that the result is prototypes whose main feature is portability? But is it appropriate in the context of comparing a tangle of wires on a table, as they say here, spaghetti style?

Interesting project, but I think you should explain quite early one exactly what it is and how it works. It took me quite some time perusing the photos to work it out, and I'd almost given up before then. How does that 0.1" header fit to those big holes, for instance.

Can you send me a link to the photo that is misleading?

So just say straight off that it's a base board with fixing holes, and each sub-module is designed to affix to that board via screwed pillars.

I think in the case of printed circuit boards the word standoff is more appropriate. Or not?

[mpp2508]

  Interesting idea, but personally I would find it unsuitable because I think it is micro-managing prototyping too much..

This prototyping micromanagement is backwards compatible and will not deviate into proprietary solutions.
The rules should not be viewed as dogma, but only as guidelines for action.

The repository has even got detail down to placement of text, and prescribed connectors. The grid may be important for things that need more precise alignment (such as mating connectors, or assembling mechanisms, or optical work) but your design is using jumper wires, which do not need the boards aligned.

The connectors are arranged in a grid for butt-joining when a regular jumper is used instead of a wire jumper, like on motherboards. This saves space and the number of protruding wires.
https://mpp2508.github.io/docs/03asmb/unsorted/img/010.png
This photo shows how the logic analyzer module is connected to the USB-B module (below, purple and green module).
Look at other photos and you will find such connections.

The defined 5.08 mm spacing and 2 mm hole diameter feels impractical,

Using breadboards for soldering as a blank for modules when there is no point or possibility to make a printed circuit board.
And these breadboards have a pitch of 5,08/2. If you use a different pitch on the base, this will be difficult. Butt jointing will become more difficult.
https://mpp2508.github.io/docs/00blog/00prehistory/img/009.png
https://mpp2508.github.io/docs/00blog/00prehistory/img/010.png
As for the 2mm hole, m2.5 and m3 would be too big for a 5.08 pitch. Maybe m2.5 would have been suitable, but I decided on compactness and butt jointing.

since many off-the-shelf existing boards may not fit.

Adapters are provided for all kinds of different modules.
https://mpp2508.github.io/docs/02m/adap/mpp_a_01/img/001.png

There's an Adafruit product which tries to address that, by having slots. I think at least making your base board have slots, or at least some slots, may improve it.

I haven't seen that from them. We still need to start collecting similar concepts over the network.
Well, as was said above, the problem of third-party modules is solved by adapters.

Personally I prefer to use a piece of plastic or wood, with holes drilled for board standoffs or spacers. That way works with almost all existing prototyping and breakout boards, using (usually) standard M3 screws. It works for plastic (often transparent or translucent) covers too.

I tend to keep a small amount of opaque, clear and translucent plastic sheets, 3 mm thick, and drill some holes in them, to act as a base and/or cover. The end result is as robust as drilled plastic is, and can look as neat as a regular-arranged grid if drilled accurately.

Well, it's hard to switch from familiar solutions because it's a habit. And you also need to make an effort. As our system administrators say, if it works, don't touch it. But on the other hand, you've probably had cases when you reluctantly mastered something new, and then thought about why you didn't do it earlier. Maybe the same will happen with mpp2508, who knows.

But I appreciate not everyone might feel comfortable cutting/drilling plastic (although there are services for it, but chargeable).

There is such a thing. There is always a task of balance based on personal capabilities.

[PlainName]

I am developing a method for creating portable prototypes of electronics.
Maybe this phrase is more appropriate? Which says that the result is prototypes whose main feature is portability? But is it appropriate in the context of comparing a tangle of wires on a table, as they say here, spaghetti style?

"... creating robust and portable prototypes."?

Can you send me a link to the photo that is misleading?

https://mpp2508.github.io/docs/03asmb/unsorted/img/010.png

It's only confusing because I didn't understand what I'm looking at. There is no depth perception for most of them, and in my mind I am thinking Manhattan style, where the sub-boards and directly attached to the carrier board. But in that style there are no holes on the base, so what are the holes in yours? If it had been clear from the start what it was about then there would have been no confusion. Perhaps a side-on photo showing just how they sub-boards are mounted would explain it.

I think in the case of printed circuit boards the word standoff is more appropriate. Or not?

Yes, much more appropriate. Despite being a native speaker I am sometimes lost for the right word 

[mpp2508]

https://mpp2508.github.io/docs/03asmb/unsorted/img/010.png
It's only confusing because I didn't understand what I'm looking at. There is no depth perception for most of them, and in my mind I am thinking Manhattan style, where the sub-boards and directly attached to the carrier board. But in that style there are no holes on the base, so what are the holes in yours? If it had been clear from the start what it was about then there would have been no confusion.

In theory, these pages were supposed to demonstrate how it looks structurally.
https://mpp2508.github.io/docs/01rul/connections/
https://mpp2508.github.io/docs/01rul/butt_conn/
And the photos of the assemblies are just an attempt to demonstrate real use. That the project is not just another theoretical idea.

https://mpp2508.github.io/docs/03asmb/unsorted/img/010.png
 Perhaps a side-on photo showing just how they sub-boards are mounted would explain it.

Apparently, I will have to shoot a video for YouTube.

And another question, did you use a translator when viewing the site? I often look at information in different languages, and for me, the action in Google Chrome to click on the menu item translate is a reflex to a language I do not know. Therefore, apparently, there was a false impression that everyone does this, and there will be no problems with the language of the site.

[PlainName]

In theory, these pages were supposed to demonstrate how it looks structurally.
https://mpp2508.github.io/docs/01rul/connections/

Perfect. Perhaps leading with that here would have saved a thousand words.

And another question, did you use a translator when viewing the site?

No. Wondering what your project was about I followed the links you provided to the photo stream.

You can't expect people to spend time trying to figure things out on their own unless they already know they are interested. Your post here should capture your audiences attention and make them want to learn more. Instead, you seemed to assume they will go off and learn all about it because... well, why? And making the effort to get Google to translate some random pages. No, not going to happen.

[tggzzz]

You can't expect people to spend time trying to figure things out on their own unless they already know they are interested. Your post here should capture your audiences attention and make them want to learn more. Instead, you seemed to assume they will go off and learn all about it because... well, why? And making the effort to get Google to translate some random pages. No, not going to happen.

Hence the concept of the "elevator pitch"... You have 30s in an elevator with someone. If you can grab their interest in that time, they will look at your proposal. If not, it doesn't matter how good your proposal is.

Another concept is to quickly tell people their problem is M, but if they do X then they will get Y (which solves M) but won't get Z (which is relatively unimportant to them). Classic Southwest Airlines example is
M is get from A to B
X is fly from A to B with Southwest
Y is frequent and cheap flights
Z is checked baggage, assigned seats, free food, baggage transfers

[mpp2508]

You can't expect people to spend time trying to figure things out on their own unless they already know they are interested. Your post here should capture your audiences attention and make them want to learn more. Instead, you seemed to assume they will go off and learn all about it because... well, why? And making the effort to get Google to translate some random pages. No, not going to happen.

I have tried many times to formulate concise formulations, but everything is intertwined and piled up. I realized how important it is to pay more attention to the first page, so that what fits on the screen when the page is opened, clearly and immediately conveys the meaning of this project. And I will do this in graphic form, in the style of the pictures in the rules section. Oh, and this is a painstaking task, especially if I am not a graphic designer, again Corel Draw. Thanks for the answers.

[PlainName]

Hence the concept of the "elevator pitch"

We need an updated version for WFH

[PlainName]

Oh, and this is a painstaking task, especially if I am not a graphic designer

Yes, but you are getting much further than most people who would have given up before this point. 

[tggzzz]

Hence the concept of the "elevator pitch"

We need an updated version for WFH

Coffee shop pitch?
Dog walking pitch?
Tower block pitch?
Tweet pitch? Or should that be twat pitch?

These are clearly inapplicable: https://www.stiltz.co.uk/home-lifts/

[mpp2508]

Yes, but you are getting much further than most people who would have given up before this point. 

I've been nurturing this idea for a long time, since about 2013. About a year and a half ago, I realized that the base can be made as a printed circuit board, decided on a 5.08 pitch and a 2mm hole for the base. (How I came to this is here https://mpp2508.github.io/docs/00blog/00prehistory/). And then I realized that this is exactly what I was looking for so long. And I began to develop material until I ran into a lack of practice, because my main activity is PLC (industrial automation) and not microelectronics. I need ideas for modules, the most commonly used, to develop an effective nomenclature. I made timid attempts to contact various manufacturers of various modules, but this did not bring results. Not really counting on this, I made an account on Patreon. In case someone likes the idea so much that he parts with a small part of his hard-earned money. As they say, an account doesn’t require upkeep.
And although a lot of work has been done, there is still more to come.

[Kean]

Interesting project, but I think you should explain quite early one exactly what it is and how it works. It took me quite some time perusing the photos to work it out, and I'd almost given up before then. How does that 0.1" header fit to those big holes, for instance. So just say straight off that it's a base board with fixing holes, and each sub-module is designed to affix to that board via screwed pillars.

Indeed.  I took a look the other day, and had no idea that the base PCB was just for mounting holes.  There is no real need for them to have any copper plating if that it the case.

In theory, these pages were supposed to demonstrate how it looks structurally.
https://mpp2508.github.io/docs/01rul/connections/
https://mpp2508.github.io/docs/01rul/butt_conn/
And the photos of the assemblies are just an attempt to demonstrate real use. That the project is not just another theoretical idea.

Aha!  You should have linked to pictures like these first, and you should feature them on the main page of your github.  They immediately explain the concept to me.

This is not something I would likely use as I have access to a good workshop with CNC, laser cutter, and have about 40 years experience with electronics prototyping.

[Kean]

OK, I now see some helpful pictures halfway down the page at https://mpp2508.github.io/docs/00blog/00prehistory/

I'll admit that didn't spend much time looking at those pages due to the text being in Russian, and I didn't bother to try translation.  You posted on an English forum, but linked to pages of Russian text.  I know it takes but a moment these days to get a computer translation, but it is in your interests to make it easier for the consumer.

You need to adjust the content for your target audience, and as suggested above grab the readers attention in the first 30 seconds or less.  Once you have their attention and if interested, then they can spend more time reading the motivation or history, and rules.

[mpp2508]

Aha!  You should have linked to pictures like these first, and you should feature them on the main page of your github.  They immediately explain the concept to me.

I slightly changed the start page on the site.

This is not something I would likely use as I have access to a good workshop with CNC, laser cutter, and have about 40 years experience with electronics prototyping.

Impressive, and what, recently you have never made any devices or prototypes from ready-made modules? A monolith right away?

[Kean]

Impressive, and what, recently you have never made any devices or prototypes from ready-made modules? A monolith right away?

Of course I make prototypes, but I usually will use parts from common evaluation kits or Sparkfun/Adafruit, as well as hand wired prototype PCBs.
If I need to mount them nicely, I will cut metal or plastic panels on my machinery.  Very easy with laser cutter or CNC mill.
I also make some simple PCBs myself, but once the design is mostly worked out I will design and order real PCBs.

[mpp2508]

Of course I make prototypes, but I usually will use parts from common evaluation kits or Sparkfun/Adafruit, as well as hand wired prototype PCBs.

Were there cases when there was no necessary module, and you made it yourself? How often does this happen?

If I need to mount them nicely, I will cut metal or plastic panels on my machinery.  Very easy with laser cutter or CNC mill.

What do you follow when you decide to assemble a monolithic prototype instead of a tangle of wires on the table? In other words, what circumstances contribute to this?
How do you connect the contacts of the modules, soldering or Dupont jumpers?

I also make some simple PCBs myself, but once the design is mostly worked out I will design and order real PCBs.

Do you mean multiple PCBs within a single prototype?
Or one PCB - one prototype? Except for cases where the final device will consist of multiple PCBs.

[Kean]

Were there cases when there was no necessary module, and you made it yourself? How often does this happen?

I don't often design my own modules, but I will quote often prototype with a ICs on generic breakout boards - like SOT23-6, MSOP, TSSOP, etc.

What do you follow when you decide to assemble a monolithic prototype instead of a tangle of wires on the table? In other words, what circumstances contribute to this?
How do you connect the contacts of the modules, soldering or Dupont jumpers?

Usually it is just a matter of quickly proving there is no obvious issues with a design before committing to the first PCB layout, but also getting a head start on firmware before the PCBs arrive.
Typically I start with grid prototype PCB with soldered components, maybe a devkit or eval PCB on 0.1" headers, and connections via point to point soldered kynar wire.
I might use "Dupont" jumper wires to connect between parts of the circuit, such as when I am expanding on an older PCB design (e.g. a recent change from ESP8266 to ESP32), or to test equipment.

Do you mean multiple PCBs within a single prototype?
Or one PCB - one prototype? Except for cases where the final device will consist of multiple PCBs.

Not sure why that is relevant, but practically all my designs involve more than one PCB.  Sometimes connected by pre-made cables, sometimes by FFC, sometimes by fixed headers.

I quickly move from one hand wired/soldered prototype, to a sample batch, to small scale production.  I run my own in-house PnP machines.  This is why your solution isn't that useful to someone like me.

[mpp2508]

I have another question: I'm continuing to work on new modules, and I sometimes have questions about their design and functionality. What section of the forum is best for asking questions about this?

[mpp2508]

While developing a module for 18650 batteries,
https://mpp2508.github.io/docs/02m/misc/mpp_18650x2/
I encountered a connector issue.
The problem with PLS connectors is that they will stick out without insulation when under voltage. With high-current batteries, this is probably not a good idea.

Using other connector types increases the number of parts needed for the prototyping system, which is undesirable.

I recently made an adapter for PLS<->QWIIC, which uses a JST SH 1.0mm connector.

https://mpp2508.github.io/docs/02m/adap/mpp_a_qwiic_pls/
I came up with the idea of ​​using the same connectors and connecting wires for battery modules and assembling batteries from them.

But these connectors only have 1 amp per pin, and apparently that's the maximum value and shouldn't be relied upon.

At the same time, the question is whether high currents might be needed.

I'd like to create a module that can be connected end-to-end to form batteries, obtain high currents, and connect a balancer.

Or decide that this functionality is unnecessary.

The question is how to do this without increasing the number of components and without overcomplicating the design.