Before CADEcomp can correctly analyse the loads applied to a member for the purpose of design checks, the combination factors for each of the load cases must be set. To do this, the Load Combination editor must be invoked.


This can be done in two ways


1.From the Load Entry Tab, Click the CC_LoadCombinations button

2.Right Click any of the load case heading tabs (at the bottom of the load display screen)


 CC_combinations 2


In both cases, the editor should appear ...




This chart controls the  way that CADEcomp, combines, checks and sorts the way the load data is applied.


In all cases, the load applied is combined with the dead or permanent loads. Each of the column headings indicate the type of data required and all data values can be changed to suit the conditions that you deem to exist. Although there is default data applied, any changes made are relevant ONLY to the current member. If you wish to apply exactly the same loading pattern to other members, you can Create a Template which can be assigned as required.


Some import things to consider (remember):


1.The C.Case 1 (first row of the table) is always defined as a dead or permanent load (For timber the K1 value is usually set to 0.57) - as this is 'value' used to check for the load as DL, if designing a steel beam this value is used to define DL's, although it is not otherwise used in the calculation process'

2.All other cases, by default, are considered as temporary loads with the combination factor used to control its design magnitude.

3.Any combination case case can be defined as a DL case by ticking the 'Dead Load Only' check box. (You may need to change the DL combination factor also.)

4.You can define any other load combination case as a DL, by setting the K1 factor the same value as the factor in row 1. (this applies for steel member also)

5.You can prevent load combination cases from being applied to other members by 'un-ticking' Apply load to other members. This can be useful in the case when you might apply a point load live load to a member as a check, but don't wants or need to extend this load pattern to members further down the structure.

6.Load combination cases can be colour coded - this makes it easier to distinguish load cases on the loading diagram.

7.You can create combination templates (using the Save & Load buttons), which are then available for use on other members.