PCA Release Notes

Refer to PCAChangeLog for further version information.

7.5.0 up to and inclusing 7.7.0
  • Due to an error in PCA, when the tolerance band of the controller deviation is displayed in the internal scope (MFU -> Internal Scope), only the absolute tolerance and not the relative one is displayed. (27.10.20 - DS)
    This issue will be fixed in future versions of PCA
All versions up to and including 7.7.0
  • The Tools -> Generate ACU_PARA.TXT file command is only executed correctly if an MFU is connected via USB. (21.10.20 - DS)
    Due to an error in PCA, it is not possible to create an ACU_PARA.TXT when PCA is in offline mode.
    Workaround
    Connect any MFU to PCA and make sure that the USB connection is active. Then the command is executed.
    This issue will be fixed in future versions of PCA.
7.7.0
  • Updates using the "frm_FW_Update" form sometimes fail. (09.09.20 - DS)
    Due to an error in the "frm_FW_Update", updates of firmware are only possible that have the old FSP045 depth of 6 bytes. If a FW is to be updated, in which the FSP has a depth of 7 bytes, the update fails.
    Workaround
    Use the update option via the USB flash drive.
    This issue will be fixed in future versions of PCA.
  • Running Tools -> ACU Module Test -> Load files generates an error message. (27.08.20 - DS)
    Due to an error when creating the setup routine, a few files are missing in the directory "C:\Program Files(x86)\PowerConfigAdvanced\TestFiles" after installation.
    These are only necessary for the functionality of PCA if module tests (Tools-> ACU Module Test) are carried out.
    Workaround
    Download the following archive: TestFiles.zip, unzip it and add its content to the installed PCA version.
  • Running Tools -> QR Code Gerenrator generates an error message. (28.08.20 - DS)
    Due to an error when creating the setup routine, a DLL library is missing in the directory "C:\Program Files (x86)\PowerConfigAdvanced\bin\Release" after installation.
    For the functionality of PCA, this is only necessary if QR codes are to be created (Tools-> QR Code Generator).
    Workaround
    Download the following file: MessagingToolkit.QRCode.dll.zip, unzip it and add it to the installed PCA version.
All versions until today
  • If an old .xpc7 configuration is opened that contains a large number of controls that are no longer available in the new version of PCA or are under a new name, the message about this may not show any relevant details. The info label is empty. (12.08.20 - DS)
    The reason for this is that the maximum permitted number of 65,536 characters for the label has been exceeded.
    Workaround
    Answer the question whether the information should be saved in a file with YES. The text file generated contains all information.
Probably all versions up to and including 7.6.3
  • If slow processes are recorded with the MFU int. Scope (slower than the readout process), the scope is read twice. This leads to incorrect artifacts in the display. (09.07.20 - DS)
    Workaround
    Stop the scope acquisition immediately after the first reading. Otherwise, the correct image will be overwritten incorrectly during the second readout.
    This issue will be fixed in future versions of PCA.
  • .xrep files may not open. (03.07.20 - DS)
    Workaround
    Please open the file in a text editor.
    If the 2nd line does NOT contain the entry: "PowerConfigAdvanced_ReportFile_XREP", replace the entry there.
    Save and close the file.
    PowerConfigAdvanced should now be able to open it.
    This issue will be fixed in future versions of PCA.
  • When creating a PDF report, the message "Debugging please in" mod_XMLHandling_SearchModulesInTheXMLFile "" may appear. (03.07.20 - DS)
    The reason for this are missing or changed entries for the module description in the .xrep file.
    This message can be ignored. Only, the "Firmware information" table of the report remains empty.
    This issue will be fixed in future versions of PCA.
  • The file name in the footer of the PDF report is incorrect. (03.07.20 - DS)
    There is the name of the .xrep file with the extension .pdf and not the selected PDF file name.
    This issue will be fixed in future versions of PCA.
  • It may happen that the loaded configuration is not displayed in offline mode if another configuration was already loaded. (03.07.20 - DS)
    Workaround
    Close PCA and open the new configuration by double-clicking on the configuration file.
    This issue will be fixed in future versions of PCA.
7.6.3
  • Logbucheinträge werden beim Auslesen immer als fehlerhaft angezeigt. Ursache ist ein falscher <> Vergleich.
    Beschädigte Einträge werden nicht angezeigt. Auch hier ist die Ursache ein falscher <> Vergleich. (14.11.19 - DS)
    Workaround
    Beim Auslesen bestätigen, dass zukünftige fehlerfahfte Logbucheinträge ignoriert werden sollen.
    Es werden alle nicht fehlerhaften EInträge korrekt angeziegt.
7.6.2
  • When creating a new MFU form, the gain for the DACs on the MFU'System configuration / disgnosis tab is set to 0.000 volts. Therefore, the DAC output does not work. (22.08.19 - DS)
    Workaround
    Set the DAC gains to 1.0000 volts and send the parameters to the MFU.
    This issue will be fixed in the next version of PCA
All versions up to and including 7.6.2
  • Because of a problem in converting read ADC offset values, the display of them in "PCA-ADCCalibration'Measured Offset" may be wrong depending on the value. (15.08.19 - DS)
    This issue will be fixed in the next version of PCA.
7.6.0
  • Due to some problems it is strongly recommended to use version 7.5.0 or 7.6.1. (28.05.19 - DS)
All versions up to and including 7.4.0
  • In the "Remote Control" MFU tab under "Controller Status" sometimes not all information is displayed correctly. (08.02.19 - DS)
    This issue will be fixed in the next version of PCA.
  • If an ADCDACIO module Ver. II is used together with an MFU FW < 7.4.0, the parameters of the ADCDACIO module are not transferred to the MFU as long as the "EnvironmentRefreshGaugeableValues" key is not activated. (08.02.19 - DS)
    Workaround
    Activate the function "EnvironmentRefreshGaugeableValues" before transferring parameters. This only applies to MFUs with FW versions < 7.4.0.
    This issue will be fixed in the next version of PCA.
All versions up to and including 7.2.1
  • In the function generator of the MFU, Lowermost value and Top value must never have the same value. In addition, Lowermost value must always be smaller than top value. (17.10.18 - DS)
    If modules do not really have these HW versions, the configuration files must be corrected manually, if a module migration is to be carried out with PCA. (29.08.18 - DS)
    This issue will be fixed in the next version of PCA.
  • When an XREP file is opened and "Save" is pressed, only the device configuration is saved in the .XREP file. The device acceptance is completely lost. Since the .XREP is automatically saved after every successful acceptance point, manual saving is not necessary. (29.08.18 - DS)
    Workaround
    If, on the other hand, the configuration of the acceptance is to be saved, please use the "Save As" function and save the configuration as an .XPC7 file.
Version 7.1.1
  • If an .xtst file is created, there are broken XML elements in it. This prevents the reopening of the created .xtst file. Opening the file aborts with an error message, PCA can then no longer be operated. (17.10.18 - DS)
    Workaround
    Remove the spaces in the broken XML elements to make the file usable. Open the created .xtst file and change the XML start elements and XML end elements in lines 4 to 6 from "File data" to "FileData", "File time" to "FileTime" and "PCA version" to "PCA_Version". Make sure the start and stop elements are scrubbed exactly the same. Then save the file.
    This issue will be fixed in the next version of PCA.
Version 7.0.0
  • If configuration files are saved with this version, the following XML elements are saved erroneously:<iFWMajorRelease> with 7, <iFWMinorRelease> with 0 and <dFWRelease> with 7.0. (17.10.18 - DS)
    If modules do not really have these HW versions, the configuration files must be corrected manually, if a module migration is to be carried out with PCA. (17.10.18 - DS)
    Workaround
    Please contact the PCA support.

-- DerekSchupp - 2018-10-17
Topic revision: r24 - 2020-10-27, DerekSchupp
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding GSI Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)