News: Contact us to upgrade your software!

Recent Posts

Pages: [1] 2 3 ... 10
Miscellaneous Analysis & Methods / Analysis Defaults
« Last post by alan.mclaughlin on March 15, 2019, 09:46:28 AM »

I've been going through the list of analysis defaults having a look at the documentation and i'm struggling to find some info on what checks hypersizer is making for:-

Buckling, Local

Local Buckling, Shear, Permanent Deformation (Metalic)


Web Normal Compression or Pull off
Web Shear
Web Interaction


Compostie Strength, Interlaminar Shear

If possible can you point me the relevant areas of the documentation?


Hi Brent

The reference plane options are all blanked out apart from the top face mid-plane, so I unable control the reference plane of the BAR element.  This might be because I using stringer segments to discretely model a machined stiffened panel.

So is there anyway to change the reference plane of the BARs for a stringer segment?
Hi Gawain,

We recommend to set the stiffener component reference plane to centroid in the sizing form, options tab. When HyperSizer updates the FEM, the bar element offsets are removed. Furthermore, the FEM moments will be consistent with the grid stiffened analysis assumptions.

See the following help topic:



I'm using the grid stiffened plugin to discretely analysis a panel, and I'm trying to use HyperFEA to size the whole panel for a given frequency.

The issue I'm having is that the panel is a double sided machining and therefore the FEM will not contain the correct BAR offsets when doing the SOL 103 frequency check within HyperFEA. i.e The updated FEM is still treated as a single sided machining when doing the SOL 103 check. Therefore when I'm using HyperFEA to optimise the whole discretely modelled panel for a given frequency, then the final frequency is incorrect once I've remove the BAR offsets.

Is there anyway within the HyperFEA process, for it to ignore the BAR offsets when doing the SOL 103 frequency check?
Thanks James

I'm managed to resolve the issue by moving the workgroup file from the C: Drive to my D: Drive.  So I'm assuming it was a permissions issues, however when I has version 7.3.37, it was in the same C: Drive folder.  So not sure why it was an issue for 7.3.68.

Anyway, it's working so thanks.
Do you have a VBA script running on the same database?
Is your workgroup file on a shared drive or saved local?

Just installed version 7.3.68 from 7.3.37, and when I try to update an old file to the new version, I get this message below:

Cannot start your application. The workgroup information file is missing or opened exclusively by another user.ÀSystem.Runtime.InteropServices.COMException (0x800A0BD4)

I check in the preferences and Hypersizer is pointing to a Workgroup file, so I not too sure what is going on.  Any ideas?
Scripting / Re: Error getting access to a component's AnalysisSelections
« Last post by danvic on February 28, 2019, 12:58:50 PM »
Unfortunately I had to use variable linking (by associating multiple components to a single group id), since a shared stringer spacing is required in this project.

Thanks for pointing that this could be the issue - I'll see what I can do and open a ticket if necessary (providing a more detailed code and database).

Scripting / Re: Error getting access to a component's AnalysisSelections
« Last post by August on February 28, 2019, 12:31:18 PM »

I was not able to replicate the issue you're having. Hard to say what the exact cause is from your code snippet, but it seems like something could be going wrong in the component or group setup.

I recommend to avoid assigning multiple components to groups unless absolutely necessary. By default, HyperSizer creates 1 group per component. Usually the only reason to deviate from this pattern is if you are doing variable linking between components.

So instead of assigning the components to a group, use the Component.GroupID property to get the group corresponding to that component, and then do your group modifications.

Here is a snippet of code where I successfully pulled the AnalysisSelections from the component.

If you're still having trouble, perhaps we could take a look at your full VBA code and database.

Code: [Select]
' Get project object
Set oProject = oHS.Projects.GetProject("Test Project")

' Get the component
Dim comp As HyperSizer.Component
Dim selections As HyperSizer.AnalysisSelectionCol
Set comp = oProject.Components.GetComponent(2)

' Get the group
Dim group As
Set group = oProject.Groups.GetGroup(comp.GroupId)

' Set the concept
Dim bpcBeamPanelConceptList(0 To 0) As HyperSizer.BeamPanelConcept
bpcBeamPanelConceptList(0) = 23 'bpcZBonded
Call group.setConcepts(bpcBeamPanelConceptList())

' Get the analysis selections
Set selections = comp.AnalysisSelections
Scripting / Error getting access to a component's AnalysisSelections
« Last post by danvic on February 28, 2019, 11:41:53 AM »


I'm trying to add code to access a component's analysisSelections object and update the buckling criteria for one of its objects (an open span for instance). The whole process to assign the single bpcZBonded concept to an assembly and its group is verified to work opening the Hypersizer GUI.

The error mentions family 4 (bpfUniaxialStiffenedPanelFamily) and a BeamPanelConcept 21 (bpcIBonded) that is not the assigned concept.

Here is a VBA pseudo-code for what I've been doing:

Code: [Select]
Dim bpcBeamPanelConceptList(0 To 0) As HyperSizer.BeamPanelConcept
bpcBeamPanelConceptList(0) = 23 'bpcZBonded
Call objGroup.setConcepts(bpcBeamPanelConceptList())
Call objGroup.SetGroupMembership(lngComponentIds)
' (assign lngComponentIds to assembly using objAssembly.ComponentIds.Add (not shown)
Dim selections As HyperSizer.AnalysisSelectionCol
Dim selection As HyperSizer.analysisSelection
Set objComponent = objProject.components.GetComponent(lngComponentId)
'lngComponentId is part of lngComponentIds
Set selections = objComponent.AnalysisSelections

The last line of code above generates the error.

Does anyone know what I could be doing wrong? Any reference to a working VBA code doing something similar would help. The sample python code from the documentation is the one I'm adapting to VBA here.

Pages: [1] 2 3 ... 10