I guess the short answer is no, I didn't really find anything useful, besides the CST documentation for VBA objects.
Most of what I figured out was from trial and error, and using the CST help files. This is basically what I think the process is:
1. With CST, you can make macros with VBA (some programming language that I'm not too familiar with).
2. Since CST is VBA-compatible, it can be accessed from other VBA-compatible programs (excel is a common example).
3. Matlab can also handle VBA-like commands, so you can use it to control CST.
CST's help files have a entire section about VBA 'objects' available for manipulation. (They also have a section specifically about using Matlab with CST, but that section only talks about getting results from CST, not making models for CST)
The CST help files give a detailed description of all the objects and their various settings. For example, if you look up the documentation for the 'Brick' object, it gives a list of a bunch of methods used to modify a brick. At the bottom, it gives an example of how to create a 'brick' object in VBA:
Code:
With Brick
.Reset
.Name ("brick1")
.Component ("component1")
.Material ("PEC")
.Xrange (0, 2)
.Yrange (0, 3)
.Zrange (0, "a+3")
.Create
End With
compare that to the matlab brick commands I have in my original post, and that's basically I've been making CST files with matlab: I found the relevant VBA documentation in CST, and translated the CST-VBA into matlab-VBA. I found out how to do the matlab-VBA commands online and from older posts in this forum.
I've attached two files: one is the VBA code used to create a template for a planar filter (mm, GHz, ns, electric boundaries, etc). I grabbed it from the history list of a CST file that used the template.
The second file is the matlab version of the template. the 'mws' variable/object in this script is the same as the one in the original post:
Code:
cst = actxserver('CSTStudio.application');
mws = cst.invoke('NewMWS');
From comparing the two, you pretty easily see how to map VBA commands to matlab; most of the objects in the file (Units, Background, Boundary, Mesh, Solver) have documentation in the CST help files. You can also see how amazingly tedious it is to build files with all the correct simulation settings.
So that's all I have to offer. I've still having the problems mentioned in the original post, though, and would gladly accept any new information anybody has to share.