F2xx0, use the PCD7. Solution The Firmware version 1. F2xx will solve this bug with the handling of the RTS signal. Please contact your local SBC Support center. F27xx, the M-Bus driver may show the error "Missing value" even though all values are correctly returned by the device. F27xx with the framing protocol , the M-Bus driver may display the error "Missing value" even though all values are correctly returned. The problem concerns only few devices; so far the following concerned devices are known:.
Reason This problem occurs because the PCD firmware older than 1. Solution This problem is corrected in the PCD firmware version 1. This firmware is e. F27x 0. During our analysis it was found that the power consumption variation of the "Hydrometer M-Bus Receiver " while receiving data is higher than specified in the M-Bus specification.
This leads to the fact that the communication between the Fx and the "Hydrometer M-Bus Receiver " receiver is not working. Note that the manufacturer is explicitly specifying that this device is only to be used with "his" M-Bus master, see screenshot below. But when sending data on the M-Bus lines, the current consumption of this slave changes by more than 10mA, and this change is seen as incoming data on the M-Bus master side.
N must be specified, values in the range from 1 to 4 are allowed. Therefore it can be by chance that it works with third party master devices. With the F27x modules the functionality is not guaranteed guaranteed functionality would require a hardware redesign of the F27x to support the special device. F the M-Bus FBox library 2. F and the M-Bus FBox library older than version 2. This is only the case with the aquametro device, other M-Bus devices can be read correctly.
F or a PCD3. F is configured. There is a possibility to update the firmware of a PCD2. F2xxx or PCD3. F2xx, in this FAQ it is explained how to proceed. In general the procedure is the same like you would update the firmware of a PCD3. Change the file for the download to the required. Problem When more than one PCD2. F2xx is plugged in the PLC there can appear some error messages. Solution In this case you have to specify the Slot in which the Module is plugged which you want to download the firmware into.
Remark The minimal system requirements are: PG5 2. F26xx PCD2. F27xx PCD3. F26x PCD3. F2xxx or a PCD3. F2xx or on the ports listed below under "Remark" are not answering to all requests. The same device does work fine when the M-Bus gateway is connected to another port e. Reason The reason for this phenomenon could be that the M-Bus device is very sensitive against inter-character delays in the telegrams.
Solution In order to avoid the inter-character delays a new feature has been implemented in the firmware of the PCD the freeze bit, see FAQ The M-Bus library 2.
Remark With firmware 1. In order to avoid these inter-character delays, please use firmware 1. M5xx0 or PCD3. This firmware can be downloaded from the according product section on the support site www. A hardware conflict on a PCD2. M5xxx between a PCD2. F2xx0 and PCD2. R leads to the fact that the communication- and memory modules do not work in this constellation. If the PCD2. Symptom In case a PCD2.
F2xx0 and the memory modules PCD2. R do not work. F, a PCD2. F or a PCD2. The file system of the PCD2. Only PCD2. M5xxx with hardware version older than C are concerned. Reason The reason for this behavior is a conflict between the PCD2. W3x0 PCD2. W, PCD2. W and the PCD2. F2xx0 or R This conflict exists only if the PCD2.
When more than 1 displays of the same type PCD7. D23x and PCD7. F2xx module, the communication doesn't work. Only one of the displays is available, the other one s is are not accessible! The ports to available on the PCDx. F2xx modules have different timing properties and are therefore not appropriate for PCD7.
D in bus terminal topoloy! Workaround: Use another RS port onboard or with F1xx. The diagnostic flag TBSY of the "Character Mode" used for sending characters over a serial line is not handled the same way on a PCD3 compared to "older" systems like e.
Symptom If the relevant port is assigned in MC mode, the diagnostic flag TBSY is indicating that the serial port is busy sending characters. This is the case on e. This behaviour is not the same on a PCD2. M5xxx or a PCD3. Mxxxx, especially not when using a PCD3. F or a F2xx x modules. M5 the TBSY flag is not any more high during the whole time the port is busy. Instead, it is only high a short time at the very beginning of the send task. Solution This difference shouldn't lead to problem is most cases.
However, in some applications the state of the TBSY is used to control e. In this case the communication working on a PCD2. In this situation one of the following workarounds could be applied:.
Those M-Bus cards have a short-cut protection on the bus but when the CPU isn't anymore power supplied and the F27x x card still has 24 V supply there is no short cut protection anymore! The 36 Volts from the M-Bus will destroy some components on the concerned serial port of the card!
F27x x card or if for some reason a different power supply has to be used be aware that in case the CPU isn't power supplied that the M-Bus is NOT short-circuited! F produced between June and September 10 , these modules do not work at all or not correctly when mounted on a PCD2. The reason for the different electrical properties is that the driver is delivered by a new manufacturer. We did not notice this malfunction in our production because the F2xx modules are delivered separately from the PCD7.
F1xx modules, as they are mounted afterwards by the customer. F applied on PCD2. F2xxx and PCD3. F2xx which were delivered between June and 10th of September production date to These modules are equipped with ICs from manufacturer Sipex and have hardware version B without modification 1.
F with production date before generally equipped with an IC from the manufacturer Max. F delivered after 10th of September, equipped with IC from Max or Sipex but with version B1 If you have concernde moduls, contact your local representation to exchange them. If the communication on both ports of a PCD3. F module. Symptom The communication on both ports of the PCD3. F does not work at all. The firmware installed is 1. Solution To solve the problem please install PCD3 firmware version 1.
There are various possibilities to plug flash memory modules PCD7. R, PCD7. RM04, PCD7. R and PCD7. R on the CPUs. R modules in the following slots:.
The "backup user program" functionality does work on any of the above mentioned slots if the module PCD7. FM04 or PCD7. R are used. The data is transmitted but obviously not properly.
F2xx module is involved in this communication. With a baudrate it works well. Reason The PCD3. If there is an S-Bus communication running with e.
F2xx as master and a PCD3. Mxxx port 2 as slave, the communication will probably report diagnostic errors with baudrates higher than If the PCD3. F2xx module is the slave, it is less critical but can lead to problems as well. F2xx is plugged has to be set to 3ms. Problem Since the new PCD3. F2xx modules where developped it was possible to have up to 8 MP-Bus Masters in a project.
The master now have a name "Channel" and the differnet F-Boxes refer to this "Channel". In this case install the version 2. Problem After installing the new version of the Belimo library which allows to have more than one MP-Bus Master in a Fupla file, it is not possible anymore to build the old projects. The library 2. M can be used. On the other hand there is no problem using the newer FT1.
M and PCD1. M systems. On other systems e. Remark We strongly recommend using FT1. The table above represent functional tests; there is no relation to the communication performance. Two series of PCD7. The series can be identified easily by the article name "PCD7.
R5" written on the white label on the module and fabrication date or This wrong configuration information can lead to malfunction of the file system access of the PCD3 and on the communication module of the PCD3. Behaviour of the malfunction If the PCD7. R module is placed together with a PCD7. R5xx, PCD3. F1xx or PCD3. R5xx or PCD7.
R5xx is no more accessible from any external device e. Also the communication ports of the PCD3. R on stock in Murten with a correct configuration.
R mo dule. In case you have received a PCD7. R module affected the above desribed wrong configuration, please contact your local Saia-Burgess Controls AG representative.
Reason There is a problem in the Belimo library 2. The easyest way for resolving the problem is updating to PG5 1. The error flag is set after the SASI instruction. List of supported ports PCD3.
M5xxx : the mode MC2 is supported on port 2. M2xxx : the mode MC2 is not supported. In some cases it can happen that the PCD3. F produced between and Febrauary works well for a certain time but suddenly stops communicating.
This behaviour is related to the hardware version of the PCD3. Symptom The PCD3. In some cases it is also possible that it doesn't work at all.
Reason The base print of the PCD3. F was designed in a way that the ground signal was not properly stabilized. This problem has been corrected in February F can be installed. Therefore please connect the pin 0 with pin 4 on the terminals on the front of the module. Remark Modules produced after February are not concerned by the problem explained in this FAQ and therefore no additional bridge is required.
In case a PCD3. F1xx module doesn't work several reasons are possible. This FAQ supplies a summary of these possible reasons. Symptom The communication on port 1 of the PCD3 does not work. In case the port is configured as PGU port e. When mounting a PCD7. F into a PCD3. F2xx or when using a PCD7. F on a PCD2.
M5, the communication doesn't work. The reason therefore is an incompatibility between the PCD7. F and PCD3. Fxxx or PCD2. M5 modules and the old. Symptom After having mounted a PCD7. Fxxx or on a PCD2. No communication is possible using the relevant port. Reason The PCD7. F does require a power supply which is not present on the PCD3. Fxxx modules or on the sockets from PCD2. M48x CPUs. This power supply is not present because the new communication module PCD7.
Solution In case you are concerned by this problem just replace the PCD7. F by a PCD7. Remark All modules PCD3. F In fact, the PCD7. F has been replaced by the PCD7.
The only situation where a problem can occur is in case an old PCD7. There is a problem when placing a communication module PCD3. F1xx and a memory module PC3. Rxxx on the same PCD3. Problem If a communication module is per example on slot 0 of the PCD3 and a memory module is per example on slot 1, it is possible that one of them will not work. If one of the modules is removed, the remaining one will work correctly. Reason There is a problem in the firmware.
As soon as more than one intelligent module e. F1xx, PCD3. F2xx, PCD3. R5xx or PCD3. R6xx are plugged on the PCD3. Mxxxx the detection of the module can fail. Solution As long as firmware is not released the two modules will not work properly together. A workaround could be to put the memory module PCD7. RM04 directly on the communication module. Open the memory module PCD3. R and remove the card PCD7.
Open the communication module PCD3. F1xx and plug the card on this module. F the error "no card echo" can be forced into the "single-master box" during the interface initialize process.
Symptom The error message "No card echo" is present in the Single master box. Physically not existing MP-interface card. Please verify the plugged PCD7. F card into the module. For the correct handling of the new flash modules PCD3.
Rxxx an and the PCD3. You can rename one file extension, selected files, or all files in any folder. You just place all the files with extension that you want to change into This Software is a device driver that is used to control test and measurement instruments, which are made by ADC Corp. This driver provides functions, which can be used in ADC's instruments, in Acer Drivers Update Utility updates your system drivers for Acer devices automatically with just several clicks.
It will scan your system first then download and install Acer official drivers to let your Acer device work properly. The Acer Driver Update Utility keeps your system up-to-date. Shoshi English to Bangla Dictionary is a complete dictionary software with all the current words. This dictionary will fulfill their needs without wasting Yahoo Messenger Archive recovery Program easily recovers and decodes all yahoo chat archive messages.
Software easily decodes yahoo archive files and saves retrieve chat conversations data in RTF or plain text format. Volume Serial Number Editor 1. Automatic Mouse and Keyboard 3. Utilities Download Automatic Mouse and Keyboard is a really powerful and easy-to-use Mouse and Keyboard automation tool.
CutFour HD 3. Change File Extension Shell Menu 2. Acer Drivers Update Utility 2.
0コメント