Blog Archives

Important CIRCLY 7.0 Update – February 2022 – Further Information

The following discussion regarding thin bituminous surface layers involves two cases:   –  an asphalt wearing course over a base asphalt course, and  –  a single wearing asphalt layer over a granular base Thin asphalt surface layers do not typically fatigue as they are usually in compression due to the proximity of the wheel loading. The following figure illustrates the transition from compression to tension for horizontal strains underneath the surface AC14 layer as the asphalt thickens from 40 mm to 50 mm.  The critical horizontal strain location under Standard Axle loading is at the centre of the inner tyre for these cases.  Note that the surface AC14 is located above an AC20 asphalt layer. The following 3D contour plot shows…

Important CIRCLY 7.0 Update – February 2022

Some changes have been made to CIRCLY 7.0. These relate to CIRCLY 7.0’s Austroads Pavement Design Method (2017), as described in the Austroads Guide to Pavement Technology Part 2: Pavement Structural Design. An issue that occasionally arose for very thin surface asphalt layers where the maximum horizontal tensile strain was not always selected has been fixed. Another change is the CDF field is now left blank when there are only compressive (positive) strains as can occur for thin surface layers as shown below:   The Job Summary File has been updated to indicate Asphalt compressive strains as shown below: There is no change with the strain sense presentation in the .CLO ‘printable’ results file. Click here for Further Information. How…

CIRCLY 7.0 Error Number 9850 – Floating Licence requires Internet Access

If you have a Floating Licence for CIRCLY 7.0, CIRCLY must be able to access the Internet. If you are using a third-party firewall, you many need to configure it to allow circly7.exe to access inbound and outbound TCP traffic on Port 29750. Please consult the vendor’s documentation.          …

CIRCLY Fatal Error Number 8204 – CIRCLY32.exe is missing or locked by antivirus

CIRCLY32.exe is the calculation engine used by CIRCLY. It is highly likely that this error is a consequence of your antivirus software which has either: deleted the file moved the file to a quarantine folder, OR locked the file   We have seen this issue arise as a consequence of a false positive introduced in a recent update of virus definitions in several antivirus programs. A false positive occurs when an antivirus program erroneously identifies a legitimate file or process as malware. Contact your IT Administrator for assistance.…

Enhanced Licence Activation Key format

We are now using an enhanced Licence Activation Key format. The old V1 keys only had 1 digit to represent the year, e.g. V1-CIR5-27019-REN-00227-COMI-991B represented 2020. The new V2 keys use 2 digits to represent the year, e.g. V2-CIR5-27019-REN-200227-COMI-1E78 represents 2020. If you use an old V1 Activation Key in the latest software (with a version date of 20 February 2019 or later), you will get this error message: Sorry, the Licence Activation Key is not the correct length. It should look something like this: V2-CIR6-27019-REN-200205-PROF-B769 Please contact Mincad Systems to get a replacement Licence Activation Key. If you use a new V2 Activation Key in any older software (with a version date prior to 20 February 2019): e.g. V2-CIR5-27019-REN-200105-COMI-1E78 Sorry,…

CIRCLY 7.0 – importing data from CIRCLY 6.0

This is how it works (​You need to be running CIRCLY 7.0 (19 April 2020) or later): Click on the Menu item, File, then Import CIRCLY 6.0 data. There are 3 options to import data from your CIRCLY 6.0 database: Only import your Materials Import your Materials and Layered Systems  Import the following items: Materials Layered Systems Full details of non-Austroads Design Method jobs (General Analysis; General Design and Haul Roads) Important – Resolving data clashes If you have records for Materials etc. that have the same IDs in both CIRCLY 6.0 and CIRCLY 7.0,  the CIRCLY 7.0 values will not be overwritten. Important – Austroads Design Method There is no way to automatically transfer all job data from CIRCLY 6.0 to…

What are the limitations of CIRCLY 7.0 Evaluation Mode?

There is only one version of CIRCLY 7.0 – and it can be used in Evaluation Mode. Are you doing a CPEE Unit? We have made CIRCLY 7.0 available to CPEE students to facilitate completion of relevant design assignments. You can use CIRCLY 7.0 in Evaluation Mode to analyse your assignments.…

CIRCLY Error Number 6101 – Traffic Load Distribution (TLD) – .csv file error

  The .csv file that you import must look like the table on the right hand side:   The .csv file that you import must conform with these requirements: The first row must be: Load,SAST,SADT,TAST,TADT,TRDT,QADT   All the proportions (from all axle groups combined) must add up to 1.0 (or very close!) Click here for more information on Importing your TLDs.…

Using CIRCLY 6.0 over a network

CIRCLY 6.0 can be run over a network, in the sense that the data files can stored and shared on a remote server or workstation. For the following procedure to work, it is assumed that the CIRCLY 6.0 data files are already installed on the server – (the core data files are *.cls and *.cmdb). To set up a client/workstation, follow these steps on the client: 1. Open Windows Explorer. 2. In Windows Explorer, open “My Network Places” and navigate to the server, then to the drive where the CIRCLY data is stored. 3. Now start CIRCLY on the client. Click . If for example the CIRCLY data files are installed in the folder “C:Users\Public\Documents\Mincad Systems\CIRCLY6\data” on the server, type in…

What CIRCLY 6.0 files do I need to backup?

To find out what data folder is currently being used: Click . The data folder will be shown in the “Data Path” field. By default this will be “C:\Users\Public\Documents\Mincad Systems\CIRCLY6\data”. To backup your data: At the very minimum you only need to back-up all the *.cls files and the database files LAYERS6.CMDB and LOADS6.CMDB. There is only one possible catch. CIRCLY is designed to use the latest (and only the latest) versions of the relevant data from the databases when you run an analysis. If you change ANY of the data that was used by previously run jobs, if you run those jobs again they will use the latest data, not the historical data. This is by design. To ensure that you can check the actual data…