MatrixFrame version 5.3 SP6 - Release notes Bug fixes · An incorrect lateral buckling curve was used if a castellated beam was used from the castellated ... In the module “ending

1 / 45

Matrix Software | Wijchenseweg 116 | 6538 SX Nijmegen (t) 024-3434380 | (f) 024-3434389 | [email protected] | www.matrix-software.nl

MatrixFrame version 5.3 SP6 - Release notes

Incorporated in version 5.3 (December 2017):

Bug fixes:

MatrixFrame® General:

For the problem with Windows 10 version 1709 (Fall Creators Update), what caused MatrixFrame to work slower, a temporary “Hot Fix” is made. If during startup from MatrixFrame, Windows 10 version 1709 build 16299.** is detected a key will be placed in registry. “HKEY_CURRENT_USER\Software\Matrix Software\MatrixFrame\5.30\ "W10_1709_fix" “with value “1”. This key will activate the “Hot fix”. This solution will not return MatrixFrame to previous speed, but makes MatrixFrame workable again. If Microsoft has solved the problem, the value of the key can be set to "0", which will disable the "Hot Fix".

End release note SP6


Incorporated in version 5.3 (September 2017):

Bug fixes:

MatrixFrame® Toolbox:

In the report from the module “Cross Calculation M+N” on the place from the Mz value the My was printed. The calculation was done correct.

Occasional the Mu was calculated to low for a column with concrete C30/37.

MatrixTools Geo:

In the "Spread Foundation" module, a number of situations have shown that an excavation on the left

side of the foundation strip has not been properly processed. In these cases, a partial pressure has

been calculated, as if there were a part of the soul present.


2 / 45



Incorporated in version 5.3 (July 2017):

Bug fixes:


The section properties for IFB-A and IFB-B were not accurately calculated. (Deviation of a few percent

for Iy)

The option “Merge load case” was not working anymore. The load cases to be merged were removed.

If the option for loads “Color by direction” was activated the color from “Visibility options” for selected loads was not used anymore but was hard coded RGB (128, 0, 0). Now the “Visibility options” color is used again.

Reports:

If there were multiple MatrixTools “Cross calculations M+V+T” modules, they were no longer displayed in the "Available Items" in Report Settings.

Loads generator NEN-EN:

When wind was generated, for a symmetrical Duo pitch roof with a flat roof part in the middle, the wind from left and right was not equal.

Mu2=0 f was calculated for a Multi-span roof with an angle of 60°. The reason for this is that in the NEN-EN 1991-1-3 in Table 5.2 there is no Mu2 given for an angle> = 60 °. In addition, NEN-EN 1991-1-3 # 5.3.4 (4) states that special attention should be paid to the snow load coefficients for Multi-span roofs, where one or both sides of the roof are at an angle greater than 60 °. At the load generator, a Mu2 = 1.6 is always used for an angle> = 60 °.

1D Beam:

In the steel control of a beam over several support, with on the support a section change, was wrongly calculated with 1 equivalent section for all fields.

2D Frame:

It was not possible to open in 5.3 models from 5.2 were a Bolted-splice joint was defined with a tapered section.

3D Frame:

If grid lines were very close to each other (0.080m.), Snap to the grid did not always work. The snap function has been adapted for this.

2D Grillage:

When a support was placed on ¼, ½ or ¾ of the length of the beam the notification Q, H and 3Q were used instead of the position in meter. This automatic ascription is now disabled and a distance will always be filled in. However, the use of Q, H and 3Q remains possible in the tables.

3 / 45


Strange moments were displayed when a GNL analysis was done when loads were defined longer then the beam length.

Several problems have been solved for import RTF.

For a beam with releases, which is divided into, for example, 7a, 7b and 7c, the stirrups were not correct in bar placement. The coverage line was lower than the shear force line.

For a beam with releases the shear force line was dotted and the shear force values were not displayed.

FEM:

For a 2-D Wall the “Temperature deflection load”was set in the wrong direction Z’. This should be Y’r.

Concrete check:

In the pictures from the cross check the values for “Asreq.” and “Asprov.” were not always shown.

Steel check:

If the "Unity check label" and "Unity check value" layers were turned of in the "Visibility Settings" of the "Code check", the label was still displayed.

An incorrect lateral buckling curve was used if a castellated beam was used from the castellated section database. As a result, the UC for lateral buckling was unfavorable.

Steel Joint connections:

If in a “Beam-Column” connection the column was defined as RHS section the drawing was showing a HE section.

In the case of a license for “Column-endplate” connections, the "Beam-Cross girder" connection was not activated.

Occasional MatrixFrame crashed when a report was printed with a joint connection in it.

MatrixTools Geo:

In the module “Bending moment in pile” the As_required was too big for a pure tension pile.

In the module “Bending moment in pile” the results were not show if the print buttons above the

document were used.


4 / 45



Incorporated in version 5.3 (June 2017):

New:

MatrixFrame & Revit:

Tabel toegevoegd met mogelijkheid tot:

Author registration (= constructor), scheduled and spent hours, status

Link with MatrixFrame, either directly, or by generating an XML file that can then be read in MatrixFrame

Generating a MatrixFrame report, as well as constructive drawing of nodes, beams & supports.

Currently, MatrixTools calculations are being added to the Project Manager list.

Ps. The way back from MatrixFrame to Revit (including UC's, MxF generated report (PDF), results for generating

report including loads, forces & code check) is realized in MatrixFrame 5.4 (thus no longer in MxF5.3)

5 / 45


Bug fixes:


Occasional MatrixFrame crashed in "Visualization of F-Euler Analysis" in a large 3D model.

A triangle load caused a warning about “Geometric unstable model” when the “Mass” combinations

were calculated.

For a beam with several fields, with loads from one floor (level 1) and “Roof not accessible” (level 2),

incorrectly, no combination was created with all fields fully loaded.

In calculation sheet loads, when selecting a dead load the program started wrongly with index Pp2.

Occasionally changing a load in the table caused MatrixFrame to crash.

In the settings for steel and timber the button “Apply” was not activated and the button “Reset” had no effect.

Reports:

In envelope results the measurement lines for the moment zero points from top and bottom where swapped.

The color bar was not printed in the pictures from the stresses.

1D Beam:

With a steel beam, with several sections, releases and supports, the field were incorrect detected and therefore the steel check was not done.

3D Frame:

Elastic foundation with tension elimination is not working for rotated sections. A message has been build in that this is not supported.

2D Grillage:

A beam that had multiple sections was wrongly divided in for example 3a and 3b. Because of this occasionally the stirrups were incorrect handled in bar placement.

It was possible in “Support optimization” to place a pile outside the beam. The calculation was done with the support placed on the begin or end of the beam. Now if a support is placed outside it’s automatically set to begin or end.

MatrixFrame could crash if user was moving supports in the grid of “Support optimization”. This was caused if another cell was clicked too fast while the calculation was still active. Now the cells will be deactivated as long as the calculation is active.

On import from a RTF with spring supports different values were filled in for ULS and SLS. For ULS the value from TRF (for example 6000) was used and for SLS the value 100000e+103. This caused not expected moment lines in the SLS combinations.

On printing “Loads Cases Each Beam (incl. pic.)” the loads were not always scaled correct. Therefore loads were drawn outside on the top of the picture.

FEM:

Manually adding grid Lines in tab loads was not working. Now grid lines can be filled in if the layer : Loads (show all)” is turned on under “Grid lines and dimension lines”.

When a new load was placed (area, poly line, point) in a new load case the next load was placed in again a new load case. This was caused by the empty dropdown from the load case description.

6 / 45


Occasional MatrixFrame was crashing if “Undo” was used after placing some loads.

For a “2D Wall” the calculation of Asreq;Sx en Asreq;Sy was incorrect. The values were to large.

The supports were not renumbered when “Whole structure” was chosen.

The grid with “As;req” was not updated if the local reinforcement direction was changed.

Concrete check:

When a GNL “Wall calculation” was done the report was incorrectly showing buckling length system information “User”.

On a wall calculation with reinforcement type “Not reinforced” was not always the decisive cut shown.

Steel check:

Occasionally the changing of a load case type was affecting the lateral buckling check. This was caused by handling the wrong table for determining the C1 and C2 parameters.

Incorrectly all cross checks were done with reduced properties form section class 3 if for the cross check section class 4 was detected.

Occasionally the lateral buckling and buckling check were turned off when a grid line or section was changed.

The lateral buckling check was occasionally different when a LE analysis was done with or without “F-Euler analysis”. This was caused by handling the wrong table for determining the C1 and C2 parameters

After user has changed sections in “UC Chart” and he gets the message “Do you want to perform analysis with changed section properties (OK) or Cancel changed sections?” MatrixFrame was crashing if “Cancel” was chosen.

Occasionally an asymmetrical buckling length was calculated for a symmetrical structure with combined structural members.


Column base plate o Occasionally the calculations were not performed when a was copied. Problem was caused by

incorrect bolt quality during copy. o In the calculation of the anchoring the “c;d” from "NEN-EN 1992-1-1 Figure 8.3" was

incorrectly determined. For “a” the h.o.h. distance was used instead of the distance between the anchors.

o It was not clear for everyone that by clicking on the button the concrete dimensions could be filled in to calculate (Ac1/Ac0)^0.5. This button has now been replaced by new button with the text “Concrete dimensions”.

o The anchor proposal was working incorrect.

With a “Beam Cross girder” connection with the beam on the web of the cross girder the check for bolt bearing for the cross girder was not done.

In the reports the labels and signs of the beams were not always correct. The calculations were done correct.

For a tube connection it was not possible to rotate the RHS beam 90°.

It was incorrectly possible to select a “Castellated beam”.

When a stability connection from 5.2 was opened the sign of the load was wrong.


Concrete: o Module “Cross calculation M+V+T”:

7 / 45


The cracking width "W;k" was incorrectly calculate because the limit of "sr; max" (the largest value of (50 - 0.8 fck) Ø and 15Ø) was incorrectly processed. As a result, the "W; k" was too favorable.

In the output was wrongly printed "VEd: 25.00 <= 23.88 kN NEN-EN1992-1-1 # 6.2.2 Not Ok" if no transverse reinforcement was required.

For a floor with “nets” where no shear reinforcement was applied was incorrectly "As;toe. = 335" printed in the report.

o Module “Cross calculation M+N”: Matrix was crashing if user defined a own concrete quality in the product table. (for

example: C20/25 pile) o The modules "Column for insolated frame" and "Column + Fire" were tested for walls at a

minimum thickness of 120 mm in accordance with NEN-EN 1992-1-1 # 9.6.1 (2). Here has now also been added the minimum thickness of 100 mm when applying a single reinforcement net.

o The module "Cross-section M + N" has now also added the construction typesetting of "Column" or "Wall" so that the correct check on size can be performed.

o In the module “Cross calculation Mu capacity” were no results shown if a tension force was filled in.

o In the module “Cross calculation Vu capacity” was the calculation from “As;req.” for a double stirrup incorrect. Therefore the "V;Rd;s" was too low.

o MatrixTools was sometimes crashing in the module “Punching calculation” when values were changed like distance to column edge or reinforcement net.

In the module “Timber beams” was occasionally after new installation the “Design working life” set to 25 years. Now default 50 years will be set and for the “Reliability Class” RC2 will be set.

MatrixTools Geo:

In the module “Bending moment in pile” it was occasionally not possible to calculate the

reinforcement. This was related to the license composition.

Occasionally the positive friction was not taken into account for a user defined pile system.

For a steel pile “Constant cross dimension; tube pile with closed base” the thickness for the base plate

is not needed anymore. The reason is that this has no influence on calculation from the Bèta factor.

Explanation has been added to the help.

For a “Concrete Shaped in soil with smooth tube pile on screw base, in which concrete is pressed to

soil directly” the positive friction was not taken into account.

After checking it was not possible to uncheck the check box for a user defined pile system.


8 / 45



Incorporated in version 5.3 (March 2017):

New:

MatrixTools Geo:

When for a new defined pile the same specification is used an index will be added.

The headers for pile systems are now showing tooltips with references to the code.

Bug fixes:


The "Undo" and "Redo" function was not always correct working with loads.

The predefined spring values were not set to 50,000 but to 500,000e02.

Reports:

The scaling of the pictures was incorrect and also to much empty space around the picture was

generated.

The begin distance for a concentrated load on a beam was not printed in the report.

In the reinforcement pictures from bar placement the mm2 were occasionally shown.

Occasionally shear force values were printed in the report for strips were no shear force

reinforcement was needed.

If a model from 5.2 was opened the “Picture options” for “Shear force“ the size and digits were not

correct imported.

Occasionally reinforcement was printed for not reinforced walls.


On determination of wind pressure on “Z” was for “b” the average width used instead of the building

width. As a result, were for small average width values different “Z” values generated.

For a roof “Category K” the concentrated loads for the helicopter categories were not shown.

1D Beam:

When a section was added with an angle of 90° the table was not updated. Calculation were done

correct.

For measurement lines on top the offset was not working correct.

2D Grillage:

In case of import "RTF" were occasional extra "empty" load cases generated.

9 / 45


In case of importing a "RTF", in which the beams were attached to grid lines, the geometry has not

been imported.

Occasional were supports which were put at the end of the beam colored red in the table.

FEM:

Plate definition was not correctly refreshed if “Undo” and “Redo” was used.

Concrete check:

Occasionally a concrete column with tension was giving an error message for the reinforcement. The

equilibrium calculation has been changed for this.

Steel check:

For a combined member with different sections the lateral buckling calculation was made to be to

favorable.

The option in steel design for each member was not working correct.

A castellated beam in section class 2 was wrongly calculated plastically.


Occasionally if a thickness of was changed for the end plate this was not changed in the reports.

For a column base plate calculation occasionally the UC changed from an existing load case if a new

load case was defined.

Occasionally the results from a column base plate were not printed.

MatrixFrame was placed “On Top” when the button in MatrixTools was pressed to activate

MatrixFrame. Therefore user had to minimize MatrixFrame to work in for example a Word document.


In the module “ET Steel” with a column calculation the “psi” value was wrongly calculated if the

moments on begin and end where having a different sign. Therefore the UC was to unfavorable.

MatrixTools Geo:

Tension pile:

o Occasionally the wrong name was shown in the tab results. The values were correct.

o In the tab "Results" the checks from the “Average results” were shown.



10 / 45


Incorporated in version 5.3 (February 2017):

New:

MatrixFrame® General

On renumber the whole structure the grid lines will be only regenerated if the button “Generate grid

lines” is active.

The SFB database has been extended with HE260B and HE260M.

If grid lines were filled in by user and the button “Generate grid lines” was active all grid lines were

deleted after drawing the first beam. The grid function has been extended with by Matrix generated

grid lines (blue text) and by user defined grid lines (black text). This means that user defined grid lines

will not be deleted if the button “Generate grid lines” is active. With the button “Delete” all by Matrix

generated as well as by user defined grid lines will be deleted.

MatrixFrame & Revit

Revit 2017 is also supported.

Toolbar for MatrixFrame in Revit

Concrete check:

If for the stirrups a double stirrup (2R8-300) is filled while only one bracket (R8-300) is needed, there

was still shown a single bracket in the dropdown list of the "Basic" and "Total" no dropdown list was

displayed. The drop-down lists for "Basic" and "Total" are now adapted to the filled in stirrups.

MatrixTools Geo:

On starting the CPT screen digitizer the select mode is now default “Cone”.

Bug fixes:


Several problems and Crashes under Windows 10 have been resolved.

MatrixFrame was crashing on import RTF.

The member color by section where incorrect shown.

Occasional the grid line references were incorrectly generated. As a result, was in making of an

additional grid line the structure deformed.

It was no longer possible to delete or change an index in the “Loads calculations”.

A shear force was wrongly shown in a cable when a concentrated was used.

“Out of Memory” and “RTE” where shown if a big amount of loads where copied to new load cases.

11 / 45


When renumbering the “Whole structure” the labels from the loads were not sorted in order.

If multiple sessions MatrixFrame were active, it could happen that a 2D Plate that was saved was

opened at the opening in 2D Frame.

After import from a DXF the structure was occasionally distorted after pushing “Run modification”.

If a cut was generated from the “Spy function” in the toolbox the beam number and position were not

displayed.

When assigning a release, which is already present in the model, a new connection was getting

generated. Now, the already existing connection is used.

Selecting begin or end of the beam for adding a release was not working correct.

Not all loads were copied when load case table was imploded.

Reports:

In 2D Grillage the arrowheads from the concentrated loads were scaled to large.

When printing “Loads Calculations” the lines were printed in the wrong order from bottom to top.

On export to Word the item “Concrete cross section (compr.)” an error message occurred “The string

is not numeric”.

In the reinforcement pictures the geometry was not drawn. So nodes, releases, supports and beam

were not visible.

In the reinforcement pictures from bar placement the mm2 were occasionally shown.


On calculation of distance “e”, for determination of the length of the loads and place of the structure,

the “Av. Width” was used for “b” instead of the structure width. Because of this it could happen that

with a small average width the length of the load was too short.

In “Loads Calculations” the tooltip in calculation was not showing the filled in values anymore.

When the code was set to NEN it was wrongly possible to start the loads generator.

Occasionally MatrixFrame was crashing if the loads generator was used for the second or third time in

the same model.

Wizard Rainwater accumulation was deleting user defined dead load case with dead loads. Also “3D-

system” was giving several error messages.

1D Beam:

If a section was added with an angle 90° the grid was not filled in correct. Calculation was correct.

2D Grillage:

On adding FNL reinforcement on top and bottom with the “Apply to All” button MatrixFrame was

crashing.

Placing of a support was not always working correct. For example if position 0.1 m. was shown in

tooltip the support was placed on the begin (0.0 m.)of the beam.

If a grillage was copied the supports and releases were not copied.

Joining members was working incorrect. Members were made with the same begin and end node and

supports were shifted.

12 / 45


3D Frame:

The loads were incorrect taken when a project was inserted with loads from the loads generator.

When a Nodal load was added the load was not placed but on every click a new empty load case was

generated.

FEM:

In report “Concrete cross section (detailed)”strange values printed for Asreq.

On changing a value from a load in the “Plate definition” the direction was changing from “Z” to “X”.

This wrong direction caused messages that “no internal equilibrium” is found.

Concrete check:

An extra basic reinforcement layer was treated as additional in bar placement. If only additional

reinforcement was defined in the extra layer it was printed in the table as basic.

For a deep beam the multiple layers of reinforcement were not taken into account for determination

of Mu.

Steel check:

In the NEN-EN the cross check of a CHS section was unfavorable. Formulas have been adapted.

Occasionally a symmetric portal gave an asymmetrical unity check.

Timber check:

The “Unity check member color” was not working correct. Only the cross check was taken into

account.


Occasionally MatrixFrame was crashing when connection type was changed.

The scaling of the UC diagrams in the reports was incorrect. Because of this they were not legible.

The tension- or compression force of a diagonal was not properly taken into account in the shearing of

the bolts.

In Tube connection it was not possible anymore to set section angle to 90° for RHS section.

It was not possible anymore to set symmetrical “Bolted splice” connection if it was activated in

MatrixFrame.

For a “Beam - Column” connection the normal force from the top column on the beam was not taken

into account for “Check on force distribution”.

After adding a “Tension plate inclined” and then a “Compression plate inclined” they were clashing. By

using the button “Proposal” this clash will be solved.


Concrete:

o In the report from “Column isolated frame” the values for M_bottom and M_max. were

swapped. Calculation was done correct.

13 / 45


o In the module “Cross calculation Vu capacity” the check Ved <= 0.5 VRd;max. was not done.

Extra column “VEd” has been added and if this value is larger than 0.5 VRd;max. double

stirrups will be used based on check 0.75d <= 500.

o In the module “Colum calculation + fire” occasionally a second order moment M2 was taken

into account if a second order calculation was not needed.

In the module masonry “Wall calculation” a UC= 0.0 was shown if the requirements were not met.

Now a red value 9999 will be shown.

Results tab was not always refreshed after a change was made in the module “Steel column

calculation”.

MatrixTools Geo:

During generation of soil layers the negative friction was not correct calculated. This happened with

analysis based on “Cone based on qc;inf and qc;sup” and “Cone based on qc”. When “Friction” was

used this interference did not occur.

Positive friction will not be taken into account anymore for a “Steel pile with constant cross

dimension; tube pile with closed base” if the base plate is extending more than 10 mm.

Positive friction was wrongly not taken into account if a negative friction layer was detected beneath

the pile foot.

If a neutral friction zone is defined (friction= 0%) the negative friction factor 1.4 will be used.

Pile base form factor ß was incorrectly calculated and also not printed in the reports.

When user is setting “Skin friction” automatically the depth of the nearest soil layer will be chosen.

When using the CPT digitizer on the screen the filled in “Level” was not correct set.

Occasionally the name from CPT diagram was not correct in tab “Results”. This happened if for

example from 4 diagrams 1 diagram was not checked. Calculations of results were correct only name

was wrong.

Tabs were not always correct refreshed if a CPT diagram was checked or unchecked.

It was not possible to copy the CPT diagram with pile results and friction to the clipboard.

Now 2 reports are possible. “Compression Pile Summary“ for the “Average results” and “Compression

Pile Summary by CPT” for the “Results”.

If a CPT diagram was not defined more than 5.0 m. beneath the pile base the calculation was not done

to filled in depth. Now results will be shown but value “Bearing capacity zone end” will be colored red

and in tooltip the maximum allowed depth is shown.

On opening a CPT diagram from 5.2 the "qc;lim" and the "qs;lim" were sometimes swapped.


MatrixFrame version 5.3 - Release notes

Incorporated in version 5.3 (December 2016):

14 / 45


New:

MatrixFrame® General

In version 5.3 loads are represented in a stacked setting. For this purpose a new option has been

added in "Visibility options" under loads”.

Loads can be represented in the color of the direction of the coordinate system: X (red), Y (green) and

Z (blue). For this purpose an extra layer has been added in “Visibility properties” under “Loads”.

Now distributed loads can continue and /or start outside the member. The “Begin distance” is marked

with a “-“symbol. The “End distance” is the total length of the load. So it can be longer than the “Begin

distance”+ the member length. In the example below there is also a rigid link of 0.5 m in X-direction on

some members.

15 / 45


Now loads can also continue on rigid links in the local X-direction. The “Begin distance” is then the

length of the rigid links and is marked with a “-“ symbol and the “End distance” is the length of the

member between the rigid links + the rigid link on the end of the member. In the sample below there

is a rigid link of 0.5 m in X-direction at the beginning and the end of the members.

For distributed loads, with the same begin- and end value, 1 value is shown now.

New import- and export function XML.

New import function MXFI with which MatrixFrame can be operated from an external model package. The model with loads and combinations can be imported. After importing a calculation is run with a concrete check if necessary. Finally a *.mxfo output file is generated.

16 / 45


By import *.mxfi it is possible to import parts of a file. For example only the loads.

Now it is also possible to add a model, in which the load generator is used, in a model in which the

load generator is used as well.

The renumbering of nodes members, section properties, supports and loads has been entirely

renewed. Now it is possible to run a renumbering of everything at once. This is possible for the entire

structure of a selection. Apart from this nodes and members can be renumbered manually. In case of

renumbering manually, a number is selected which already has been used, the member- or node

number of the renumbering object will be assigned to that object.

Autosave files now include file name and time. You can find them in

“C:\Users\...\AppData\Local\Temp\MxTemp” with the extension "file name.mxfautosave".

Reports:

The option "New page after every picture" is replaced by "Single picture on the page ".

17 / 45


MatrixFrame & Revit, Tekla and IC-Prefab:

MatrixFrame offers new options (this is an expansion module) for exchanging calculation models and

for interactive cooperation of leading CAD software for engineers. There are three options available:

Model exchange with Autodesk Revit and Tekla Structures: Models within Autodesk Revit and Tekla can be represented as a geometric model, where all structural components can be visualized in their true form. Less well known is that all structural elements also have an analytical representation within Revit and Tekla. Relevant data for system lines, connections, eccentricities, boundary conditions, support and even loads, load cases and load combinations can be entered in the model and can be managed. Matrix Software has developed a new interface for opening the analytical model directly within MatrixFrame structural analysis software. This can be both for the complete model, as for a part of the model. The structural engineer can decide if models will be designed in 1D beams, 2D grillage, 2D & 3D portal frames or in FEM plates.

Interactive structural design for Autodesk Revit: Another new feature in MatrixFrame is a direct interface between Revit and MatrixTools. The toolbox

consists of about 40 modules for detailed calculations for structural components in concrete, steel and

wood. A selection of these MatrixTools features will be installed as a plugin. Modelers thereby gain an

additional toolbar with MatrixTools features. By clicking structural parts in the model, a structural

analysis can be started. The result of the design is updated directly in Revit. In addition, the

MatrixTools files are stored in the same Revit project file. This makes revision management very easy.

This is a new and productive tool for integrated modeling and engineering has become available.

Integrated structural engineering for IC-Prefab: In collaboration with IT-Concrete, developer of CAD software IC-Prefab, a seamless interface is

designed for production of prefab concrete flooring systems. Draftsman can calculate simultaneously

one or more floor fields with one push on a button. If the structural analysis is OK, the draftsman

directly can use the results for designing concrete reinforcement. If a floor field does not comply, the

structural analysis can be provided to a more experienced structural engineer. This workflow will

reduce design time and will reduce errors.

Less time will be spent on designing concrete prefabricated slabs, while the risk of making mistakes

and double work declines. The data exchange between IC-Prefab and MatrixFrame is realized by a

18 / 45


MXFI-file, which replaces the exchange by a MDB-file.

Installing and activating plug-ins and commercial modules:

During the installation of MatrixFrame a detection is made whether there is a license of Tekla or Revit

or both is installed in the system. In that case the system asks if MatrixFrame and/or the MatrixTools

plug-ins should be installed in Revit or Tekla. The dialogue below appears during the installation.

Contact the sales department for the license of commercial modules.

The smooth interface with IT-Concrete requires no plug-ins of Matrix. In order to acquire the new

functionalities, you need to extend the license for MatrixFrame and the license for IC-Prefab. For the

extension of licenses contact the sales department.

Load generator NEN-EN:

In "Calculation sheet loads" for wind loads, a special tab is generated for the general wind settings such as the wind territory and territory classification. Now these settings don’t need to be adapted in every tab separately.

With wind the “Average Width" is set by default equal to the "Sys. Width".

When applying a cantilever for wind, now a message appears if there is no roof type selected.

1D Beam:

Now there is a 1D "Advanced" in which the beam is a fully 3D member. This means that 3D supports and loads can be added as well. (This is an expansion module)

The dimension lines in the picture geometry are dynamically now. So they are moved automatically when a dimension line is measured.

2D Grillage:

Now it is possible to assign a distributed torsion, according to the local coordinated system (Xr'), to a

member.

19 / 45


When positioning a support a dialogue window appears. Position is rounded off to 0.1m.

In the shear force diagram values are shown at the position of releases.

20 / 45


3D-Frames:

It is possible to detect the rotation of a member by assigning a referencepoint.

21 / 45


It is possible to assign a distributed local moment (Xr', Yr', Zr') to a member.

22 / 45


FEM:

Now tension elimination with elastic foundation is possible.

Now the reinforcement can be visualized in a grid. The measurements of the grid can be set by the

user and are set by default on 1.00 m. You can choose between As;req” en “As;req -As;prov”.

23 / 45


The calculation of the average reinforcement for the grid can be made: “Accurate” or “Fast”. This can

be set in the menu “Customize” with settings for concrete at Settings for concrete.

o If the setting is switched on “Accurate” the value of the grid is calculated including the

“weight” of the vertex (This is the area of round the vertex) that is taken into account.

o If the setting is switched on “Fast” the average of the values in the grid are defined.

o If the mesh is symmetrical, and the elements are nearly rectangular and nearly similar, and

the edge of the grid results in more or less symmetrical sets, both methods will give the same

answers.

o If there are many differences in the measurements and the shape of the mesh then

“Accurate” will give the most accurate results. Especially on the edges.

24 / 45


Concrete check:

The concrete modules are updated according to "EN 1992-1-1/A1:2016”.

The concrete module of Matrix has been extended spectacular. A great number of functionalities have

been added. The worked-out options below are added to dimension prefab floor systems such as

prestressed and not prestressed floor plates for floor systems and hollow core slabs. The options are

implemented generically, so they can be used for all kinds of concrete calculations, prefab as well as

in-situ.

Multiple layer reinforcement can be applied now. Click with the right mouse button on the cell and

select: “Add multiple reinforcement layer(s)”.

Now “h-d” can be filled in and the reinforcement can be defined. At the same time the new option

“App.” (Apply) reinforcement can be defined for the As;req calculation. This means that when

determining the required reinforcement, the defined reinforcement already has been taken into

account.

Now it is difficult to define reinforcement on the floor plate for floor systems with multiple layer

reinforcement. (hB + R/2).

Now lattice girders can be defined with bottom reinforcement. Click with the right mouse button on

the cell land select: “Defining lattice girders…”.

25 / 45


Now a dialogue window appears to define the lattice girders

The bottom reinforcement and the top reinforcement of the lattice girders are taken into account as

multiple layer reinforcement in the input.

With the stirrups you find back the reinforcement for shear surface.

With settings an option has been added: "Allow stirrups for thin slabs (ignore art. #9.3.2(1))". This can

be set in the menu “Extra” with settings for concrete.

26 / 45


With slabs it is possible to fill in secondary reinforcement.

With concrete settings the default diameter for the additional reinforcement has been added.

When calculating a floor plate for floor systems you should activate in “Concrete settings” in tab

“Group data” the checkbox “Prefab”. At the same time the required data for defining the creep factor

of the floor plate for floor systems are filled in.

Because of this an extra tab “Prefab Prestress + top layer” is available for required settings. The

roughness of the intersection between the floor plate and the in-situ top layer and also the required

data for the calculation of the creep factor of the in-situ top layer.

27 / 45


With floor plate you can indicate whether there are stirrups in the floor plate for floor system. If it’s

not switched on, de stirrups will lay on the floor plate.

The shear reinforcement between the floor plate and the in-situ top layer is calculated now. The

stirrups which are located in the floor plate for floor systems are taken into account.

Now you can work with prestress. For this, you should activate in “Concrete settings” in the tab

“Group data” the checkbox for prefab. (This is an expansion module)

Now an extra tab is available for “Prefab prestress + top layer” in which the required checkboxes can

be activated.

In the “Concrete Crosscheck” there are 3 extra tabs available now.

In the tab “Prestress” the prestresses can be filled in.

28 / 45


In de tab “Prestress bar pos” generated positions can be adapted. At the same time “σpd” can be

adapted per string.

After the prestress strings are defined the initial- and acting prestress loads needs to be generated.

The generated prestresses can be found in the “Loads calculations”.

29 / 45


Now there are 2 load cases created. “Initial prestress” and “Acting prestress”.

30 / 45


In the tab “Prestress results” the results and checks are shown. By putting the mouse cursor on the

cell “Prestress” or “Concrete” a tooltip appears with detailed information.

With sections the values of hollow-core slabs are added.

With “Concrete crosscheck” you can select a reinforcement pattern in the tab “Prestress”.

31 / 45


In the tab “Prestress bar pos” the generated strings are shown.

Now they can be adapted for example if the number of strings applied differ from the number of

strings applied in the database, or if there is another σpd available for example the string R7.5 at the

top in hollow-core slab.

Generate the initial and acting prestress.

32 / 45


Go to “Prestress results”.

The reinforcement propositions of the concrete wizard are extended with extra functionality.

For slabs extra reinforcement combinations of nets are added.

The setting below makes it possible that you can work with reduced nets.

The reinforcement propositions of the concrete wizard are extended with extra functionality.

Design on bending.

With reinforcement As;req. and As;prov. can be visualized graphically now.

33 / 45


It is possible to apply a stirrup with an odd number of sections. A stirrup with 3 sections is filled in as

1.5R8-300.

It is now possible to calculate crack width according NEN-EN 1992-1-1#7.3.4. This can be set in

concrete settings.

34 / 45


Defining decisive sections for the calculation of reinforcement a minimum moment of 1.00 kNm was

used. Now this can be influenced by the user in concrete settings.

Steel check:

With a fire check of a column the static system now is set automatically on "Bending & Pressure bar" when it contains a moment.

Steel connections:

The steel connection module is renewed entirely. Now we work with a universal connection entirely

applicable for 3D. The type of connection is now linked to the beam. For convenience’s sake there are

a number of templates available.

Dependent on the number of beams one possible configuration can be chosen.

35 / 45


By setting the type for each beam it is possible to work with several types.

36 / 45


Take care: in order to fill in or change the loads, endplate and stiffeners

you should select the appropriate bar!

With a "Beam-Cross girder” connection it is possible to position a plate on or between the flanges with

a stiffener.

New type: Column Endplate with RHS/CHS tubes and UNP

37 / 45


With an angular joint connection now a check is made on the bending of the angular joint connection.

With a "Beam- Cross girder" connection the value "hr" can now be changed by the user.

The default bolt- and anchor quality has been changed. For bolts now 8.8 is set and for anchors 4.6.

38 / 45


MatrixTools:

Calculation sheet loads is a new option.

Here you find the same functionality as in MatrixFrame to make a weight calculation.

In the module M+N extra information is added about the total reinforcement, with a universal

reinforcement. This is shown in the tab results with a tooltip and also added to the report.

MatrixTools Geo:

MatrixTools Geo is now entirely integrated in MatrixTools and updated according to "NEN-EN 1997-

1/NB: 2016”.

An important change for compression piles per 01-01-2017 is the reduction of the αp for the

compressive capacity with 30%. This factor is stated in the menu “Customize/settings/Geotechnic”.

39 / 45


Also the input dialogue windows are designed newly and the results can be seen in different tabs.

In the new GEO all files are saved in 1 file.

40 / 45


In the new GEO several CPT-diagrams with different extension can be imported at once. (*.snx, *.gef, *.mxft)

With table input for cone- of friction values in the new GEO the depth is automatically raised with 0.25. This value can be set by the user.

It is possible to make a calculation check or a calculation design.

The report is extended and flexible when using several CPT-diagrams.

The load-deflection diagram can be linked to MatrixFrame Non-linear supports. For this purpose go to

“Definition supports” tab. “Special” and select “Z” “Spring”. Now the option appears “Synchronize ULS

and SLS diagrams” available and a file within this model can be selected.

If there is still no compression pile in the model go to the menu “Tools” and click on “General” on

MatixTools.

Then click on the “Main button” and select add project.

41 / 45


Go back to MatrixFrame and with Running diagram values via Geo” the desired file can be selected.

Now 2 different diagrams are made for the ULS and the SLS.

By activating the checkbox “Synchronize ULS and SLS diagrams” the SLS is synchronized with ULS.

You can also make a new compression pile calculation in MatrixFrame. For this option you go to the

menu “Tools” and at Geotechnics select “Compression pile”.

42 / 45


There is a new module for defining a elastic foundation constant. The results can be linked to

MatrixFrame. (see explanation about the steps to follow above with Load-deflections diagram)(This is

an expansion module)

In the new Geo it is now possible to copy soil types from another region in a new region.

Bug fixes:


With a GNL calculation in combination with elastic foundation with tension elimination strange unexpected moments appeared. Problem was caused by the fact that the GNL was not divided into the same amount of segments for the GNL part and the elastic foundation.

43 / 45


Problem with filename which was illegible with maximized screen in the default settings of W8.1 and W10 is solved.

Incidentally MatrixFrame crashed, when activating the Toolbox, in case the model contained toolbox files.

When calculating the tensions for a RHS with different wall thickness for the top, the bottom and left/right, the Tau was calculated everywhere with the thickness of the left/right.

When adapting an Arcelor T-section, by changing the name in the table, an incorrect section was filled in. This caused an irregular section with the same name in de Matrix library.

Scrolling through the results with a mouse wheel doesn’t work in Windows 10. It does work when keys go up and down by means of arrows.

In the toolbar of the spy was stated 2x Vy instead of Vy and Vz.

In calculation sheet loads, when selecting a dead load the program started wrongly with index Pp2.

The use of "calculation engine 2.0" was only saved in the model. Now it is also registered in the rergister.

Label for supports of "Yr" is corrected to kN*m/rad.

Incidentally MatrixFrame crashed when opening a model with both timber and steel sections.

During downloading, or after starting after the download, Windows came with a security notification. "Windows protected your PC. Windows Smart screen prevented an unrecognized app from starting. Running this app might put your PC at risk" This was caused by security protocols of Windows.

When applying the concrete quality of C55/67 and higher the E-modulus could not be modified.

When renaming a load case part of the left text field was not visualized.

With copy paste "polar" an angle with decimals was not calculated correctly. Because of this different

measurements existed alternately.

Reports:

Incidentally pictures were printed too small when exporting to rtf. The solution is then to select type "wmf".

With the table supports with export to rtf, the "z" was not printed in the headline incidentally.

The calculation headers with project data of MatrixFrame and the Toolbox are identical.

Load generator NEN-EN:

When generating loads on a porch MatrixFrame got stuck incidentally.

With a cantilever, an incorrect angle was calculated incidentally for the "category H inaccessible roofs. For example 6° became 174°.

With the report of "Concrete column (short)" in the tables with column "Nr.", the sequence of the labels was not represented correctly. On the other hand, the values in the tables were printed in the correct sequence.

With a duo pitch roof with a negative angle the wind loads were generated incorrectly.

1D beam:

With a model with supports and in the centre an elastic foundation, the support reactions were not symmetrical. This was caused by the number of elements which were selected.

2D Frame:

When creating a connection in MatrixFrame, a button is added in connections, to go back easily to MatrixFrame. Because of this you don’t need to minimize or close the connection screen.

With a calculation with an elastic foundation with tension elimination, the soil pressure was not shown incidentally.

44 / 45


2D Grillage:

Incidentally a beam with releases was mirrored in the concrete drawings.

3D Frame:

With a GNL calculation in combination with an elastic foundation on a 90° rotated section, strange moment leaps occurred.

FEM:

When assigning reinforcement it was not al was visible, because of the different mouse symbol, that the program was still running.

Incidentally the assigning of the reinforcement was unaccepted slowly.

Several models with mesh problems checked. It turned out that as a result of model mistakes, there wasn’t enough space between 2 figures, 12 mm interspaces. This can be detected by the user by running the Check on Geometry with a larger tolerance each time.

Concrete check:

In the concrete wizard additional reinforcement was positioned at supports incidentally. This was unnecessary.

In 1D beam with "outrebound of the support" the moment was not correctly topped off when a release occurred in the beam.

Steel check:

The bending check was switched off when starting up again the steel check, when a selection was made for a larger or smaller section in the UC Histogram.

Incidentally at an angular section, not under pressure, the cross section classification 1 was used when calculating.

With assembled structural parts lateral buckling was graphically not positioned correctly.

When opening a model, incidentally the notification was given: "Warning! Missing steel members ". If this happens again there will be a survey in the log file of the members and the members will be generated again.

Timber check:

With round sections no UC was calculated incidentally because the torsion of the section was not calculated.

In the output of the timber check you can see clearly with which load duration classification is calculated now.

Incidentally the timber check caused a crash in MatrixFrame.


If a welded connection was selected in 2D-Frame, the welds of the column or de beam could not be modified.

The possibility to assign to an angular joint only one row of bolts is blocked. The calculation rules are not appropriate.

With column base the anchor code is updated to "NVN-CEN TS 1992-4-2:2012" and reference to "CUR/BMS#10" has been added.

45 / 45


With the output of a "Column-Beam" the name of the column gives incorrectly on several places. The calculation, on the other hand, was correct.

With the check of a weld for column base, the symbol "-" had an incorrect positive influence.


In the module "Cross section properties" now the values for small cross sections are rounded off less fast. For example Iy = 1e+04 is now Iy = 59e+02.

Concrete: o With the model "Moment in pile" the report items were over written if another model was

activated. o With the module "Cross section calculation M+N" the corrected moment of the "Check MEd <

NEd * e0" is not shown in the report. o With "Column calculation+ fire" for a wall heated on 1 side, an extreme high As,req was

calculated. o When applying all sided reinforcement with a concrete column, incidentally a not expected

high reinforcement was calculated.

With welding calculation the label of the results for Sigma-HH was incorrect. It stated"*sqrt (3)" instead of. "/sqrt (3)".

In the module "Timber beams" the impulse load was not printed in the report.

The report from wind on a “Beam inclined roof” has been updated. Now it’s more clearly that wind compression is combined with under pressure.

MatrixTools Geo:

When calculating a compression or tension pile with several CPT’s, which are not of the same height, now, the program will always make the same calculation and will stop automatically with the maximum permitted depth.

End release note

Documents

MatrixFrame version 5.3 SP6 - Release notes Bug fixes · An incorrect lateral buckling curve was used if a castellated beam was used from the castellated ... In the module “ending