11.01.2014 Views

SYCON.net PROFIBUS DP Slave DTM

SYCON.net PROFIBUS DP Slave DTM

SYCON.net PROFIBUS DP Slave DTM

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Error Codes 117/132<br />

ODM Error Codes DBM V4<br />

Error Code (Definition) Value Description<br />

CDBM_ERROR_FROM_VAR_ CHANGE_TYPE 0XC004C848 Function VariantChangeType return an<br />

error when trying to convert the Parameter<br />

CDBM_E_MINERROR 0XC004C849 Error while comparing the Value with the<br />

lower range<br />

CDBM_E_MAXERROR 0XC004C84A Error while comparing the Value with the<br />

upper range<br />

CDBM_E_RANGE_ERROR 0XC004C84B Value out of Range<br />

CDBM_E_TABLE_TYPE1 0XC004C84C Table type 1 doesn’t have a unique record<br />

length over all records<br />

CDBM_E_TABLE_TYPE3_ ADDREC 0XC004C84D Table type 3 doesn’t allow to insert more<br />

than one Record<br />

CDBM_E_TABTYPE1 0XC004C84E It's not allowed to insert more Records<br />

than structure definitions in Table Type 1<br />

CDBM_E_TOGGLE_NOT_FOUND 0XC004C84F Could not find the string for this value in<br />

the list of valid toggle strings<br />

CDBM_E_TOGGLE_VALUE_IS_ EMPTY_STRING 0XC004C850 The toggle string for this value is empty.<br />

CDBM_VARIANT2BYTEARRAY_ ERROR 0XC004C851 Error during conversion of Variant to byte<br />

array<br />

CDBM_E_SET_ELEM_PROP_ DEPENDENCY 0XC004C852 The Toggle Type needs also the additional<br />

string and the additional number entries in<br />

the Method<br />

CDBM_E_TABTYPE1_REC_<br />

DOESNT_CORRESPOND_ WITH_ELEMENT<br />

CDBM_TABTYPE1_NO_DATA_<br />

FOUND_FOR_RECORD<br />

CDBM_E_TABTYPE1_WRITE_<br />

ELEMENT_NE_RECORD<br />

CDBM_E_TABTYPE1_WRITE_<br />

ELEMENT_NOT_FOUND<br />

CDBM_I_TABLE_NAME_EXCEEDS_<br />

RCS_RANGE<br />

CDBM_W_CUT_STRING<br />

CDBM_I_STRING_TOO_SHORT<br />

CDBM_I_STRING_TOO_LONG<br />

CDBM_E_STRING_TOO_SHORT<br />

CDBM_E_STRING_TOO_LONG<br />

0XC004C853 When reading the records of Table type 1<br />

elementwise the record number must<br />

correspond with the element number<br />

0XC004C854 When reading the records of Table type 1<br />

and structure definitions are present it's<br />

assumed that for each structure element a<br />

corresponding record must exist<br />

0XC004C855 When writing the records of Table type 1<br />

elementwise and structure definitions are<br />

present it's only allowed to write the<br />

corresponding element number in each<br />

record<br />

0XC004C856 When writing the records of Table type 1<br />

with an array and structure definitions are<br />

present it's assumed that a corresponding<br />

element number of this record exist<br />

0X4004C857 The Table name exceeds the maximum<br />

(Informational)<br />

length of RCS compatible Table names<br />

0X8004C858 The string exceeds the maximum length<br />

(Warning)<br />

and will be limited to the maximum length<br />

0X4004C859 The string is below the minimum length.<br />

(Informational)<br />

The minimum length will be reduced.<br />

0X4004C85A The string is exceeding the maximum. The<br />

(Informational)<br />

maximum length will be extended.<br />

0XC004C85B The string is below the minimum length.<br />

(Error)<br />

0XC004C85C The string is exceeding the maximum<br />

(Error)<br />

length<br />

CDBM_E_WRONG_TYPE_ FOR_WRITE 0XC004C85D Writing on the Element type with the given<br />

Data type is not implemented<br />

CDBM_E_NO_APPEND_IN_<br />

STRUCTURED_RECORDS<br />

0XC004C85E<br />

Method IDbmRecord::AppendData is not<br />

allowed for structured records<br />

<strong>DTM</strong> for Hilscher <strong>PROFIBUS</strong> <strong>DP</strong> <strong>Slave</strong> Device | Configuration of Hilscher <strong>Slave</strong> Devices<br />

DOC091001OI07EN | Revision 7 | English | 2011-09 | Released | Public © Hilscher, 2009-2011

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!