6/7/2009 9:51 PM | |
Joined: 1/5/2007 Last visit: 4/7/2023 Posts: 1690 Rating:
|
Hi, similar as in my german contribution under "Hinweise zu bekanntem (Fehl-)Verhalten von LOGO!Soft Comfort und der LOGO!" I would like here now collect the recognized errors behaviour of the new LOGO!-0BA6- basic modules and the corresponding programming software LOGO!SoftComfort V6... - still always in the hope, that such information penetrate to the LOGO!-developer once. Because up to now the well-known errors of the modules 0BA5 are olso present at the modules 0BA6! As ever - in the following you find the beginning of a collecting of errors or at least unexpected behavior of the LOGO!-modules and the programming software V6.xx: 1) In the german contribution "Random number generator 0BA6/0BA5" (with example in the file appendix: workaround.zip) is told from an error response of the LOGO!-0BA6-Basismodule while using from more than a blocks "random number generator" and given also to circuit design in order to balance the error response, quotation: Hicks wrote in the german forum part: 2)In the german contribution "Siemens LOGO! Comfort V6.1.5" are reported about an error response of the LOGO!-Programmiersoftware concerning the simulation of the block "operation time counters". I attempted once to examine the ACTUAL behavior and to combine my results in the following: a) The basic devices of the series 0BA5 and 0BA6 work, I think, correctly! b) All up to now publishes versions of the programming software LOGO!SoftComfort have in the simulation mode an indicated error response on: The block "operation time counter" always adds all the time constantly after a first activating with the pin "En". An interrupting and/or shutdown of this signal has not the effect it should - to stop the added time. When this pin "En" is activated e.g. a second one after a long time with "0", then the parameter OT is updated and shows the totel time above the first activation of the pin "En"! c) Also the previous version V.x has this error response! However, one must make for this purpose a long run the simulation over an hour in order to be able to recognize this then by means of two blocks "operation time counters" and after correspondingly different excitation. That is surely also the ground for this not being noticed up to now by us... Best regards |
==> Meine TAG-Listen: "deut." |
|
Follow us on