PLE forum - PLE User Interface

Possibly resulting total gap between pipeline element and soil

Thu, 12 Oct 2017 13:29:00 +0200

Ref: Tables Reference > Output Tables > Additional cross-sectional loads [ADDCROS] > Data description/Result options / ID: H610541

Dear Support Staff,

According to the user manual, see below, a gap can be calculated according to U_Z - SETLZ*F - SOILNB / KLS > 0.
[attachment=909]

This is true in the case when the Z-coordinate of polygon point (n) is on the bottom of the pipeline.
In normal cases and cases when there is a large diameter a user will fill the Z-axis of the pipeline according to the screenshot below.
[attachment=910]

Does this mean that the gap can be calculated as U_Z - SETLZ*F - SOILNB / KLS - (DOUT / 2) > 0.
If correct than the note in helpfile should point out that the DOUT / 2 is conditional only for the case if Z-coordinate is the axis of the pipeline in POLYDIF.

Typos in the Change Logs of v4.4.0 and v4.4.1

Thu, 29 Dec 2016 06:54:36 +0100

Hello,

"3d" is written with a lowercase letter; it should be written with a uppercase letter "3D" like the other texts in the Change Logs of v4.4.0, see screenshot below:

[attachment=836]

"soil wizard" is sometimes written with lowercase letters; it should be written with uppercase letters "Soil Wizard" like the other texts in the Change Logs of v4.4.0 and v4.4.1, see screenshots below:

[attachment=837]

[attachment=838]

[attachment=840]

Online user manual still on v4.4.0 instead v4.4.1

Mon, 31 Oct 2016 23:27:41 +0100

Since the v4.4.1 release of Ple4Win on October the 12th, the online user manual is not updated from 4.4.0 to 4.4.1. If this is in the pipeline, then this post is not relevant.

Typo in the Change Logs of v4.4.1

Thu, 13 Oct 2016 08:40:35 +0200

Hello,

There is a typo in the Change Logs of version 4.4.1, see screenshot below:

[attachment=829]

"de" should be "the" in the sentence.

Typo helpfile ADIDENT input table

Tue, 14 Jun 2016 13:02:42 +0200

Ref: Tables Reference > Input Tables > Additional idents [ADIDENT] > Data description/conditions / ID: H200151

[attachment=797]

[attachment=798]

According to the latest Ple4Win v4.4.0 (revision May 2016) program the column name 'IDENT' in the input table ADIDENT has been changed into 'NEWIDENT'. To make it consistent with helpfile, this typo in the helpfile needs to be changed according to the program.

Wrting error in DF 6.1

Mon, 02 May 2016 17:45:51 +0200

Affected version: Ple4Win Professional v4.4.0 build 16042
Reproducible: always

There are 2 issues which gives a writing error.

Issue 1 - Setbacking DF 6.1 of v4.3.1. and copy paste new TOPLOAD
Step 1: Open attached project file (v4.3.1) in this topic;
Step 2: Accept converting to new database according to v4.4.0;
Step 3: Set back DF 6.1;
Step 4: Destroy the TOPLOAD input table;
Step 5: Copy TOPLOAD from Excel to the clipboard (Excel file is attached in this topic) and paste it in the TOPLOAD table.
Step 6: Calculate and lock the DF 6.1 function. A write error will occur, see screenshot below:
[attachment=791]

Issue 2- Setbacking DF 6.1 of v4.3.1 and copy paste topload by mistake in LAMBDA
Step 1: Open attached project file (v4.3.1) in this topic;
Step 2: Accept converting to new database according to v4.4.0;
Step 3: Set back DF 6.1;
Step 4: Destroy the LAMBDA input table;
Step 5: Copy TOPLOAD from Excel to the clipboard (Excel file is attached in this topic) and paste it in the LAMBDA table. A bug warning message will occur, see screenshot below:
[attachment=792]
In this case a warning popup should appear, but instead of that it gives a bug warning message.

SIS input tables active in DF2 without the H module

Tue, 26 Apr 2016 11:34:54 +0200

In Ple4Win v4.4.0 the SIS input tables are active in DF2 without the H module. Is this standard?
It is strange that SIS input tables are working without the H module.

.NET Framework 4.5.2 system requirements

Sun, 24 Apr 2016 09:15:11 +0200

The Ple4Win v4.4.0 application uses now .NET Framework 4.5 according to the change logs.

I think the system requirements needs to be updated also to .NET Framework 4.5.2, see screenshot below.

The Microsoft website link should be referred to this link.

[attachment=779]

DF6.2 Legend not updating after importing Excel file

Wed, 20 Apr 2016 10:59:43 +0200

Affected version: Ple4Win Professional v4.3.1 build 15032

Steps to reproduce the issue:
Step 1: Open Ple4Win;
Step 2: Save new project file;
Step 3: Change in Analysis Type 'General' into 'NEN 3650-2'
Step 4: Import the attached Excel file;
Step 5: Process calculation.

After step 4 you will see that the legend icon is not updated, see screenshot below:

[attachment=769]

This issue happens only if in step 3 the Analyssis Type is changed into 'NEN 3650-2'.
This was reported earlier, but the topic was deleted by accident.

Typo ovalising or ovalizing

Thu, 04 Feb 2016 17:11:12 +0100

In the helpfile ovalising is written with a "s" and "z".

[attachment=756]

[attachment=754]

[attachment=755]

It should be consistent in the program and the helpfile.

Floating point issue from Excel or Clipboard to Ple4Win

Mon, 25 Jan 2016 15:02:12 +0100

Affected version: Ple4Win v4.3.1 build 15032

When one imports data from Excel to Ple4Win, Ple4Win doesn't imports the whole double digit value. The floating point value is trimmed at the 5th digit. I have attached an example Excel file with maximum 9 digits.

Value of Cell C3 of the POLYDIF sheet is 94833.25568275
In Ple4Win the first DX_N value is 94833.25568.
Somehow the values after the 94833.25568 are cleared. This means that my calculated values in Excel doesn't match with Ple4Win, which means that points are not in the same location as calculated in Excel.

This issue also happens when copy manually with (Ctr+C) from cell C3 value and paste (Ctrl+V) it into Ple4Win. So the values are also trimmed when the Clipboard is used.

This is a small issue, but at disconituity points this can be issue because it is not exactly on the node/AX-L/AX-LP as calculated in Excel due to this isconsistency which can give stress peak points in the calculations for example when one uses slack points.

switch is missing for the 'Switch' menu in POLYDIF

Wed, 11 Nov 2015 08:52:10 +0100

Affected version: Ple4Win Professional v4.3.1 build 15032

In the current version of Ple4Win a user can't use the Alt switch for the 'Switch' menu in the POLYDIF input table.

[attachment=740]

A user should use for example {w} to activate the 'Switch' menu following with {A} for 'Absolute' and {R} for 'Relative' toggling.

String length incosistency TEE-REF

Wed, 28 Oct 2015 13:59:42 +0100

Affected version: Ple4Win Professional v4.3.1 build 15032

There is a incosistency in the TEE-REF input table.
The TEE-REF in TEECONF and TEESPEC should also have 8 characters possible.

[attachment=731]
[attachment=732]
[attachment=733]

The column table abbreviated ShortName is limited to 7 characters. This is correct, but the input values are limited to 8 characters, see
MATREF and MATBRN.

[attachment=735]
A wish is to increase the limitation of 7 characters to 8 characters for TEE-REF in the TEECONF and TEESPEC input table. The value '7' in the warning message should be changed into the value '8'.

Project324 is missing in v4.3.1 build 15032

Wed, 12 Aug 2015 14:36:33 +0200

The Project324 tool v3 to v4 conversion tool has been silently removed in the v4.3.x Ple4Win installation files.
According to the latest version helpfile the Project324 tool should be available. Helpfile Ref: Getting Started > Design Process > Create/Open a Project > Converting PLE3 project / ID: Converting_PLE3_project

We have checked the installation MSI file and indeed the Project324 was missing in the MSI file. We have extracted the Project324 executable with a MSI extractor from Ple4Win v4.2.3 (latest version where this tool was available), but the tool did not work in Ple4Win v4.3.1.
Mark did send us also the Project423 executable; this was the same version we had extracted from the old Ple4Win v4.2.3 version. It did not work. So we have had to install the old Ple4Win v4.2.3 back in another PC to convert the database.

The removal of the Project324 tool was not explicitly mentioned in the changelogs of Ple4Win v4.3.x on the Ple4Win website. Okay I can understand that this tool has been removed from the v4.3.x, but due to legacy reasons this tool should be available online (as a standalone version on the Ple4Win website like the old PLE3 v3 technical software notices; the helpfile should be updated then) to convert a old PLE v3 project file to a v4.2.3 project file. The tool should work standalone without a hardware license key to make it compatible for all future Ple4Win versions. So after a user has converted a project file with the Project324 tool to a v4.2.3 Ple4Win database it can be runned in a v4.3.x Ple4win version and will be converted internally to the latest v4 database standards during loading of the project file.

Infinite loop during cancelling Visualisation

Tue, 26 May 2015 11:42:36 +0200

Affected version: Ple4Win Professional v4.3.1 build 15032

When one clicks on the roadmap by accident during activation of the Visualisation module the program will stay in an infinite loop.

Procedure to reproduce the issue:
Step 1: Open Ple4Win and import the attached XLS file;
Step 2: Do a NEN 3650-2 calculation by selecting NEN 3650-2 in DF1;
Step 3: Process all DFs;
Step 4: Go to table NENSMAX and view the (Element, Sv/f(Reb)-M) and click on the visualisation button;
Step 5: Click on the roadmap at DF5 with your mouse during opening/activating of the visualisation window. This step was done by accident.

After step 5 you will see the screenshot given below.
Cancelling will not happen and Ple4Win will stay in an infinite loop!
is the only solution to cancel the program.

[attachment=710]