OMO ElectronicOMO Electronic
Expand menu
Hello, Sign inMy Account
0 Cart

NCN5130MNTWG

P1-P3P4-P6P7-P9P10-P12P13-P15P16-P18P19-P21P22-P24P25-P27P28-P30P31-P33P34-P36P37-P39P40-P42P43-P45P46-P48P49-P51P52-P54P55-P57P58-P58
NCN5130
www.onsemi.com
31
Services
Execution of services depends on the digital state (Figure 29). Certain services are rejected if received outside the Normal
State. The following table gives a view of all services and there acceptance during the different digital states.
Table 11. ACCEPTANCE OF SERVICES
Service
State
Normal Stop Sync Power−Up Bus Monitor
U_Reset.req E E E E E
U_State.req E E E E I
U_SetBusy.req E E E E I
U_QuitBusy.req E E E E I
U_Busmon.req E E E E I
U_SetAddress.req E E E E I
U_SetRepetition.req E E E E I
U_L_DataOffset.req E E E E I
U_SystemStat.req E E E E I
U_StopMode.req E I E E E
U_ExitStopMode.req I E I I E
U_Ackn.req E R R R I
U_Configure.req E E E E I
U_IntRegWr.req E E E E E
U_IntRegRd.req E E E E E
U_L_DataStart.req E R R R I
U_L_DataCont.req E R R R I
U_L_DataEnd.req E R R R I
U_PollingState.req E E E E I
NOTE:
Bus Monitor state is not a separate state. It is applied on top of Normal, Stop, Sync or Power−Up State.
Legend: E = service is executed
I = service is ignored (not executed and no feedback sent to the host controller)
R = service is rejected (not executed, protocol error is sent back to the host controller through U_State.ind)
See Internal Register Read Service (p39) for limitations of U_IntRegRd.req
NCN5130
www.onsemi.com
32
Table 12. SERVICES FROM HOST CONTROLLER
Control Field
Service Name Hex Remark
Extra Following
Bytes
Total
Bytes
7 6 5 4 3 2 1 0
INTERNAL COMMANDS – DEVICE SPECIFIC
0
0 0 0 0 0 0 1 U_Reset.req 01 1
0 0 0 0 0 0 1 0 U_State.req 02 1
0 0 0 0 0 0 1 1 U_SetBusy.req 03 1
0 0 0 0 0 1 0 0 U_QuitBusy.req 04 1
0 0 0 0 0 1 0 1 U_Busmon.req 05 1
1 1 1 1 0 0 0 1 U_SetAddress.req F1 AddrHigh
AddrLow
X (don’t care)
4
1 1 1 1 0 0 1 0 U_SetRepetition.req F2 RepCntrs
X (don’t care)
X (don’t care)
4
0 0 0 0 1 i i i U_L_DataOffset.req 08−0C iii = MSB byte
index (0…4)
1
0 0 0 0 1 1 0 1 U_SystemState.req 0D 1
0 0 0 0 1 1 1 0 U_StopMode.req 0E 1
0 0 0 0 1 1 1 1 U_ExitStopMode.req 0F 1
0 0 0 1 0 n b a U_Ackn.req 10−17 n = nack
b = busy
a = addressed
1
0 0 0 1 1 p c m U_Configure.req 18−1F p = auto−polling
c = CRC−CCITT
m = frame end
with MARKER
1
0 0 1 0 1 0 a a U_IntRegWr.req 28−2B
aa = address of
internal register
Data to be written 2
0 0 1 1 1 0 a a U_IntRegRd.req 38−3B 1
1 1 1 0 s s s s U_PollingState.req E0−EE s = slot number
(0 … 14)
PollAddrHigh
PollAddrLow
PollState
4
KNX TRANSMIT DATA COMMANDS
1
0 0 0 0 0 0 0 U_L_DataStart.req 80 Control Octet (CTRL) 2
1 0 i i i i i i U_L_DataCont.req 81−BF i = index (1…63) Data octet (CTRLE,
SA, DA, AT, NPCI, LG,
TPDU)
2
0 1 l l l l l l U_L_DataEnd.req 47−7F l = last index + 1
(7 … 63)
Check Octet (FCS) 2
With respect to command length, there are two types of services from the host controller:
• Single−byte commands: the control byte is the only data sent from the host controller to NCN5130.
• Multiple−byte commands: the following data byte(s) need to be handled according to the already received control byte.
With respect to command purpose there are two types of services from the host controller:
• Internal command: does not initiate any communication on the KNX bus.
• KNX transmit data command: initiates KNX communication
NCN5130
www.onsemi.com
33
Table 13. SERVICES TO HOST CONTROLLER
Control Field
Service Name Remark
Extra
Following
Bytes
Total
Bytes
7 6 5 4 3 2 1 0
DLL (LAYER 2) SERVICES (DEVICE IS TRANSPARENT)
1
0 r 1 p1 p0 0 0 L_Data_Standard.ind
r = not repeated (‘1’) or
repeated L_Data frame (‘0’)
p1, p0 = priority
n
0 0 r 1 p1 p0 0 0 L_Data_Extended.ind n
1 1 1 1 0 0 0 0 L_Poll_Data.ind n
ACKNOWLEDGE SERVICES (DEVICE IS TRANSPARENT IN BUS MONITOR MODE)
x
x 0 0 x x 0 0 L_Ackn.ind x = acknowledge frame 1
z 0 0 0 1 0 1 1 L_Data.con z = positive (‘1’) or negative
(‘0’) confirmation
1
CONTROL SERVICES – DEVICE SPECIFIC
0
0 0 0 0 0 1 1
U_Reset..ind
1
sc re te pe tw 1 1 1 U_State.ind sc = slave collision
re = receive error
te = transmit error
pe = protocol error
tw = temperature warning
1
re ce te 1 res 0 1 1 U_FrameState.ind re = parity or bit error
ce = checksum or length
error
te = timing error
res = reserved
1
0 b aa ap c m 0 1 U_Configure.ind b = reserved
aa = auto−acknowledge
ap = auto−polling
c = CRC−CCITT
m = frame end with
MARKER
1
1 1 0 0 1 0 1 1 U_FrameEnd.ind 1
0 0 1 0 1 0 1 1 U_StopMode.ind 1
0 1 0 0 1 0 1 1 U_SystemStat.ind V20V, VDD2,
VBUS, VFILT,
XTAL, TW,
Mode
2
Each data byte received from the KNX bus is transparently transmitted to the host controller. An exception is the
Acknowledge byte which is transmitted to the host controller only in bus monitoring mode. Other useful information can be
transmitted to the host controller by request using internal control services.
A detailed description of the services is given on the next pages. For all figures, the MSB bit is always given on the left side
no matter how the arrow is drawn.
Host Ctrl NCN5130 KNX Bus
MSB
6
5
4
3
2
1
LSB
MSB
6
5
4
3
2
1
LSB
MSB
6
5
4
3
2
1
LSB
MSB
6
5
4
3
2
1
LSB
Figure 30. Bit Order of Services
P1-P3P4-P6P7-P9P10-P12P13-P15P16-P18P19-P21P22-P24P25-P27P28-P30P31-P33P34-P36P37-P39P40-P42P43-P45P46-P48P49-P51P52-P54P55-P57P58-P58

NCN5130MNTWG

Mfr. #:
Buy NCN5130MNTWG
Manufacturer:
ON Semiconductor
Description:
Communication ICs - Various KNXB FULL FEATURE
Lifecycle:
New from this manufacturer.
Delivery:
DHL FedEx Ups TNT EMS
Payment:
T/T Paypal Visa MoneyGram Western Union

Products related to this Datasheet