Assembly-Oriented Design: Difference between revisions
Jump to navigation
Jump to search
(Created page with "<html><iframe width="560" height="315" src="https://www.youtube.com/embed/AFROcGW73j0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-w...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Robossembler: | |||
<html><iframe width="560" height="315" src="https://www.youtube.com/embed/AFROcGW73j0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html> | <html><iframe width="560" height="315" src="https://www.youtube.com/embed/AFROcGW73j0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></html> | ||
*This speaks OSE language: modular, designed for automated assembly. That is what OSE does, except we are working on a slightly different angle: producing for design-for-assembly, as we are interested in large complex devices (houses, tractors, etc). Our second step will be designing for gradual automation of build. In Robossembler, the approach is to design an automated assembler, then develop applications. At OSE, we design applications, then design the automated assembler. | |||
Revision as of 16:53, 19 May 2022
Robossembler:
- This speaks OSE language: modular, designed for automated assembly. That is what OSE does, except we are working on a slightly different angle: producing for design-for-assembly, as we are interested in large complex devices (houses, tractors, etc). Our second step will be designing for gradual automation of build. In Robossembler, the approach is to design an automated assembler, then develop applications. At OSE, we design applications, then design the automated assembler.