-
PCD2.M4x60
-
Central processing units
-
The freely programmable PCD2.M4x60 controller is based on a flat, space-saving housing design that has been used successfully for many years in OEM and project business.
It has four freely assignable slots for input/output modules and can be extended for up to 1,024 data points.
It has sufficient processor power and a 2 MB user program memory to ensure to handle demanding communication tasks with up to 14 interfaces.
Operating data is saved by non-volatile FRAM technology to ensure maintenance-free (no battery) operation.
Documentation
System Catalogue : PCD2
Extract | 26-215_A0140 | System Catalogue : PCD2 |
PCD2.M4x60
Flyer | PP31-048 | PCD2.M4x60 |
PCD2.M4160, PCD2.M4560
Manual | 27-648 | PCD2.M4160, PCD2.M4560 |
PCD2.C1000 Extension module holder for 4 I/O mod.
Datasheet | 31-531 | PCD2.C1000 Extension module holder for 4 I/O mod. |
IO-Modules
Manual | 27-600 | IO-Modules |
Systemcable and adapter
Manual | 26-792 | Systemcable and adapter |
PCD2.F2xxx - serial interface modules
Manual | 27-649 | PCD2.F2xxx - serial interface modules |
File System and FTP Server
TCP/IP - Ethernet for the Saia PCD® Serie
Manual | 26-776 | TCP/IP - Ethernet for the Saia PCD® Serie |
TCP/IP-Enhancements
Manual | 26-867 | TCP/IP-Enhancements |
App notes incl. examples PPP, DHCP, DNS and SNTP
Info | Application Notes | App notes incl. examples PPP, DHCP, DNS and SNTP |
Leaflet: PCD2.M4x6x
Leaflet: PCD2.C1000
Readme | 35-006 | Leaflet: PCD2.C1000 |
Saia PCD2.C1000 extension module holder
ENG04 |
![]() |
0.16 MB | Download |
Leaflet: PCD2.C2000
Readme | 35-007 | Leaflet: PCD2.C2000 |
Saia PCD2.C2000 extension module holder with internal power supply
ENG08 |
![]() |
0.17 MB | Download |
Firmware used in production
The actual COSinus FW is available from the COSinus firmware page.
Good to know

- PCD2.M4x60 with hardware version A and B dosen't support the use of analog/ISDN or GSM modems.To use modems on a PCD2.M4x60 it's necessary that the PCD2.M4x60 have a least a hardware version C and the FW 1.26.15, see FAQ 101986
- To support the PCD7.W600 it's also necessary to use the hardware C or newer of the PCD2.M4x60.

PCD2 / M4x60
-
How to know whether the circuit board of the PCD is fitted with a Swissbit micro-SD memory card? (FAQ #102070)
It is only possible to determine whether the PCD's circuit board is fitted with a Swissbit micro-SD memory card by visual inspection.
The attached document describes how to know whether the circuit board of the PCD is fitted with a Swissbit micro-SD memory card.
-
How to copy csv-Files and Webeditorproject files which are stored on the Intflash of a PCD, if you are replacing an internal micro-SD memory card which is used on the circuit board of the PCD? (FAQ #102069)
The attached document describes how to proceed if you want to copy csv-Files (e.g., from HDLog) and Webeditorproject files which are stored on the Intflash of a PCD.
This could be useful if you are replacing an internal micro-SD memory card which is used on the circuit board of the PCD and you want to re-use the files stored on the old micro-SD memory card.
-
What is stored on the micro-SD memory card which is used on the circuit board of the PCD? (FAQ #102068)
Newer PCD types and newer PCD7.D4xx devices have micro-SD memory card (uSD) on the PCB (printed circuit boards)
The following data’s are stored on the this uSD card on the PCD’s PCB:
- Firmware for the PCD
- Device configurator settings (PG5)
- Application program done with PG5
- Webeditor 8 project (PG5)
- DATA (e.g HDLog) created by the application program in runtime
- Setup, Calibration (PCD7.D443, PCD7.D450, PCD.D470)
- Program Backup on internal Flash
-
How can the micro SD memory card on the circuit board of a PCD controller be replaced? (FAQ #102067)
In some cases, it is necessary to replace the micro-SD memory card (uSD) of the PCD.
This FAQ describes how to replace the micro-SD memory card (uSD) which is mounted on the PCD controller's PCB (printed circuit boards)
The attached .pdf describes how to replace the micro-SD memory card (uSD) used on the PCB of the PCD
-
It's possible to connect SBC PCD's directly to the internet? (FAQ #102060)
Yes it’s possible to connect a PCD directly to the internet, but you have to protect your PCD against unauthorised access or cyber-attacks.
To protect the PCD against unauthorised access or cyber-attacks, it’s imperatively needed to take some protective measures.
Information about protective measures can be found on the support hp
If you need a PCD with cyber security levels SL3+ and based on ANSI ISA 62443 then checkout our PCD3.M6893 (QronoX PCD), this PCD was developed for cybersecure applications.
Information's can be found here.
-
What are the differences between the COSinus firmwares FW 1.28.11 and FW 1.28.51? (FAQ #102058)
In January 2024:
the COSinus BACnet FW 1.28.59 was put on the support homepage.In April 2022:
the COSinus FW 1.28.51 was introduced into production for the systems:- PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60 and PCD3.M6880.
In February 2019:
the COSinus FW 1.28.37 was released as maintenance version for the systems:- PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668.
In June 2017:
the COSinus FW 1.28.16 was introduced into production for the systems:- PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668.
the BACnet and LonIP FW 1.28.51/1.28.59 was put into production, which do support the BACnet Revision 14.
To support the BACnet Revision 9 it's necessary to use the PCD and the BACnet FW 1.26.xx.Attention:
The firmware 1.28.xx or later can be used only on the following PCD's with 8 MB onboard firmware memory:
PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668
The table below does show the hardware dependencies in relation with the COSinus firmware versionsDo use at least the PG5 firmware downloader version 2.1.311 or newer (included in PG5 patch 2.1.311 or newer) to prevent the loading of the FW 1.24.xx, 1.26.xx or newer to a not compatible PCD
Firmware 1.28.59 (only BACnet firmware) (January 2024)
Main corrections
- BACnet: MI/MO/MV objects, invalid values for Alarm_Values and Fault_Values are rejected
- BACnet: BI/BV/BO objects, present value of can only be 0 or 1
- BACnet: COMMAND object, present value writing returns an error if bigger that the number of actions
- BACnet: Trendlog objects, property value check is done according to specifications
- BACnet: Limit COV subscription to 3000 and send PDU-Error if length of response is too big
- BACnet: Disable I-Have response when state is disable / disable-init
- BACnet: Calendar Object Date List, don’t allow wild card in this property entries
- BACnet: writing invalid array to Array properties returns correct Error code
- BACnet: Pulse Converter Object, send out-of-range PDU-Error if count processing is < 0
- BACnet: Controller goes to HALT with SWTO error
- BACnet: MS/TP Controller goes to HALT with SWTO error
- BACnet: Schedule accepts Sundays in Week and Day
- BACnet: GetEnrollmentSummary: correct reply if list is empty
Firmware 1.28.51 (April 2022)
Main corrections
- All PCD’s: Saia PCD Modbus diag does not work if diag flag > 9999
- All PCD’s: SNTP and hardware RTC is diverging from more than 2 seconds, then History message ‘RTC Fail error’ is generated
- All PCD’s: SNTP Time synchronization does not work with DHCP
- All PCD’s: E-Mails send from PCD could contain unwanted characters like 0 or others
- All PCD’s: S-Monitoring values for S-Monitoring bar graphs are sometime wrong
- All PCD’s: S-Monitoring Year graph scaling displayed wrongly
- All PCD’s: TCP, open data mode protocol, communication is blocked after rejection of 32 connections
- All PCD’s: LonIP CSF is locked when an error occurs
- PCD2.M45x0: SRXM does not support FB parameters as operand 3 and 4 for source and destination
- PCD1.M2220-C15: Watchdog LED does not follow Relay when PCD goes in STOP or HALT
- PCD3.M6880: Data exchange between CPU 0 and CPU 1 does not work reliable if STL instruction is used
- BACnet: Calendar state not updating after add/remove list element service
- BACnet: Exception schedule writing to certain array index fails
- BACnet: Schedule crashes with SWTO error
- BACnet: MS/TP client properties are not written if many values change simultaneously
- BACnet: Problem reliability & out of service, reliability is not written when oos is high
- BACnet: Web CGI commands to read BACnet platform tags like ..AddFW,Version,BACnet don’t work
- BACnet: Web scheduler/calendar templates do not work
- BACnet: PCD3.M6860 no BACnet communication on ETH2 if router is used
- BACnet: Rev 4 not working with Name based Client
- BACnet: Rev14 does not allow high limit value below 5 on analogue input
Firmware 1.28.37 (February 2019)
New features
- All PCD’s: FW extension to close all open FTP connections
- BACnet: Calendar objects have been extended with a synchronization mode. Each server calendar object can be configured as Slave or Master calendar
- BACnet: New mappings for alarming counters have been added to Notification-Class objects.
- BACnet: The PCD will now accept AcknowledgeAlarm service requests, which use complete wildcards as timestamps.
Main corrections
- All PCD’s: On S-Bus data mode, if S-Bus CRC contains a S-Bus DLE as last character then S-Bus telegram is incorrect and not accepted from S-Bus recipient. (Since FW 1.28.20)
- All PCD’s: Not all bytes are transmitted when working with MC4 or MC5 mode on F2xxx module
- All PCD’s: RS485 driver keep holding bus after a while
- All PCD’s: Http request ‘is modified’ is not handled correctly on the PCD Web-Server which lead to the effect that web project is not loaded correctly on the browser
- All PCD’s: PCD can crash when breakpoint is updated during conditional RUN
- All PCD’s: PCD can crash on download in run since FW 1.28.27.
- All PCD’s: PCD can crash on download in run when Graftec is used
- All PCD’s: PCD crashes when using browser to access the default page of PCD with "Display Root Content Enabled = YES"
- All PCD’s: RCOB does not start COB when it was stopped before with SCOB
- All PCD’s: Profibus communcation using onboard FDL port. The FCS test for SD2 telegram was not implemented correctly.
- All PCD’s: When S-Bus IP Nodelist is used it’s possible that the communication using nodes does no more work after execute a download in run
- All PCD’s: XOB parameter as Registers does not work if 16bit addressing was used
- All PCD’s: LonFT10: SNVT_obj_status and SNVT_obj_request can be used in user profiles
- PCD3.Mxx60, PCD3.T6xx, PCD1.M2xx0, PCD2.M4x60: usage of I/O media mapping slows done the cycle time 2 times in comparison to FW 1.26.xx
- PCD2.M4x60: Download LonIP config not possible
- PCD2.M4x60: RTC gets sometime corrupted data when PCD7.F7500 is used on PCD2.M4x60
- PCD2.M4x60: RTC Time is wrong after several days of run
- PCD7.D443WTxR: uBrowser use alphapad.teq even if screen is rotated by 90°
- PCD7.D443WT5R: History entry Memory ‘Lost -1’ written in the History
- BACnet; Event Enrolment does not work correctly with external reference devices.
- BACnet; When using BACNet Webvisu the memory used increase each time the scheduler is edited.
- BACnet; PCD crash when BACnet Webvisu edit scheduler.
- BACnet; BACnet WebVisu does not display correct value for the WeeklySchedule value.
- BACnet; ACK Required bit in notification message is not set according to the related NV ack_required bits
- BACnet: The PCDAlarmStatus mapping property does not work correctly.
- BACnet: Mappings, which changed to the value 0 directly after a program download, are not updated correctly on the BACnet property.
- BACnet: The Priority-Array mapping does not work correctly after startup.
- BACnet: Initialization of Puls converter count with input reference gives error
- BACnet: Fix issue with weekly scheduler.
- BACnet: Fix issue with WeekNDay entries
- BACnet: The Restore functionality over BACnet does not work, when the PCD has been reset over factory reset.
- BACnet: The Action property in the command object does not handle NULL datatype and priority entries correctly, if they are used in the ActionCommand. Additionally, the Action property can now be read via index.
- BACnet: Priority_Array entry 16 will be overwritten on startup with the last Present_Value mapping
- BACnet: Out of Service -> Value for PV overridden after reboot by Input ref
- BACnet: The Log_Buffer to csv conversion for trend-log objects does not skip time change entries
- BACnet: Unmapped Priority-Array property array entries are not stored persistent
- BACnet: BACnet configuration on the PCD is not deleted when "unlinked" from PG5
- BACnet: Change Client Time_Of_Restart mapping to Unix time
- BACnet: Client mapping - Threshold is not implemented correctly
- BACnet: Mapped Reliability properties within analogue objects does interfere with the objects functionality. When the Reliability is mapped, the mapping has not full control over the property value.
- BACnet: The program download fails, when the BACnet config contained notification-class objects with event-counter mappings
- BACnet: BACnet Trend-Log(-Multiple) data can’t be retrieved as csv data
- BACnet: The SubscribeCOVProperty service can’t be executed on complete Priority_Arrays
Firmware 1.28.16 (June 2017)
New features
- All PCD's: When push button is pressed while power on then do not update FW from FS in order to execute a delete all.
- PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668:
Enhancement for HTTP server to transparently support sending compressed files.
Main corrections
- All PCD's SBUS parity mode, correction when NAK character is received as first byte of response.
- All PCD's: When download new Ethernet-RIO Program with the option ‘Delete all backups’ it can happen that the RIO is not commission and no goes no more in ‘data exchange mode’ until the PCD reboots.
- All PCD's: When RIO name is not in upper case the RIO file is not updated until a restart is executed.
- All PCD's: When RIO file is downloaded with download changed RIO file then RIO file is not sent to RIO until a restart is executed.
- All PCD's: Ethernet Frame Padding Information Leakage fixed (CVE-2017-9628)
- All PCD's: The Modbus CSF CloseSRPort does not free the port then a open/SASI call give an error and the port does not work.
- PCD1.M2xx0 PCD1.M22x0 PCD2.M4x60: PCD can crash while power down when XOB 0 is programmed.
- PCD1.M2xx0 PCD1.M22x0 PCD2.M4x60: MC0 mode with start/stop flag working again.
- PCD7.D443WT5R: Alarming does not work since 1.28.00 FW.
- PCD7.D443WT5R: When watchdog timeout occurs PCD7.D443WT5R does't reboot and stays locked.
Firmware 1.28.11 (Arpil 2017)
New features
- All PCD's: Support of BACnet Revision 14
Main corrections
- All PCD's: Various Open Data Mode fixes: Read Timeout enhancement, Client Connection timeout and Client Keep alive with anonymous port issue fixed
- All PCD's: Modbus RTU on all ports but specially on the F2xx module has been corrected to handle the response timeout processing in the case that the response is just occurring at the moment of the timeout.
- All PCD's: Battery status shows FAIL also if battery module is missing.
All PCD's: Various minor issues fixed - PCD1.M2xx0 & PCD3+: 38400/115200 baud settings adjustment
- PCD2.M4x60: PCD7.F7500 initialization
-
On a PCD2.M4560 or PCD3.M5560, why the measured PT100 temperature values are not correct if the PT100 sensors are connected to PCD2.W220Z18 or PCD3.W220Z18 modules? (FAQ #102052)
If the PCD2/3.W220Z18 card is plugged in to a ‘Power PCD‘ or a PCD2.C1000 or PCD2.C2000 and if all 8 analog inputs channels of the PCD2/3.W220Z18 module are connected to 8 PT100 sensors then the measured PT100 temperature values of the 8 channels are not correct.
‘Power PCD’s’ are:
- PCD1.M2x20, PCD1.M2160, PCD1.M2220-C15
- PCD2.M5540, PCD2.M5440, PCD2.M4160, PCD2.M4560
- PCD3.Mxx60
To solve the issue, use and connect only up to 7 PT100 sensors to the PCD2/3.W220Z18 or do use a PCD2/3.W350 module, if all 8 PT100 are needed.
On the ‘old’ PCD’s like PCD2.M170 or PCD3.M5540 the PCD internal power supply V+ was at 24V
On the ‘new’ ‘Power-PCD’s’ and the PCD2.C1000 and PCD2.C2000 the V+ is 16,5V
The electrical design of the PCD2/3.W220Z18 was done in that the way, that the internal power V+ of 24V was required to handle all 8 PT100 channels.
Since the ‘Power PCD’s’ and the PCD2.C1000/C2000 have a V+ of 16,5V the driver on the PCD2/3.W220Z18 don’t have enough power to handle all 8 PT100 signals correctly.
To solve the issue, use and connect only up to 7 PT100 sensors to the PCD2/3.W220Z18 or do use a PCD2/3.W350 module, if all 8 PT100 are needed.
-
Why on a PCD3.M5/6xxx or a PCD2.M45xx the battery LED is switched on and the battery error message is activated in the application program after a new battery was inserted? (FAQ #102039)
The battery voltage is checked in the battery module for undervoltage and overvoltage.
New batteries have a too high voltage which causes the overvoltage limit to be exceeded.
Solution:
With the FBox 'PCD3.BAT0', selectable from the ‘System information’ family it is possible to switch off the overvoltage limit check on the battery module to prevent the battery LED from being switched on and the battery error message in the application program from being activated if the battery voltage is above the overvoltage limit.
The battery voltage check is performed in the battery module and the changes made by the FBox 'PCD3.BAT0' are stored in the battery module and not in the PCD3.M5/6, PCD2.M45xx.
As all information concerning the overvoltage limit check are stored in the battery module, it is possible to make the modifications in one PCD 'A' and after the modification, to insert the battery module in another PCD 'B'.
Battery modules with hardware version < C have a factory default battery undervoltage and overvoltage check.
Battery modules with hardware version >= C have the battery undervoltage test function ex works.
The battery overvoltage is not checked.After the FBox 'PCD3.BAT0' has deactivated the overvoltage limit check, modification 8 is activated on the battery module.
Picture shows a battery module with hardware version A and modification 1 and 3
The modification number is displayed also on PG5 Online configurator, hardware information.
After the usage of the FBox 'PCD3.BAT0' the following information is visible on the PG5 hardware information. (Modification 8 was added)
Modification number 8 is only activated for this purpose 'Overvoltage limit check disabled'.
After changes have been made with the FBox 'PCD3.BAT0', the 24VDC power supply to the PCD must be switched off and on again so that the changes relating to the battery LED, battery error message in the application program and the update of the modification number in the hardware information can be adopted.
More information are available on the online FBox help.
Overview battery module hardware version, modification, under- and overvoltage test.
The FBox library ‘SBC Maintenance’ which includes the 'PCD3.BAT0' FBox can be loaded from this FAQ, over the PG5 update manager and will be installed automatically with newer PG5 versions.
-
What are the differences between the COSinus firmwares FW 1.28.11 and FW 1.28.51? (FAQ #102010)
In April 2022:
the COSinus FW 1.28.51 was introduced into production for the systems:- PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60 and PCD3.M6880.
In February 2019:
the COSinus FW 1.28.37 was released as maintenance version for the systems:- PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668.
In June 2017:
the COSinus FW 1.28.16 was introduced into production for the systems:- PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668.
the BACnet and LonIP FW 1.28.16 was put into production, which do support the BACnet Revision 14.
To support the BACnet Revision 9 it's necessary to use the PCD and the BACnet FW 1.26.xx.Attention:
The firmware 1.28.xx or later can be used only on the following PCD's with 8 MB onboard firmware memory:
PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668
The table below does show the hardware dependencies in relation with the COSinus firmware versionsDo use at least the PG5 firmware downloader version 2.1.311 or newer (included in PG5 patch 2.1.311 or newer) to prevent the loading of the FW 1.24.xx, 1.26.xx or newer to a not compatible PCD
Firmware 1.28.51 (April 2022)
Main corrections
- All PCD’s: Saia PCD Modbus diag does not work if diag flag > 9999
- All PCD’s: SNTP and hardware RTC is diverging from more than 2 seconds, then History message ‘RTC Fail error’ is generated
- All PCD’s: SNTP Time synchronization does not work with DHCP
- All PCD’s: E-Mails send from PCD could contain unwanted characters like 0 or others
- All PCD’s: S-Monitoring values for S-Monitoring bar graphs are sometime wrong
- All PCD’s: S-Monitoring Year graph scaling displayed wrongly
- All PCD’s: TCP, open data mode protocol, communication is blocked after rejection of 32 connections
- All PCD’s: LonIP CSF is locked when an error occurs
- PCD2.M45x0: SRXM does not support FB parameters as operand 3 and 4 for source and destination
- PCD1.M2220-C15: Watchdog LED does not follow Relay when PCD goes in STOP or HALT
- PCD3.M6880: Data exchange between CPU 0 and CPU 1 does not work reliable if STL instruction is used
- BACnet: Calendar state not updating after add/remove list element service
- BACnet: Exception schedule writing to certain array index fails
- BACnet: Schedule crashes with SWTO error
- BACnet: MS/TP client properties are not written if many values change simultaneously
- BACnet: Problem reliability & out of service, reliability is not written when oos is high
- BACnet: Web CGI commands to read BACnet platform tags like ..AddFW,Version,BACnet don’t work
- BACnet: Web scheduler/calendar templates do not work
- BACnet: PCD3.M6860 no BACnet communication on ETH2 if router is used
- BACnet: Rev 4 not working with Name based Client
- BACnet: Rev14 does not allow high limit value below 5 on analogue input
Firmware 1.28.37 (February 2019)
New features
- All PCD’s: FW extension to close all open FTP connections
- BACnet: Calendar objects have been extended with a synchronization mode. Each server calendar object can be configured as Slave or Master calendar
- BACnet: New mappings for alarming counters have been added to Notification-Class objects.
- BACnet: The PCD will now accept AcknowledgeAlarm service requests, which use complete wildcards as timestamps.
Main corrections
- All PCD’s: On S-Bus data mode, if S-Bus CRC contains a S-Bus DLE as last character then S-Bus telegram is incorrect and not accepted from S-Bus recipient. (Since FW 1.28.20)
- All PCD’s: Not all bytes are transmitted when working with MC4 or MC5 mode on F2xxx module
- All PCD’s: RS485 driver keep holding bus after a while
- All PCD’s: Http request ‘is modified’ is not handled correctly on the PCD Web-Server which lead to the effect that web project is not loaded correctly on the browser
- All PCD’s: PCD can crash when breakpoint is updated during conditional RUN
- All PCD’s: PCD can crash on download in run since FW 1.28.27.
- All PCD’s: PCD can crash on download in run when Graftec is used
- All PCD’s: PCD crashes when using browser to access the default page of PCD with "Display Root Content Enabled = YES"
- All PCD’s: RCOB does not start COB when it was stopped before with SCOB
- All PCD’s: Profibus communcation using onboard FDL port. The FCS test for SD2 telegram was not implemented correctly.
- All PCD’s: When S-Bus IP Nodelist is used it’s possible that the communication using nodes does no more work after execute a download in run
- All PCD’s: XOB parameter as Registers does not work if 16bit addressing was used
- All PCD’s: LonFT10: SNVT_obj_status and SNVT_obj_request can be used in user profiles
- PCD3.Mxx60, PCD3.T6xx, PCD1.M2xx0, PCD2.M4x60: usage of I/O media mapping slows done the cycle time 2 times in comparison to FW 1.26.xx
- PCD2.M4x60: Download LonIP config not possible
- PCD2.M4x60: RTC gets sometime corrupted data when PCD7.F7500 is used on PCD2.M4x60
- PCD2.M4x60: RTC Time is wrong after several days of run
- PCD7.D443WTxR: uBrowser use alphapad.teq even if screen is rotated by 90°
- PCD7.D443WT5R: History entry Memory ‘Lost -1’ written in the History
- BACnet; Event Enrolment does not work correctly with external reference devices.
- BACnet; When using BACNet Webvisu the memory used increase each time the scheduler is edited.
- BACnet; PCD crash when BACnet Webvisu edit scheduler.
- BACnet; BACnet WebVisu does not display correct value for the WeeklySchedule value.
- BACnet; ACK Required bit in notification message is not set according to the related NV ack_required bits
- BACnet: The PCDAlarmStatus mapping property does not work correctly.
- BACnet: Mappings, which changed to the value 0 directly after a program download, are not updated correctly on the BACnet property.
- BACnet: The Priority-Array mapping does not work correctly after startup.
- BACnet: Initialization of Puls converter count with input reference gives error
- BACnet: Fix issue with weekly scheduler.
- BACnet: Fix issue with WeekNDay entries
- BACnet: The Restore functionality over BACnet does not work, when the PCD has been reset over factory reset.
- BACnet: The Action property in the command object does not handle NULL datatype and priority entries correctly, if they are used in the ActionCommand. Additionally, the Action property can now be read via index.
- BACnet: Priority_Array entry 16 will be overwritten on startup with the last Present_Value mapping
- BACnet: Out of Service -> Value for PV overridden after reboot by Input ref
- BACnet: The Log_Buffer to csv conversion for trend-log objects does not skip time change entries
- BACnet: Unmapped Priority-Array property array entries are not stored persistent
- BACnet: BACnet configuration on the PCD is not deleted when "unlinked" from PG5
- BACnet: Change Client Time_Of_Restart mapping to Unix time
- BACnet: Client mapping - Threshold is not implemented correctly
- BACnet: Mapped Reliability properties within analogue objects does interfere with the objects functionality. When the Reliability is mapped, the mapping has not full control over the property value.
- BACnet: The program download fails, when the BACnet config contained notification-class objects with event-counter mappings
- BACnet: BACnet Trend-Log(-Multiple) data can’t be retrieved as csv data
- BACnet: The SubscribeCOVProperty service can’t be executed on complete Priority_Arrays
Firmware 1.28.16 (June 2017)
New features
- All PCD's: When push button is pressed while power on then do not update FW from FS in order to execute a delete all.
- PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668:
Enhancement for HTTP server to transparently support sending compressed files.
Main corrections
- All PCD's SBUS parity mode, correction when NAK character is received as first byte of response.
- All PCD's: When download new Ethernet-RIO Program with the option ‘Delete all backups’ it can happen that the RIO is not commission and no goes no more in ‘data exchange mode’ until the PCD reboots.
- All PCD's: When RIO name is not in upper case the RIO file is not updated until a restart is executed.
- All PCD's: When RIO file is downloaded with download changed RIO file then RIO file is not sent to RIO until a restart is executed.
- All PCD's: Ethernet Frame Padding Information Leakage fixed (CVE-2017-9628)
- All PCD's: The Modbus CSF CloseSRPort does not free the port then a open/SASI call give an error and the port does not work.
- PCD1.M2xx0 PCD1.M22x0 PCD2.M4x60: PCD can crash while power down when XOB 0 is programmed.
- PCD1.M2xx0 PCD1.M22x0 PCD2.M4x60: MC0 mode with start/stop flag working again.
- PCD7.D443WT5R: Alarming does not work since 1.28.00 FW.
- PCD7.D443WT5R: When watchdog timeout occurs PCD7.D443WT5R does't reboot and stays locked.
Firmware 1.28.11 (Arpil 2017)
New features
- All PCD's: Support of BACnet Revision 14
Main corrections
- All PCD's: Various Open Data Mode fixes: Read Timeout enhancement, Client Connection timeout and Client Keep alive with anonymous port issue fixed
- All PCD's: Modbus RTU on all ports but specially on the F2xx module has been corrected to handle the response timeout processing in the case that the response is just occurring at the moment of the timeout.
- All PCD's: Battery status shows FAIL also if battery module is missing.
All PCD's: Various minor issues fixed - PCD1.M2xx0 & PCD3+: 38400/115200 baud settings adjustment
- PCD2.M4x60: PCD7.F7500 initialization
-
It’s possible to use the ‘old’ PCD7.F1xx module (not the PCD7.F1xxS) on PCD1.M2 and PCD2.M4x60 CPU’s? (FAQ #102005)
No, the PCD7.F110, PCD7.F120, PCD7.F150 and PCD7.F180 can’t be used on PCD1.M2 and PCD2.M4x60 devices.
Only the PCD7.F1xxS modules are supported on the PCD1.M2 and PCD2.M4x60 CPU’s.
-
It’s possible to use the PCD7.W600 analogue input module on a PCD2.M4x60? (FAQ #101993)
Yes, the PCD7.W600 analogue input module is supported on the PCD2.M4x60 since the hardware version C of the PCD2.M4x60.
-
Why the PCD7.W600 analogue input module doesn’t work on a PCD2.M4x60? (FAQ #101992)
Due of an error in the hardware the first series (hardware version A and B) of the PCD2.M4x60 is not able to use the PCD7.W600 analogue input module.
The error was fixed in the hardware version C of the PCD2.M4x60. -
What are the differences between the COSinus firmwares FW 1.24.67 and FW 1.26.31? (FAQ #101987)
In June 2017:
the COSinus FW 1.26.31 was released as maintenance version for the systems:- PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668.
the BACnet and LonIP FW 1.26.31 was released as maintenance version, which do support the BACnet Revision 9.
To support the BACnet Revision 14 it's necessary to use the PCD and the BACnet FW 1.28.xx.In March 2017:
the COSinus FW 1.26.28 was introduced into production for the systems:- PCD1.M2220, PCD1.Mxx60, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668.
the BACnet and LonIP FW 1.26.28 was introduced into production
In June 2016:
the COSinus FW 1.26.15 was introduced into production for the systems:- PCD1.M0xx0, PCD1.M2xx0, PCD2.M4x60, PCD3.Mxx60 and PCD3.M6880.
The COSinus FW 1.26.16 was introduced into production for the systems: PCD3.T665/T666/T668.
The BACnet and LonIP FW 1.26.15 was introduced into production
Attention:
The firmware 1.26.xx or later can be used only on the following PCD's with 8 MB onboard firmware memory:
PCD1.M0xx0/M2xx0, PCD2.M4x60, PCD3.Mxx60, PCD3.M6880 and PCD3.T665/T666/T668
The table below does show the hardware dependencies in relation with the COSinus firmware versions
Do use at least the PG5 firmware downloader version 2.1.311 or newer (included in PG5 patch 2.1.311 or newer) to prevent the loading of the FW 1.24.xx or 1.26.xx to a not compatible PCD.
Firmware 1.26.31 (June 2017)
Main corrections
- All PCD's SBUS parity mode, correction when NAK character is received as first byte of response.
- All PCD's: When download new Ethernet-RIO Program with the option ‘Delete all backups’ it can happen that the RIO is not commission and no goes no more in ‘data exchange mode’ until the PCD reboots.
- All PCD's: When RIO name is not in upper case the RIO file is not updated until a restart is executed.
- All PCD's: When RIO file is downloaded with download changed RIO file then RIO file is not sent to RIO until a restart is executed.
- All PCD's: Ethernet Frame Padding Information Leakage fixed (CVE-2017-9628)
- All PCD's: The Modbus CSF CloseSRPort does not free the port then a open/SASI call give an error and the port does not work.
- PCD1.M2xx0 PCD1.M22x0 PCD2.M4x60: PCD can crash while power down when XOB 0 is programmed.
- PCD1.M2xx0 PCD1.M22x0 PCD2.M4x60: MC0 mode with start/stop flag working again.
Firmware 1.26.28 (March 2017)
Improvements
- Text Ram can now be cleared (all chars are set to blank space) with the cgi interface by writing a zero length string.
- Ping request on ETH2 over rooter from different sub net.
- LonIP Mapper improvement
- Web Server RAM Disk increased
- Error Led not set on IR overflow
Main corrections
- All PCD's: MC0 communication with F2xx module and related communication flags are handled correctly in case of transmission
- All PCD's: Text Ram can now be cleared (all chars are set to blank space) with the cgi interface by writing a zero length string.
- All PCD's: Multiple AlarmLists with similar names will now be "initialized" correctly.
- All PCP's: TCP client keep alive is not working when anonymous port is used.
- All PCD's: Profi-SBus GWY does not wor, Profi-SBus Master/GWY stop working after cable is re plugged.
- All PCD's: PCD crash when use DIGI(R)/DIGO(R) with first parameter as FB parameter.
- All PCD's: Correction for modbus RTU communication over F2xx communication module
- All PCD's: When RIO file is downloaded with download changed RIO file then RIO file is not sent to RIO until a restart is executed.
- PCD1.M22x0: While changing the analog output value, the Watchdog is switching. Switching the Watchdog Relais over the corresponding flag has no influence.
- PCD2.M4x60: Sometimes the Profibus DP module is not initialized correctly on startup.
- PCD2.M5xx0: When Restore program because of a missing or dead battery configuration (SBus/IP,..) is not restored correctly.
- PCD2.M5xx0: Modbus RTU on all ports but specially on the F2xx module has been corrected to handle the response timeout processing in the case that the response is just occuring at the moment of the timeout.
- PCD2.M5xx0: Sometimes config is lost after download project with self-download tool.
- PCD3.Mxxx0: Battery status shows FAIL also if battery module is missing.
- PCD3.Mxxx0: FTP server processing with long commands resolved.
- PCD3.Mxxx0: Modbus RTU on all ports but specially on the F2xx module has been corrected to handle the response timeout processing in the case that the response is just occuring at the moment of the timeout.
- PCD3.Mxxx0: Sometimes config is lost after download project with self-download tool.
- PCD3.Mxx60: Profi-SBus/DP/SIO does not work on port 2 on PCD3.M3x60 & PCD3.M5360.
- PCD3.M6860: Ping request from over rooter from different sub net is not respond.
- PCD3.M6860/M880: Profibus/S-IO/Profi-SBus does not work stable.
- PCD3.M6860: Set PCD to HALT if there is no or incompatible media transfer between the two CPU's.
- PCD3.T66x: The RIO Status web page does not allow to clear the diagnostics.
- BACnet: The memory usage of the BACnet FW was increasing for every SubscrobeCOVProperty service, which has been received by the PCD.
- BACnet: A client configuration for Priority_Array properties in commadable objects (e.g. Analog-Value) does now allow reading (ReadProperty/COV) and writing (WriteProperty service to server) at the same time.
Firmware 1.26.15 (June 2016)
New features
- Support of PCD1.M2220-C15
- Support of PCD2.M4x60
- Support of PCD3.M3160/PCD3.M3360/PCD3.M5360
- Support of PCD3.M6880, PCD3.T668 Standby-CPU-System
Improvements
- PCD2.M4x6x, support Interrupt when reaching the configured ref Value
- PCD1.Mxxx0, PCD2.M4x60, PCD3.Mxx60 PCD7.D4xx: Increase None Volatile Register to 1000
- PCD3.T666/8: Increase the User Program Memory for to 256k
- PCD3.T66x: Support the ESIO manager use tag values for IP address
- PCD2/3.F2xx modules Baudrate: Support 300/600/1200 baud settings for in MC mode.
- S-Monitoring: In bar displays where the current time is visible, the average for the period is calculated not in a optimal way (time slice, ref time, is a bar). New it's displayed in seconds
Main corrections
- PCD3.M6860/M6880: When update FW on extension using the file system after update the extension FW can stay in an endless loop
- PCD3.M6880: crash wen Timmer/Counter is mapped in the Read Symbols
- PCD3.M6880: PCD can crash with MuKe Error when use the SBus GWY in parallel with modbus TCP
- PCD3.M6880: Standby CPU1 does not always HALT when CPU0 crash
- PCD3.M6880: CPU0 to 1 From Read data communication sometimes stop works
- PCD3.M6880: Add a Transmit Error diagnostic tag "DataTxErrors"
- PCD3.Mxxx0: Battery module on IO slot 3 does not show battery status in history
- PCD3.Mxxx0/PCD1.M2xx0: Some baudrates on onboard ports are not correct
- PCD2.M4x60: RTC read/write locks the PCD for about 30ms
- PCD2.M4x60: Modem does not work because of the not working DCD
- PCD3.T66x: Add ELine CSF library
- PCD3.T66x: Serial com does not work with SASI instruction
- PCD3.T66x: CSF Modbus Server Init gives an error when port 502 is used becasue this port is already open
- PCD7.D443WT5R: Assignation/Configuration of port 1 should return an error because port 1 is not supported
- PCD7.D443WT5R: Remove IO access from the system. PCD goes now in HALT with "INVALIDE OPCODE"
- PCD2.W220 with Pt1000: Significant deviation between singel channels
- BACnet: List Properties (like Date_List, Exception_Schedule, ...) could disappear after a PCD restart, if a WriteProperty request with an empty list value has been received for these properties before the restart. This behavior was only present for persistent properties
- BACnet: The Log_Buffer property of a Trend-Log object could not be read anymore using the ReadRange service, after a Event-Log or Trend-Log-Multiple has been read via ReadRange
- BACnet: Writing a single analog output channel is not working. The output is not changing. Writing output channels over the mapped functionality is working
- BACnet: PCD with BACNet loops with restart if program has "INVALIDE OPCODE"
- Restart Warm does not work
- SBus ELine has sometimes retries
- When create a Text/DB the backup fails until a restart is done
- PCD Crash with BUS ERROR on STXT instruction when text is empty
- Modem does not work correctly
- Modem does not work or PCD crash when modem is configure
- PCD can crash when error occurs in Modbus RTU
- The PCD crash if a BITI is executed with number as FB parameter
- PCD crash when use Profi-S-Bus Master
- Sometimes the program is lost when update FW from 1.24.xx to 1.26.xx
- MOVX/DIVX function where not working on Task or Temporary data when use indexed
- Add config tag value for GWY mode "data_no_secure" to deasble the secure data mode
- Not possible to upload a file through the Web server FTP interface (ftp.cgi or ftp.json) if that file starts with a white space character (either a space or a tab)
- CSF CopyDBBytesToR crash when destination is bigger than last Register
- Diagnostic Flags in S-Bus Master mode are not correct if there are collisions on the RS-485 network
- CSF Backup/Restore Media does give an error on restore when data change while backup/restore
- MOV instruction with type position as FB parameter gives error flag and fails
- Web-Alarm: Fix alarming color with "group color mode" and group bigger than 8
-
Why it’s not possible to communicate with a modem which is connected to a PCD2.M4x60? (FAQ #101986)
Due of an error in the hardware and the firmware the first series (hardware version A and B) of the PCD2.M4x60 is not able to use the analog/ISDN or GMS modem which is connected to the RS232 of the PCD2.M4x60.
The error was fixed in the hardware version C.
To be able to use the modem correctly it’s necessary to have at least a HW version C and at least a FW 1.26.15 on the PCD2.M4x60.