Quartz sync: Jan 30, 2024, 9:15 AM

content/Application Notes/ProfDia/Combined Inner- and Outer contours.md

@@ -0,0 +1,56 @@
+---
+dg-publish: true
+---
+
+## Preparing DXF contour
+
+![[comb_innerouter_001.png]]<br>
+The DXF path has to be prepared in a way that:
+
+1.  The wire is clear from PCD and tool body at the end points of the
+    contour
+2.  The X-coordinate of contour start point and end point is not
+    identical, because the software has to determine the "main profile
+    direction" (blue arrow) from the difference of X-start-point and
+    X-end-point
+
+## Determining the "machining mode"
+
+![[comb_innerouter_002.png]]<br>
+Due to the detected "main profile direction" (blue arrow), with the above
+contour example, the situation fits to the upper right sketch in the
+profile window. This means "Outer machining" has to be selected in this
+situation.
+
+------------------------------------------------------------------------
+
+![[comb_innerouter_003.png]] <br>
+With this selection the relief angles on the outer contour section will be
+applied according to the general settings. But for the inner contour
+section the radial relief angle has to be applied in opposite direction.
+To enable this, the checkbox "Angle valid for entire profile" has to be
+unchecked.
+
+### Edit individual angles
+
+![[comb_innerouter_004.png]]<br>
+With the setting above the button "Edit individual angles" can be used to
+open the geometry window for setting individual relief angles for each
+contour element. In this window each contour element of the inner
+contour section (beginning with the vertical line on the front end) has
+to be identified and a suitable negative "Radial relief angle" has to be
+assigned.
+
+### Setting the "Backw. Path **B**"
+
+For a "collision free" escape from the inner contour end point the
+"Backw. path" has to be extended. With this setting the machine will
+move 8mm in X-direction before moving in Y-direction (Purple lines in
+simulation) .
+
+The simulation also shows the correct change to the negative radial
+relief for the inner contour section
+
+![[comb_innerouter_005.png]]<br>
+
+![[comb_innerouter_006.png]]<br>

content/Application Notes/ProfDia/Programming Additional Relief Angles.md

@@ -0,0 +1,57 @@
+---
+dg-publish: true
+---
+
+
+![[ang_offset_prog_001.png]]
+
+For tools with small diameters it is very important to make
+sure that the relief surface has clearance to the enclosing circle all
+around. The first and second relief angles which can be specified in the
+ProfDia profile section window are not able to ensure this when the tip
+thickness is big in relation to the tool diameter. The sketch shows that
+the second relief angle would leave a lot of material outside the
+enclosing circle.
+
+------------------------------------------------------------------------
+
+![[ang_offset_prog_002.png]]
+
+To remove the remaining material ProfDia offers the possibility to create
+further profile sub sections with the same contour and to execute these
+cuts with angular offsets to the initial angular position. It is
+possible to add as many additional cuts as necessary to get clearance
+all around.
+
+------------------------------------------------------------------------
+
+![[ang_offset_prog_003.png]]
+
+The example sketch shows the situation after five cuts with increasing
+angular offsets. With an additional cut (using a separate DXF contour,
+0° radial relief and 180° angular offset) the rear of the tip is trimmed
+in a definite distance to the centre. The desired shape of the relief
+surface can be determined by modifying the angular offset and the relief
+angle in every sub section. To get suitable parameters the best way is
+to draw the desired shape and to determine the parameters in the sketch.
+For the example above there is one main profile section which is just
+used for measuring. All other sections are moved to the right as sub
+sections and inherit the measuring data from the main section. The
+profile section names explain what each sub section is doing.
+
+------------------------------------------------------------------------
+
+![[ang_offset_prog_004.png]]
+
+**Important parameters**:
+
+In the main profile section the "Minimum diameter for rake angle
+calculation" has to be set to a value below the smallest diameter of the
+tool
+
+In the sub sections for the additional relief angles the "Offset to
+angular position" has to be set to the appropriate value. If the
+parameter "Offset to angular position" is not visible in "Additional
+parameters" this option has to be activated by opening the "Feature
+Manager" (ProfDia program folder on the desktop). Then switch on the
+item "Parameters for angular and contour offset".

content/CodeMeter/Create CodeMeter Content File.md

@@ -0,0 +1,28 @@
+---
+dg-publish: true
+---
+
+### Q: How can I manually create a control file for a CodeMeter Dongle?
+
+### A: Create CodeMeter Content file for remote activation
+
+> [!hint]
+> If you have an up to date verion of the ProfDia Toolbox (2019 or later) you can use     the inbuild function.
+> Otherwise you can create a control file as described in this chapter.
+> 
+
+
+1. Ensure that the Dongle is plugged in and the CodeMeter runtime is installed.<br>
+2. Right click on Windows Desktop<br>
+3. Select new > Wibu Control File<br>
+![New WIBU Document: Select type](images/CodeMeterControlFile_01.png)<br>
+4. CmDongle Remote Programming Context-File is selected by default<br>
+5. Click on create<br>
+![Firm Codes CmDongle](images/CodeMeterControlFile_02.png)<br>
+6. Make sure that the item **100160** is selected and Click on ok<br>
+7. Wait for the process to be finished<br>
+![CmRmtAct64](images/CodeMeterControlFile_03.png)<br>
+8. Click ok to close the dialog<br>
+9. Find the newely created file "MyCodeMeter.WibuCmRaC" on the Windows Desktop<br>
+![Cm File](images/CodeMeterControlFile_04.png)<br>
+10. Send this file by e-mail to your GTR contact.<br>

content/CodeMeter/Network Error 100.md

@@ -0,0 +1,17 @@
+---
+dg-publish: true
+---
+
+### Q: Error: A network error occured, Error 100
+
+### A: Dongle not in PC or a Network problem
+
+![[A_network_error_occured_ Error_100.png]]
+
+1. Ensure that the Dongle is plugged in and the CodeMeter runtime is installed.<br>
+2. Check your Network connection<br>
+3. Insert ProfDia Dongle directly into PC<br>
+4. Check if it's working now.
+
+The error message can also come up, when the requested license is not coded on the found / plugged in license key.
+

content/CodeMeter/No Entry Found Error 200.md

@@ -0,0 +1,23 @@
+---
+dg-publish: true
+---
+
+### Q: CodeMeter Runtime Error: Cm Container Entry not found, Error 200
+
+### A1: Dongle damaged or runtime problem
+
+![Error Message](images/CodeMeter_NoEntryFound_200.png)<br>
+
+
+1. Restart the PC / machine<br>
+2. Plug out the CM Dongle<br>
+3. Open the CodeMeter Control Center (Icon in the Windows Taskbar) by double clicking on it ![Runtime Icon](images/CodeMeterRuntime_Icon.png)<br>
+3.1 When no Windows taskbar is visible, open Windows Explorer and enter CodeMeterCC.exe as address and press enter
+4. The icon should be colored gray, showing that no CM stick is inserted.
+5. Re-Insert the GTR CM Dongle
+6. The CM Dongle must now be shown in the control center.
+
+### A2: License missing
+
+This problem can also occur, when the requested license is not found on the plugged-in license key.
+

content/Database/BDE (Borland Database Engine)/Tips and Tricks.md

@@ -0,0 +1,31 @@
+---
+dg-publish: true
+---
+
+On this page all known problems related to the BDE database engine will be listed with a possible solution.
+
+## BDE Error 2501
+
+**Error message:**
+Exception EDBEngineError in module Prdncsrv.exe at "00205166" An error occurred while attempting to initialize the Borland Database Engine (error $2501)
+
+![[bde2501_003.png]]
+
+
+**Possible cause:**
+When this error occurs it is possible you don't have enough space available.
+
+**Solution:**
+
+-   Control Panel > Open BDE Administrator 
+-   At the left tabs select the configuration tab
+-   Here select the subitem System > INIT
+-   In the right view, increase the SHAREDMEMSIZE value from 2048 to 4096.<br> ![[bde2501_001.png]]
+
+- Confirm the change with ENTER. For safety, click with the mouse in another field to force the PDC administrator to recognize the change.
+-   When you close the BDA Administrator, you will be prompted to accept the changes. Confirm this with Yes. 
+
+
+
+![[bde2501_002.png]]
+

content/Database/Firebird/Change Password.md

@@ -0,0 +1,81 @@
+---
+dg-publish: true
+---
+
+# Change Password for a Firebird Database user
+
+The default credentials for FireBird are
+
+| | |
+|--- |--- |
+|Username: | SYSDBA |
+|Password: | MASTERKEY |
+
+If this default settings need to be changed follow the guide below
+
+## Change Password for Database
+
+- Open a Terminal (cmd or PowerShell)
+- Enter the directory of the gsec.exe by entering the following command:
+
+````sh
+ cd '.\Program Files (x86)\Firebird\Firebird_2_5\bin\'
+````
+
+![](images/fb_001_changepwd.png)
+
+call gsec.exe to set a new password like shown below:
+
+
+![](images/fb_002_changepwd.png)
+
+````sh
+.\gsec.exe -user sysdba -password masterkey -database "C:\Program Files (x86)\Firebird\Firebird_2_5\security2.fdb"
+````
+
+you should now be inside the **gsec** shell.
+
+The line is starting with **GSEC>** (the above screenshot)
+
+Enter the next command to change the password:
+
+````sh
+
+modify sysdba -pw correct_horse_battery_staple
+
+````
+
+
+> [!note] 
+>   Replace the **correct_horse_battery_staple** with your password[^1]
+
+> [!warning] 
+>  The new password can only be 8 digits long, otherwise only the first 8 digits are used
+    
+leave the **GSEC** shell by entering quit
+
+````sh
+quit
+````
+
+
+## Adjust Configuration
+
+Start ProfDia / ExProg Toolbox and open the **Database configuration** tab
+
+Click **Load from INI** to load the current configuration
+
+![](images/fb_003_changepwd.png)
+
+Enter the new password in the password field and apply the changes by pressing the **Setup Database** button.
+
+The database configuration will then be updated accordingly.
+
+For additional security the checkbox **Encrypt Passwords** can be checked.
+
+> [!note] 
+> For the encrypted password option, the file **EncryptionModule.dll** must be available inside the program folder. Please make sure that the file exists before enabling this option.
+> 
+> The password will then be stored as an **AES-256** encrypted string.
+
+[^1]: [Link](https://xkcd.com/936/)

content/Database/Firebird/Setup Common Firebird Server.md

@@ -0,0 +1,4 @@
+---
+dg-publish: true
+---
+To be added

content/Database/Microsoft SQL Server/Migrate from Firebird to MSSQL.md

@@ -0,0 +1,64 @@
+---
+dg-publish: true
+---
+>[!summary] 
+>When the BDE database was migrated to Firebird in a first step, or a company decides to move from Firebird to MS SQL at a later point, this guide can be used
+
+
+## Preparation
+
+- Copy the existing database configuration file **NCPro_DB.INI** file in the application directory to **NCPro_DB_Source.INI**
+- Start an up to date version of [ProfDiaToolbox](http://pubfiles.gtr.de/ProfDiaToolbox.zip)
+- Go to **Database Configuration**
+- Click on Load From INI
+
+![[Pasted image 20231024152108.png]]
+
+- Adjust the elements at (1) and (2) according to your new MS SQL Server
+
+![[Pasted image 20231024152320.png]]
+
+When the modifications are entered, click on **Setup Database** then **Test Connection**
+
+When everything was setup correct, the success message should pop up
+
+![[Pasted image 20231024153007.png]]
+
+otherwise an error message showing the actual problem will be shown.
+
+When the connection to the new Database can be established continue with the next step
+
+## Data Migration Standard Procedure
+
+![[Pasted image 20231025111724.png]]
+
+- open the **Migrate/Merge SQL->SQL** tab
+- Copy the absolute path to your "old" database configuration in the **Source Database Config File** field
+- Copy the absolute path to your updated database configuration in the **Target Database Config File** field
+
+
+![[Pasted image 20231025112745.png]]
+
+- When the target database is empty (default), click on the **migrate** button to start the database migration
+- Wait for the process to be finished
+- When everything is done, the ProfDia Toolbox can be closed and the new database is ready for use
+
+## Data Migration Special Cases
+
+The first migration to the new database has to be done like described above in [[#Data Migration Standard Procedure]].
+
+>[!note]
+>The migration script has to be run from the PC having the access rights to the original source database
+
+
+As soon as the database already contains some projects, the **Merge Settings** have to be applied.
+
+![[Pasted image 20231025113256.png]]
+
+- Check the **Use Merge Mode** option and select the merge type:
+
+| Type | Description |
+| --- | --- |
+| Skip Existing Projects | Only projects that are not already stored in the new database will be added |
+| Overwrite Existing Projects | New projects will be added and existing projects will be overwritten |
+| Add with Suffix | All projects from the source database will be added with the **Suffix** value (e.g. original project: 12345, migrated project: 12345_MachineID ) |