NCN5130
www.onsemi.com
46
re (receive error): ‘1’ if newly received frame contained corrupted bytes (wrong parity, wrong stop bit or
incorrect bit timings)
ce (checksum or length error): ‘1’ if newly received frame contained wrong checksum or length which does not correspond
to the number of received bytes
te (timing error): ‘1’ if newly received frame contained bytes whose timings do not comply with the KNX
standard
res (reserved): Reserved for future use (will be ‘0’).
Remarks:
− If the repeat flag is not set (see Set Repetition Service p36), the device will only perform one attempt to send the KNX
telegram.
− Sending of the KNX telegram over the KNX bus is only started after all data bytes are received and the telegram is
assembled.
− When starting transmission of a new frame with U_L_DataStart.req, the device automatically resets the internal offset of
the data index to zero.
− Data offsets of 5, 6 and 7 are forbidden (U_L_DataOffset.req)!
Remarks on Figures 44 to 49:
− x = don‘t care (in respect with KNX standard)
− See Tables 12 and 13 for more details on all the bits
− Code of U_FrameEnd.ind (0xCB) can also be part of the KNX frame content (Data Octet). When NCN5130 transmits
the data octet (0xCB) on the KNX bus, 2 bytes (2 times 0xCB) will be transmitted back to the host controller to make it
possible for the host controller to distinguish between a data octet (0xCB) and U_FrameEnd.ind. This remark is only
valid if frame end with MARKER is enabled.
− See p53 for info on CRC−CCITT.