zeroLengthContact2D element error

[yegoroff]

Hello,

I am using a zeroLengthContact2D element in my script to simulate the friction between the base of the SDoF and the soil deposit.
However, after running the script I end up with the following error:

WARNING FullGenLinLapackSolver::solve() - lapack solver failed - 1 returned
WARNING AcceleratedNewton::solveCurrentStep() -the LinearSysOfEqn failed in solve()
StaticAnalysis::analyze() - the Algorithm failed at iteration: 0 with domain at load factor 1
OpenSees > analyze failed, returned: -3 error flag

This is the section of my script, which describes the process:
----------------------------------------------------------------------------------------------------------
---Define SDoF
model BasicBuilder -ndm 2 -ndf 2

set n1 100000001
set n2 100000002
set n3 100000003

node $n1 1.0 0.0
#SDoF base node

node $n2 1.0 0.0

node $n3 1.0 1.0
#SDoF free end node

mass $n3 $M 1e-18
#mass assigned to node 3 (top of SDOF) in X direction

uniaxialMaterial Steel01 20000001 0.118623 1.949551 0.03
uniaxialMaterial Viscous 20000002 $c 1
uniaxialMaterial Parallel 20000003 20000001 20000002

element truss 80000001 $n2 $n3 1 20000003

equalDOF $n1 $n2 1 2
#move the base of SDoF together with the contact slave mode

---Define 2d contact element
set Kn 0.1
set Kt 0.1
#penalties in (m)
set mu [::tcl::mathfunc::tan [expr {$SoilFrictionAngle*($pi/180)}]]
#set friction coefficient
set Nx 0
set Ny 1

element zeroLengthContact2D 987654321 $n1 $MasterNode $Kn $Kt $mu -normal $Nx $Ny

---Analysis
system FullGeneral
test NormDispIncr 1.e-12 25 0
constraints Transformation
integrator LoadControl 1 1 1 1
algorithm KrylovNewton
numberer RCM
analysis Static

analyze 1

----------------------------------------------------------------------------------------------------------

I have read the topic http://opensees.berkeley.edu/community/ ... =2&t=54235, where a person had the same kind of problem and it seems like it is not a convergence issue, but a geometry inconsistency.
If you could point out where is the mistake and explain all the parameters of zeroLengthContact2D in a non-scientific manner I would be extremely grateful to you.