- Ip booter meter driver#
- Ip booter meter Patch#
- Ip booter meter download#
Ip booter meter download#
PCD2.M4圆0: Download LonIP config not possible. PCD3.Mx圆0, PCD3.T6xx, PCD1.M2xx0, PCD2.M4圆0: usage of I/O media mapping slows done the cycle time 2 times in comparison to FW 1.26.xx. All PCD’s: LonFT10: SNVT_obj_status and SNVT_obj_request can be used in user profiles. All PCD’s: XOB parameter as Registers does not work if 16bit addressing was used. 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. The FCS test for SD2 telegram was not implemented correctly. All PCD’s: Profibus communcation using onboard FDL port. All PCD’s: RCOB does not start COB when it was stopped before with SCOB. All PCD’s: PCD crashes when using browser to access the default page of PCD with "Display Root Content Enabled = YES". All PCD’s: PCD can crash on download in run when Graftec is used. All PCD’s: PCD can crash on download in run since FW 1.28.27. All PCD’s: PCD can crash when breakpoint is updated during conditional RUN. 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. Ip booter meter driver#
All PCD’s: RS485 driver keep holding bus after a while. All PCD’s: Not all bytes are transmitted when working with MC4 or MC5 mode on F2xxx module. 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. BACnet: The PCD will now accept AcknowledgeAlarm service requests, which use complete wildcards as timestamps. BACnet: New mappings for alarming counters have been added to Notification-Class objects. Each server calendar object can be configured as Slave or Master calendar BACnet: Calendar objects have been extended with a synchronization mode. All PCD’s: FW extension to close all open FTP connections. BACnet: Rev14 does not allow high limit value below 5 on analogue input. BACnet: Rev 4 not working with Name based Client. BACnet: PCD3.M6860 no BACnet communication on ETH2 if router is used. BACnet: Web scheduler/calendar templates do not work. BACnet: Web CGI commands to read BACnet platform tags like. 
BACnet: Problem reliability & out of service, reliability is not written when oos is high. BACnet: MS/TP client properties are not written if many values change simultaneously. BACnet: Schedule crashes with SWTO error. BACnet: Exception schedule writing to certain array index fails. 
BACnet: Calendar state not updating after add/remove list element service. PCD3.M6880: Data exchange between CPU 0 and CPU 1 does not work reliable if STL instruction is used. PCD1.M2220-C15: Watchdog LED does not follow Relay when PCD goes in STOP or HALT. PCD2.M45x0: SRXM does not support FB parameters as operand 3 and 4 for source and destination. All PCD’s: LonIP CSF is locked when an error occurs. All PCD’s: TCP, open data mode protocol, communication is blocked after rejection of 32 connections. All PCD’s: S-Monitoring Year graph scaling displayed wrongly. All PCD’s: S-Monitoring values for S-Monitoring bar graphs are sometime wrong. All PCD’s: E-Mails send from PCD could contain unwanted characters like 0 or others. All PCD’s: SNTP Time synchronization does not work with DHCP. 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: Saia PCD Modbus diag does not work if diag flag > 9999. Ip booter meter Patch#
The table below does show the hardware dependencies in relation with the COSinus firmware versionsĭo 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 The firmware 1.28.xx or later can be used only on the following PCD's with 8 MB onboard firmware memory: To support the BACnet Revision 9 it's necessary to use the PCD and the BACnet FW 1.26.xx. The BACnet and LonIP FW 1.28.16 was put into production, which do support the BACnet Revision 14. The COSinus FW 1.28.16 was introduced into production for the systems: The COSinus FW 1.28.37 was released as maintenance version for the systems: The COSinus FW 1.28.51 was introduced into production for the systems:
0 kommentar(er)
