![]() The problem may be related to a loose contact on the PCD3.K010 connectors used to connect the PCD3.M/Txxx CPU's and the PCD3.Cxxx expansion modules. If there is heavy communication on both Ethernet interfaces the user program execution is slowed down correspondingly There are 2 Ethernet interfaces but only one CPU which processes the Ethernet communication -> Ethernet communication performance is not increasedĬommunication via Ethernet 2 uses (about 2x) more CPU power than communication via Ethernet 1Ĭommunication via Ethernet 2 is slower (about 2x) than via Ethernet 1 FW download normally goes via USB 1 and Ethernet (1 or 2). USB connector on extension (under blue cover) is not used.Ĭan only be used for FW download if there is no FW (Booter only). The same behavior does also apply for the S-Bus communication F-Boxes, means that the channel defined in the master/slave F-Box has no effect in the relation to the two Ethernet ports. On the PCD3.M6860, both Ethernet ports are active at the same time (and also active for the Ether S-Bus communication, if activated on the device configurator) regardless of the channel number. The CPU can remain in run during the download process, but always restarts before deploying the new program (download changed blocks in run is not yet possible). For this reason, the CPU of the PCD3.M6860 differs in its behaviour regarding program download, backup and restore requirements from existing PCD3 CPUs. ![]() ![]() There is a program example for the PCD3.M6860 available in the Getting Started section.Īpplication programs are stored in the onboard flash. The configuration of the PCD3.M6860 is possible since PG5 2.1.100. ![]() No more possible to set the PCD3.M6860 in to the firmware download mode with the help of the run/stop switch (since booter version 1.24.11) The configuration of the PCD3.M6880 is possible since PG5 2.1.400. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |