Problem: After building a PG5 2.1 project which does include smart RIO Network the error message " Fatal Error 2004: File specified more than once: Device1.obj " appears. Reason [...] App Firmware 1.22.48 (March 2015) Main corrections FTP error due of username cgi access trough SBC.NET Solved problem when downloading .sprg file in PG5 with download [...] ! Solution Please use Saia PG5®2.0.210 which corrects will no longer be concerned of this problem
Problem: After building a PG5 2.1 project which does include smart RIO Network the error message " Fatal Error 2004: File specified more than once: Device1.obj " appears. Reason [...] App Firmware 1.22.48 (March 2015) Main corrections FTP error due of username cgi access trough SBC.NET Solved problem when downloading .sprg file in PG5 with download [...] ! Solution Please use Saia PG5®2.0.210 which corrects will no longer be concerned of this problem
An Easy Template is a collection of graphical elements on a px page. There are standard options available how px files represent themselves. The user can decide to have either an overlapping [...] Problem In relation with the DeviceTemplate, there can be a problem on the Saia PCD Supervisor, which occurs after an automatic logout, a restart of the station or a restart of the web server [...] latest visited ord. This cookie is valid until page is closed or reloaded. he deviceTemplate cannot prevent this from happening. The problem occurs in all Saia PCD Supervisor versions
Plugable memory modules PCD3.Rxxx,PCD7.Rxxx Link to PCD3.R550 (File System) page Link to PCD3.R600 (SD Card holder) page [...] losses. In case a telegram was lost (due to network problems) the transfer was interrupted by the PCD firmware. Because of the interruption the BACnet firmware was not notified, but it remained in a state [...] . Problem A configuration calculated with the old Excel sheet did not have the same current limitation for the CPUs. The same configuration is maybe rejected by the Device Configurator. Reason The
Plugable memory modules PCD3.Rxxx,PCD7.Rxxx Link to PCD3.R550 (File System) page Link to PCD3.R600 (SD Card holder) page [...] losses. In case a telegram was lost (due to network problems) the transfer was interrupted by the PCD firmware. Because of the interruption the BACnet firmware was not notified, but it remained in a state [...] . Problem A configuration calculated with the old Excel sheet did not have the same current limitation for the CPUs. The same configuration is maybe rejected by the Device Configurator. Reason The
Documentation Technical Reports Software / Tools EPLAN product macros, DWG and DXF files can be found here Softwaretool for printing on the Labeling-Strips for PCD [...] losses. In case a telegram was lost (due to network problems) the transfer was interrupted by the PCD firmware. Because of the interruption the BACnet firmware was not notified, but it remained in a state [...] . Problem A configuration calculated with the old Excel sheet did not have the same current limitation for the CPUs. The same configuration is maybe rejected by the Device Configurator. Reason The
3.M6xx7 Central processing units (xx7) Documentation Software / Tools EPLAN Product Macros and DXF Files can be found here. Saia PCD®xx7-series Device [...] losses. In case a telegram was lost (due to network problems) the transfer was interrupted by the PCD firmware. Because of the interruption the BACnet firmware was not notified, but it remained in a state [...] . Problem A configuration calculated with the old Excel sheet did not have the same current limitation for the CPUs. The same configuration is maybe rejected by the Device Configurator. Reason The
moving the file manually you can solve the problem. The old folder used by PG5 2.0.110: "c:\Documents and Settings\All Users\Application Data\Saia Burgess\" The new folder used by PG5 2.0.150 and later [...] . Solution: Every time when you connect an old motor with a frequency converter, connect between the devices a sinus filter to avoid such kind of problem [...] version" but not both in parallel; this could lead to inconsistent file combinations
floating point registers are not correctly detected (if PG5 2.0.210 or earlier is used). Instead of floats they are configured as integers. Reason The symbol files generated by PG5 2.0.210 (and [...] . Solution PG5 2.0.220 adds the indications again to the symbol files. If only an older version of PG5 2.0 can be used the following work-around could be applied: the configuration can be corrected [...] Possibility to export/import the header line on the export/import file. OPC Server version 2.02.17.20 (January 2014) New features Support of PG5 2.1.120 or later enhance the
files generated by PG5 2.0.210 (and earlier) are missing the indication to be a floating point register (a {F} in the comment of the symbol). As this indication is missing, the OPC Server can not figure out it is a floating point value. Solution PG5 2.0.220 adds the indications again to the symbol files. If only an older version of PG5 2.0 can be used the following work-around could be applied [...] Possibility to export/import the header line on the export/import file. OPC Server version 2.02.17.20 (January 2014) New features Support of PG5 2.1.120 or later enhance the
