{"id":473,"date":"2015-03-11T16:11:52","date_gmt":"2015-03-11T15:11:52","guid":{"rendered":"http:\/\/norman\/wordpress\/?page_id=473"},"modified":"2015-03-11T16:34:43","modified_gmt":"2015-03-11T15:34:43","slug":"parameter-error-code","status":"publish","type":"page","link":"http:\/\/bj-ig.de\/service\/verfuegbare-dokumentationen\/s7-kommunikation\/aufbau-eines-data-tpdus\/parameter-part\/parameter-error-code\/","title":{"rendered":"Parameter Error Code"},"content":{"rendered":"
Folgende Fehlercodes kommen nur im Parameterteil vor. Der Gro\u00dfteil der Codes und Meldungen wurde aus PanelMate Siemens Communication Driver Manual<\/a> und Panel & PLC Error Code Tables<\/a> entnommen.<\/p>\n
Error\u00a0Code<\/b><\/td>\n | <\/td>\n | Description<\/b><\/td>\n<\/tr>\n0x0000<\/td>\n | <\/td>\n | no error<\/td>\n<\/tr>\n | 0x0001<\/td>\n | <\/td>\n | hardware fault<\/td>\n<\/tr>\n | 0x0003<\/td>\n | <\/td>\n | object access not allowed: occurs when access to timer and counter data type is set to signed integer and not BCD<\/td>\n<\/tr>\n | 0x0004<\/td>\n | <\/td>\n | context not supported<\/td>\n<\/tr>\n | 0x0005<\/td>\n | <\/td>\n | address out of range: occurs when requesting an address within a data block that does not exist or is out of range<\/td>\n<\/tr>\n | 0x0006<\/td>\n | <\/td>\n | address out of range<\/td>\n<\/tr>\n | 0x0007<\/td>\n | <\/td>\n | write data size mismatch<\/td>\n<\/tr>\n | 0x000A<\/td>\n | <\/td>\n | object does not exist: occurs when trying to request a data block that does not exist<\/td>\n<\/tr>\n | 0x0101<\/td>\n | <\/td>\n | communication link not available<\/td>\n<\/tr>\n | 0x010A<\/td>\n | <\/td>\n | negative acknowledge \/ time out error<\/td>\n<\/tr>\n | 0x010C<\/td>\n | <\/td>\n | data does not exist or is locked<\/td>\n<\/tr>\n | 0x0200<\/td>\n | <\/td>\n | unknown error<\/td>\n<\/tr>\n | 0x0201<\/td>\n | <\/td>\n | wrong interface specified<\/td>\n<\/tr>\n | 0x0202<\/td>\n | <\/td>\n | too many interfaces<\/td>\n<\/tr>\n | 0x0203<\/td>\n | <\/td>\n | interface already initialized<\/td>\n<\/tr>\n | 0x0204<\/td>\n | <\/td>\n | interface already initialized with another connection<\/td>\n<\/tr>\n | 0x0205<\/td>\n | <\/td>\n | interface not initialized; this may be due to an invalid MPI address (local or remote ID) or the PLC is not communicating on the MPI network<\/td>\n<\/tr>\n | 0x0206<\/td>\n | <\/td>\n | can\u2019t set handle<\/td>\n<\/tr>\n | 0x0207<\/td>\n | <\/td>\n | data segment isn\u2019t locked<\/td>\n<\/tr>\n | 0x0209<\/td>\n | <\/td>\n | data field incorrect<\/td>\n<\/tr>\n | 0x0302<\/td>\n | <\/td>\n | block size is too small<\/td>\n<\/tr>\n | 0x0303<\/td>\n | <\/td>\n | block boundary exceeded<\/td>\n<\/tr>\n | 0x0313<\/td>\n | <\/td>\n | wrong MPI baud rate selected<\/td>\n<\/tr>\n | 0x0314<\/td>\n | <\/td>\n | highest MPI address is wrong<\/td>\n<\/tr>\n | 0x0315<\/td>\n | <\/td>\n | address already exists<\/td>\n<\/tr>\n | 0x031A<\/td>\n | <\/td>\n | not connected to MPI network<\/td>\n<\/tr>\n | 0x031B<\/td>\n | <\/td>\n | –<\/td>\n<\/tr>\n | 0x0320<\/td>\n | <\/td>\n | hardware error<\/td>\n<\/tr>\n | 0x0381<\/td>\n | <\/td>\n | hardware error<\/td>\n<\/tr>\n | 0x4001<\/td>\n | <\/td>\n | communication link unknown<\/td>\n<\/tr>\n | 0x4002<\/td>\n | <\/td>\n | communication link not available<\/td>\n<\/tr>\n | 0x4003<\/td>\n | <\/td>\n | MPI communication in progress<\/td>\n<\/tr>\n | 0x4004<\/td>\n | <\/td>\n | MPI connection down; this may be due to an invalid MPI address (local or remote ID) or the PLC is not communicating on the MPI network<\/td>\n<\/tr>\n | 0x8000<\/td>\n | <\/td>\n | interface is busy<\/td>\n<\/tr>\n | 0x8001<\/td>\n | <\/td>\n | not permitted in this mode<\/td>\n<\/tr>\n | 0x8101<\/td>\n | <\/td>\n | hardware error<\/td>\n<\/tr>\n | 0x8103<\/td>\n | <\/td>\n | access to object not permitted<\/td>\n<\/tr>\n | 0x8104<\/td>\n | <\/td>\n | context not supported<\/td>\n<\/tr>\n | 0x8105<\/td>\n | <\/td>\n | address invalid. This may be due to a memory address that is not valid for the PLC<\/td>\n<\/tr>\n | 0x8106<\/td>\n | <\/td>\n | data type not supported<\/td>\n<\/tr>\n | 0x8107<\/td>\n | <\/td>\n | data type not consistent<\/td>\n<\/tr>\n | 0x810A<\/td>\n | <\/td>\n | object doesn\u2019t exist. This may be due to a data block that doesn\u2019t exist in the PLC<\/td>\n<\/tr>\n | 0x8301<\/td>\n | <\/td>\n | not enough memory on CPU<\/td>\n<\/tr>\n | 0x8402<\/td>\n | <\/td>\n | maybe CPU already in RUN or already in STOP<\/td>\n<\/tr>\n | 0x8404<\/td>\n | <\/td>\n | serious error<\/td>\n<\/tr>\n | 0x8500<\/td>\n | <\/td>\n | wrong PDU (response data) size<\/td>\n<\/tr>\n | 0x8702<\/td>\n | <\/td>\n | address not valid<\/td>\n<\/tr>\n | 0xD002<\/td>\n | <\/td>\n | Step7: variant of command is illegal.<\/td>\n<\/tr>\n | 0xD004<\/td>\n | <\/td>\n | Step7: status for this command is illegal.<\/td>\n<\/tr>\n | 0xD0A1<\/td>\n | <\/td>\n | Step7: function is not allowed in the current protection level.<\/td>\n<\/tr>\n | 0xD201<\/td>\n | <\/td>\n | syntax error: block name<\/td>\n<\/tr>\n | 0xD202<\/td>\n | <\/td>\n | syntax error: function parameter<\/td>\n<\/tr>\n | 0xD203<\/td>\n | <\/td>\n | syntax error: block type<\/td>\n<\/tr>\n | 0xD204<\/td>\n | <\/td>\n | no linked data block in CPU<\/td>\n<\/tr>\n | 0xD205<\/td>\n | <\/td>\n | object already exists<\/td>\n<\/tr>\n | 0xD206<\/td>\n | <\/td>\n | object already exists<\/td>\n<\/tr>\n | 0xD207<\/td>\n | <\/td>\n | data block in EPROM<\/td>\n<\/tr>\n | 0xD209<\/td>\n | <\/td>\n | block doesn\u2019t exist<\/td>\n<\/tr>\n | 0xD20E<\/td>\n | <\/td>\n | no block available<\/td>\n<\/tr>\n | 0xD210<\/td>\n | <\/td>\n | block number too large<\/td>\n<\/tr>\n | 0xD240<\/td>\n | <\/td>\n | coordination rules were violated<\/td>\n<\/tr>\n | 0xD241<\/td>\n | <\/td>\n | protection level too low<\/td>\n<\/tr>\n | 0xD242<\/td>\n | <\/td>\n | protection violation while processing F-blocks; F-blocks can only be processed after password input<\/td>\n<\/tr>\n | 0xD401<\/td>\n | <\/td>\n | invalid SSL ID<\/td>\n<\/tr>\n | 0xD402<\/td>\n | <\/td>\n | invalid SSL index<\/td>\n<\/tr>\n | 0xD406<\/td>\n | <\/td>\n | information doesn\u2019t exist<\/td>\n<\/tr>\n | 0xD409<\/td>\n | <\/td>\n | diagnosis: DP error<\/td>\n<\/tr>\n | 0xD802<\/td>\n | <\/td>\n | this job does not exist<\/td>\n<\/tr>\n | 0xDC01<\/td>\n | <\/td>\n | maybe invalid BCD code or Invalid time format<\/td>\n<\/tr>\n | 0xEF01<\/td>\n | <\/td>\n | wrong ID2, cyclic job handle<\/td>\n<\/tr>\n | 0xFFCF<\/td>\n | <\/td>\n | API function called with an invalid parameter<\/td>\n<\/tr>\n | 0xFFFF<\/td>\n | <\/td>\n | timeout, check RS232 interface<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":" | Parameter Error Codes Folgende Fehlercodes kommen nur im Parameterteil vor. Der Gro\u00dfteil der Codes und Meldungen wurde aus PanelMate Siemens Communication Driver Manual und Panel & PLC Error Code Tables entnommen. Error\u00a0Code Description 0x0000 no error 0x0001 hardware fault 0x0003 object access not allowed: occurs when access to timer and counter data type is set […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":465,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"index-grey.php","meta":{"footnotes":""},"_links":{"self":[{"href":"http:\/\/bj-ig.de\/wp-json\/wp\/v2\/pages\/473"}],"collection":[{"href":"http:\/\/bj-ig.de\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"http:\/\/bj-ig.de\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"http:\/\/bj-ig.de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/bj-ig.de\/wp-json\/wp\/v2\/comments?post=473"}],"version-history":[{"count":2,"href":"http:\/\/bj-ig.de\/wp-json\/wp\/v2\/pages\/473\/revisions"}],"predecessor-version":[{"id":490,"href":"http:\/\/bj-ig.de\/wp-json\/wp\/v2\/pages\/473\/revisions\/490"}],"up":[{"embeddable":true,"href":"http:\/\/bj-ig.de\/wp-json\/wp\/v2\/pages\/465"}],"wp:attachment":[{"href":"http:\/\/bj-ig.de\/wp-json\/wp\/v2\/media?parent=473"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}} |