 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| ? semiconductor components industries, llc, 2013 april, 2013 ? rev. 2 1 publication order number: NCN5120/d NCN5120 transceiver for knx twisted pair networks introduction NCN5120 is a receiver ? transmitter ic suitable for use in knx twisted pair networks (knx tp1 ? 256). it supports the connection of actuators, sensors, microcontrollers, switches or other applications in a building network. NCN5120 handles the transmission and reception of data on the bus. it generates from the unregulated bus voltage stabilized voltages for its own power needs as well as to power external devices, for example, a microcontroller. NCN5120 assures safe coupling to and decoupling from the bus. bus monitoring warns the external microcontroller for loss of power so that critical data can be stored in time. key features ? 9600 baud knx communication speed ? supervision of knx bus voltage ? supports bus current consumption up to 13 and 26 ma ? selectable knx bus current (0.5 ma/ms and 1.0 ma/ms) ? high efficient dc ? dc converters ? 3.3 v fixed ? 3.3 v to 21 v selectable ? control and monitoring of power regulators ? linear 20 v regulator ? prepared for sleep mode ? buffering of sent data frames (extended frames supported) ? selectable uart or spi interface to host controller ? selectable uart and spi baud rate to host controller ? optional crc on uart to the host ? optional received frame ? end with marker service ? optional direct coupling of rxd and txd to host (analog mode) ? operates with industry standard low cost 16 mhz quartz ? generates clock of 8 or 16 mhz for external devices ? auto acknowledge (optional) ? auto polling (optional) ? temperature monitoring ? operating t emperature range ? 25 c to +85 c ? these devices are pb ? free and are rohs compliant http://onsemi.com qfn40 mn suffix case 485au see detailed ordering and shipping information in the package dimensions section on page 53 of this data sheet. ordering information a = assembly location wl = wafer lot yy = year ww = work week g = pb ? free package xxx = product variant = (contact on semiconductor if = product variant is 001) marking diagram 40 1 NCN5120 21245 ? xxx awlyywwg
NCN5120 http://onsemi.com 2 block diagram figure 1. block diagram NCN5120 por tw tsd uvd dc/dc converter 1 dc/dc converter 2 osc NCN5120 cav vbus1 ccp txo fanin/wake vbus2 v20v xtal1 xtal2 xsel xclk saveb resetb testout vss2 vdd2 vdd2mv vdd2mc vsw2 vss1 vdd1 vdd1m vsw1 vin mode2 mode1 treq csb/uc1 sdo/txd sdi/rxd sck/uc2 vssd vddd vdda vssa vfilt ceq2 ceq1 20v ldo fan ? in control vaux bus coupler impedance control transmitter osc receiver uart spi knx dll mode interface controller rc osc diagnostics wake ? up pin out vssa vbus2 txo ccp cav vbus1 ceq1 ceq2 vfilt vdd2mv vdd2mc vdd2 vss2 vsw2 vsw1 vss1 vdd1 vdd1m nc nc mode1 mode2 treq csb/uc1 sdi/rxd sdo/txd sck/uc2 vddd vssd xclk xsel xtal2 xtal1 saveb resetb fanin/wake testout vdda 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 30 29 28 27 26 25 24 23 22 21 40 39 38 37 36 35 34 33 32 31 NCN5120 v20v figure 2. pin out NCN5120 (top view) vin NCN5120 http://onsemi.com 3 pin description table 1. pin list and description name pin description type equivalent schematic vssa 1 analog supply voltage ground supply vbus2 2 ground for knx transmitter supply tx0 3 knx transmitter output analog output type 1 ccp 4 ac coupling external capacitor connection analog i/o type 2 cav 5 capacitor connection to average bus dc voltage analog i/o type 3 vbus1 6 knx power supply input supply type 5 ceq1 7 capacitor connection 1 for defining equalization pulse analog i/o type 4 ceq2 8 capacitor connection 2 for defining equalization pulse analog i/o type 4 vfilt 9 filtered bus voltage supply type 5 v20v 10 20v supply output supply type 5 vdd2mv 11 voltage monitor of voltage regulator 2 analog input type 8 vdd2mc 12 current monitor input 1 of voltage regulator 2 analog input type 9 vdd2 13 current monitor input 2 of voltage regulator 2 analog input type 8 vss2 14 voltage regulator 2 ground supply vsw2 15 switch output of voltage regulator 2 analog output type 6 vin 16 voltage regulator 1 and 2 power supply input supply type 5 vsw1 17 switch output of voltage regulator 1 analog output type 6 vss1 18 voltage regulator 1 ground supply vdd1 19 current input 2 and voltage monitor input of voltage regulator 1 analog input type 8 vdd1m 20 current monitor input 1 of voltage monitor 1 analog input type 9 nc 21, 22 not connected (do not connect) mode1 23 mode selection input 1 digital input type 12 mode2 24 mode selection input 2 digital input type 12 treq 25 transmit request input digital input type 12 csb/uc1 26 chip select output (spi) or configuration input (uart) digital output or digital input type 13 or 14 sdi/rxd 27 serial data input (spi) or receive input (uart) digital input type 14 sdo/txd 28 serial data output (spi) or transmit output (uart) digital output type 13 sck/uc2 29 serial clock output (spi) or configuration input (uart) digital output or digital input type 13 or 14 vddd 30 digital supply voltage input supply type 7 vssd 31 digital supply voltage ground supply xclk 32 oscillator clock output digital output type 13 xsel 33 clock selection (quartz or digital clock) digital input type 12 xtal2 34 clock generator output (quartz) or input (digital clock) analog output or digital input type 10 or 14 xtal1 35 clock generator input (quartz) analog input type 10 saveb 36 save signal (open drain with pull ? up) digital output type 15 resetb 37 reset signal (open drain with pull ? up) digital output type 15 fanin/wake 38 fan ? in and wake ? up input digital input type 11 testout 39 test output (do not connect) analog output vdda 40 analog supply voltage input supply type 7 note: type of csb/uc1 and sck/uc2 is depending on status mode1 ? mode2 pin type of xtal1 and xtal2 pin is depending on status xsel pin. NCN5120 http://onsemi.com 4 equivalent schematics following figure gives the equivalent schematics of the user relevant inputs and outputs. the diagrams are simplified representations of the circuits used. txo 60v ccp 60v 60v cav 7v ceqx 60v type 1: txo ? pin type 2: ccp ? pin type 3: cav ? pin type 4: ceq1 and ceq2 ? pin vbus1 60v vbus1 vfilt 60v vfilt v20v 60v v20v vin 60v vin vswx vin 60v type 5: vbus1 ? , vfilt ? , v20v and vin ? pin type 6: vsw1 and vsw2 ? pin vdda vdda 7v vddd vddd 7v vdd2mv 7v vdd2 60v vdd1 7v type 7: vddd ? and vdda ? pin type 8: vdd1 ? , vdd2 ? and vdd2mv ? pin vdd1m vdd1 7v 7v vdd2mc vdd2 7v 60v xtal2 vddd xtal1 vddd type 9: vdd1m ? and vdd2mc ? pin type 10: xtal1 ? and xtal2 ? pin in vddd r down out vddd in vddd out vddd r up type 12: mode1 ? , mode2 ? , treq ? and xsel ? pin type 13: csb/uc1 ? , sdo/txd ? , sck/uc2 ? and xclk ? pin type 14: csb/uc1 ? , sdi/rxd ? , sck/uc2 and xtal2 ? pin type 15: resetb ? and saveb ? pin fanin/wake r up 7v vaux type 11: fanin/wake ? pin note: type of csb/uc1 and sck/uc2 is depending on status mode1 ? mode2 pin type of xtal1 and xtal2 pin is depending on status xsel pin. figure 3. in ? and output equivalent diagrams NCN5120 http://onsemi.com 5 electrical specification table 2. absolute maximum ratings (notes 1 and 2) symbol parameter min max unit v txo knx transmitter output voltage ? 0.3 +45 v i txo knx transmitter output current (note 3) 250 ma v ccp voltage on ccp ? pin ? 10.5 +14.5 v v cav voltage on cav ? pin ? 0.3 +3.6 v v bus1 voltage on vbus1 ? pin ? 0.3 +45 v i bus1 current consumption vbus1 ? pin 0 60 ma v ceq voltage on pins ceq1 and ceq2 ? 0.3 +45 v v filt voltage on vfilt ? pin ? 0.3 +45 v v 20v voltage on v20v ? pin ? 0.3 +25 v v dd2mv voltage on vdd2mv ? pin ? 0.3 +3.6 v v dd2mc voltage on vdd2mc ? pin ? 0.3 +25 v v dd2 voltage on vdd2 ? pin ? 0.3 +25 v v sw voltage on vsw1 ? and vsw2 ? pin ? 0.3 +45 v v in voltage on vin ? pin ? 0.3 +45 v v dd1 voltage on vdd1 ? pin ? 0.3 +3.6 v v dd1m voltage on vdd1m ? pin ? 0.3 +3.6 v v dig voltage on pins mode1, mode2, treq, csb/uc1, sdi/txd, sdo/rxd, sck/ uc2, xclk, xsel, saveb, resetb and fanin/wake ? 0.3 +3.6 v v dd voltage on vddd ? and vdda ? pin ? 0.3 +3.6 v v xtal voltage on xtal1 ? and xtal2 ? pin ? 0.3 +3.6 v t st storage temperature ? 55 +150 c t j junction temperature (note 4) ? 25 +155 c v hbm human body model electronic discharge immunity (note 5) ? 2 +2 kv stresses exceeding maximum ratings may damage the device. maximum ratings are stress ratings only. functional operation above t he recommended operating conditions is not implied. extended exposure to stresses above the recommended operating conditions may af fect device reliability. 1. convention: currents flowing in the circuit are defined as positive. 2. vbus2, vss1, vss2, vssa and vssd form the common ground. they are hard connected to the pcb ground layer. 3. room temperature, 27 shunt resistor for transmitter, 250 ma over temperature range. 4. normal performance within the limitations is guaranteed up to the thermal w arning level. between thermal w arning and thermal shutdown temporary loss of function or degradation of performance (which ceases after the disturbance ceases) is possible. 5. according to jedec jesd22 ? a114. NCN5120 http://onsemi.com 6 recommend operation conditions operating ranges define the limits for functional operation and parametric characteristics of the device. note that the functionality of the chip outside these operating ranges is not guaranteed. operating outside the recommended operating ranges for extended periods of time may affect device reliability. table 3. operating ranges symbol parameter min max unit v bus1 vbus1 voltage (note 6) +20 +33 v v dd digital and analog supply voltage (vddd ? and vdda ? pin) +3.13 +3.47 v v in input voltage dc ? dc converter 1 and 2 (note 7) +8.47 +33 v v ccp input voltage at ccp ? pin ? 10.5 +14.5 v v dd1 input voltage on vdd1 ? pin +3.13 +3.47 v v dd1m input voltage on vdd1m ? pin +3.13 +3.57 v v dd2 input voltage on vdd2 ? pin +3.1 +21 v v dd2mc input voltage on vdd2mc ? pin +3.1 +21.1 v v dd2mv input voltage on vdd2mv ? pin +1.2 vdd v v dig input voltage on pins mode1, mode2, treq, csb/uc1, sdi/rxd, sck/uc2, and xsel 0 vdd v v wake input voltage on fanin/wake ? pin 0 3.6 v f clk clock frequency external quartz 16 mhz t a ambient temperature ? 25 +85 c t j junction temperature (note 8) ? 25 +125 c 6. voltage indicates dc value. with equalization pulse bus voltage must be between 11 v and 45 v. 7. minimum operating voltage on vin ? pin should be equal to the lowest value of vdd1 and vdd2. 8. higher junction temperature can result in reduced lifetime. table 4. dc parameters the dc parameters are given for a device operating within the recommended operating conditions unless otherwise specified. convention: currents flowing in the circuit are defined as positive. symbol pin(s) parameter remark/test conditions min typ max unit power supply v bus1 vbus1 bus dc voltage excluding active and equalization pulse 20 33 v i bus1_int bus current consumption normal operating mode. no external load, dc1 and dc2 enabled, continuous trans ? mission of ?0? on the knx bus by another knx device (50% bus load), based on figure 14 5 ma i sleep sleep mode current consumption 1.35 1.8 ma v bush undervoltage release level v bus1 rising, see figure 4 17.1 18.0 18.9 v v busl undervoltage trigger level v bus1 falling, see figure 4 15.9 16.8 17.7 v v bus_hyst undervoltage hysteresis 0.6 v v ddd vddd digital power supply 3.13 3.3 3.47 v v dda vdda analog power supply 3.13 3.3 3.47 v v aux auxiliary supply 2.8 3.3 3.6 v knx bus coupler i coupler_lim bus coupler current limitation fanin/wake = 1, v filt > v filth 13 30 ma fanin/wake = 0, v filt > v filth 26 60 ma NCN5120 http://onsemi.com 7 table 4. dc parameters the dc parameters are given for a device operating within the recommended operating conditions unless otherwise specified. convention: currents flowing in the circuit are defined as positive. symbol unit max typ min remark/test conditions parameter pin(s) knx bus coupler v coupler_drop vbus1, vfilt coupler voltage drop i bus1 = 12 ma v coupler_drop = v bus1 ? v filt 3.5 6.5 v i bus1 = 24 ma v coupler_drop = v bus1 ? v filt 4.5 8 v v filth vfilt undervoltage release level v filt rising, see figure 5 10.1 10.6 11.2 v v filtl undervoltage trigger level v filt falling, see figure 5 8.4 8.9 9.4 v fixed dc ? dc converter v in vin input voltage 8.47 33 v v dd1 vdd1 output voltage 3.13 3.3 3.47 v v dd1_rip output voltage ripple v in = 25 v, i dd1 = 40 ma 40 mv i dd1_lim overcurrent threshold r 2 = 1 , see figure 14 ? 100 ? 200 ma vdd1 power efficiency (dc converter only) v in = 25 v, i dd1 = 35 ma, l 1 = 220 h (1.26 esr), see figure 13 90 % r ds(on)_p1 r ds(on) of power switch see figure 17 8 r ds(on)_n1 r ds(on) of flyback switch see figure 17 4 v dd1m vdd1m input voltage vdd1m ? pin 3.57 v adjustable dc ? dc converter v in vin input voltage v dd2 33 v v dd2 vdd2 output voltage v in v dd2 3.3 21 v v dd2h undervoltage release level v dd2 rising, see figure 6 0.9 x v dd2 v v dd2l undervoltage trigger level v dd2 falling, see figure 6 0.8 x v dd2 v v dd2_rip output voltage ripple v in = 25 v, v dd2 = 3.3 v, i dd2 = 40 ma 40 mv i dd2_lim overcurrent threshold r 3 = 1 , see figure 14 ? 100 ? 200 ma vdd2 power efficiency (dc converter only) v in = 25 v, v dd2 = 3.3 v, i dd2 = 35 ma, l 2 = 220 h (1.26 esr), see figure 14 90 % r ds(on)_p2 r ds(on) of power switch see figure 17 8 r ds(on)_n2 r ds(on) of flyback switch see figure 17 4 v dd2m vdd2mc input voltage vdd2mc ? pin 21.1 v r vdd2m vdd2mv input resistance vdd2mv ? pin 60 100 140 k v20v regulator v 20v v20v v20v output voltage i 20v < 4 ma, v filt 21 v 18 20 22 v i 20v v20v output current 0 ? 4 ma i 20v_lim v20v output current limitation ? 11 ma v 20vh v20v undervoltage release level v 20v rising, see figure 7 12.6 13.4 14.2 v v 20vl v20v undervoltage trigger level v 20v falling, see figure 7 11.8 12.6 13.4 v v 20v_hyst v20v undervoltage hysteresis v 20v_hyst = v 20vh ? v 20vl 0.8 v NCN5120 http://onsemi.com 8 table 4. dc parameters the dc parameters are given for a device operating within the recommended operating conditions unless otherwise specified. convention: currents flowing in the circuit are defined as positive. symbol unit max typ min remark/test conditions parameter pin(s) xtal oscillator v xtal xtal1, xtal2 voltage on xtal ? pin v ddd v fan ? in and wake ? up control v wake_h fanin/ wake fanin/wake ? pin release level see figure 8 1.5 1.8 2.1 v v wake_l fanin/wake ? pin active level see figure 8 0.9 1.2 1.4 v v wake_hyst hysteresis on fanin/wake ? pin see figure 8 0.6 v r wake pull ? up resistor fanin/ wake ? pin pull ? up connected to v aux 80 165 270 digital inputs v il sck/uc2, sdi/rxd, csb/uc1, treq, mode1, mode2, xsel logic low threshold 0 0.7 v v ih logic high threshold 2.65 v ddd v r down internal pull ? down resistor sck/uc2 ? , sdi/rxd ? and csb/uc1 pin excluded. only valid in normal state. 5 10 28 k digital outputs v ol sck/uc2, sdo/txd, csb/uc1, xclk logic low output level 0 0.4 v v oh logic high output level v ddd ? 0.45 v ddd v i l sck/uc2, xclk load current ? 8 ma sdo/txd, csb/uc1 ? 4 ma v ol saveb, resetb logic low level open drain i ol = 4 ma 0.4 v r up internal pull ? up resistor 20 40 80 k temperature monitor t tw thermal warning rising temperature see figure 9 105 115 135 c t tsd thermal shutdown rising temperature see figure 9 125 140 155 c t hyst thermal hysteresis see figure 9 5 11 15 c t delta t tsd and t tw see figure 9 25 c package thermal resistance value rth ja thermal resistance junction ? to ? ambient simulated conform jedec jesd ? 51, (2s2p) 30 k/w simulated conform jedec jesd ? 51, (1s0p) 60 k/w rth jp thermal resistance junction ? to ? exposed pad 0.95 k/w NCN5120 http://onsemi.com 9 table 5. ac parameter the ac parameters are given for a device operating within the recommended operating conditions unless otherwise specified. symbol pin(s) parameter remark/test conditions min typ max unit power supply t bus_filter vbus1 vbus1 filter time see figure 4 2 ms fixed dc ? dc converter t vsw1_rise vsw1 rising slope at vsw1 ? pin 0.45 v/ns t vsw1_fall falling slope at vsw1 ? pin 0.6 v/ns adjustable dc ? dc converter t vsw2_rise vsw2 rising slope at vsw2 ? pin 0.45 v/ns t vsw2_fall falling slope at vsw2 ? pin 0.6 v/ns xtal oscillator f xtal xtal1, xtal2 xtal oscillator frequency 16 mhz fan ? in and wake ? up control t wake fanin/ wake debounce time on fanin/ wake ? pin see figure 8 100 ms watchdog t wdpr prohibited watchdog acknowledge delay see watchdog, p18 2 33 ms t wdto watchdog timeout interval selectable over uart or spi 33 524 ms t wdto_acc watchdog timeout interval accuracy =xtal accuracy t wdrd watchdog reset delay 0 ns t reset reset duration 8 s master serial peripheral interface (master spi) t sck sck spi clock period spi baudrate depending on configuration input bits (see interface mode, p23). tolerance is equal to xtal oscillator tolerance. see also figure 11 2 s 8 s t sck_high spi clock high time t sck / 2 t sck_low spi clock low time t sck / 2 t sdi_set sdi spi data input setup time 125 ns t sdi_hold spi data input hold time 125 ns t sdo_valid sdo spi data output valid time c l = 20 pf, see figure 11 100 ns t cs_high csb spi chip select high time see figure 11 0.5 x t sck t cs_set spi chip select setup time 0.5 x t sck t cs_hold spi chip select hold time 0.5 x t sck t treq_low treq treq low time see figure 12 125 ns t treq_high treq high time 125 ns t treq_set treq setup time 125 ns t treq_hold treq hold time 125 ns universal asynchronous receiver/transmitter (uart) f uart txd, rxd uart interface baudrate baudrate depending on configuration input pins (see interface mode , p23). tolerance is equal to tolerance of xtal oscillator tolerance. 19200 baud 38400 baud NCN5120 http://onsemi.com 10 v bus t v bush v busl t bus_filter NCN5120 http://onsemi.com 11 t v 20v v 20vl v 20vh NCN5120 http://onsemi.com 12 NCN5120 http://onsemi.com 13 typical application schematics figure 13. typical application schematic NCN5120, 9 ? bit uart mode (19200bps), single supply NCN5120 vssa 1 vbus2 2 txo 3 ccp 4 cav 5 vbus1 6 ceq1 7 ceq2 8 vfilt 9 vdd2mv 11 vdd2mc 12 vdd2 13 vss2 14 vsw2 15 vin 16 vsw1 17 vss1 18 vdd1 19 vdd1m 20 nc 21 nc 22 mode1 23 treq 25 mode2 24 csb/uc1 26 sdi/rxd 27 sdo/txd 28 v20v 10 sck/uc2 29 vddd 30 vssd 31 xclk 32 xsel 33 xtal2 34 xtal1 35 saveb 36 resetb 37 fanin/wake 38 testout 39 vdda 40 3.3 c 5 d 1 d 2 r 1 c 1 c 3 c 4 c 7 c 2 l 1 c 10 3.3 3.3 c 9 c 8 a b gnd vcc 3.3 txd rxd saveb resetb r 2 x 1 uc clk 3.3 c 6 figure 14. typical application schematic NCN5120, spi (500 kbps), dual supply and wake ? up NCN5120 vssa 1 vbus2 2 txo 3 ccp 4 cav 5 vbus1 6 ceq1 7 ceq2 8 vfilt 9 vdd2mv 11 vdd2mc 12 vdd2 13 vss2 14 vsw2 15 vin 16 vsw1 17 vss1 18 vdd1 19 vdd1m 20 nc 21 nc 22 mode1 23 treq 25 mode2 24 csb/uc1 26 sdi/rxd 27 sdo/txd 28 v20v 10 sck/uc2 29 vddd 30 vssd 31 xclk 32 xsel 33 xtal2 34 xtal1 35 saveb 36 resetb 37 fanin/wake 38 testout 39 vdda 40 3.3 c 5 d 1 d 2 r 1 c 1 c 3 c 4 c 7 c 2 l 1 c 10 3.3 3.3 c 6 c 9 c 8 a b gnd vcc 3.3 sdo sdi saveb resetb r 2 l 2 r 3 r 4 r 5 c 11 v2 v2 vcc2 sck scb s 1 uc clk x 1 treq NCN5120 http://onsemi.com 14 typical application schematics figure 15. typical application schematic NCN5120, analog mode, single supply, 1.0 ma/ms current slope (fanin/wake ? pin pulled to ground) NCN5120 vssa 1 vbus2 2 txo 3 ccp 4 cav 5 vbus1 6 ceq1 7 ceq2 8 vfilt 9 vdd2mv 11 vdd2mc 12 vdd2 13 vss2 14 vsw2 15 vin 16 vsw1 17 vss1 18 vdd1 19 vdd1m 20 nc 21 nc 22 mode1 23 treq 25 mode2 24 csb/uc1 26 sdi/rxd 27 sdo/txd 28 v20v 10 sck/uc2 29 vddd 30 vssd 31 xclk 32 xsel 33 xtal2 34 xtal1 35 saveb 36 resetb 37 fanin/wake 38 testout 39 vdda 40 3.3 c 5 d 1 d 2 r 1 c 1 c 3 c 4 c 7 c 2 l 1 c 10 3.3 3.3 c 6 c 9 c 8 a b gnd vcc 3.3 txd rxd saveb resetb r 2 x 1 uc clk 3.3 table 6. external components list and description (note 9) comp. function value tolerance remarks notes c 1 ac coupling capacitor 47 nf 20% 50 v, ceramic c 2 equalization capacitor 4.7 nf 10% 25 v, ceramic c 3 capacitor to average bus dc voltage 100 nf 20% 50 v, ceramic c 4 storage and filter capacitor vfilt 100 f 20% 35 v c 5 vdda hf rejection capacitor 100 nf 20 % 6.3 v, ceramic c 6 vddd hf rejection capacitor 100 nf 20% 6.3 v, ceramic c 7 load capacitor v20v 1 f 10% 35 v, ceramic, esr < 2 c 8 , c 9 parallel capacitor x ? tal 10 pf 20% 6.3 v, ceramic c 10 load capacitor vdd1 10 f 20% 6.3 v, ceramic, esr < 0.1 c 11 load capacitor vdd2 10 f 20% 10 v, ceramic, esr < 0.1 note 10 r 1 shunt resistor for transmitting 22 10% 1 w r 2 dc1 sensing resistor 1 5% 0.0625 w r 3 dc2 sensing resistor 1 5% 0.0625 w r 4 voltage divider to specify vdd2 10 k 5% 0.0625 w see p16 to calculate the value note 10 r 5 27 k l 1 , l 2 dc1/dc2 inductor 220 h 10% coils electronic da54np ? 221k d 1 reverse polarity protection diode ss16 on semiconductor d 2 voltage suppressor 1sma40ca on semiconductor x 1 crystal oscillator fa ? 238 epson toyocom, 16 mhz, 50 ppm, 10 pf s 1 push button 9. components based on absolute maximum ratings! 10. c 11 , r 4 and r 5 are based on 5 v vdd2 voltage. NCN5120 http://onsemi.com 15 analog functional description because NCN5120 follows the knx standard only a brief description of the knx related blocks is given in this datasheet. detailed information on the knx bus can be found on the knx website ( www.knx.org ) and in the knx standards. knx bus interfacing each bit period is 104 s. logic 1 is simply the dc level of the bus voltage which is between 20 v and 33 v. logic 0 is encoded as a drop in the bus voltage with respect to the dc level. logic 0 is known as the active pulse. the active pulse is produced by the transmitter and is ideally rectangular. it has a duration of 35 s and a depth between 6 and 9 v (v act ). each active pulse is followed by an equalization pulse with a duration of 69 s. the latter is an abrupt jump of the bus voltage above the dc level followed by an exponential decay down to the dc level. the equalization pulse is characterized by its height v eq and the voltage v end reached at the end of the equalization pulse. see the knx twisted pair standard (knx tp1 ? 256) for more detailed knx information. dc level v bus t 104 s 35 s69 s active pulse equalization pulse 104 s 0 1 v eq v act v end figure 16. knx bus voltage versus digital value knx bus transmitter the purpose of the transmitter is to produce an active pulse (see figure 16) between 6 v and 9 v regardless of the bus impedance (note 1). in order to do this the transmitter will sink as much current as necessary until the bus voltage drops by the desired amount. knx bus receiver the receiver detects the beginning and the end of the active pulse. the detection threshold for the start of the active pulse is ? 0.45 v (typ.) below the average bus voltage. the detection threshold for the end of the active pulse is ? 0.2 v (typ.) below the average bus voltage giving a hysteresis of 0.25 v (typ.). bus coupler the role of the bus coupler is to extract the dc voltage from the bus and provide a stable voltage supply for the purpose of powering the NCN5120. this stable voltage supplied by the bus coupler will follow the average bus voltage. the bus coupler also makes sure that the current drawn from the bus changes very slowly. for this a large filter capacitor is used on the vfilt ? pin. abrupt load current steps are absorbed by the filter capacitor. long ? term stability requires that the average bus coupler input current is equal to the average (bus coupler) load current the bus coupler is implemented as a linear voltage regulator. for efficiency purpose, the voltage drop over the bus coupler is kept minimal (see table 4). knx impedance control the impedance control circuit defines the impedance of the bus device during the active and equalization pulses. the impedance can be divided into a static and a dynamic component, the latter being a function of time. the static impedance defines the load for the active pulse current and the equalization pulse current. the dynamic impedance is produced by a block, called an equalization pulse generator, that reduces the device current consumption (i.e. increases the device impedance) as a function of time during the equalization phase so as to return energy to the bus. 1. maximum bus impedance is specified in the knx twisted pair standard NCN5120 http://onsemi.com 16 fixed and adjustable dc ? dc converter the device contains two dc ? dc buck converters, both supplied from vfilt. dc1 provides a fixed voltage of 3.3 v. this voltage is used as an internal low voltage supply (v dda and v ddd ) but can also be used to power external devices (vdd1 ? pin). dc1 is automatically enabled during the power ? up procedure (see analog state diagram, p19). dc2 provides a programmable voltage by means of an external resistor divider. it is not used as an internal voltage supply making it not mandatory to use this dc ? dc converter (if not needed, tie the vdd2mv pin to vdd1, see also figure 13). dc2 can be monitored ( v dd1 i dd1 v dd2 i dd2 1 (eq. 2) i bus will be limited by the knx standard and should be lower or equal to i coupler (see table 4). minimum v bus is 20 v (see knx standard). v dd1 and v dd2 can be found back in table 4. i dd1 , i dd2 and i 20v must be chosen in a correct way to be in line with the knx specification (note 2). v20v regulator this is the 20 v low drop linear voltage regulator used to supply external devices. as it draws current from vfilt, this current is seen without any power conversion directly at the vbus1 pin. the v20v regulator starts up by default but can be disabled by a command from the host controller ( NCN5120 http://onsemi.com 17 the fanin/wake ? pin can also be used to exit from sleep mode (see p18). when in sleep mode, a low level on the fanin/wake ? pin initiates the power ? up procedure of the device. because fanin/wake ? pin has an internal pull ? up a simple push button can be used to exit sleep mode (see also figure 14). this functionality is not available when the fanin/wake ? pin is pulled to ground. when using the fanin/wake ? pin, timings must be respected (see table 5 and figure 8). resetb ? and saveb ? pin the resetb signal can be used to keep the host controller in a reset state. when resetb is low this indicates that the bus voltage is too low for normal operation and that the fixed dc ? dc converter has not started up. it could also indicate a thermal shutdown (tsd). the resetb signal also indicates if communication between host and NCN5120 is possible. the saveb signal indicates correct operation. when saveb goes low, this indicates a possible issue (loss of bus power or too high temperature) which could trigger the host controller to save critical data or go to a save state. resetb ? and saveb ? pin are open ? drain pins with an internal pull ? up resistor to v ddd . voltage supervisors NCN5120 has different voltage supervisors monitoring vbus, vfil t, vdd2 and v20v. the general function of a voltage supervisor is to detect when a voltage is above or below a certain level. the levels for the different voltages monitored can be found back in t able 4 (see al so figures 4, 5, 6 and 7). the status of the voltage supervisors can be monitored by the host controller (see system status service, p33). depending on the voltage supervisor outputs, the device can enter different states (see analog state diagram, p19). vsw1 vin vss1 vdd1m vdd1 vsw2 vss2 vdd2mv vdd2mc vdd2 comp switch controller comp switch controller from vfilt 1 10 f vdd1 = 3.3v 1 10 f vdd2= 3.3v ? 21v NCN5120 r 5 r 4 l 2 l 1 p 2 n 2 p 1 n 1 figure 17. fixed (vdd1) and adjustable (vdd2) dc ? dc converter r down osc 16mhz 8 mhz NCN5120 xclk xtal1 xtal2 xsel figure 18. xtal oscillator figure 19. external clock generator or 16 mhz r down osc 8mhz or 16mhz NCN5120 3.3v xtal2 xtal1 xclk xsel clkout 3.3v vcc gnd micro ? controller NCN5120 http://onsemi.com 18 table 7. status of several blocks during the different (analog) states state osc xclk vdd1 vdd2/v20v spi/uart knx reset off off off off inactive inactive start ? up off off start ? up off inactive inactive stand ? by (note 11) off 4 mhz on start ? up active inactive (note 16) stand ? by (note 12) on (note 14) on (note 14) on on (note 15) active inactive (note 16) normal on on (note 13) on on active active sleep off off off off inactive inactive 11. only valid when entering stand ? by from start ? up state. 12. only valid when entering stand ? by from normal state. 13. 8 mhz 14. 4 mhz signal if stand ? by state was entered due to oscillator issue. otherwise 8 mhz clock signal. 15. only operational if stand ? by state was not entered due to vdd2 or v20v issue. 16. under certain conditions knx bus is (partly) active. see digital state diagram for more details. temperature monitor the device produces an over ? temperature warning (tw) and a thermal shutdown warning (tsd). whenever the junction temperature rises above the thermal w arning level (t tw ), the saveb ? pin will go low to signal the issue to the host controller. because the saveb ? pin will not only go low on a thermal warning (tw), the host controller needs to verify the issue by requesting the status ( NCN5120 http://onsemi.com 19 table 8. watchdog timings wdt[3:0] t wdto [ms] t wdpr [ms] 0000 33 2 0001 66 4 0010 98 6 0011 131 8 0100 164 10 0101 197 12 0110 229 14 0111 262 16 1000 295 18 1001 328 20 1010 360 23 1011 393 25 1100 426 27 1101 459 29 1110 492 30 1111 524 31 analog state diagram the analog state diagram of NCN5120 is given in figure 20. the status of the oscillator, xclk ? pin, dc ? dc converters, v20v regulator, serial and knx communication during the different (analog) states is given in table 7. figure 21 gives a detailed view on the start ? up behavior of NCN5120. after applying the bus voltage, the filter capacitor starts to charge. during this reset state, the current drawn from the bus is limited to i coupler (for details see the knx standards). once the voltage on the filter capacitor reaches 10 v (typ.), the fixed dc ? dc converter (powering vdda) will be enabled and the device enters the start ? up state. when v dd1 gets above 2.8 v (typ.), the otp memory is read out to trim some analog parameters (otp memory is not accessible by the user). when done, the stand ? by state is entered and the resetb ? pin is made high. if at this moment v bus is above v bush , the vbus ? bit will be set ( NCN5120 http://onsemi.com 20 figure 20. analog state diagram reset resetb = ?0? saveb = ?0? start ? up resetb = ?0? saveb = ?0? stand ? by resetb = ?1? saveb = ?0? normal resetb = ?1? saveb = ?1? sleep resetb = ?0? saveb = ?0? v filt > 10 v and temp < tsd v filt < 6.5 v v dda ok and otp read done NCN5120 http://onsemi.com 21 figure 21. start ? up behavior NCN5120 http://onsemi.com 22 figure 22. shut ? down behavior NCN5120 http://onsemi.com 23 interface mode the device can communicate with the host controller by means of a uart interface or an spi interface. the selection of the interface is done by the pins mode1, mode2, treq, sck/uc2 and csb/uc1. table 9. interface selection treq mode2 mode1 sck/uc2 csb/uc1 sdi/rxd sdo/txd description 0 0 0 0 0 rxd txd 9 ? bit uart ? mode, 19200 bps 0 0 0 0 1 9 ? bit uart ? mode, 38400 bps 0 0 0 1 0 8 ? bit uart ? mode, 19200 bps 0 0 0 1 1 8 ? bit uart ? mode, 38400 bps 1 0 0 x x driver receiver analog mode treq 0 1 sck (out) csb (out) sdi sdo spi master, 125 kbps treq 1 0 spi master, 500 kbps note: x = don?t care uart interface the uart interface is selected by pulling pins treq, mode1 and mode2 to ground. pin uc2 is used to select the uart mode (?0? = 9 ? bit, ?1? = 8 ? bit) and pin uc1 is used to select the baudrate (?0? = 19200 bps, ?1? = 38400 bps). the uart interface allows full duplex, asynchronous communication. the difference between 8 ? bit mode and 9 ? bit mode is that in 9 ? bit an additional parity bit is transmitted. in 8 ? bit mode one extra service is available (u_framestate.ind). the sdi/rxd ? pin is the NCN5120 uart receive pin and is used to send data from the host controller to the device. pin sdo/txd is the NCN5120 uart transmit pin and is used to transmit data between the device and the host controller. figure 13 gives an uart application example (9 ? bit, 19200 bps). data is transmitted lsb first. start (= 0) bit 0 bit 1 bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 stop (= 1) figure 23. 8 ? bit uart mode start (= 0) bit 0 bit 1 bit 2 bit 3 bit 4 bit 5 bit 6 bit 7 parity stop (= 1) figure 24. 9 ? bit uart mode one special uart mode is foreseen called analog mode. when this mode is selected (treq = ?1?, modex = ?0?) an immediate connection is made with the knx transmitter receiver (see figure 25). bit level coding/decoding has to be done by the host controller. keep in mind that the signals on the sdi/rxd ? and sdo/txd ? pin are inverted. figure 15 gives an analog mode application example. figure 25. analog uart mode por tw/ tsd uvd dc/dc converter 1 dc/dc converter 2 osc NCN5120 cav vbus1 ccp txo fanin/wake vbus2 v20v xtal1 xtal2 xsel xclk saveb resetb testout vss2 vdd2 vdd2mv vdd2mc vsw2 vss1 vdd1 vdd1m vsw1 vin mode2 mode1 treq (treq = 1) csb/uc1 sdo/txd sdi/rxd sck/uc2 vssd vddd vdda vssa vfilt ceq2 ceq1 20v ldo fan ? in control vaux bus coupler impedance control transmitter osc receiver rc osc diagnostics wake ? up NCN5120 http://onsemi.com 24 spi interface the spi interface is selected by mode1 ? and mode2 ? pin. the baudrate is determined by which mode ? pin is pulled high (mode1 pulled high = 125 kbps, mode2 pulled high = 500 kbps). the spi interface allows full duplex synchronous communication between the device and the host controller. the interface operates in mode 0 (cpol and cpha = ?0?) meaning that the data is clocked out on the falling edge and sampled on the rising edge. the lsb is transmitted first. sck sdi csb lsb 1 2 3 4 5 6 msb sdo 1 0 3 2 5 4 7 6 lsb 1 2 3 4 5 6 msb figure 26. spi transfer during spi transmission, data is transmitted (shifted out serially) on the sdo/txd ? pin and received (shifted in serially) on the sdi/rxd ? pin simultaneously. sck/uc2 is set as output and is used as the serial clock (sck) to synchronize shifting and sampling of the data on the sdi ? and sdo ? pin. the speed of this clock signal is selectable (see table 9). the slave select line (csb/uc1 ? pin) will go low during each transmission allowing to selection the host controller (csb ? pin is high when spi is in idle state). shift register control NCN5120 sdo/txd sdi/rxd sck/uc2 csb/uc1 shift register host controller miso mosi sclk ss control figure 27. spi master in an spi network only one spi master is allowed (in this case NCN5120). to allow the host controller to communicate with the device the treq ? pin can be used (transmit request). when NCN5120 detects a negative edge on treq, the device will issue dummy transmission of 8 bits which will result in a transmission of data byte from the host controller to the device. see figure 12 for details on the timings. see figure 14 for an spi application example. sck sdi csb sdo treq 01234 567 ddddd ddd 01234 ddddd dummy start dummy transmission figure 28. transmission request NCN5120 http://onsemi.com 25 digital functional description the implementation of the data link layer as specified in the knx standard is divided in two parts. all functions related to communication with the physical layer and most of the data link layer services are inside NCN5120, the rest of the functions and the upper communication layers are implemented into the host controller (see figure 29). the host controller is responsible for handling: ? checksum ? parity ? addressing ? length the NCN5120 is responsible for handling: ? checksum ? parity ? acknowledge ? repetition ? timing digital state diagram the digital state diagram is given in figure 30. the current mode of operation can be retrieved by the host controller at any time (when resetb ? pin is high) by issuing the u_systemstat.req service and parsing back u_systemstat.ind service (see system status service, p33). table 10. NCN5120 digital states state explanation reset entered after power on reset (por) or in response to a u_reset.req service issued by the host controller. in this state NCN5120 gets initialized, all features disabled and services are ignored and not executed. power ? up / power ? up stop entered after reset state or when vbus, vfilt or xtal are not operating correctly (operation of vbus, vfilt and xtal can be verified by means of the system status service, p33). communication with knx bus is not allowed. u_systemstat.ind can be used to verify this state (code 00). sync NCN5120 remains in this state until it detects silence on the knx bus for at least 40 tbits. although the receiver of NCN5120 is on, no frames are transmitted to the host controller. u_systemstat.ind can be used to verify this state (code 01). stop this state is useful for setting ? up NCN5120 safely or temporarily interrupting reception from the knx bus. u_systemstat.ind can be used to verify this state (code 10). normal in this state the device is fully functional. communication with the knx bus is allowed. u_systemstat.ind can be used to verify this state (code 11). NCN5120 http://onsemi.com 26 application layer presentation layer session layer transport layer network layer data link layer logic link control media access control physical layer 7 6 5 4 3 2 1 NCN5120 host controller figure 29. osi model reference reset initialize device deactivate all features por or u_reset.req power ? up code: 00 knx rx = off knx tx = off sync code: 01 knx rx = on knx tx = off stop code: 10 knx rx = off knx tx = off normal code: 11 knx rx = on knx tx = on power ? up stop code: 00 knx rx = off knx tx = off NCN5120 http://onsemi.com 27 services execution of services depends on the digital state (figure 30). 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 (p35) for limitations of u_intregrd.req NCN5120 http://onsemi.com 28 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 NCN5120. ? 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 NCN5120 http://onsemi.com 29 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 sid e no matter how the arrow is drawn. host ctrl NCN5120 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 31. bit order of services NCN5120 http://onsemi.com 30 reset service reset the device to the initial state. 0 0 0 0 0 0 0 1 u_reset.req 0 0 0 0 0 0 1 1 u_reset.ind host ctrl NCN5120 knx bus figure 32. reset service remark: u_reset.ind will be send when entering normal state (see digital state diagram, p25). state service get internal communication state of the device. 0 0 0 0 0 0 1 0 u_state.req sc re te pe tw 1 1 1 u_state.ind host ctrl NCN5120 knx bus figure 33. state service sc (slave collision): ?1? if collision is detected during transmission of polling state re (receive error): ?1? if corrupted bytes were sent by the host controller. corruption involves incorrect parity (9 ? bit uart only) and stop bit of every byte as well as incorrect control octet, length or checksum of frame for transmission. te (transceiver error): ?1? if error detected during frame transmission (sending ?0? but receiving ?1?). pe (protocol error): ?1? if an incorrect sequence of commands sent by the host controller is detected. tw (thermal warning): ?1? if thermal warning condition is detected. set busy service activate busy mode. during this time and when autoacknowledge is active (see set address service p31), NCN5120 rejects the frames whose destination address corresponds to the stored physical address by sending the busy acknowledge. this service has no effect if autoacknowledge is not active. 0 0 0 0 0 0 1 1 u_setbusy.req host ctrl NCN5120 knx bus figure 34. set busy service remark: busy mode is deactivated immediately if the host controller confirms a frame by sending u_ackn.req service. quit busy service deactivate the busy mode. restores back to the normal autoacknowledge behavior with ack sent on the bus in response to addressing frame (only if autoacknowledge is active). this service has no effect if autoacknowledge is not active or busy mode was not set. 0 0 0 0 0 1 0 0 u_quitbusy.req host ctrl NCN5120 knx bus figure 35. quit busy service NCN5120 http://onsemi.com 31 bus monitor service activate bus monitoring state. in this mode all data received from the knx bus is sent to the host controller without performing any filtering on data link layer. acknowledge frames are also transmitted transparently. this state can only be exited by the reset service (see p30). 0 0 0 0 0 1 0 1 u_busmon.req x x x x x x x x knx message host ctrl NCN5120 knx bus x x x x x x x x knx message x x x x x x x x knx message x x x x x x x x knx message 0 0 0 0 0 0 0 1 u_reset.req 0 0 0 0 0 0 1 1 u_reset.ind x x 0 0 x x 0 0 acknowledge x x 0 0 x x 0 0 acknowledge figure 36. bus monitor service remark: x = don?t care set address service sets the physical address of the device and activates the auto ? acknowledge function. NCN5120 starts accepting all frames whose destination address corresponds to the stored physical address or whose destination address is the group address by sending iack on the bus. in case of an error detected during such frame reception, NCN5120 sends nack instead of iack. when issued several times after each other, the first call will set the physical address and activate the auto ? acknowledge. following calls will only set the physical address because auto ? acknowledge is already activated. NCN5120 confirms activation of auto ? acknowledge function by sending the u_configure.ind service to the host controller. 1 1 1 1 0 0 0 1 u_setaddress.req host ctrl NCN5120 knx bus x x x x x x x x address high byte x x x x x x x x address low byte 0 b aa ap c m 0 1 u_configure.ind x x x x x x x x dummy figure 37. set address service NCN5120 http://onsemi.com 32 b (busy mode): ?1? if busy mode is active. can be enabled with u_setbusy.req (see set busy service, p30) and disabled with u_quitbusy.req service (see quit busy service , p30) or u_ackn.req service (see receive frame service , p43). aa (auto ? acknowledge):?1? if auto ? acknowledge feature is active. can be enabled with u_setaddress.req service (see set address service , p31). ap (auto ? polling): ?1? if auto ? polling feature is active. this feature can be enabled with u_configure.req service (see configure service , p34). c (crc ? ccitt): ?1? if crc ? ccitt feature is active. this feature can be enabled with u_configure.req service (see configure service , p34). m (frame end with marker): ?1? when feature is active. this feature can be enabled with u_configure.req service (see configure service , p34). remarks: ? set address service can be issued any time but the new physical address and the autoacknowledge function will only get active after the knx bus becomes idle. ? autoacknowledge can only be deactivated by a reset service (p30) ? x = don?t care ? dummy byte can be anything. NCN5120 completely disregards this information. set repetition service specifies the maximum repetition count for transmitted frames when not acknowledged with iack. separate counters can be set for nack and busy frames. initial value of both counters is 3. if the acknowledge from remote data link layer is busy during frame transmission, NCN5120 tries to repeat after at least 150 bit times knx bus idle. the busy counter determines the maximum amount of times the frame is repeated. if the busy acknowledge is still received after the last try, an l_data.con with a negative conformation is sent back to the host controlle r. for all other cases (nack acknowledgment received, invalid/corrupted acknowledge received or time ? out after 30 bit times) NCN5120 will repeat after 50 bit times of knx bus idle. the nack counter determines the maximum retries. l_data.con with a negative confirmation is send back to the host controller when the maximum retries were reached. in worst case, the same request is transmitted (nack + busy + 1) times before NCN5120 stops retransmission. figure 38. set repetition service 1 1 1 1 0 0 1 0 u_setrepetition.req host ctrl NCN5120 knx bus 0 b 0 n maximum repetitions b b n n x x x x dummy x x x x x x x x dummy x x x x bbb: busy counter (a frame will be retransmitted bbb ? times if acknowledge with busy). nnn: nack counter (a frame will be retransmitted nnn ? times if acknowledge with nack). remark: bit 3 and 7 of the second byte need to be zero (?0?)! NCN5120 http://onsemi.com 33 system status service request the internal system state of the device. 0 0 0 0 1 1 0 1 u_systemstat .req host ctrl NCN5120 knx bus 0 1 0 0 1 0 1 1 u_systemstat .ind 2 nd byte xtal vfilt vbus vdd2 v20v tw mode figure 39. system state service v20v: ?1? if v20v linear voltage regulator is within normal operating range vdd2: ?1? if dc2 regulator is within normal operating range vbus: ?1? if knx bus voltage is within normal operating range vfilt: ?1? if voltage on tank capacitor is within normal operating range state service xtal: ?1? if crystal oscillator frequency is within normal operating range tw: ?1? if thermal warning condition is present (can also be verified with u_state.ind service (see state service, p30) mode: operation mode (see also digital state diagram, p25). bit mode 1 0 0 0 power ? up 0 1 sync 1 0 stop 1 1 normal note: saveb ? pin is low if any of bits 3 to 7 is ?0? (zero) or bit 2 is ?1?. stop mode service go to stop state. a confirmation is sent to indicate that device has switched to the stop state. see also digital state diagram , p25 0 0 0 0 1 1 1 0 u_stopmode.req host ctrl NCN5120 knx bus 0 0 1 0 1 0 1 1 u_stopmode.ind figure 40. stop mode service NCN5120 http://onsemi.com 34 exit stop mode service request transition from stop to sync state. an acknowledge service is send later to confirm that device has switched from sync to normal state. see also digital state diagram, p25. 0 0 0 0 1 1 1 1 u_exitstopmode .req host ctrl NCN5120 knx bus 0 0 0 0 0 0 1 1 u_reset.ind figure 41. exit stop mode service configure service activate additional features (which are disabled after reset). u_configure.ind service is send back to the host controller at the exact moment when the new features get activated. this is done during bus idle or outside the normal state. it confirms the execution of the request service. host ctrl NCN5120 knx bus 0 0 0 1 1 m u_configure.req c p 0 b aa ap c 1 u_configure.ind 0 m figure 42. configure service p (auto polling): when active, NCN5120 automatically fills in corresponding poll slot of polling telegrams. host controller is responsible to provide appropriate polling information with the u_pollingstate.req service (see slave polling frame service and master polling frame service, p46 and 47). c (crc ? ccitt): when active, NCN5120 accompanies every received frame with a 2 ? byte crc ? ccitt value. crc ? ccitt is also known as crc ? 16 ? ccitt. m (frame end with marker): end of received frames is normally reported with a silence of 2.6 ms on the tx line to the host controller. with this feature active, NCN5120 marks e nd of frame with u_frameend.ind + u_framestate.ind services (see send frame service and receive frame service, p35 and 43). b: ?1? if busy mode is active. can be enabled with u_setbusy.req (see set busy service, p30) and disabled with u_quitbusy.req service (see quit busy service, p30) or u_ackn.req service (see receive frame service, p43). aa: ?1? if auto ? acknowledge feature is active. can be enabled with u_setaddress.req service (see set address service, p31). ap (auto ? polling): ?1? if auto ? polling feature is active. this feature can be enabled with u_configure.req service. c (crc ? ccitt): ?1? if crc ? ccitt feature is active. see p49 for info on crc ? ccitt. this feature can be enabled with u_configure.req service. m (frame end with marker): ?1? when feature is active. this feature can be enabled with u_configure.req service. remark: activation of the additional features is done by setting the corresponding bit to ?1?. setting the bit to ?0? (zero) has no eff ect (will not deactivate feature). features can only be deactivated by a reset. set all bits (m, c and p) to ?0? (zero) to poll the current configuration status. NCN5120 http://onsemi.com 35 internal register write service write a byte to an internal device ? specific register (see internal device ? specific registers , p50). the address of the register is specified in the request. the data to be written is transmitted after the request. 0 0 1 0 1 0 a a u_intregwr .req host ctrl NCN5120 knx bus x x x x x x x x data byte figure 43. internal register write service aa: address of the internal register remark: x = don?t care (in line with internal device ? specific registers , p50). internal register read service read a byte from an internal device ? specific register (see internal device ? specific registers , p50). the address of the register is specified in the request. the next byte returns the data of the addressed register. 0 0 1 1 1 0 a a u_intregrd.req host ctrl NCN5120 knx bus x x x x x x x x data byte figure 44. internal register read service aa: address of the internal register remarks: ? x = don?t care (in line with internal device ? specific registers , p50). ? it?s advised to only use this service in stop, power ? up stop or power ? up state. in the other state erroneous behavior could occur. send frame service send data over the knx bus. the u_l_datastart.req is used to start transmission of a new frame. the byte following this request is the control byte of the knx telegram. the different bytes following the control byte are assembled by using u_l_datacont.req. the byte following u_l_datacont.req is the data byte of the knx telegram. u_l_datacont.req contains the index which specifies the position of the data byte inside the knx telegram. it?s allowed to transmit bytes in random order and even overwrite bytes (= write several times into the same index). it?s up to the host controller to correctly populate all data bytes of the knx telegram. u_l_dataend.req is used to finalize the frame and start the knx transfer. the byte following u_l_dataend.req is the checksum of the knx telegram. if the checksum received by the device corresponds to the calculated checksum, the device starts the transmission on the knx bus. if not, the device returns u_state.ind message to the host controller with receive error flag set (see state service p30 for u_state.ind). u_l_datastart/datacont/dataend only provides space for 6 index bits. because an extended frame can consist out of 263 bytes, an index of 9 bits long is needed. u_dataoffset.req provides the 3 most significant bits of the data byte index. the value is stored internally until a new offset is provided with another call. each transmitted data octet on the knx bus will also be transmitted back to the host controller. each transmission is ended with a l_data.con service where the msb indicates if an acknowledgment was received or not. when operating in spi or uart 8 ? bit mode, l_data.con is preceded with u_framestate.ind. depending on the activated features, a crc ? ccitt service and/or a marker could be included. next figures give different examples of send frames. NCN5120 http://onsemi.com 36 1 0 0 0 0 0 0 0 u_l_datastart.req host ctrl NCN5120 knx bus x x x x x x x x control byte 1 0 i i i i i i u_l_datacont.req x x x x x x x x data octet 1 0 0 0 0 1 i i i u_l_dataoffset .req 1 0 i i i i i i u_l_datacont.req x x x x x x x x data octet n 0 1 l l l l l l u_l_dataend .req x x x x x x x x checksum x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data.ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn re ce te 1 res 0 1 1 u_framestate .ind x 0 0 0 1 0 1 1 l_data.con 2.6ms silence figure 45. send frame, spi or 8 ? bit uart mode, frame end with silence, no crc ? ccitt NCN5120 http://onsemi.com 37 1 0 0 0 0 0 0 0 u_l_datastart.req host ctrl NCN5120 knx bus x x x x x x x x control byte 1 0 i i i i i i u_l_datacont.req x x x x x x x x data octet 1 0 0 0 0 1 i i i u_l_dataoffset .req 1 0 i i i i i i u_l_datacont.req x x x x x x x x data octet n 0 1 l l l l l l u_l_dataend .req x x x x x x x x checksum x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data.ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn x 0 0 0 1 0 1 1 l_data.con 2.6ms silence figure 46. send frame, 9 ? bit uart mode, frame end with silence, no crc ? ccitt NCN5120 http://onsemi.com 38 1 0 0 0 0 0 0 0 u_l_datastart.req host ctrl NCN5120 knx bus x x x x x x x x control byte 1 0 i i i i i i u_l_datacont.req x x x x x x x x data octet 1 0 0 0 0 1 i i i u_l_dataoffset .req 1 0 i i i i i i u_l_datacont.req x x x x x x x x data octet n 0 1 l l l l l l u_l_dataend.req x x x x x x x x checksum x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data.ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn x x x x x x x x crc ? ccitt low byte 2.6 ms silence x x x x x x x x crc ? ccitt high byte x 0 0 0 1 0 1 1 l_data.con figure 47. send frame, 9 ? bit uart mode, frame end with silence, with crc ? ccitt NCN5120 http://onsemi.com 39 1 0 0 0 0 0 0 0 u_l_datastart.req host ctrl NCN5120 knx bus x x x x x x x x control byte 1 0 i i i i i i u_l_datacont.req x x x x x x x x data octet 1 0 0 0 0 1 i i i u_l_dataoffset .req 1 0 i i i i i i u_l_datacont.req x x x x x x x x data octet n 0 1 l l l l l l u_l_dataend .req x x x x x x x x checksum x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data.ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn x x x x x x x x crc ? ccitt low byte 2.6ms silence x x x x x x x x crc ? ccitt high byte re ce te 1 res 0 1 1 u_framestate .ind x 0 0 0 1 0 1 1 l_data.con figure 48. send frame, spi or 8 ? bit uart mode, frame end with silence, with crc ? ccitt NCN5120 http://onsemi.com 40 1 0 0 0 0 0 0 0 u_l_datastart .req host ctrl NCN5120 knx bus x x x x x x x x control byte 1 0 i i i i i i u_l_datacont .req x x x x x x x x data octet 1 0 0 0 0 1 i i i u_l_dataoffset .req 1 0 i i i i i i u_l_datacont .req x x x x x x x x data octet n 0 1 l l l l l l u_l_dataend.req x x x x x x x x checksum x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data.ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn re ce te 1 res 0 1 1 u_framestate .ind x 0 0 0 1 0 1 1 l_data.con 1 1 0 0 1 0 1 1 u_frameend.ind figure 49. send frame, all modes, frame end with marker, no crc ? ccitt NCN5120 http://onsemi.com 41 1 0 0 0 0 0 0 0 u_l_datastart .req host ctrl NCN5120 knx bus x x x x x x x x control byte 1 0 i i i i i i u_l_datacont .req x x x x x x x x data octet 1 0 0 0 0 1 i i i u_l_dataoffset .req 1 0 i i i i i i u_l_datacont .req x x x x x x x x data octet n 0 1 l l l l l l u_l_dataend.req x x x x x x x x checksum x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data.ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn x x x x x x x x crc ? ccitt low byte x x x x x x x x crc ? ccitt high byte re ce te 1 res 0 1 1 u_framestate .ind x 0 0 0 1 0 1 1 l_data.con 1 1 0 0 1 0 1 1 u_frameend.ind figure 50. send frame, all modes, frame end with marker and with crc ? ccitt NCN5120 http://onsemi.com 42 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 p32), 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 45 to 50: ? 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 NCN5120 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 p49 for info on crc ? ccitt. NCN5120 http://onsemi.com 43 receive frame service receive data over the knx bus. upon reception from the control byte, the control byte is checked by the device. if correct, the control byte is transmitted back to the host (l_data_standard.ind or l_data_extended.ind depending if standard or extended frame type is received). after the control byte, all data bytes are transparently transmitted back to the host controller. handling of this data is a ta sk for the data link layer which should be implemented in the host controller. the host controller can indicate if the device is addressed by setting the nack, busy or ack flag (u_ackn.req). when working in spi or 8 ? bit uart mode, each frame is ended with an u_framestate.ind. depending on the activated features, a crc ? ccitt or marker could be added to the complete frame. below figures give different examples of receive frames. host ctrl NCN5120 knx bus x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data .ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn re ce te 1 0 0 1 1 u_framestate .ind 0 0 0 1 0 n b a u_ackn .req x x x x x x x x data octet n 2.6 ms silence figure 51. receive frame, spi or 8 ? bit uart mode, frame end with silence, no crc ? ccitt NCN5120 http://onsemi.com 44 host ctrl NCN5120 knx bus x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data .ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn 0 0 0 1 0 n b a u_ackn .req x x x x x x x x data octet n 2.6 ms silence figure 52. receive frame, 9 ? bit uart mode, frame end with silence, no crc ? ccitt host ctrl NCN5120 knx bus x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data.ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn 0 0 0 1 0 n b a u_ackn.req x x x x x x x x data octet n 2.6ms silence x x x x x x x x crc ? ccitt low byte x x x x x x x x crc ? ccitt high byte figure 53. receive frame, 9 ? bit uart mode, frame end with silence, with crc ? ccitt NCN5120 http://onsemi.com 45 host ctrl NCN5120 knx bus x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data.ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn 0 0 0 1 0 n b a u_ackn.req x x x x x x x x data octet n 2.6ms silence x x x x x x x x crc ? ccitt low byte x x x x x x x x crc ? ccitt high byte re ce te 1 res 0 1 1 u_framestate.ind figure 54. receive frame, spi or 8 ? bit uart mode, frame end with silence, with crc ? ccitt host ctrl NCN5120 knx bus x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data.ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn 0 0 0 1 0 n b a u_ackn.req x x x x x x x x data octet n re ce te 1 res 0 1 1 u_framestate.ind 1 1 0 0 1 0 1 1 u_frameend.ind figure 55. receive frame, all modes, frame end with marker, no crc ? ccitt NCN5120 http://onsemi.com 46 host ctrl ncn 5120 knx bus x x x x x x x x control byte x x x x x x x x data octet 1 x x x x x x x x checksum x 0 r 1 p1 p0 0 0 l_data.ind x x x x x x x x data octet 1 x x x x x x x x data octet n x x x x x x x x checksum x x x x x x x x immediate ackn 0 0 0 1 0 n b a u_ackn .req x x x x x x x x data octet n x x x x x x x x crc ? ccitt low byte x x x x x x x x crc ? ccitt high byte re ce te 1 res 0 1 1 u_framestate .ind 1 1 0 0 1 0 1 1 u_frameend .ind figure 56. receive frame, all modes, frame end with marker, with crc ? ccitt 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 on figures 51 to 56: ? 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). to make a distinguish between a data octet and u_frameend.ind, NCN5120 duplicates the data content (if 0xcb). this will result in 2 bytes transmitted to the host controller (two times 0xcb) corresponding to 1 byte received on the knx bus. above is only valid if frame end with marker is enabled. ? see p49 for info on crc ? ccitt. slave polling frame service upon reception and consistency check of the polling control byte, the control byte is send back to the host controller (l_poll_data.ind). the host controller will send the slot number to the device (u_pollingstate.req), followed by the polling address and the polling state. at the same time the source address, polling address, slot count and checksum is received over the knx bus. if the polling address received from the knx bus is equal to the polling address received from the host controller , NCN5120 will send the polling data in the slot as define by u_pollingstate.req (only if the slotcount is higher as the define slot). u_pollingstate.req can be sent at any time (not only during a transmission of a polling telegram). the information is stored internally in NCN5120 and can be reused for further polling telegrams if auto ? polling function gets activated. NCN5120 http://onsemi.com 47 host ctrl NCN5120 knx bus 1 1 1 1 0 0 0 0 control byte x x x x x x x x source address x x x x x x x x checksum 1 1 1 1 0 0 0 0 l_poll_data.ind 1 1 1 0 s s s s u_pollingstate .req x x x x x x x x slot 0 x x x x x x x x polladdrhigh x x x x x x x x source address x x x x x x x x polladdrlow x x x x x x x x poll address x x x x x x x x poll address x x x x x x x x slot count x x x x x x x x pollstate x x x x x x x x slot n figure 57. slave polling frame service remarks: x = don?t care (in respect with knx standard) ssss = slot number master polling frame service when NCN5120 receives the polling frame from the host controller, the polling frame will be transmitted over the knx bus. NCN5120 http://onsemi.com 48 host ctrl NCN5120 knx bus 1 1 1 1 0 0 0 0 control byte x x x x x x x x source address x x x x x x x x checksum 1 1 1 1 0 0 0 0 l_poll_data.ind 1 1 1 0 s s s s u_pollingstate .req x x x x x x x x slot 0 x x x x x x x x poll address x x x x x x x x source address x x x x x x x x polladdrlow x x x x x x x x poll address x x x x x x x x poll address x x x x x x x x slot count x x x x x x x x pollstate x x x x x x x x slot n x x x x x x x x source address x x x x x x x x polladdrhigh x x x x x x x x source address x x x x x x x x poll address x x x x x x x x slot count x x x x x x x x checksum x x x x x x x x slot 0 x x x x x x x x slot n 1 1 1 1 0 0 0 0 control byte x x x x x x x x source address x x x x x x x x checksum x x x x x x x x source address x x x x x x x x poll address x x x x x x x x poll address x x x x x x x x slot count figure 58. master polling frame service remarks: x = don?t care (in respect with knx standard) ssss = slot number NCN5120 http://onsemi.com 49 crc ? ccitt crc order - 16 bit crc polynom (hex) - 1021 initial value (hex) ? ffff final xor value (hex) ? 0 no reverse on output crc test string ?123456789? is 29b1h crc ? ccitt value over a buffer of bytes can be calculated with following code fragment in c, where pbuf is pointer to the start of frame buffer ulength is the frame length in bytes unsigned short calc_crc_ccitt(unsigned char* pbuf, unsigned short ulength) { unsigned short u_crc_ccitt; for (u_crc_ccitt = 0xffff; ulength ?? ; p++) { u_crc_ccitt = get_crc_ccitt(u_crc_ccitt, *p); } return u_crc_ccitt; } unsigned short get_crc_ccitt(unsigned short u_crc_val, unsigned char btval) { u_crc_val = ((unsigned char)(u_crc_val >> 8)) | (u_crc_val << 8); u_crc_val ^= btval; u_crc_val ^= ((unsigned char)(u_crc_val & 0xff)) >> 4; u_crc_val ^= u_crc_val << 12; u_crc_val ^= (u_crc_val & 0xff) << 5; return u_crc_val; } NCN5120 http://onsemi.com 50 internal device ? specific registers in total 4 device-specific register are available: ? watchdog register (0x00) ? analog control register 0 (0x01) ? analog control register 1 (0x02) ? analog status register 0 (0x03) watchdog register the watchdog register is located at address 0x00 and can be used to enable the watchdog and set the watchdog time. table 14. watchdog register extwatchdogctrl (extwr) address bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00 access r/w r/w r/w r/w r/w r/w r/w r/w reset 0 0 0 0 1 1 1 1 data wden - - - wdt table 15. watchdog register parameters parameter value description info wden 0 disable enables/disables the watchdog p18 1 enable wdt 0000 33 ms defines the watchdog time. the watchdog needs to be re-enabled (wden) within this time or a watchdog event will be triggered. 0001 66 ms 0010 98 ms 0011 131 ms 0100 164 ms 0101 197 ms 0110 229 ms 0111 262 ms 1000 295 ms 1001 328 ms 1010 360 ms 1011 393 ms 1100 426 ms 1101 459 ms 1110 492 ms 1111 524 ms remark: bit 4 ? 6 are reserved. analog control register 0 the analog control register 0 is located at address 0x01 and can be used to enable sleep mode, to disable the v20v and the dc2 regulator, to disable the xclk-pin and to set the frequency of the xclk output signal. table 16. analog control register 0 analog control register 0 (anactrl0) address bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x01 access r/w r/w r/w r/w r/w r/w r/w r/w reset 0 1 1 1 0 0 0 0 data slpen v20ven dc2en xclken xclkfreq - - - NCN5120 http://onsemi.com 51 table 17. analog control register 0 parameters parameter value description info slpen 0 disable enables/disables sleep mode ( going to sleep mode) p 18 1 enable v20ven 0 disable enables/disables the v20v regulator p 16 1 enable dc2en 0 disable enables/disables the dc2 converter p 16 1 enable xclken 0 disable enables/disables the xclk output signal p 16 1 enable xclkfreq 0 8 mhz sets the frequency of the xclk output signal (if enabled) 1 16 mhz remark: bit 0 ? 2 are reserved. analog control register 1 the analog control register 1 is located at address 0x02 and can be used to put the device in sleep mode. table 18. analog control register 1 analog control register 1 (anactrl1) address bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x02 access r/w r/w r/w r/w r/w r/w r/w r/w reset 0 0 0 0 0 0 0 0 data slp - - - - - - - table 19. analog control register 1 parameters parameter value description info slp 0 disable if ?1?, device goes to sleep mode (if slpen = ?1?). once in sleep mode, only way to get out is a wake-up event on the fanin/wake-pin. p 16 and 18 1 enable remark: bit 0 ? 6 are reserved. analog status register the analog status register is located at address 0x03 and can be used to verify the sleep mode, voltage monitors, xtal and thermal status. table 20. analog status register analog status register (anastat) address bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x03 access r r r r r r r r reset 0 0 0 0 0 0 0 0 data slpmode v20v vdd2 vbus vfilt xtal tw tsd NCN5120 http://onsemi.com 52 table 21. analog status register parameters parameter value value description info slpmode 0 disabled contains information about the previous sleep mode of the device p 18 1 enabled v20v 0 nok ?1? if voltage on v20v-pin is above the v20v undervoltage level p 16 1 ok vdd2 0 nok ?1? if voltage on vdd2-pin is above the vdd2 undervoltage level p 16 1 ok vbus 0 nok ?1? if bus voltage is above the vbus undervoltage level p 15 1 ok vfilt 0 nok ?1? if voltage on vfilt-pin is above the vfilt undervoltage level p 15 1 ok xtal 0 nok ?1? if xtal is up and running p 16 1 ok tw 0 no tw ?1? if thermal warning detected p 18 1 tw tsd 0 no tsd contains information about the previous thermal shutdown situation 1 tsd NCN5120 http://onsemi.com 53 package thermal characteristics the NCN5120 is available in a qfn40 package. for cooling optimizations, the qfn40 has an exposed thermal pad which has to be soldered to the pcb ground plane. the ground plane needs thermal vias to conduct the heat to the bottom layer. figure 59 gives an example of good heat transfer. the exposed thermal pad is soldered directly on the top ground layer (left picture of figure 59). it?s advised to make the top ground layer as large as possible (see arrows figure 59). to improve the heat transfer even more, the exposed thermal pad is connected to a bottom ground layer by using thermal vias (see right picture of figure 59). it?s advised to make this bottom ground layer as large as possible and with as less as possible interruptions. for precise thermal cooling calculations the major thermal resistances of the device are given (t able 4). the thermal media to which the power of the devices has to be given are: ? static environmental air (via the case) ? pcb board copper area (via the exposed pad) the major thermal resistances of the device are the rth from the junction to the ambient (rth ja ) and the overall rth from the junction to exposed pad (rth jp ). in table 4 one can find the values for the rth ja and rth jp , simulated according to jesd ? 51. the rth ja for 2s2p is simulated conform jedec jesd ? 51 as follows: ? a 4 ? layer printed circuit board with inner power planes and outer (top and bottom) signal layers is used ? board thickness is 1.46 mm (fr4 pcb material) ? the 2 signal layers: 70 m thick copper with an area of 5500 mm 2 copper and 20% conductivity ? the 2 power internal planes: 36 m thick copper with an area of 5500 mm 2 copper and 90% conductivity the rth ja for 1s0p is simulated conform to jedec jesd ? 51 as follows: ? a 1 ? layer printed circuit board with only 1 layer ? board thickness is 1.46 mm (fr4 pcb material) ? the layer has a thickness of 70 m copper with an area of 5500 mm 2 copper and 20% conductivity 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 30 29 28 27 26 25 24 23 22 21 40 39 38 37 36 35 34 33 32 31 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 30 29 28 27 26 25 24 23 22 21 40 39 38 37 36 35 34 33 32 31 figure 59. pcb ground plane layout condition (left picture displays the top ground layer, right picture displays the bottom ground layer) ordering information device number temperature range package shipping ? NCN5120mng ? 25 c to 85 c qfn ? 40 (pb ? free) 50 units / tube 100 tubes / box NCN5120mntwg ? 25 c to 85 c qfn ? 40 (pb ? free) 3000 / tape & reel ?for information on tape and reel specifications, including part orientation and tape sizes, please refer to our tape and reel packaging specification brochure, brd8011/d. NCN5120 http://onsemi.com 54 package dimensions qfn40 6x6, 0.5p case 485au issue o seating note 4 k 0.15 c (a3) a a1 d2 b 1 11 20 21 40 e2 40x 10 30 l bottom view top view side view d a b e 0.15 c pin one location 0.10 c 0.08 c c 31 e a 0.10 b c 0.05 c notes: 1. dimensioning and tolerancing per asme y14.5m, 1994. 2. controlling dimensions: millimeters. 3. dimension b applies to plated terminal and is measured between 0.15 and 0.30mm from terminal tip. 4. coplanarity applies to the exposed pad as well as the terminals. dim min max millimeters a 0.80 1.00 a1 0.00 0.05 a3 0.20 ref b 0.18 0.30 d 6.00 bsc d2 3.10 3.30 e 6.00 bsc 3.30 e2 3.10 e 0.50 bsc l 0.30 0.50 k plane dimensions: millimeters 0.50 pitch 3.32 0.28 3.32 40x 0.63 40x 6.30 6.30 *for additional information on our pb ? free strategy and soldering details, please download the on semiconductor soldering and mounting techniques reference manual, solderrm/d. soldering footprint* 1 l1 detail a l optional constructions l 0.20 min l1 ??? 0.15 a 0.10 b c a 0.10 b c package outline on semiconductor and are registered trademarks of semiconductor co mponents industries, llc (scillc). scillc owns the rights to a numb er of patents, trademarks, copyrights, trade secrets, and other intellectual property. a list ing of scillc?s product/patent coverage may be accessed at ww w.onsemi.com/site/pdf/patent ? marking.pdf. scillc reserves the right to make changes without further notice to any products herein. scillc makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose, nor does scillc assume any liability arising out of the application or use of any product or circuit, and s pecifically disclaims any and all liability, including without limitation special, consequential or incidental damages. ?typical? parameters which may be provided in scillc data sheets and/ or specifications can and do vary in different applications and actual performance may vary over time. all operating parame ters, including ?typicals? must be validated for each customer application by customer?s technical experts. scillc does not convey any license under its patent rights nor the right s of others. scillc products are not designed, intended, or a uthorized for use as components in systems intended for surgical implant into the body, or other applications intended to support or sustain life, or for any other application in whic h the failure of the scillc product could create a situation where personal injury or death may occur. should buyer purchase or us e scillc products for any such unintended or unauthorized appli cation, buyer shall indemnify and hold scillc and its officers, employees, subsidiaries, affiliates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unin tended or unauthorized use, even if such claim alleges that scil lc was negligent regarding the design or manufacture of the part. scillc is an equal opportunity/affirmative action employer. this literature is subject to all applicable copyrig ht laws and is not for resale in any manner. publication ordering information n. american technical support : 800 ? 282 ? 9855 toll free usa/canada europe, middle east and africa technical support: phone: 421 33 790 2910 japan customer focus center phone: 81 ? 3 ? 5817 ? 1050 NCN5120/d knx and the knx logos are trademarks of knx association. literature fulfillment : literature distribution center for on semiconductor p.o. box 5163, denver, colorado 80217 usa phone : 303 ? 675 ? 2175 or 800 ? 344 ? 3860 toll free usa/canada fax : 303 ? 675 ? 2176 or 800 ? 344 ? 3867 toll free usa/canada email : orderlit@onsemi.com on semiconductor website : www.onsemi.com order literature : http://www.onsemi.com/orderlit for additional information, please contact your local sales representative |
Price & Availability of NCN5120
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |