Hi James
I have looked at your model and found a bug in it.
When i tried to run the kinematic analysis it tells that the model
is kinematically overconstrained with two dofs.
I checked in the JointAndDrivers.any file and found that the neck is
driven with all three rotations. This is not possible since the neck
joint is a revolute joint. So i removed all of them except the
flexion.
In general for a running model then when you add a driver to the
model you should always also remove a driver, to keep balance in the
DOF count.
However this was still not enough to make the model run
kinematically, i have found that if the rotation around y is above
90 deg then the model do not run, please jsut try to lower the
rotations around y. This is because the initial position of the
pelvis is calculated differently than the way it is driven in the
JointsAndDriver.any file, please have a look in the
InitialPosition.any file also for the details. For some reason which
it turns out that for a y angle larger than -90 the starting guess
is not a good one.
So please try to reduce this angle and keep it below this value.
Alternatively you can turn the global reference system around.
By setting the KinematicTol=5 it means that the kinematic error is
allowed to be 5m. So when you try to solve the kinemtatics it
already is solved because the error toleranceon the kinemtatics is
so high, this is why it do not move. So in general it should be
left as the default value.
I hope this helps you to move on, oherwise please ask again.
Best regards
Søren, AnyBody Support
— In anyscript@yahoogroups.com, “jamesshippen” <jamesshippen@…>
wrote:
>
> Hi
>
> With no kinematic tolerance specificed (presumably defaulting to
1e-
> 6?) the final kinematic erro was 4.17. I therefore specified a
> tolerance of 5.
>
> The kinematicAnalysis then reported that all of the steps had been
> completed however there was no segmental motion displayed in the
> Model View; also the high speed with which the model executed
> suggested that no processing was being performed.
>
> I have uploaded the files to shippen_no_movement.zip.
>
> Thanks
>
> James
>
>
> In anyscript@yahoogroups.com, “AnyBody Support” <support@> wrote:
> >
> > Hi James
> >
> > Yes… the answer was for you;-)
> > I am not sure what you mean?
> >
> > Best regards
> > Christian, AnyBody Support
> >
> > — In anyscript@yahoogroups.com, “jamesshippen” <jamesshippen@>
> wrote:
> > >
> > > Hi Christian (and Robin)
> > >
> > > I think the reply was directed at me at the suggestion
certainly
> had
> > > an affect on my model.
> > >
> > > By introducting a kinematic tolerance of slightly greater than
> > > reported in the error message, no further errors were
reported,
> > > however nor was there any movement of the figure during
> > > kinematicAnalysis.
> > >
> > > The plot thickens! All suggestions appreciated.
> > >
> > > Ta!
> > >
> > > James
> > >
> > > — In anyscript@yahoogroups.com, “AnyBody Support” <support@>
> > > wrote:
> > > >
> > > > Hi Robin
> > > >
> > > > I get the error:
> > > > ERROR(OBJ.MCH.KIN2) :
> > > >
> > >
>
H:\Dokumenter\2b\AnyBody\ARep\Aalborg\FreePostureTrial\FreePostureMov
e
> > > .Main.any(80)
> > > > : ‘Study’ : Model is kinematically over-constrained :
> Position
> > > > analysis failed : 2 unsolvable constraint(s) found
> > > >
> > > > when I run your model.
> > > > The one you get, sounds like one you can remove by putting a
> > > > KinematicTol into the study. The error you describes comes
> because
> > > > there, for some reason is some kinematic problems, as far as
I
> > > remember.
> > > >
> > > > Best regards
> > > > Christian, AnyBody Support
> > > >
> > > > — In anyscript@yahoogroups.com, “jamesshippen”
> <jamesshippen@>
> > > wrote:
> > > > >
> > > > > Hi
> > > > >
> > > > > I have attempted to use MoCap data to drive
FreePostureMove.
> The
> > > > > ARep files are in the uploaded file
> shippen_FreePostureTtrial.zip.
> > > > >
> > > > > The only modification I have made to the BRep is to
replace
> the
> > > > > revolute joint between the neck and skull with a
sphereical
> one
> > > (and
> > > > > the appropriate drivers). This modification seems to have
> been
> > > > > sucessful.
> > > > >
> > > > > However when I use the MoCap data I receive many error
> messages
> > > of
> > > > > the type:
> > > > >
> > > > > …
> > > > > Constraint no. 191 above error tolerance 0.000001, error =
> > > 0.000002. -
> > > > > constr. #1
> > > > >
> > >
> in ‘Main.Model.ModelEnvironmentConnection.Drivers.AnkleDriverRight’
> > > > > Constraint no. 192 above error tolerance 0.000001, error =
> > > 0.000005. -
> > > > > constr. #0
> > > > >
> in ‘Main.Model.ModelEnvironmentConnection.Drivers.HipDriverLeft’
> > > > > Constraint no. 194 above error tolerance 0.000001, error =
> > > 0.000006. -
> > > > > constr. #2
> > > > >
> in ‘Main.Model.ModelEnvironmentConnection.Drivers.HipDriverLeft’
> > > > > Constraint no. 196 above error tolerance 0.000001, error =
> > > 0.000005. -
> > > > > constr. #0
> > > > >
> in ‘Main.Model.ModelEnvironmentConnection.Drivers.AnkleDriverLeft’
> > > > > ERROR(OBJ.MCH.KIN3) : C:\research\Repository.6
\Repository.6
> > > > > \ARep\Aalborg\FreePostureTrial\FreePostureMove.Main.any
> > > > > (80) : ‘Study’ : Kinematic analysis failed in time
step 0
> > > > >
> > > > > Does that mean anything to you?
> > > > >
> > > > > Thanks
> > > > >
> > > > > James Shippen
> > > > >
> > > >
> > >
> >
>
