Full CAD - Revision history

Adamcolton: Adamcolton moved page CAD to Full CAD

2020-09-25T13:32:54Z

Adamcolton moved page CAD to Full CAD

← Older revision	Revision as of 13:32, 25 September 2020
(No difference)

Adamcolton: /* Boards */

2020-06-14T12:49:25Z

Boards

← Older revision		Revision as of 12:49, 14 June 2020
Line 53:		Line 53:
	Advanced feature, but there should be a way to provide some physical description of the board layout to simulate wire resistance, heat and RF.		Advanced feature, but there should be a way to provide some physical description of the board layout to simulate wire resistance, heat and RF.

	== Boards ==		=== Boards ===
	Boards lays out parts on a circuit board. I want to focus on homebrew, so breadboards, veroboard, perfboard and pcb's with toner transfer or UV. Most boards will be created from circuits, but a board can also be created directly.		Boards lays out parts on a circuit board. I want to focus on homebrew, so breadboards, veroboard, perfboard and pcb's with toner transfer or UV. Most boards will be created from circuits, but a board can also be created directly.

Line 60:		Line 60:
	After the Solids component is working, we should be able to export a board as a solid and import a package from a solid.		After the Solids component is working, we should be able to export a board as a solid and import a package from a solid.

	=== Breadboard ===		==== Breadboard ====
	Shows a picture of the breadboard with the components labeled and placed. Need a way to describe the breadboard; holes per row, pitch, rails. The router will try and minimize the number of leads needed, the number of overlapping leads and there will be an option to avoid short leads.		Shows a picture of the breadboard with the components labeled and placed. Need a way to describe the breadboard; holes per row, pitch, rails. The router will try and minimize the number of leads needed, the number of overlapping leads and there will be an option to avoid short leads.

	==== Jumper Patterns ====		===== Jumper Patterns =====
	Sort of an off the cuff idea; if we had a huge database of projects, we might be able to come up with a few jumper patterns that are common. Using some header pins and perfboard, users could make a few of these to speed up breadboarding.		Sort of an off the cuff idea; if we had a huge database of projects, we might be able to come up with a few jumper patterns that are common. Using some header pins and perfboard, users could make a few of these to speed up breadboarding.

	=== Perfboard ===		==== Perfboard ====
	Places the objects on the perfboard and lays out where wire jumpers need to go. Again, need a way to describe the board.		Places the objects on the perfboard and lays out where wire jumpers need to go. Again, need a way to describe the board.

Line 73:		Line 73:
	I'd also like a way to do "header stacks", layout multiple boards that connect with header pins (like an arduino shield), if that will simplify the board design. Needs to take into account the physical size of the components.		I'd also like a way to do "header stacks", layout multiple boards that connect with header pins (like an arduino shield), if that will simplify the board design. Needs to take into account the physical size of the components.

	=== Veroboard ===		==== Veroboard ====
	Much like perfboard. In addition, it shows where to cut.		Much like perfboard. In addition, it shows where to cut.

	=== PCB ===		==== PCB ====
	The assumption here is either toner transfer or UV transfer, but it's pretty much the same thing either way. Boards are defined as either single or double layer. Can produce silk screens for each side.		The assumption here is either toner transfer or UV transfer, but it's pretty much the same thing either way. Boards are defined as either single or double layer. Can produce silk screens for each side.

Adamcolton at 15:04, 4 September 2019

2019-09-04T15:04:24Z

← Older revision		Revision as of 15:04, 4 September 2019
Line 111:		Line 111:

	This is going to need it's own language and environment. I want the ability to show a graphic window representing the work and do work there. Set a workspace as 2d or 3d, move a cursor around.		This is going to need it's own language and environment. I want the ability to show a graphic window representing the work and do work there. Set a workspace as 2d or 3d, move a cursor around.

			== Assembly ==
			Once a model is designed, it can be broken down into components and a set of assembly steps created. This needs to be easy to do, because it's the easiest step to dismiss as not important. But it can produce very useful outputs.

			The most obvious value is that it shows how to assemble the piece. This can create a nice animation, or be broken down into something like a PDF.

			But the more valuable is that it can serve as an automated test. During assembly we can automatically check for collision. If no path can be resolved, assembly may not be possible (imagine an instruction to install a piece inside an already closed assembly). We can also simulate tools and make sure there is room for them.

	[[Category:Vulcan]]		[[Category:Vulcan]]
	[[Category:Code]]		[[Category:Code]]
	[[Category:Projects]]		[[Category:Projects]]

Adamcolton: /* Vectors */

2019-02-14T16:11:25Z

Vectors

← Older revision		Revision as of 16:11, 14 February 2019
Line 97:		Line 97:
	Box(boardThickness, w, d, h) {		Box(boardThickness, w, d, h) {
	l = rect({0,0},{boardThickness, d})		l = rect({0,0},{boardThickness, d})
	f = rect({0,0},{w,boardThickness})		f = rect({boardThickness, 0},{w-boardThickness, boardThickness})
	r = l.Add({w-boardThickness, 0})		r = l.Add({w-boardThickness, 0})
	b = f.Add({0, d-boardThickness})		b = f.Add({0, d-boardThickness})
Line 110:		Line 110:
	I'm also kind of thinking that variables will be stored and can be read. So you could grab the l rect and use that.		I'm also kind of thinking that variables will be stored and can be read. So you could grab the l rect and use that.

			This is going to need it's own language and environment. I want the ability to show a graphic window representing the work and do work there. Set a workspace as 2d or 3d, move a cursor around.

	[[Category:Vulcan]]		[[Category:Vulcan]]
	[[Category:Code]]		[[Category:Code]]
	[[Category:Projects]]		[[Category:Projects]]

Adamcolton: /* Vectors */

2019-02-14T16:03:50Z

Vectors

← Older revision		Revision as of 16:03, 14 February 2019
Line 85:		Line 85:

	== Vectors ==		== Vectors ==
	~~Describes points on plane and Bezier curves defined by those paths. The points can be described absolutely or using functions to reference each other~~.
			=== 2D ===
			Package for 2D primitives.

	=== Shapes ===		=== Shapes ===
	~~Describes a~~ 3D ~~shape~~, I ~~should~~ be ~~able to~~ use ~~the Canvas native 3D support to do this~~.		Package for 3D primitives.

			=== Parametric ===
			Uses parameters to build up contextual scenes.

			Box(boardThickness, w, d, h) {
			l = rect({0,0},{boardThickness, d})
			f = rect({0,0},{w,boardThickness})
			r = l.Add({w-boardThickness, 0})
			b = f.Add({0, d-boardThickness})
			e = {0,0,h}
			Insert(Extrude(XYPlane, e, l, f, r, b)...)
			}

			where
			Extrude( s Surface3, extrusion V3, shapes... Surface2) []Solid
			Insert( SceneElement )

			I'm also kind of thinking that variables will be stored and can be read. So you could grab the l rect and use that.

	~~Shapes can be defined using vectors. All sort of interesting ways to extrude or intersect.~~

	[[Category:Vulcan]]		[[Category:Vulcan]]
	[[Category:Code]]		[[Category:Code]]
	[[Category:Projects]]		[[Category:Projects]]

Adamcolton: /* Shapes */

2019-02-14T15:39:08Z

Shapes

← Older revision		Revision as of 15:39, 14 February 2019
Line 87:		Line 87:
	Describes points on plane and Bezier curves defined by those paths. The points can be described absolutely or using functions to reference each other.		Describes points on plane and Bezier curves defined by those paths. The points can be described absolutely or using functions to reference each other.

	== Shapes ==		=== Shapes ===
	Describes a 3D shape, I should be able to use the Canvas native 3D support to do this.		Describes a 3D shape, I should be able to use the Canvas native 3D support to do this.

Adamcolton: /* Core Tools */

2019-02-14T15:38:47Z

Core Tools

← Older revision		Revision as of 15:38, 14 February 2019
Line 11:		Line 11:

	; Vectors		; Vectors
	: ~~Describes Bezier curves on a plane~~		: A purely mathematical model of geometry. Handles both 2d and 3d

	~~; Solids~~
	~~: Builds solid shapes~~

	; Link		; Link

Adamcolton at 15:34, 23 August 2018

2018-08-23T15:34:50Z

← Older revision		Revision as of 15:34, 23 August 2018
Line 95:		Line 95:
	Shapes can be defined using vectors. All sort of interesting ways to extrude or intersect.		Shapes can be defined using vectors. All sort of interesting ways to extrude or intersect.

	[[Category:~~Cobl~~]]		[[Category:Vulcan]]
			[[Category:Code]]
			[[Category:Projects]]

Adamcolton at 15:28, 31 July 2018

2018-07-31T15:28:44Z

← Older revision		Revision as of 15:28, 31 July 2018
Line 1:		Line 1:
	~~A suite of CAD/CAM tools designed to work together and with the Cobl Workshop.~~

	== Core Tools ==		== Core Tools ==

Adamcolton: Adamcolton moved page Cobl Suite to CAD

2018-07-31T15:28:32Z

Adamcolton moved page Cobl Suite to CAD

← Older revision	Revision as of 15:28, 31 July 2018
(No difference)