continuing off of last post...
what would be needed to accurately compute things?
---rotation ? or rather degrees of rotation?
---length measurement of course.
---center of each hole (were a pin would go) or rather make that center of the hinge point.
*rubs chin* how do you go back and forth between hyd cylinders....
i suppose loops within loops within loops, or rather, for each cylinder, the computer puts in, a "loop" would be done.
---FOR EACH (X, in Y_cylinders, step Z <= Y_cylinders_max_extending)
-----call function
-----another loop...
-------call function
-------another loop...
the functions. are going to need to go through each extending and contracting of each cylinder in say increments of 1/64" of an inch.
if i keep following this path of thought, it could take a long time for a heavy duty server to go through enough variations to get something back... that could even be useable...
there needs to be a way for computer to "track" lengths of bars / cylinders and were they connect... yikes... feel sorry for database.
--perhaps incrementing a number.
--but still the database would get large. even with using a secondary table. just to hold data for tracking, and another table for things that pass.
there needs to be a way to limit how many "solid bars" and how many "cylinders", and how many points of connections (pins / hinge points) just to reduce and stop a non ending loop...
also there needs to be a way to limit how close (pin / hinge / pivot) point happens to another. or less on same x,y axis plot point.
---solid bars, and then simply Teeing off up off of bar for a cylinder attachment point... (off set amount) yikes..
---i suppose you could limit solid bars extending off of other solid bars via only in perpendicular notation at fixing the point so they do not hinge / pivot.
---then placing some sort of variable / constant by user. of how many perpendicular bars could be done. guessing 3, times, maybe up to 5 times max.
===============
there would need to be limiting boundaries for implement.... so implement side (furthest away from SSTT)) does not bend down, when it is being folded to transport mode. so it does not "tip" the SSTT over
the "box shape" of an implement would not be allowed to go into the transport wheel areas. along with under the transport wheels.
--but linkages (solid bars and cylinders could go through wheels)
--so looking at perhaps a secondary layer per say. for boundary points. i should say collision points.
===============
===============
===============
===============
===============
min/max length
--solid bars ======= solid metal bar. Like lower link arms on a 3pt hitch.
--cylinders ======= hydraulic cylinder
--rod of cylinders ======= a rod only extends / contracts so far. These settings give the space needed for seals, and spots for hyd hose hook ups, and like
--rod length ======= this is how far a ROD is extended (beyond the contracting / extending) that is taking into account with cylinder.
--implement connection 1 ======= distance a solid bar can come off the implement for a hinged point
--implement connection 2 ======= second connection point.
--implement connection 1 ======= how far back on implement connection can be
--implement connection 2 ======= second connection point.
min/max (how many)
--connecting points ======= how many (hinged / pivot / pins) can there be
--cylinders ======= how many cylinders can be used
--straight solid bars ======= how many straight solid bars that there can be.
--off set solid bars ======= how many times a perpendicular solid bar can come off another straight solid bar.
increments for lengths for the next "LOOP" irritation
--solid bars
--cylinders
--off set solid bars
--rod length
increments +/- for computer to extending or contracting a cylinder during each loop.
x,y plot points
--fixed position x,y plot points ======= hinged / pivot points that solid bars, or cylinders or rods connect to. but points never move ((think of them as points connected directly to frame of the SSTT))
--dynamic position x,y plot points ======= for connection points between cylinders, rods, solid bars. that change based on movement of a hyd cylinder
--4 sets of X,Y plot points. --transport wheels ======= just treat them as a box shape, area were implement can never move into.
--4 sets of X,Y plot points. --transport wheels, (opposite side)
--4 sets of X,Y plot points. physical boundry limits of everything. ======= total height, total width. that anything can move within
--4 sets of X,Y plot points. linkages going below "axles" of tires. ======= exception... once linkages get past out side edge of wheels
--4 sets of X,Y plot points. location of implement when "unfolded" and down on the ground.
--4 sets of X,Y plot points. location of implement when "folded up" and ready for transport down the road.
--4 sets of X,Y plot points, that linkages (solid bars, cylinders, rods,) need to be within, when implement is fully folded up ready for transport mode.
--4 sets of X,Y plot points. dimensions of implement. ((assume top X,Y points = top frame of an implement))
boundary laws / conditions
--implement can never go into area of were wheels are.
--implements can never go past the physical over all boundaries (max/min height, min/max width)
--same goes for solid bars and cylinders.
--no solid bars, or cylinders can extend into an implement but may attach to implement
--no solid bars or cylinders, can extend below wheel axles with exception of being past outside edge of wheels.
--no solid bars or cylinders, can have fixed connection point (think connection point to frame of SSTT) below wheel axles.
pass/fail laws / conditions.
--an implement must fully fold and unfold, then fold backup again, then unfold one more time. without changing anything beyond extending / contracting cylinders.
--folding/unfolding all boundary laws/ conditions are taken into account.
pass/fail database
--record lengths, and X,Y plot points. for each solid bar, off set perpendicular bar, cylinder, rod. fixed connection points. and implement connection points.
--if it fails, nothing gets recorded to database.
saving/pausing/stopping/resume/loading program database
--just holds incremental numbers of everything? every time or perhaps after so many irritations. database records get updated?
--on resume, inserting code to load a specific setup of X,Y coordinates, and lengths, etc... for preset doings someone came up with?
=========
posting before i loose stuff.