-protocols are disabled by default on the deivce configurator of new PG5 projects: - S-Bus over TCP/IP - FTP - HTTP (Web-Server) PG5 projects made with precedent version of PG5 2.1 are upward compatible [...] default on the deivce configurator of new PG5 projects: - S-Bus over TCP/IP - FTP - HTTP (Web-Server) - The user has to turn on the appropriate IP protocols deliberately in the Device [...] Update Manager Web Editor 8.0 Project Generator - Excel-Import Improvements of Fupla - Cyclical transmission of S-Bus telegrams - HTTP file transfer library - Display the history of Adjust
-protocols are disabled by default on the deivce configurator of new PG5 projects: - S-Bus over TCP/IP - FTP - HTTP (Web-Server) PG5 projects made with precedent version of PG5 2.1 are upward compatible [...] default on the deivce configurator of new PG5 projects: - S-Bus over TCP/IP - FTP - HTTP (Web-Server) - The user has to turn on the appropriate IP protocols deliberately in the Device [...] Update Manager Web Editor 8.0 Project Generator - Excel-Import Improvements of Fupla - Cyclical transmission of S-Bus telegrams - HTTP file transfer library - Display the history of Adjust
Analyse einer Ether-S-Bus Kommunikation oder Ethernet Kommunikation generell, empfehlen wir den Einsatz der kostenlosen Software Wireshark ( www.wireshark.org ). Es handelt sich hier um ein Open Source Analyseprogramm (inklusive Matching Log File Creator WinPcap). Der Wireshark Analysator ist in der Lage, Ether-S-Bus ab Verson 1.1. aufzugliedern. Für zusätzliche Informationen lesen Sie bitte die entsprechende
Analyse einer Ether-S-Bus Kommunikation oder Ethernet Kommunikation generell, empfehlen wir den Einsatz der kostenlosen Software Wireshark ( www.wireshark.org ). Es handelt sich hier um ein Open Source Analyseprogramm (inklusive Matching Log File Creator WinPcap). Der Wireshark Analysator ist in der Lage, Ether-S-Bus ab Verson 1.1. aufzugliedern. Für zusätzliche Informationen lesen Sie bitte die entsprechende
, befor sie ein neues Programm anwendet (download geänderter Blöcke in Run ist noch nicht möglich) Bei der PCD3.M6860 sind beide Ethernet Schnittstellen gleichzeitig aktiv, (und auch für die Ether S-Bus Kommunikation aktiv wenn diese im Device Konfigurator aktiviert ist), unabhängig von der Kanal Nummer. Das gleiche gilt auch für die S-Bus Kommunikations F-Boxen, was bedeutet, dass der in der master/slave F [...] 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
, befor sie ein neues Programm anwendet (download geänderter Blöcke in Run ist noch nicht möglich) Bei der PCD3.M6860 sind beide Ethernet Schnittstellen gleichzeitig aktiv, (und auch für die Ether S-Bus Kommunikation aktiv wenn diese im Device Konfigurator aktiviert ist), unabhängig von der Kanal Nummer. Das gleiche gilt auch für die S-Bus Kommunikations F-Boxen, was bedeutet, dass der in der master/slave F [...] 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
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 [...] 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
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 [...] 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
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 [...] 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
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 [...] 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
