Hi,
Not that I know of. I wrote this API a while back to do just that, but never found the functionnality that useful so I didnt push further...
AP
Sub Main
Dim App As femap.model
Set App = feFemap()
Dim l1 As Long
Dim grSet As femap.Set, gr As femap.Group
Set grSet =...
Hi,
Do you mean different models?
Here's what the API can do: for one FEMAP instance with multiple models/windows in it, you can retrieve all opened models. Check out Help > 3.16.1.6 feAppGetAllModels.
Then you can retrieve the models' names, put them in a droplist box so the user can select...
Hi,
Look for "NASTRAN Section1 Composites" in a web search engine. You should get MSC NASTRAN's "Introduction to composites" presentation.
Look for the failure theories. Most of them require solving a 2nd degree equation => min strength ratio is the lowest solution.
There is a trap: I think in...
Hi,
Tet10 is the default, most FEA software won't orient the user towards tet4 which are frowned upon in the mecanical world.
If you want to make sure FEMAP will build parabolic elements, when you create the property, and click on the "Elem/Porperty Type..." button ==> look at the top of the...
Hi,
You are mixing 2 things:
- the "Modify > Element > Material" command deals with elements which can be oriented at component level (i.e. at element level), so in the element NASTRAN card.
- solids are orientable through their property, not through the CHEXA card.
So you need to use Modify >...
Hi,
I'm not a layer user but here a few tips:
1) multiple groups can be displayed, starting from FEMAP v10.3 or so developpers added the "Show Multiple Groups" capacity
2) I don't get "a layer can only have one entity vs group can have as many entities". Layers have a smany entities as you...
Hi,
Yes, starting in FEMAP v10.3 (or maybe v11), in the "Select Post Processing Data" window (the "{}" button) you have the "Multiple Contour Vectors" button, which is thought out for this: plotting results on different types of elements.
Be advised though: if you select 2 vectors on the same...
Seif's answer is correct: if you're coding in .NET you need
Dim s_normal as Object
Don't dimension it.
Usually in .NET I need to add "s_normal = Nothing" in loops, prior to the function call, because once the method has been called once the object has a dimension.
Example (in Visual Studio)...
This might help, wrote it a while back. Launch it in the API window.
This macro will do the following:
1) ask you for a selection of elements you want to copy
Internally it will retrieve all nodes used by these elements
2) ask you for the original CSys
3) As you for the destination CSys...
Hi,
Your problem is that you clear the set but not the group! Think of the group as a "set of sets", or rather a double vector with a rule on one side, and a list of IDs on the other.
You never clear you group therefore the surfaces are cumulated in it.
The easiest way to do this is to re-set...
Hi,
Yes what you describe is possible. If you are a beginner with NASTRAN let's take it back a bit: there are different levels/steps when defining laminate composites in NASTRAN:
1) individual ply/core material: this uses MAT cards, up to you to choose between isotropic (MAT1), orthotropic...
What you describe can actually be done 4 ways:
- full 2D + PSHELL: derive equivalent PSHELLs for your panel properties. In the end this is what NASTRAN does anyways (with an echo = PUNCH you can retrieve the equivalent PSHELLs)
- full 2D + PCOMP: your 1rst solution
- 3D + PCOMP for laminate...
There are workarounds, depending on how you prefer your code to work.
Perhaps the trackdata object works when renumbering, I've never tested that scenario.
But the underlying concept is the same: you could use a first set with all elements for ex, then renumber, then make a second set with all...
Hello,
I'm on v11.1.1 and don't have the problem you describe. For example create a new model with only one element and run the code below. For me FEMAP returns 1 then 10000, therefore the ID has been updated.
Sub Main
Dim App As femap.model
Set App = feFemap()
Dim el As...
A little insight into (what I understand of) FEMAP's API logic: when you select entities (nodes, elements, loadcases...) you want to end up with a list of IDs, not a list of objects. That is a set! So the moethod you're thinking of is a set method, not a loadcase method. You already applied this...
To retrieve nodes in the order you select them, use a sort set:
Dim set1 As femap.SortSet
Set set1 = App.feSort
If set1.Select(FT_NODE,False,"Select nodes") = FE_CANCEL Then End
The rest of your code doesn't make much sense I'm afraid.
Your loop is closed by the "Loop" statement...
Hello,
Perhaps this will help. This create a FEMAP function (which you can then see and use in Model > Function)
AP
Const pi = 4*Atn(1)
Sub Main
Dim App As femap.model
Set App = feFemap()
'set size (ex: 10 below)
Dim freq(10) As Double, PSD(10) As Double
Dim f As...
Hey tlemonds!
Hmmm yes a few mistakes in your code:
"Dim checkoutput(26) As femap.OutputSet" won't do, you can't dimension an outputset object (or at least i don't think you can), I doubt VB6 will allow you to turn an objet into an array
Next the method you use belongs to the "femap.model"...
