Seismosoft | Earthquake Engineering Solutions

I have problem with new version of Seismostruct v5.2.1
Sometimes with no particular reason the program stops with message:
Range Check Error

NB* Always i'm using the same data
Any idea?

I have also had "Range Check Error".

For me it will always occur when I try to edit the node restraints. I am running Windows 7 64-bit.

Antwn, Slowas,

Please send us your models, so that we may check it out.

Thanks,

Seismosoft Support

Where to send my model?

I sent my model.

Dear Slow As,

For cases like yours, where the error appears when editing the model, we overcame the problems by following one of the two following procedures:

Possible solution A
- Right-click on SeismoStruct's executable file
- Select "Properties"
- Click on the "Compatibility" tab
- Check the box "Run this program in a compatibility mode"
- Select "Windows XP (Service Pack 2)" from the drop-down menu

Possible solution B
- Open two instances of SeismoStruct
- In one of these load the model that is giving you problems
- Copy, module by module, the corresponding model data into the second running instance of SeismoStruct (thus duplicating the old model in a brand new file)

Hope the above helps,

Seismosoft Support

Dear antwn,

For cases such as yours, where the error appears when running the analysis, you may try the following:

- Settings -> Analysis -> select 'Skyline Solver' (which, even if slower, tends to be more numerically stable than its 'Frontal' counterpart)

- if your link elements possess extremely high stiffness values (e.g. 10^40), replace them with values 100-250 times larger the stiffness of the adjacent elements (more on this topic in Help System and other posts in this Forum)

Hope the above helps,

Seismosoft Support

I have problem with new version of Seismostruct v5.2.1.
When running the analysis, the program stops with message:
"Range Check Error".
We have tried to overcame the problems by following one of the previous procedures but the error always appear.
Can we send our model?
Thanks

Obviously, a "Range Check Error" is a bug, however it most commonly occurs in unstable structural models.
Have you tried to run eigenvalue analysis with the same model? Does it converge? Does it give meaningful results? (for instance a beam that is not connected to a column, can be identified with eigenvalue analysis).