03 DM_12_CH03_sketch_WS1

DMT32240C028_06WTC2.8英寸240×320图形点阵65K色DGUS屏（DGUS II）2.8Inches,320xRGBx240,65K Colors,DGUS LCM（DGUS II）修订记录/Record of Revisio日期/Revise Date描述/Content2018-11-10首次发布/First Edition2020-08-25更新实物图/Update physical drawing●参数/Item数据/Parameter说明/Description颜色Color 65K（65536）色65K(65536)colors16bit调色板5R6G5B16bit color5R6G5B显示尺寸（A.A.）Active Area(A.A.)57.6mm(宽)×43.2mm(高)57.6mm(W)×43.2mm(H)240×320像素模式240*320分辨率Resolution 240×320像素240*320可设置成0°/90°/180°/270°显示模式Support0°/90°/180°/270°rotated displaySupport0°/90°/180°/270°rotated display背光模式Brightness LED 不低于10000H（以最高亮度连续工作，亮度减半时间）≥10000H（Continuous working with maximum brightness,time of brightness halves）亮度Brightness300nit 可进行100级亮度调节（当亮度调节至最高亮度的1%~30%时，可能出现闪烁现象，不建议在此范围使用）100levels adjustment(It's not recommend to set brightness to 1%~30%of the maximum,which may lead a flicker)注：超过30分钟长时间显示高对比度静止画面可能导致显示残影，请增加屏保避免该问题.Notice:Displaying a high contrast still screen for more than30minutes may result in an image blurring.Please add the screensaver to avoid.●电性能参数/Voltage&Current参数/Item测试条件/Conditions最小值/Min典型值/Typ 最大值/Max单位/Unit工作电压Power Voltage- 4.5 5.0 5.5V工作电流（不接扬声器时）Operation Current (None Speaker)VCC＝＋5V，背光亮度最大VCC=+5V,Backlight on-220-mA VCC＝＋5V，背光关闭VCC=+5V,Backlight off-80-mA推荐工作电源：5V1A的直流稳压电源Recommended power supply:5V1A DC ●工作环境和可靠性参数/Reliability Test参数/Item测试环境/Conditions最小值/Min典型值/Typ 最大值/Max单位/Unit工作温度Working Temperature 5V电压下，湿度60%60%RH at5V voltage-202570℃储存温度StorageTemperature--302585℃工作湿度Working Humidity25℃10%60%90%RH三防处理Protective Paint--无/None--出厂前老化时间Aging Test--无/None-H ●接口性能参数/Reliability Test参数/Item测试条件/Conditions最小值/Min典型值/Typ 最大值/Max单位/Unit串口波特率Baudrate 用户自定义（硬件配置文件设置）User set78411152007833600bps串口输出电平（TXD）Output Voltage (TXD)输出1，Iout=1mAOutput1,Iout=1mA3.0 3.3-V 输出0，Iout=-1mAOutput0,Iout=-1mA-00.3V串口输入电平（RXD）Input Voltage (RXD)输入1，Iin=1mAInput1,Iin=1mA2.43.3 5.0V 输入0，Iin=-1mAInput0,Iin=-1mA0-0.5V串口模式Interface UART2：N81,3.3V TTL/CMOSUART4：N81/E81/O81/N82四种模式可选,3.3V TTL/CMOS UART2:N81,3.3V TTL/CMOSUART4:Optional N81/E81/O81/N82mode,3.3V TTL/CMOS用户接口方式Socket10Pin_1.0mm FCCSD卡接口SD Slot 有（FAT32文件格式，SDHC）Yes(FAT32file format,SDHC)扬声器接口Speaker 2PIN_2.0mm 2Pin_2.0mm●存储器类别/Item参数/Parameter最小值/Min典型值/Typ 最大值/Max单位/UnitFLASH存储器Flash 字库储存空间Space of Font--64Mbytes 注：64MB字库空间后面32Mbytes为字库和音乐空间复用Font and audio file share the back half(32Mbytes)of Font Space.全屏图片储存数量Picture Storage--245幅/PcsRAM存储器RAM 变量存储空间Variable Storage Space-128-KbytesNor Flash用户数据库User database-320-Kbytes ●UI&外设支持/UI&PeripheralsUI和外设/UI&PeripheralUI版本UI VersionT5UID1支持外设Peripherals 电容式触摸屏，扬声器Capacitive touch panel,Speaker●包装和物理尺寸/Packing Capacity&Dimension尺寸/Dimension外形尺寸Dimension 85.2(宽)×55.6(高)×12.0(厚)mm 85.2(W)×55.6(H)×12.0(T)mm净重量Net Weight44g 包装标准/Packing Capacity包装箱型号Model 包装箱尺寸Size层数（层）Layer数量/层（片）Quantity/Layer总数量（片）Quantity(Pcs)1号箱/Carton1：220mm(L)×160mm(W)×47mm(H)1222号箱/Carton2：250mm(L)×200mm(W)×80mm(H)2243号箱/Carton3：320mm(L)×270mm(W)×80mm(H)2484号箱/Carton4：450mm(L)×350mm(W)×300mm(H)225505号箱/Carton5：600mm(L)×450mm(W)×300mm(H)260120备注：不影响性能参数和使用的产品设计变更，恕不另行通知。

ASAHI KASEI[AK4122]AK412224-Bit 96kHz SRC with DIRGENERAL DESCRIPTION The AK4122 is a digital sample rate converter (SRC) with the digital audio receiver (DIR). The input sample rate ranges from 8kHz to 96kHz. The output sample rate is 32kHz, 44.1kHz, 48kHz or 96kHz. By using the AK4122, the system can take very simple configuration because the AK4122 has an internal PLL and does not need any master clock at slave mode. Then the AK4122 is suitable for the application interfacing to different sample rates like Car Audio, DVD recorder, etc.FEATURES 1. SRC • Asynchronous Sample Rate Converter • Input Sample Rate Range (fsi) : 8kHz ∼ 96kHz • Output Sample Rate (fso) : 32kHz, 44.1kHz, 48kHz, 96kHz • Input to Output Sample Rate Ratio : 0.33 to 6 • THD+N : −113dB • I/F format : MSB justified, LSB justified (16/24bit) and I2S compatible • Clock for Master mode : 256/384/512/768fs • SRC Bypass mode • Soft Mute Function 2. DIR • 4-Channel Inputs Selector & 1-Channel Through Output • AES3, IEC60958, S/PDIF, EIAJ CP1201 Compatible • Low Jitter Analog PLL • PLL Lock Range : 32kHz ∼ 96kHz • Auto detection - Non-PCM Bit Stream - DTS-CD Bit Stream - Validity Flag - Sampling Frequency (32kHz, 44.1kHz, 48kHz, 88.2kHz, 96kHz) - Unlock & Parity Error - DAT Start ID • 40-bit Channel Status Buffer • Burst Preamble bit Pc, Pd Buffer for Non-PCM bit streams • Q-subcode Buffer for CD bit streams 3. 4-wire Serial µP Interface 4. Power Supply • AVDD: 3.0 ∼ 3.6V (typ. 3.3V) • DVDD: 3.0 ∼ 3.6V (typ. 3.3V) 5. Ta = −10 ∼ 70°C 6. Package : 48pin LQFPMS0267-E-03 -1-2004/08ASAHI KASEI[AK4122]Block DiagramINT0 INT1 INT2 RX1 RX2 RX3 RX4RX1 RX2 RX3 RX4 OPS1-0RFILTTXTX PDNIPS1-0DIR PORT3 De-em FilterOSELSMUTE Serial Audio I/FLRCK BICK SDTOPORT1 BICK1 LRCK1 SDTIBICK1 LRCK1 SDTISerial Audio I/F PORT2SRCBYPSISEL1-0LRCK BICK SDTO OMCLKPLLBICK2 LRCK2 SDTIO MCLK2BICK2 LRCK2 SDTIOSerial Audio I/F Control RegisterM/S2 M/S3AVDD AVSSDVDD DVSSCDTO CDTI CCLK CSNBlock diagramMS0267-E-03 -2-2004/08ASAHI KASEI[AK4122]Ordering GuideAK4122VQ AKD4122 −10 ∼ +70°C 48pin LQFP (0.5mm pitch) Evaluation Board for AK4122Pin LayoutOMCLKDVDDSDTODVSSCCLKLRCKBVSSBICKINT148 47 46 45 44 43 42 41 40 39 38 37 CDTI CDTO TST1 INT2 TST2 TST3 M/S2 M/S3 SMUTE TST4 TST5 FILT 1 2 3 4 5 6 7 8 9 10 11 36 35 34 33 32 SDTIO BICK2 LRCK2 MCLK2 DVDD DVSS SDTI BICK1 LRCK1 PDN AVSS RAK4122VQTop ViewINT0 31 30 29 28 27 26 TST11CSN12 25 13 14 15 16 17 18 19 20 21 22 23 24 TST10 AVDDAVSSTST6TST7TST8TST9RX1RX2RX3MS0267-E-03 -3-RX4TX2004/08ASAHI KASEI[AK4122]PIN/FUNCTIONNo. 1 2 3 4 5 6 7 8 9 10 11 Pin Name CDTI CDTO TST1 INT2 TST2 TST3 M/S2 M/S3 SMUTE TST4 TST5 I/O I O O O O I I I I I I Function Control Data Input Pin Control Data Output Pin Test 1 Pin Interrupt 2 Pin Test 2 Pin Test 3 Pin This pin should be connected to DVSS. Master / Slave Mode Pin for PORT2 “H” : Master mode, “L” : Slave Mode Master / Slave Mode Pin for PORT3 “H” : Master mode, “L” : Slave Mode Soft Mute Pin “H” : Soft Mute, “L” : Normal Operation Test 4 Pin This pin should be connected to AVSS. Test 5 Pin This pin should be connected to AVSS. PLL Loop Filter Pin 470Ω±5% resistor and 2.2µF±50% ceramic capacitor in parallel with a 2.2nF±50% ceramic capacitor should be connected to AVSS externally. Analog Ground Pin Analog Power Supply Pin, 3.0 ∼ 3.6V Test 6 Pin This pin should be connected to AVSS. Receiver Input 1 Pin with Amp for 0.2Vpp (Internal Biased Pin) Test 7 Pin This pin should be connected to AVSS. Receiver Input 2 Pin with Amp for 0.2Vpp (Internal Biased Pin) Test 8 Pin This pin should be connected to AVSS. Receiver Input 3 Pin with Amp for 0.2Vpp (Internal Biased Pin) Test 9 Pin This pin should be connected to AVSS. Receiver Input 4 Pin with Amp for 0.2Vpp (Internal Biased Pin) Test 10 Pin This pin should be connected to AVSS. Test 11 Pin12 13 14 15 16 17 18 19 20 21 22 23 24FILT AVSS AVDD TST6 RX1 TST7 RX2 TST8 RX3 TST9 RX4 TST10 TST11O I I I I I I I I I ONote: All input pins except internal biased pins should not be left floating.MS0267-E-03 -4-2004/08ASAHI KASEI[AK4122]25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48R AVSS PDN LRCK1 BICK1 SDTI DVSS DVDD MCLK2 LRCK2 BICK2 SDTIO INT0 INT1 TX SDTO BICK LRCK OMCLK DVSS DVDD BVSS CSN CCLKI I I I I I/O I/O I/O O O O O I/O I/O I I IExternal Resistor Pin 12kΩ±5% resistor should be connected to AVSS externally. Analog Ground Pin Power-Down Mode Pin “H”: Power up, “L”: Power down reset and initializes the control register. Input Channel Clock Pin Audio Serial Data Clock Pin Audio Serial Data Input Pin Digital Ground Pin Digital Power Supply Pin, 3.0 ∼ 3.6V Master Clock Input Pin Input / Output Channel Clock Pin Audio Serial Data Clock Pin Audio Serial Data Input / Output Pin Interrupt 0 Pin Interrupt 1 Pin Transmitter Output Pin Audio Serial Data Output Pin Audio Serial Data Clock Pin Output Channel Clock Pin Master Clock Input Pin Digital Ground Pin Digital Power Supply Pin, 3.0 ∼ 3.6V Substrate Ground Pin This pin should be connected to AVSS. Chip Select Pin Control Data Clock PinNote: All input pins except internal biased pins should not be left floating.MS0267-E-03 -5-2004/08ASAHI KASEI[AK4122]Handling of Unused pinsThe unused digital I/O pins should be processed appropriately as below. Classification PORT1 Pin Name BICK1, LRCK1, SDTI MCLK2 BICK2, LRCK2 SDTIO M/S2 OMCLK PORT3 BICK, LRCK SDTO M/S3 RX1, RX2, RX3, RX4 INT0, INT1, INT2, TX CSN, CCLK, CDTI CDTO SMUTE TST1, TST2, TST11 TST3 TST4, TST5, TST6, TST7, TST8, TST9, TST10 Setting These pins should be connected to DVSS. This pin should be connected to DVSS. These pins should be connected to DVSS in slave mode or open in master mode. This pin should be connected to DVSS. This pin should be connected to DVDD or DVSS. This pin should be connected to DVSS. These pins should be connected to DVSS in slave mode or open in master mode. This pin should be open. This pin should be connected to DVDD or DVSS. These pins should be open. These pins should be open. These pins should be connected to DVSS. This pin should be open. This pin should be connected to DVSS. These pins should be open. This pin should be connected to DVSS. These pins should be connected to AVSS.PORT2DIR Control PORT Other TESTMS0267-E-03 -6-2004/08ASAHI KASEI[AK4122]ABSOLUTE MAXIMUM RATINGS(AVSS, BVSS, DVSS=0V; Note 1) Parameter Power Supplies: Analog Digital |BVSS − DVSS| (Note 2) Input Current, Any Pin Except Supplies Digital Input Voltage 1 (Except RX1-4 pins) Digital Input Voltage 2 (RX1-4 pins) Ambient Temperature (Power applied) Storage Temperature Symbol AVDD DVDD ∆GND IIN VIND1 VIND2 Ta Tstg min −0.3 −0.3 −0.3 −0.3 −10 −65 max 4.6 4.6 0.3 ±10 DVDD+0.3 AVDD+0.3 70 150 Units V V V mA V V °C °CNote 1. All voltages with respect to ground. Note 2. AVSS, BVSS and DVSS must be connected to the same ground.WARNING: Operation at or beyond these limits may result in permanent damage to the device. Normal operation is not guaranteed at these extremes.RECOMMENDED OPERATING CONDITIONS (AVSS, BVSS, DVSS=0V; Note 1) Parameter Symbol min typ Power Supplies Analog AVDD 3.0 3.3 (Note 3) Digital DVDD 3.0 3.3Note 1. All voltages with respect to ground. Note 3. The power up sequence between AVDD and DVDD is not critical.max 3.6 AVDDUnits V VWARNING: AKM assumes no responsibility for the usage beyond the conditions in this datasheet.MS0267-E-03 -7-2004/08ASAHI KASEI[AK4122]SRC CHARACTERISTICS (Ta=25°C; AVDD=DVDD=3.3V; AVSS=BVSS=DVSS=0V; data = 24bit; measurement bandwidth = 20Hz ~ FSO/2; unless otherwise specified.) Parameter Symbol min typ max Units SRC Characteristics: Resolution (Note 4) 24 Bits Input Sample Rate FSI 8 96 kHz Output Sample Rate FSO 32 96 kHz THD+N (Input = 1kHz, 0dBFS, Note 5) FSO/FSI = 44.1kHz/48kHz −113 dB FSO/FSI = 48kHz/44.1kHz −113 dB FSO/FSI = 32kHz/48kHz −114 dB FSO/FSI = 96kHz/32kHz −111 dB Worst Case (FSO/FSI = 48kHz/8kHz) −103 dB Dynamic Range (Input = 1kHz, −60dBFS, Note 5) FSO/FSI = 44.1kHz/48kHz 114 dB FSO/FSI = 48kHz/44.1kHz 115 dB FSO/FSI = 32kHz/48kHz 115 dB FSO/FSI = 96kHz/32kHz 116 dB Worst Case (FSO/FSI = 32kHz/44.1kHz) 112 dB Dynamic Range (Input = 1kHz, −60dBFS, A-weighted, Note 5) FSO/FSI = 44.1kHz/48kHz 117 dB Ratio between Input and Output Sample Rate (Note 6) FSO/FSI 0.33 6 Note 4. Input data for SRC corresponds to 24bit data. When LSB 4bit data is input, the AK4122 calculates as “0” data because SRC is 20bit calculation. Therefore, SRC outputs “0” data. Note 5. Measured by ROHDE & SCHWARZ UPD04, Rejection Filter = wide, 8192point FFT. Note 6. The “0.33” is the ratio of FSO/FSI when FSI is 96kHz and FSO is 32kHz. The “6” is the ratio of FSO/FSI when FSI is 8kHz and FSO is 48kHz.S/PDIF RECEIVER CHARACTERISTICS (Ta=25°C; AVDD, DVDD=3.0 ∼ 3.6V) Parameter Symbol min typ Input Resistance Zin 10 Input Voltage VTH 200 Input Sample Frequency fs 32 -max 96Units kΩ mVpp kHzMS0267-E-03 -8-2004/08ASAHI KASEI[AK4122]FILTER CHARACTERISTICS (Ta=25°C; AVDD, DVDD=3.0 ∼ 3.6V; DEM=OFF) Parameter Symbol min Digital Filter Passband −0.001dB 0.985 ≤ FSO/FSI ≤ 6.000 PB 0 0.905 ≤ FSO/FSI < 0.985 PB 0 0.714 ≤ FSO/FSI < 0.905 PB 0 0.656 ≤ FSO/FSI < 0.714 PB 0 0.536 ≤ FSO/FSI < 0.656 PB 0 0.492 ≤ FSO/FSI < 0.536 PB 0 0.452 ≤ FSO/FSI < 0.492 PB 0 0.333 ≤ FSO/FSI < 0.452 PB 0 Stopband 0.985 ≤ FSO/FSI ≤ 6.000 SB 0.5417FSI 0.905 ≤ FSO/FSI < 0.985 SB 0.5021FSI 0.714 ≤ FSO/FSI < 0.905 SB 0.3965FSI 0.656 ≤ FSO/FSI < 0.714 SB 0.3643FSI 0.536 ≤ FSO/FSI < 0.656 SB 0.2974FSI 0.492 ≤ FSO/FSI < 0.536 SB 0.2732FSI 0.452 ≤ FSO/FSI < 0.492 SB 0.2510FSI 0.333 ≤ FSO/FSI < 0.452 SB 0.1822FSI Passband Ripple PR Stopband Attenuation SA 96 Group Delay (Note 7) GD -typmax 0.4583FSI 0.4167FSI 0.3195FSI 0.2852FSI 0.2245FSI 0.2003FSI 0.1781FSI 0.1092FSIUnits kHz kHz kHz kHz kHz kHz kHz kHz kHz kHz kHz kHz kHz kHz kHz kHz dB dB 1/fs±0.01 58.5 -Note 7. This value is the time from the rising edge of LRCK after data is input to rising edge of LRCK after data is output, when LRCK for Output data corresponds with LRCK for Input.DC CHARACTERISTICS (Ta=25°C; AVDD, DVDD=3.0 ∼ 3.6V) Parameter Symbol min High-Level Input Voltage VIH 70%DVDD Low-Level Input Voltage VIL High-Level Output Voltage (Iout=−400µA) VOH DVDD−0.4 Low-Level Output Voltage (Iout=400µA) VOL Input Leakage Current Iin Parameter Power Supply Current Normal operation (PDN pin = “H”) (Note 8) FSI=FSO=48kHz at Slave Mode: AVDD=DVDD=3.3V FSI=FSO=96kHz at Master Mode: AVDD=DVDD=3.3V FSI=FSO=96kHz at Master Mode: AVDD=DVDD=3.6V Power down (PDN pin = “L”) (Note 9) AVDD+DVDD mintyp typmax 30%DVDD 0.4 ±10 maxUnits V V V V µA Units15 29 1045 100mA mA mA µANote 8. Typ and max values are the value of AVDD+DVDD in each power supply voltage. Power supply current of each path@Slave Mode, AVDD=DVDD=3.3V, FSI=FSO=48kHz 1. PORT1 → SRC → PORT3: AVDD=5mA(typ), DVDD=10mA(typ) 2. PORT2 → SRC → PORT3: AVDD=5mA(typ), DVDD=10mA(typ) 3. DIR → SRC → PORT3: AVDD=6mA(typ), DVDD=9mA(typ) Note 9. All digital input pins are held DVSS.MS0267-E-03 -9-2004/08ASAHI KASEI[AK4122]SWITCHING CHARACTERISTICS (Ta=25°C; AVDD, DVDD=3.0 ∼ 3.6V; CL=20pF) Parameter Symbol min Master Clock Timing Frequency fCLK 8.192 Pulse Width Low tCLKL 0.4/fCLK Pulse Width High tCLKH 0.4/fCLK LRCK for Input data (LRCK1, LRCK2) Frequency fs 8 Duty Cycle Duty 48 LRCK for Output data (LRCK, LRCK2) Frequency (Note 10) fs 32 Duty Cycle Slave Mode Duty 48 Master Mode DutyS/PDIF Clock Recover Frequency Audio Interface Timing Input for PORT1 BICK1 Period BICK1 Pulse Width Low Pulse Width High LRCK1 Edge to BICK1 “↑” (Note 11) BICK1 “↑” to LRCK1 Edge (Note 11) SDTI Hold Time from BICK1 “↑” SDTI Setup Time to BICK1 “↑” Input for PORT2 (Slave mode) BICK2 Period BICK2 Pulse Width Low Pulse Width High LRCK2 Edge to BICK2 “↑” (Note 11) BICK2 “↑” to LRCK2 Edge (Note 11) SDTIO Hold Time from BICK2 “↑” SDTIO Setup Time to BICK2 “↑” Output for PORT2 (Slave mode) BICK2 Period BICK2 Pulse Width Low Pulse Width High LRCK2 Edge to BICK2 “↑” (Note 11) BICK2 “↑” to LRCK2 Edge (Note 11) LRCK2 to SDTIO (MSB) (Except I2S mode) BICK2 “↓” to SDTIO fPLL 32typmax 36.864Units MHz ns ns kHz % kHz % % kHz5096 52 96 52 9650 50tBCK tBCKL tBCKH tLRB tBLR tSDH tSDS tBCK tBCKL tBCKH tLRB tBLR tSDH tSDS tBCK tBCKL tBCKH tLRB tBLR tLRS tBSD1/64fs 65 65 30 30 30 30 1/64fs 65 65 30 30 30 30 1/64fs 65 65 30 30 30 30ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns ns nsNote 10. Min value is 8kHz at BYPASS mode. Note 11. BICK1 rising edge must not occur at the same time as LRCK1 edge. BICK2 rising edge must not occur at the same time as LRCK2 edge.MS0267-E-03 - 10 -2004/08ASAHI KASEI[AK4122]Parameter Output for PORT3 (Slave mode) BICK Period BICK Pulse Width Low Pulse Width High LRCK Edge to BICK “↑” (Note 11) BICK “↑” to LRCK Edge (Note 11) LRCK to SDTO (MSB) (Except I2S mode) BICK “↓” to SDTO Output for PORT2 (Master mode) BICK2 Frequency BICK2 Duty BICK2 “↓” to LRCK2 BICK2 “↓” to SDTIO Output for PORT3 (Master mode) BICK Frequency BICK Duty BICK “↓” to LRCK BICK “↓” to SDTO Control Interface Timing CCLK Period CCLK Pulse Width Low Pulse Width High CDTI Setup Time CDTI Hold Time CSN “H” Time CSN “↓” to CCLK “↑” CCLK “↑” to CSN “↑” CDTO Delay CSN “↑” to CDTO Hi-Z Reset Timing PDN Pulse Width (Note 12)Symbol tBCK tBCKL tBCKH tLRB tBLR tLRS tBSD fBCK dBCK tMBLR tBSD fBCK dBCK tMBLR tBSD tCCK tCCKL tCCKH tCDS tCDH tCSW tCSS tCSH tDCD tCCZ tPDmin 1/64fs 65 65 30 30typmaxUnits ns ns ns ns ns ns ns Hz % ns ns Hz % ns ns ns ns ns ns ns ns ns ns ns ns ns30 30 64fs 50 −20 −20 64fs 50 −20 −20 200 80 80 40 40 150 50 50 20 30 1000 20 3045 70 150(Note 13)Note 11. BICK rising edge must not occur at the same time as LRCK edge. Note 12. In case of using INT2. When INT2 is not used, the max value is not limited. Note 13. The AK4122 can be reset by bringing the PDN pin = “L”.MS0267-E-03 - 11 -2004/08ASAHI KASEI[AK4122]Timing Diagram1/fCLK VIH MCLK VIL tCLKH 1/fs VIH LRCK VIL tBCK VIH BICK VIL tBCKH tBCKLClock TimingtCLKLVIH LRCK VIL tBLR tLRB VIH BICK VIL tLRS tBSDSDTO tSDS tSDH50%DVDDVIH SDTI VILAudio Interface Timing (Slave mode) Note : BICK shows BICK1 of PORT1, BICK2 of PORT2 and BICK of PORT3. LRCK shows LRCK1 of PORT1, LRCK2 of PORT2 and LRCK of PORT3. SDTI shows SDTI of PORT1 or SDTIO of PORT2 that is used as input port. SDTO shows SDTO of PORT3 or SDTIO of PORT2 that is used as output port.MS0267-E-03 - 12 -2004/08ASAHI KASEI[AK4122]LRCK50%DVDDtMBLRdBCK 50%DVDDBICKtBSDSDTO tSDS tSDH50%DVDDVIH SDTI VILAudio Interface Timing (Master mode) Note : BICK shows BICK1 of PORT1, BICK2 of PORT2 and BICK of PORT3. LRCK shows LRCK1 of PORT1, LRCK2 of PORT2 and LRCK of PORT3. SDTI shows SDTI of PORT1 or SDTIO of PORT2 that is used as input port. SDTO shows SDTO of PORT3 or SDTIO of PORT2 that is used as output port.VIH CSN VIL tCSS tCCKL tCCKH VIH CCLK VIL tCDS CDTI C1 C0 tCDH VIH R/W VIL Hi-ZCDTOWRITE/READ Command Input TimingMS0267-E-03 - 13 -2004/08ASAHI KASEI[AK4122]tCSW VIH CSN VIL tCSH VIH CCLK VILVIH CDTI D2 D1 D0 VIL Hi-ZCDTOWRITE Data Input TimingVIH CSN VILVIH CCLK VILVIH CDTI A1 A0 VIL tDCD CDTO Hi-Z D7 D6 50%DVDDREAD Data Output Timing 1MS0267-E-03 - 14 -2004/08ASAHI KASEI[AK4122]tCSW VIH CSN VIL tCSH VIH CCLK VILVIH CDTI VIL tCCZ Hi-ZCDTOD2D1D050%DVDDREAD Data Output Timing 2tPD PDN VILPower Down & Reset TimingMS0267-E-03 - 15 -2004/08ASAHI KASEI[AK4122]OPERATION OVERVIEW Internal Signal PathThe input source of the SRC can be switched between the outputs of the DIR, PORT1 or PORT2. The input source of the PORT2 and PORT3 can be switched between the outputs of the SRC or BYPASS. When PORT2 is used as input port, PORT2 cannot use as output port. The signal path should be controlled during PWN bit = “0”. The Switch Names (ISEL1-0 bits etc) in Figure 1 correspond to the register bits that control the switch function. Refer to Table 1.DIR PORT3 De-em FilterOSELPORT1 Serial Audio I/F PORT2 Serial Audio I/F SRCBYPSISEL1-0Serial Audio I/FPLLFigure 1. Connection Input Source & Output SourceMode 0 1 2 3 4 5 6 7 8 9Input PORT ISEL1-0 bit 00 : PORT1 01 : PORT2 10 : DIR 00 : PORT1 01 : PORT2 10 : DIR 00 : PORT1 10 : DIR 00 : PORT1 10 : DIRSRC / Bypass BYPS bit 0 : SRCOutput PORT OSEL bitPath PORT1 → SRC → PORT3 PORT2 → SRC → PORT3 DIR → SRC → PORT3 PORT1 → PORT3 PORT2 → PORT3 DIR → PORT3 PORT1 → SRC → PORT2 DIR → SRC → PORT2 PORT1 → PORT2 DIR → PORT20 : PORT3 (Note 1) 1 : Bypass 0 : SRC 1 : Bypass1 : PORT2 (Note 2)Table 1. Path Select Default is Mode 0. (Path : PORT1 → SRC → PORT3) After PDN pin = “L” → “H”, SDTIO pin of PORT2 is the input pin. The DIF1-0 bits of the PORT1 should be set a value except “10” (I2S Compatible) when the DIR is selected as an input port. Refer to Table 6 and 7 for Master/Slave mode setting.MS0267-E-03 - 16 -2004/08ASAHI KASEI[AK4122]Note 1. In this case, PORT2 is input port. If PORT2 is unused, the digital I/O pins should be processed appropriately by Table 2. M/S2 pin L Mode Slave Unused pin Pin I/O Setting MCLK2 I This pin should be connected to DVSS. BICK2 I This pin should be connected to DVSS. LRCK2 I This pin should be connected to DVSS. SDTIO I This pin should be connected to DVSS. MCLK2 I This pin should be connected to DVSS. BICK2 O This pin should be open. LRCK2 O This pin should be open. SDTIO I This pin should be connected to DVSS. Table 2. Pin Setting for PORT2HMasterNote 2. In this case, PORT3 is output port. If PORT3 is unused, the digital I/O pins should be processed appropriately by Table 3. M/S3 pin L Mode Slave Unused pin Pin I/O Setting OMCLK I This pin should be connected to DVSS. BICK I This pin should be connected to DVSS. LRCK I This pin should be connected to DVSS. SDTO O This pin should be open. OMCLK I This pin should be connected to DVSS. BICK O This pin should be open. LRCK O This pin should be open. SDTO O This pin should be open. Table 3. Pin Setting for PORT3HMasterSystem ClockPORT1 can be operated in slave mode only. PORT2 and PORT3 work in master mode and slave mode. Internal system clock is created by internal PLL using LRCK1, LRCK2 or LRCK of DIR. The MCLK is not needed when PORT2 and PORT3 are in slave mode and then please set MCLK2 pin and OMCLK pin to DVSS. However, when PORT2 and PORT3 are used in master mode, MCLK2 pin and OMCLK pin should be supplied to MCLK. The M/S2 pin and M/S3 pin select between master and slave mode. Table 4 and 5 show setting of MCLK frequency that PORT2 and PORT3 are master mode. In case of detecting the sampling frequency by MCLK when DIR is used, MCLK (MCLK2 or OMCLK) of selected output port (PORT2 or PORT3) should be input. ICKS1 0 0 1 1 ICKS0 MCLK2 32kHz ≤ fs ≤ 48kHz 48kHz < fs ≤ 96kHz 0 256fs 256fs 1 384fs 384fs 0 512fs N/A 1 768fs N/A Table 4. MCLK2 frequency select for Master modeDefaultOCKS1 0 0 1 1OCKS0OMCLK 32kHz ≤ fs ≤ 48kHz 48kHz < fs ≤ 96kHz 0 256fs 256fs 1 384fs 384fs 0 512fs N/A 1 768fs N/A Table 5. OMCLK frequency select for Master modeDefaultMS0267-E-03 - 17 -2004/08ASAHI KASEI[AK4122]Master Mode and Slave ModeWhen PORT2 and PORT3 are used as output port, the M/S2 pin and M/S3 pin select either master or slave mode. “H” is master mode, “L” is slave mode. In master mode, MCLK should be input and the AK4122 outputs BICK and LRCK. In slave mode, BICK and LRCK are input externally and MCLK is not needed. If PORT2 is used as input port, M/S2 pin should be set “H” or “L”. M/S2 pin L L H H Data I/O Mode BICK, LRCK I/O Slave, SRC Input Input Available 1 Output Not Available 0 I/O Master, SRC Output 1 I/O Master, Bypass Table 6. Master mode/Slave mode for PORT2 BYPS bit Data I/O Mode BICK, LRCK 0 Output Slave, SRC Input 1 Output Not Available 0 Output Master, SRC Output 1 Output Master, Bypass Table 7. Master mode/Slave mode for PORT3 BYPS bit 0M/S3 pin L L H HAudio Interface FormatThe audio interface should be controlled during PWN bit = “0”. When in BYPASS mode, BICK1, BICK2 and BICK are fixed to 64fs. (1) PORT1 Four kinds of data formats can be chosen with the DIF1-0 bits (Table 8). In all modes, the serial data is in MSB first, 2’s compliment format. The SDTI is latched on the rising edge of BICK1. PORT1 corresponds to slave mode only. Mode 0 1 2 3 DIF1 0 0 1 1 DIF0 Input Format LRCK 0 16bit, LSB justified H/L 1 24bit, MSB justified H/L 0 24bit, I2S Compatible L/H 1 24bit, LSB justified H/L Table 8. Audio Interface Format for PORT1 BICK ≥ 32fs ≥ 48fs ≥ 48fs ≥ 48fsDefaultNote: The DIF1-0 bits of the PORT1 should be set a value except “10” (I2S Compatible) when the DIR is selected as an input port.LRCK0 1 2 3 9 10 11 12 13 14 15 0 1 2 3 9 10 11 12 13 14 15 0 1BICK(32fs) SDTI(i) BICK(64fs) SDTI(i)Don't Care 15 14 13 12 1 0 Don't Care 15 14 13 12 2 1 0 15 14 13 0 1 2 3 7 6 5 4 3 2 1 0 15 14 13 17 18 19 20 31 0 1 2 3 7 6 5 4 3 2 1 0 15 17 18 19 20 31 0 1SDTI-15:MSB, 0:LSB Lch Data Rch DataFigure 2. Mode 0 Timing MS0267-E-03 - 18 2004/08ASAHI KASEI[AK4122]LRCK0 1 2 20 21 22 23 24 31 0 1 2 20 21 22 23 24 31 0 1BICK(64fs) SDTI(i)23 22 4 3 2 1 0 Don't Care 23 22 4 3 2 1 0 Don't Care 2323:MSB, 0:LSB Lch Data Rch DataFigure 3. Mode 1 TimingLRCK0 1 2 3 21 22 23 24 25 0 1 2 21 22 23 24 25 0 1BICK(64fs) SDTI(i)23 22 4 3 2 1 0 Don't Care 23 22 4 3 2 1 0 Don't Care23:MSB, 0:LSB Lch Data Rch DataFigure 4. Mode 2 TimingLRCK0 1 2 8 9 24 31 0 1 2 8 9 24 31 0 1BICK(64fs) SDTI(i)Don't Care 23:MSB, 0:LSB Lch Data Rch Data 23 8 1 0 Don't Care 23 8 1 0Figure 5. Mode 3 Timing (2) PORT2 Four kinds of data formats can be chosen with the IDIF1-0 bits (Table 9). In all modes, the serial data is in MSB first, 2’s compliment format. If PORT2 is selected the output port, the SDTIO is clocked out on the falling edge of BICK2, and if PORT2 is selected the input port, the SDTIO is latched on the rising edge of BICK2. The audio interface supports both master and slave modes. In master mode, BICK2 and LRCK2 are output with the BICK2 frequency fixed to 64fs and the LRCK2 frequency fixed to 1fs. Mode 0 1 2 3 IDIF1 0 0 1 1 IDIF0 0 1 0 1 Output Format Input Format 24bit, MSB justified 16bit, LSB justified 24bit, MSB justified 24bit, MSB justified 24bit, I2S Compatible 24bit, I2S Compatible 24bit, MSB justified 24bit, LSB justified Table 9. Audio Interface Format for PORT2 LRCK H/L H/L L/H H/L BICK ≥ 32fs ≥ 48fs ≥ 48fs ≥ 48fsDefaultMS0267-E-03 - 19 -2004/08ASAHI KASEI[AK4122]LRCK0 1 2 3 9 10 11 12 13 14 15 0 1 2 3 9 10 11 12 13 14 15 0 1BICK(32fs) SDTIO(o) SDTIO(i)23 22 21 15 14 13 0 1 2 3 15 14 13 12 11 10 9 8 23 22 21 7 6 5 4 3 2 1 0 15 14 13 17 18 19 20 31 0 1 2 3 15 14 13 12 11 10 9 8 23 7 6 5 4 3 2 1 0 15 17 18 19 20 31 0 1BICK(64fs) SDTIO(o) SDTIO(i)23 22 21 Don't Care 7 6 5 4 3 15 14 13 12 1 0 23 22 21 Don't Care 7 6 5 4 3 15 14 13 12 2 1 0 23SDTIO-23:MSB, 0:LSB SDTIO-15:MSB, 0:LSB Lch Data Rch DataFigure 6. Mode 0 TimingLRCK0 1 2 20 21 22 23 24 31 0 1 2 20 21 22 23 24 31 0 1BICK(64fs) SDTIO(o) SDTIO(i)23 22 23 22 4 3 2 1 0 4 3 2 1 0 23 22 Don't Care 23 22 4 3 2 1 0 4 3 2 1 0 23 Don't Care 2323:MSB, 0:LSB Lch Data Rch DataFigure 7. Mode 1 TimingLRCK0 1 2 3 21 22 23 24 25 0 1 2 21 22 23 24 25 0 1BICK(64fs) SDTIO(o) SDTIO(i)23 22 23 22 4 3 2 1 0 4 3 2 1 0 23 22 Don't Care 23 22 4 3 2 1 0 4 3 2 1 0 Don't Care23:MSB, 0:LSB Lch Data Rch DataFigure 8. Mode 2 TimingLRCK0 1 2 8 9 24 31 0 1 2 8 9 24 31 0 1BICK(64fs) SDTIO(o) SDTIO(i)23 22 16 15 23 0 8 1 0 23 22 16 15 23 0 8 1 0 23Don't Care 23:MSB, 0:LSBDon't CareLch DataRch DataFigure 9. Mode 3 TimingMS0267-E-03 - 20 -2004/08(3) PORT3Two kinds of data formats can be chosen with the ODIF bit (Table 10). In both modes, the serial data is in MSB first, 2’s compliment format. The SDTO is clocked out on the falling edge of BICK. The audio interface supports both master and slave modes. In master mode, BICK and LRCK are output with the BICK frequency fixed to 64fs and the LRCK frequency fixed to 1fs.Format LRCK BICKMode ODIF OutputDefault0 0 24bit, MSB justified H/L ≥ 48fsI2S Compatible L/H ≥ 48fs1 1 24bit,Table 10. Audio Interface Format for PORT3 Array LRCKBICK(64fs)SDTO(o)Figure 10. Mode 0 Timing Array LRCKBICK(64fs)SDTO(o)Figure 11. Mode 1 TimingSoft Mute OperationSoft mute operation is performed in the digital domain of the SRC output. Soft mute can be controlled by SMUTE bit or SMUTE pin. The SMUTE bit and SMUTE pin are ORed between pin and register. When SMUTE bit goes “1” or SMUTE pin goes “H”, the SRC output data is attenuated by −∞ within 1024 LRCK cycles. When the SMUTE bit returned “0” and SMUTE pin goes “L” the mute is cancelled and the output attenuation gradually changes to 0dB during 1024 LRCK cycles. If the soft mute is cancelled before mute state after starting of the operation, the attenuation is discontinued and returned to 0dB by the same cycles. The soft mute is effective for changing the signal source.DATT LevelAttenuation-∞SDTIO / SDTOFigure 12. Soft Mute Function(1) The output data is attenuated by −∞ during 1024 LRCK cycles (1024/fs).(2) Digital output delay from the digital input is called the group delay (GD).(3) If the soft mute is cancelled before attenuating to −∞ after starting the operation, the attenuation is discontinued andreturned to 0dB by the same number of clock cycles.De-emphasis Filter ControlThe AK4122 includes the digital de-emphasis filter (tc=50/15µs) by IIR filter corresponding to three sampling frequencies (32kHz, 44.1kHz and 48kHz).(1) When input port is DIRWhen the input port is DIR and DEAU bit = “1”, the de-emphasis filter is enabled automatically by sampling frequency (FS3-0 bit) and pre-emphasis information in the channel status. DEM1-0 bits can control the de-emphasis filter when DEAU bit = “0”. When the de-emphasis filter is OFF, the internal de-emphasis filter is bypassed. When PEM bit = “0”,the internal de-emphasis filter is always bypassed.PEM FS3 FS2 FS1 FS0 Mode1 0 0 0 0 44.1kHz1 0 0 1 0 48kHz1 0 0 1 1 32kHz1 (Others) OFF0 x x x x OFFTable 11. De-emphasis Auto Control (DEAU bit = “1”)PEM DEM1 DEM0 Mode1 0 0 44.1kHz1 0 1 OFF Default1 1 0 48kHz1 1 1 32kHzTable 12. De-emphasis Manual Control (DEAU bit = “0”)(2) When input port is PORT1 or PORT2When PORT1 or PORT2 is selected as input port, DEM1-0 bits can control the de-emphasis filter even if DEAU bit = “0”or DEAU bit = “1”. In this case, the de-emphasis filter cannot enable automatically. When the de-emphasis filter is OFF,the internal de-emphasis filter is bypassed.DEM1 DEM0 Mode44.1kHz0 0Default0 1 OFF48kHz1 032kHz1 1Table 13. De-emphasis Manual ControlSystem Reset and Power-DownThe AK4122 has a full power-down mode for all circuits that is activated by the PDN pin, and a partial power-down mode activated by the PWN bit. The AK4122 should be reset once at power-up by bringing PDN pin = “L”.PDN pin:All analog and digital circuits are placed in power-down and reset modes by bringing PDN pin = “L”. All theregisters are initialized and clocks are stopped. Read/Write operations to the registers are disabled.PWN bit (Address 00H; D0):Unlike the PDN pin operation described above, internal registers and mode settings are not initialized. Read/Write operations to the registers are enabled.。

Protocol DefinitionDräger RS 232 MEDIBUSRevision Level 6.00 WARNING!Strictly follow the Instructions for Use.Any use of the software protocolrequires full understanding and strictobservation of these instructions. Thesoftware protocol is only to be used forpurposes specified here.Contents2Dräger RS 232MEDIBUSContentsIntended Use . . . . . . . . . . . . . . . . . . . . . . . . . .3MEDIBUS Introduction . . . . . . . . . . . . . . . . . .4Initializing Communication . . . . . . . . . . . . . . . .4Terminating Communication. . . . . . . . . . . . . . .5Time-Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Allowable Characters . . . . . . . . . . . . . . . . . . . .5Software Handshaking. . . . . . . . . . . . . . . . . . .6Suspending data transmission. . . . . . . . . . . . .6Resuming data transmission . . . . . . . . . . . . . .6Aborting data transmission. . . . . . . . . . . . . . . .6MEDIBUS Commands . . . . . . . . . . . . . . . . . .7Structure of Commands . . . . . . . . . . . . . . . . . .7Command Codes . . . . . . . . . . . . . . . . . . . . . . .8Request Trend Data Command . . . . . . . . . . . .11MEDIBUS Responses . . . . . . . . . . . . . . . . . . .12Structure of Responses . . . . . . . . . . . . . . . . . .12Responding to Control Commands and unknown Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . .13Responding to corrupt Commands. . . . . . . . . .13Responding to Data Request Commands . . . .14MEDIBUS Device Extension forInfusion Pumps . . . . . . . . . . . . . . . . . . . . . . . .22Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . .22MEDIBUS Device Extension Protocol Concept 22Infusion Pump Commands. . . . . . . . . . . . . . . .23Infusion Pump Communication Life Cycle . . . .24Request Infusion Pump Configuration . . . . . . .25Infusion Pump Configuration ChangedCommand. . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Infusion Pump Data Update Commands . . . . .27MEDIBUS Realtime-Extension Introduction30Time-Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Allowable Characters for RealtimeTransmission . . . . . . . . . . . . . . . . . . . . . . . . . .31MEDIBUS Realtime-Extension Commands .33Command Codes . . . . . . . . . . . . . . . . . . . . . . .33Request Realtime Configuration Command. . .33Configure Realtime Transmission Command . 34Realtime Configuration Changed Command. . 34MEDIBUS Realtime-Extension Responses . 35Realtime Configuration Response. . . . . . . . . . 35MEDIBUS Realtime-Extension Realtime-Data Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Structure of Realtime-Data Records . . . . . . . . 36Sync-Commands. . . . . . . . . . . . . . . . . . . . . . . 38Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40MEDIBUS-Life-Cycle. . . . . . . . . . . . . . . . . . . . 40MEDIBUS Realtime-Extension Life-Cycle. . . . 42ASCII HEX Format . . . . . . . . . . . . . . . . . . . . . 45MEDIBUS example 1 . . . . . . . . . . . . . . . . . . . 46MEDIBUS example 2 . . . . . . . . . . . . . . . . . . . 47MEDIBUS example 3 . . . . . . . . . . . . . . . . . . . 48MEDIBUS example 4 . . . . . . . . . . . . . . . . . . . 49MEDIBUS example 5 . . . . . . . . . . . . . . . . . . . 50MEDIBUS example 6 . . . . . . . . . . . . . . . . . . . 51Frequently Asked Questions. . . . . . . . . . . . . . 55Logbook of Changes. . . . . . . . . . . . . . . . . . . . 58Table of used ASCII-Codes. . . . . . . . . . . . . . .59Intended Use Intended UseMEDIBUS is a software protocol intended to beused for exchanging data between a Dräger medi-cal device and external medical or non-medicaldevices via RS 232 interfaces.WARNINGData transferred via MEDIBUS interfaces are forinformation only and are not intended as a basisfor diagnosis or therapy decisions.MEDIBUS consists of two independent softwareprotocols one for the transmission of "slow" andone for the transmission of "fast" data."Slow" data:Generated or updated in intervals of the magnitudeof seconds. This part is called MEDIBUS."Fast" data:Intended for the transmission of e. g. realtimecurves. This part of MEDIBUS is called the "Real-time-Extension".This manual contains a general description of theprotocol including formats of commands andresponses.For device dependent descriptions of supportedcommands and data sets, port hardware and con-figurations for Dräger devices please refer to theindividual device-specific MEDIBUS documenta-tion.Dräger RS232MEDIBUS3MEDIBUS IntroductionMEDIBUS IntroductionThe MEDIBUS protocol distinguishes two basictypes of messages:–commands–responses.A command is transmitted by one device to requestdata from the other device or to control its function.A response is transmitted by one device uponreceipt of a command from the other device.Responses may contain embedded commands.Initializing Communication(refer to MEDIBUS-life-cyle-diagram, see page40)–To initialize communication or to restart commu-nication after a time-out, a device must send the"Initialize Communications Command" ICC.Refer to section "Control commands" for the for-mat of commands.– A device considers communication initializedafter having received either a response to atransmitted ICC or an ICC from the otherdevice. Refer to section "Responding to com-mands" for the format of responses.–Commands embedded in a response to an ICCare disregarded.4Dräger RS232MEDIBUSMEDIBUS Introduction Terminating Communication–To stop the communication the "STOP" com-mand has to be sent.–The command echo has to be checked to makesure the "Stop Communication" command hasbeen received correctly. Further commandsfrom the linked device may be ignored until thecommunication has been reinitialized.Time-Out–Any pause in the data flow exceeding 3 sec-onds leads to a time-out, terminating the com-munication link. To resume communication aftera time-out, the device must re-initialize commu-nication by transmitting an ICC command (seesection "Initializing communication", page4).Whenever a device receives an ICC command,it must send a response to it (see section"Responses", page12).–After receiving a command the device has tosend a complete response within 10 seconds.–If there is no need for sending commands orresponses the "NOP"–command has to be sentin 2-second-intervals to keep the communica-tion alive.Allowable Characters–Printable ASCII characters.–Control characters defined in this Instructionsfor Use.Dräger RS232MEDIBUS5MEDIBUS Introduction6Dräger RS 232MEDIBUSSoftware HandshakingSome control characters can be sent at any time to control the flow of data. They do not require responses.Suspending data transmission–If a receiving device wants the transmitting device to suspend transmission, the ASCII "DC1" character (11H) must be sent.–Upon receipt of this character, the sending device will suspend any transmission immedi-ately until it receives the ASCII "DC3" character.Resuming data transmission–To request the transmitting device to resume data transmission, the ASCII "DC3" character (13H) must be sent within 3 seconds. Else com-munication will be reinizialized with an ICCcom-mand.Aborting data transmission–To request the other device to abort sending a response or a command, the ASCII "CAN" character (18H) must be sent.–Upon receipt of this character, any transmission in progress will be immediately aborted. Com-munication may be restarted by repetition of the last sent command immediately.Dräger RS 232MEDIBUS7MEDIBUS CommandsMEDIBUS CommandsStructure of Commands–A command is a string of ASCII characters transmitted by one device to request data from the other device or to control its function.–A command may be embedded in the response to another command, but a new command must not be transmitted until the response to the pre-vious command has been received.–If, however, the response to a command has not been received in full within 10 seconds since the transmission of the last command byte, the command may be repeated or a new command may be transmitted.Commands have one of the following formats:ESC ASCII "escape" character (1BH)Command-Code Single byte code specifying the command.ARGUMENTThe argument string is of variable length n, but n must not exceed 251(0FBH) bytes. The string consists of printable ASCII characters, either text or ASCII HEX numbers. The for-mat of the different arguments are specified in the following sections.CHECKSUM Least significant 8-bit sum of all preceding bytes beginning with "ESC" in ASCII HEX format (see section "ASCII HEX Format", page 45). CRASCII "carriage return" character (0DH)010NOTETo avoid communication breakdown, commands with arguments must not be sent to devices with a MEDIBUS version less than 3.00.MEDIBUS CommandsCommand CodesControl CommandsControl commands are used to initialize, controland stop communication.Command CodeNo Operation (NOP)30HInitialize Communication (ICC)51HStop Communication (STOP)55HData Request CommandsData request commands are used to request data.Command CodeRequest current Alarms (Codepage 3)23HRequest current measured Data (Codepage 1) 24HRequest current low Alarm Limits (Codepage 1) 25HRequest current high Alarm Limits (Codepage 1) 26HRequest current Alarms (Codepage 1) 27HRequest current Date and Time 28HRequest current Device Setting 29HRequest current Text Messages 2AHRequest current measured Data (Codepage 2) 2BHRequest current low Alarm Limits (Codepage 2) 2CHRequest current high Alarm Limits (Codepage 2) 2DHRequest current Alarms (Codepage 2) 2EHRequest Device Identification 52HRequest Trend Data Status6CHRequest Trend Data6DH8Dräger RS232MEDIBUSMEDIBUS CommandsMiscellaneous CommandsCommand CodeTime changed49HConfigure Data Response Command4AHTime Changed CommandThe "Time changed" command is sent if duringruntime the time or date of the device has beenchanged. The receiving device can now ask for cur-rent date and time. Because of the "Time changed"command there is no need for sending periodicallythe "Request Current Date and Time" command.Dräger RS232MEDIBUS9MEDIBUS Commands10Dräger RS 232MEDIBUSConfigure Data Response CommandThe "Configure Data Response" command is used to limit the number of data responded by a data source on a data request command. On receipt of any of these data request commands the receiver has to send all actual valid data. In cases where only a few of the possible data are used, the requesting device may configure the responding device to send only these used data by sending a "Configure Data Response" command. The codes of useful data are given in the argument as follows:DATA TYPE:One byte identifying the data type to configure.This may be:DATA CODE:Two byte ASCII HEX data code. See appendices for code numbers.The configuration stays valid until receipt of a new "Configure Data Response" command. After re-ini-tializiation of communication (ICC) and if the "Con-figure Data Response" is send without data codes, the configuration is set to its default state, where internal programmed configuration is used. An example is given in Appendix.01124H for current Data, low Alarm Limits and high Alarm Limits (codepage 1)27H for current Alarms (codepage 1)29H for current Device Settings 2AH for current Textmessages2BH for current Data, low Alarm Limits and high Alarm Limits (codepage 2)2EHfor current Alarms (codepage 2)MEDIBUS Commands Request Trend Data CommandThe “Request Trend Data” command (6DH) is usedto request a sequence of samples of one trendparameter.The command argument has the following format:CODE PAGE DATA CODE COUNT BEGIN0+2+4+6+14CODE PAGE:Two byte ASCII HEX number identifying the code page of the trend parameter: 24H for data code page 12BH for data code page 2DATA CODE:Two byte ASCII HEX number containing the data code of the trend parameter. A param-eter's data code is the same as used for the "Request current measured data" response. COUNT:Two byte ASCII HEX number defining the maximal number of trend samples allowed in the response.BEGIN:Eight byte ASCII HEX number specifying the time stamp of the eldest requested trend sample. (Note: BEGIN is undefined if COUNT is 0.)The time stamp is packed in accordance to the Microsoft Windows™ 32-bit date andtime format:NOTEBEGIN ist undefined if COUNT is 0.YYYYYYYMMMMDDDDDhhhhhmmmmmmsssssMSB LSBwithYYYYYYY year relative to 1980 (range 0 - 119)MMMM month (range 1 - 12)DDDDD day (range 1 - 31)hhhhh hour (range 0 - 23)mmmmmm minute (range 0 - 59)sssss second (range 0 - 29 in 2-second intervals)NOTEPrior to the "Trend Data Request" the device shouldrequest the trend data status in order to know theavailability of trend data (refer to chapter "Trend DataStatus Response" for the respective response).Dräger RS232MEDIBUS11MEDIBUS Responses12Dräger RS 232MEDIBUSMEDIBUS ResponsesStructure of ResponsesUpon receipt of a command, a device must respond to it within 10 seconds. A command may be embed-ded within the response. The following format has to be used:The response is of variable length, but must not exceed 3845 bytes.012SOHASCII "Start of Header" character (01H) Command ECHO Echo of the command code being responded to.RESPONSE Data as requested by the command, see sections "MEDIBUS Specification"CHECKSUM Least significant 8-bit sum of all preceeding bytes beginning with "SOH" in ASCII HEX format (see section "ASCII HEX Format", page 45).CRASCII "carriage return" character (0DH)Dräger RS 232MEDIBUS 13MEDIBUS ResponsesResponding to Control Commands and unknown CommandsA response to a control command or unknown com-mand acknowledges receipt of the command, but contains no data:–Refer to section "Control commands" for cur-rently defined control commands.Responding to corrupt CommandsIf the received command is corrupt (bad check-sum), the command echo field must consist of an ASCII "NAK" character (15H) and there must be no response field:013SOHASCII "Start of Header" character (01H).Command ECHO Echo of control command being responded to.CHECKSUM Least significant 8-bit sum of all preceeding bytes beginning with "SOH" in ASCII HEX format (see section "ASCII Hex format", see page 45).CR ASCII "carriage return" character (0DH).014MEDIBUS Responses14Dräger RS 232MEDIBUSResponding to Data Request CommandsResponses to data request commands contain the current values of a device. In case a value isn't available at a certain time (for example caused by temporary measurement problems) nothing must be sent for this value. Vice versa this means, that a value is invalid if it is not included in a data request responseCurrent Measured Data and Alarm Limit ResponseThis response must be sent in reply to the "Request current measured Data (codepage 1)" command (24H), "Request current low Alarm Limits (codep-age 1)" command (25H), "Request current high Alarm Limits (codepage 1)" command (26H), "Request current measured Data (codepage 2)" command (2BH), "Request current low Alarm Lim-its (codepage 2)" command (2CH) or "Request cur-rent high Alarm Limits (codepage 2)" command (2DH). It contains the current values of all mea-sured parameters or alarm limits available on the responding device. The response field has the fol-lowing format:.015DATA CODE Two byte ASCII HEX number identifying the parameter or alarm limit.DATAFour byte ASCII field containing the current value of the parameter or alarm limit. See appendix for data formats. Surplus character positions and leading zeros must be replaced by an ASCII "Space" (20H).Dräger RS 232MEDIBUS 15MEDIBUS ResponsesAlarm Status ResponseThis response must be sent in reply to the "Request current Alarms (codepage 1)" command (27H) or "Request current Alarms (codepage 2)" command (2EH). It contains the alarm priority, alarm code, and alarm message for all currently active alarms on the responding device. The response field has the following format:ALARM PriorityOne byte field specifying the alarm priority (number in the range of 1 to 31),31 being the highest priority. The priority is encoded by adding 30H. The pri-orities, therefore, lie in the range from ASCII "1" (31H) to ASCII character "O" (4FH).ALARM CODE Two byte ASCII HEX number identifying the alarm.ALARM PHRASETwelve byte ASCII character string describing the alarm.016MEDIBUS Responses16Dräger RS 232MEDIBUSTime & Date Update ResponseThis response is sent in reply to the "Request Cur-rent Date & Time" command (28H). It contains the current date and time from the responding device. The response field has the following format:German month representation in time & Date update responses 017TIME:Eight byte field containing ASCII numeric characters representing the current time in hours (HH), minutes (MM), and seconds (SS). Leading zeroes shall not be sup-pressed.1)DATE:Nine byte field containing ASCII alpha-numeric characters representing the current day (DD), month (MMM), and year (YY). The first three letters for each month are sent in ASCII. Leading zeroes shall not be suppressed.1)1)The PM 8040 substitudes leading zeros in the hours, day and year field with ASCII spaces (20H), e.g. ' 8:06:05 4-MAR 2'.NOTEThe month representing letters (MMM) has to be sent in German language.MONTH REPRESENTIVE January JAN February FEB March MAR April APR May MAI June JUN July JUL August AUG September SEP October OKT November NOV DecemberDEZDräger RS 232MEDIBUS 17MEDIBUS ResponsesDevice Setting ResponsesThis response must be sent in reply to the "Request Current Device Settings" command (29H). It con-tains the current values of all device settings appli-cable with the responding device. The response field has the following format:018SETTING CODE Two Byte ASCII HEX number identifying the parameter.SETTINGFive byte ASCII field containing the current value of the specified parameter. Referto appendix for the specific formats of the parameters. Surplus character positions and leading zeros must be filled up with ASCII "SPACE" (20H).MEDIBUS Responses18Dräger RS 232MEDIBUSText Message ResponseThis response must be sent in reply to the "Request Text Messages" command (2AH). It contains all the text messages the requested device currently holds for user information, along with the text code, text length and an end-of-text marker. The response field has the following format:019TEXT CODE Two byte ASCII HEX number identifying the text messages.LENGTHOne byte field specifying the text length, a number in the range from 1 to 32. A text must not be longer than 32 characters. The length is encoded to ASCII format by adding 30H to the decimal length value. Thus, the text length ranges from ASCII "1" (31H) to ASCII "P" (50H).TEXT ASCII character string. Refer to appendix for text messages.ETXEnd-of-text marker (ASCII-Code 03H).NOTEThe length of the response field is limited to 3840 bytes. Due to different lengths of text messages, the maximum number of text messages in a response field depends on the length of the indi-vidual text messages.MEDIBUS ResponsesDevice Identification ResponseThis response must be sent in reply to the "RequestDevice Identification" command (52H). It containsthe identification number, name and release num-ber of the responding device and the MEDIBUSrelease number. The response field has the follow-ing format:All identification numbers will be defined by, Lübeck.0 2 0ID NUMBER Four byte field containing the ASCII device identification number NNNN.NAME ASCII character string delimited by apostrophes (ASCII Code 27H). Therefore, the device name itself must not contain apostrophes. The length of the device namemay range from 1 to 32 characters.REVISION Eleven byte field containing ASCII characters representing the device revision level (DD.DD) and the MEDIBUS revision level (MM.MM).Dräger Medical GmbHDräger RS232MEDIBUS19MEDIBUS ResponsesTrend Data Status ResponseThis response sends information about the avail-able trend samples for each trend parameter. It issent on reply to the “Request Trend Data Status”command (6CH). The response field has the follow-ing format:PARAMETER 1PARAMETER 2CODE PAGE DATA CODE COUNT BEGIN CODE PAGE DATA CODE COUNT BEGIN 0+2+4+10+18+20+22+28+36CODE PAGE:Two byte ASCII HEX number identifying the code page of the trend parameter: 24H for data code page 12BH for data code page 2DATA CODE:Two byte ASCII HEX number containing the data code of the trend parameter. A pa-rameter's data code is the same as used for the "Request current measured data"response.COUNT:Six byte ASCII HEX number defining the number of trend samples available for the respective parameter.Leading zeros may be replaced by ASCII spaces (20H).BEGIN:Eight byte ASCII HEX number containing the time stamp of the eldest available trend sample of the respective parameter.For the format of the time stamp refer to chapter "Request Trend Data Command". 20Dräger RS232MEDIBUSMEDIBUS ResponsesTrend Data ResponseThis response is sent in reply to the "Request TrendData" command (6DH). It contains a sequence ofsamples of one parameter with the respective timestamps.The response field has the following format:CODE PAGE DATACODECOUNT= NVALUE1TIME1VALUE2TIME2...VALUENTIMEN N d2550+2+4+6+10+18+22+30+n-12+n-8+n n < 3066CODE PAGE:Two byte ASCII HEX number identifying the code page of the trend parameter: 24H for data code page 12BH for data code page 2DATA CODE:Two byte ASCII HEX number containing the data code of the trend parameter. A parameter's data code is the same as used for the "Request current measured data"response.COUNT:Two byte ASCII HEX number defining the number of trend samples contained in the response.VALUE:Four byte ASCII field containing the value of the trend sample. The format for each parameter is the same as used for the "Request current measured data" response. TIME:Eight byte ASCII HEX number containing the time stamp of the trend sample.For the format of the time stamp refer to chapter "Request Trend Data Command".Dräger RS232MEDIBUS21MEDIBUS Device Extension for Infusion PumpsMEDIBUS Device Extension for Infusion PumpsIntroductionThe standard MEDIBUS protocol is designed fordata exchange between two medical devices,where each of the devices can support only onesource of a certain data item. In opposite to thestandard protocol the MEDIBUS device extensionfor infusion pumps is meant to support severalpumps on one communication port, all pumpssourcing identical data items, e.g. the same mea-sured data, alarms, settings etc.MEDIBUS Device Extension Protocol ConceptThe basic concept of the MEDIBUS device exten-sion is stacking the MEDIBUS Device Extensioncommand 59H with sub-command codes andaddressing a specific pump by a channel number.Stacking of command codes means that a deviceextension telegram always uses the leading com-mand code 59H to indicate that the telegram is aMEDIBUS Device Extension command orresponse for infusion pumps. The leading com-mand is followed by a sub-command code, e.g.specifying the actual data update request. If appli-cable the sub-command is followed by a channelnumber, defining to which device the telegram isrelated.22Dräger RS232MEDIBUSMEDIBUS Device Extension for Infusion Pumps Infusion Pump CommandsLeading Command Code Device Extension Command for Infusion Pumps59HSub-Commands Code Request current measured data24H Request current low alarm limits25H Request current high alarm limits26H Request current alarms27H Request current device settings29H Request current text messages2AH Request infusion pump configuration41H Infusion pump configuration changed42HDräger RS232MEDIBUS23MEDIBUS Device Extension for Infusion PumpsInfusion Pump Communication Life CycleThe following diagram shows a typical communica-tion life cycle for a device being connected to aninfusion pump device.324Dräger RS232MEDIBUSDräger RS 232MEDIBUS 25MEDIBUS Device Extension for Infusion PumpsRequest Infusion Pump ConfigurationAfter communication has initialized the requesting device first has to ask the pump device for available pumps using the Request Infusion Pump Configu-ration sub-command (41H).The pump device will respond with a list of identifier for available pump channels.Later these pump channel identifier have to be used by the requesting device to request data from a specific pump.Request Infusion Pump Configuration Command:Infusion Pump Configuration Response:ESC Lead-CommandSub-Command 41H Checksum D9H CR 1BH59H34H31H44H39H0DHESCLead-Com-mand Sub-Command 41H Pump channel01H ….Pump channelxyH ChecksumCR01H 59H34H31H30H31H….xxHyyHCS1CS20DHSub-Command: 2 bytes ASCII-Hex field.Pump channel:2 bytes ASCII-Hex field specifying the identifier of available infusion pump channels within the range of 0 to 255 (00H to FFH).MEDIBUS Device Extension for Infusion PumpsInfusion Pump Configuration Changed CommandIf an infusion pump has been added to or removedfrom the pump device and the pump device hasbeen asked for its configuration before, the pumpdevice will issue an Infusion Pump ConfigurationChanged sub-command (42H).After receiving the Infusion Pump ConfigurationChanged sub-command the requesting device hasto restart the infusion pump communication againby sending the Request Infusion Pump Configura-tion sub-command.Infusion Pump Configuration ChangedCommand:ESC Lead-Command Sub-Command 42H Checksum DAH CR 1BH59H34H32H44H41H0DHInfusion Pump Configuration ChangedResponse:SOH Lead-Command Sub-Command 42H Checksum C0H CR 01H59H34H32H43H30H0DHSub-Command: 2 bytes ASCII-Hex field.26Dräger RS232MEDIBUS。

KDD40 – 12 S 01MODEL LISTMODEL NO.INPUT VOLTAGEOUTPUT WATTAGEOUTPUT VOLTAGEOUTPUT CURRENTEFF . (MIN.)CASESingle Output ModelsKDD40 – 12S01 9~18 VDC 40 WATTS + 5 VDC 8000 mA 75% C KDD40 – 12S02 9~18 VDC 42 WATTS + 12 VDC 3500 mA 78% C KDD40 – 12S03 9~18 VDC 45 WATTS + 15 VDC 3000 mA 79% C KDD40 – 12S04 9~18 VDC 48 WATTS + 24 VDC 2000 mA 80% C KDD40 – 12S05 9~18 VDC 33 WATTS +3.3 VDC 10000 mA 73% C KDD40 – 24S01 18~36 VDC 40 WATTS + 5 VDC 8000 mA 79% C KDD40 – 24S02 18~36 VDC 42 WATTS + 12 VDC 3500 mA 81% C KDD40 – 24S03 18~36 VDC 45 WATTS + 15 VDC 3000 mA 81% C KDD40 – 24S04 18~36 VDC 48 WATTS + 24 VDC 2000 mA 81% C KDD40 – 24S05 18~36 VDC 33 WATTS +3.3 VDC 10000 mA 77% C KDD40 – 48S01 36~72 VDC 40 WATTS + 5 VDC 8000 mA 79% C KDD40 – 48S02 36~72 VDC 42 WATTS + 12 VDC 3500 mA 81% C KDD40 – 48S03 36~72 VDC 45 WATTS + 15 VDC 3000 mA 82% C KDD40 – 48S04 36~72 VDC 48 WATTS + 24 VDC 2000 mA 84% C KDD40 – 48S0536~72 VDC33 WATTS+3.3 VDC10000 mA77%C12 : 9~18V IN24 : 18~36V IN 48 :36~72V INWATTAGE 01: 5V or ±5V or +5V/±12V OUT02: 12V or ±12V or +5V/±15V OUT 03: 15V or ±15V or +5V/+12V/-5V OUT 04: 24V OUT 05: 3.3V OUTMODEL NO. INPUTVOLTAGEOUTPUTWATTAGEOUTPUTVOLTAGEOUTPUTCURRENTEFF.(MIN.)CASE Dual Output ModelsKDD40 – 12D01 9~18 VDC37.5 WATTS± 5 VDC+7000/-500 mA75% C KDD40 – 12D02 9~18 VDC42 WATTS± 12 VDC+3000/-500 mA78% C KDD40 – 12D03 9~18 VDC37.5 WATTS± 15 VDC+2000/-500 mA79% C KDD40 – 24D01 18~36 VDC42.5 WATTS± 5 VDC+8000/-500 mA77% C KDD40 – 24D02 18~36 VDC42 WATTS± 12 VDC+3000/-500 mA78% C KDD40 – 24D03 18~36 VDC37.5 WATTS± 15 VDC+2000/-500 mA80% C KDD40 – 48D01 36~72 VDC42.5 WATTS± 5 VDC+8000/-500 mA79% C KDD40 – 48D02 36~72 VDC42 WATTS± 12 VDC+3000/-500 mA81% C KDD40 – 48D03 36~72 VDC37.5 WATTS± 15 VDC+2000/-500 mA82% CTriple Output ModelsKDD40 – 12T01 9~18 VDC42 WATTS+5V/±12V+6000/±500 mA76% C KDD40 – 12T02 9~18 VDC45 WATTS+5V/±15V+6000/±500 mA77% C KDD40 – 24T01 18~36 VDC42 WATTS+5V/±12V+6000/±500 mA77% C KDD40 – 24T02 18~36 VDC45 WATTS+5V/±15V+6000/±500 mA78% C KDD40 – 24T03 18~36 VDC38.5 WATTS+5V/+12V/-5V+6A/+0.5A/-0.5A78% C KDD40 – 48T01 36~72 VDC42 WATTS+5V/±12V+6000/±500 mA78% C KDD40 – 48T02 36~72 VDC45 WATTS+5V/±15V+6000/±500 mA79% C KDD40 – 48T03 36~72 VDC38.5 WATTS+5V/+12V/-5V+3000/-500 mA79% CFEATURES* 2:1 INPUT RANGE* ISOLATION INPUT AND OUTPUT 1.5KV DC* HIGH PERFORMANCE UP TO 84%* SHORT CIRCUIT PROTECTION* 2 YEARS WARRANTYSPECIFICATIONAll Specifications Typical At Nominal Line, Full Load, 25 Unless Otherwise Noticed ℃GENERAL SPECIFICATION* Switching frequency: ......................... * Isolation voltage: .............................. * Isolation resistance: .......................... * Operating ambient temperature: ......... * Storage temperature: ........................ * Max. Case temperature: ..................... * M.T .B.F .: .......................................... * Cooling: ........................................... * Transient recovery time: .................... * Temperature coefficient: .................... * Dimension: ......................................>80KHz 1,500VDC >1G Ω(min.) -25 to +71℃ -40 to +85℃ 85℃389,000Hrs at @ GF40, according to MIL-HDBK-217F Free air convection500µS, 25% load step change ±0.02% / ℃70 x 100 x 23mm INPUT SPECIFICATIONS* Input voltage range / frequency: ........ * Input filter: ....................................... 9 ~ 18VDC for 12V 18 ~ 36VDC for 24V 36 ~ 72VDC for 48V Pi typeOUTPUT SPECIFICATIONS* Output voltage accuracy: ................... * Minimum load: .................................. * Line regulation: ................................ * Load regulation: ............................... * Ripple & noise: ................................. * Efficiency: ........................................ * Derating: ......................................... * Case material: .................................. ±1% at Vo_nom for single output models ±2% at Vo_nom for dual output models ±2% at Vo_nom for triple output models (±3% for -5V_out) No load for single output models ±20% at Vo_nom for dual & triple output models ±1% at Vo_nom±2% at Vo_nom for single output models ±2% for +V_out / ±5% for -V_out for dual output models ±2% for +5V/±5% for ±12V & ±15V & +12V/±15V for triple 20MHZ BM, Vout x ±1% mV p-p 150mV p-p for -5Vout for triple Up to 84%, see model list See table 1 MetalCONTROL AND PROTECTION* Output short circuit: ..........................ContinuousDerating:[TABLE 1]P o w e r o u t [%]100Ambient Temperture [℃]-25708560。

AN-1875LM5073HE Evaluation Board With Active BridgeUser's GuideLiterature Number:SNVA355July2008Contents 1Introduction (5)2Features (5)3Theory of Operation (5)4Important Information About theMaximum Power Capability,Cable Usage and PoE Input Potentials (5)5Loading (6)6Efficiency (7)7Printed Circuit Layout (7)2Table of Contents SNVA355–July2008Submit Documentation FeedbackCopyright©2008,Texas Instruments IncorporatedList of Figures1LM5073HE Evaluation Board Block Diagram (6)2Typical Evaluation Setup (7)3Efficiency at48V Input (7)4Top Silkscreen (8)5Top Copper (8)6Bottom Copper (8)7LM5073Evaluation Board:Input40-57V Startup,720mA (8)List of Tables1Bill of Materials (9)3 SNVA355–July2008List of Figures Submit Documentation FeedbackCopyright©2008,Texas Instruments IncorporatedUser's GuideSNVA355–July2008 AN-1875LM5073HE Evaluation Board With Active BridgeThe LM5073HE(High Efficiency)evaluation board is designed as a high performance solution for both IEEE802.3af fully compliant and non-compliant High Power over Ethernet(HPoE)applications.The possible intake power of the unit is a minimum of26.6W for a minimum input voltage of37VDC.All trademarks are the property of their respective owners.4AN-1875LM5073HE Evaluation Board With Active Bridge SNVA355–July2008Submit Documentation FeedbackCopyright©2008,Texas Instruments Incorporated Introduction 1IntroductionThe LM5073HE(High Efficiency)evaluation board is designed as a high performance solution for both IEEE802.3af fully compliant and non-compliant High Power over Ethernet(HPoE)applications.Thepossible intake power of the unit is a minimum of26.6W for a minimum input voltage of37VDC.To make a complete evaluation possible,the board also includes integrated Ethernet RX and TXmagnetics and an RJ45interface.2Features•IEEE802.3af fully compliant•Programmable maximum input dc current through PD interface:800mA•Input voltage ranges:–PoE input voltage range at startup:40to57V–PoE input voltage range with normal operation:33to57V•Efficient Mosfet Bridge polarity protection at input•Measured Efficiency:98%@37VDC,720mA input•Measured Efficiency:98.5%@48VDC,555mA input3Theory of OperationThe LM5073is a100V Power over Ethernet PD interface with auxiliary support.The low RDS(ON)PDinterface hot swap MOSFET and programmable DC current limit extend the range of LM5073applications up to twice the power level of IEEE802.3af compliant devices.In a typical configuration,the input ispolarity protected by a bridge rectifier that can cause an efficiency loss of up to3.5%.This configuration assumes that the design requirements include maximum possible efficiency.Therefore,the polarityprotection is provided by an input controlled mosfet bridge which yields a typical worse case loss of0.44%.For a more detailed description of the various features and customizations afforded,please referto application note AN-1574.4Important Information About theMaximum Power Capability,Cable Usage and PoE Input PotentialsThe LM5073HE evaluation board supports a maximum intake power of26.6W.The user must make sure that the Power Sourcing Equipment(PSE)used can provide at least30W,more if long cables are used.Important:Please note that the CAT-5cable may not supportthe maximum power over two pairs oftwisted wires understrict safety ers shall select the proper cablewires to support thedesign power level without compromisingthe applicable safety ing an improper cable at such power levels may violate various safety regulations and may cause damage.Polarity Precaution:PoE applications are typically-48V systems,in which the notations GND and-48V normally refer to the high and low input potentials,respectively.However,for easy readability,the LM5072 datasheet was written in the positive voltage convention with positive input potentials referenced to the VEE pin of the LM5073.Therefore,when testing the evaluation board with a bench power supply,thenegative terminal of the power supply is equivalent to the PoE system’s-48V potential,and the positive terminal is equivalent to the PoE system ground.To prevent confusion between the datasheet and this application note,the same positive voltage convention is used.5 SNVA355–July2008AN-1875LM5073HE Evaluation Board With Active Bridge Submit Documentation FeedbackCopyright©2008,Texas Instruments IncorporatedLoading Figure1.LM5073HE Evaluation Board Block Diagram5LoadingIf using an electronic load,be sure that the“LOAD ON”switch does not cause a large current surge when turned on.The LM5073cannot have a load applied until one of the shutdown outputs attempts to turn on the DC/DC converter.At this time,too much startup current may cause the LM5073to detect an over-current condition.The typical DC/DC converter has a soft-start feature to prevent this from being aproblem.If unable to monitor the shutdown outputs,simply wait a couple of seconds after applying input power before turning on the load.If you wish to test the evaluation board with an actual DC/DC converter as a load,be sure to connect the appropriate shutdown pin(or inverted shutdown pin)of the LM5073HE board to the appropriate shutdown pin(or inverted shutdown pin)of the DC/DC converter.The dual row6pin socket on the LM5073HE board will mate to a standard0.1”center dual row header.The pin out is shown below.The typical evaluation setup shown uses an LM5030evaluation board as a load.There are many other possible choices,but make sure that the electronic load at the output of the LM5030accounts for theefficiency loss of the LM5030board and does not exceed the limits of the LM5073HE board.Other possible evaluation boards to consider as loads include:L M5005Evaluation Board,a2.5A buck regulator for low cost non-isolated PD applicationsLM5020Evaluation Board,a current mode flyback converterLM5025Evaluation Board,a voltage mode active clamp forward converterLM5026Evaluation Board,a current mode active clamp forward converterLM5032Evaluation Board,a current mode dual interleaved converterLM5034Evaluation Board,a current mode dual interleaved converter with active clampLM5115Evaluation Board,a5A buck regulator with synchronous rectification6AN-1875LM5073HE Evaluation Board With Active Bridge SNVA355–July2008Submit Documentation FeedbackCopyright©2008,Texas Instruments Incorporated EfficiencyFigure2.Typical Evaluation Setup6EfficiencyFigure3shows the typical efficiency curve at48VDC input verses load.Since losses are almost entirely resistive,a value of1.05Ohms may be used to estimate losses for other levels of current and voltage.Figure3.Efficiency at48V Input7Printed Circuit LayoutThe layers of the printed circuit board are shown in top down order in Figure4to Figure6.View is from the top of the board.Scale is approximately X1.5.The printed circuit board consists of2layers of2ounce copper on FR4material with a total thickness of0.065inches.7 SNVA355–July2008AN-1875LM5073HE Evaluation Board With Active Bridge Submit Documentation FeedbackCopyright©2008,Texas Instruments IncorporatedPrinted Circuit Layout Figure4.Top SilkscreenFigure5.Top CopperFigure6.Bottom CopperFigure7.LM5073Evaluation Board:Input40-57V Startup,720mA8AN-1875LM5073HE Evaluation Board With Active Bridge SNVA355–July2008Submit Documentation FeedbackCopyright©2008,Texas Instruments Incorporated Printed Circuit LayoutTable1.Bill of MaterialsDesigna Description Manufacturer Part Number torC18.0pF,50V,CER,NPO,0603AVX06031A8R0CAT2A C28.0pF,50V,CER,NPO,0603AVX06031A8R0CAT2A C38.0pF,50V,CER,NPO,0603AVX06031A8R0CAT2A C48.0pF,50V,CER,NPO,0603AVX06031A8R0CAT2A C50.047µF,100V,X7R,0805TDK C2012X7R2A473K C60.047µF,100V,X7R,0805TDK C2012X7R2A473K C70.047µF,100V,X7R,0805TDK C2012X7R2A473K C822µF,100V,ALUM ELECT,LOW ESR PANASONIC EEV-FK2A220PJ1JACK,MODULAR,2PORT RJ45TYCO5569381-1J2SOCKET,.025"SQ POST,3X2,R/A TYCO6-535512-2L1INDUCTOR,4.7µH,1.8A,56m COILCRAFT MSS6132-472MLP1TEST POINT,MINIATURE KEYSTONE5002P2TEST POINT,MINIATURE KEYSTONE5002P3TERMINAL,TURRET KEYSTONE1503P4TERMINAL,TURRET KEYSTONE1503P5TERMINAL,TURRET KEYSTONE1503P6TERMINAL,TURRET KEYSTONE1503Q1MOSFET,P-CH,100V,134mΩ,1212-8VISHAY SI7113DNQ2MOSFET,P-CH,100V,134mΩ,1212-8VISHAY SI7113DNQ3MOSFET,DUAL N-CH,100V,62mΩ,SO8FAIRCHILD FDS3992Q4MOSFET,P-CH,100V,134mΩ,1212-8VISHAY SI7113DNQ5MOSFET,P-CH,100V,134mΩ,1212-8VISHAY SI7113DNQ6MOSFET,DUAL N-CH,100V,62mΩ,SO8FAIRCHILD FDS3992R1RESISTOR,150K,1%,1/8W,0805VISHAY CRCW0805150KFR2RESISTOR,150K,1%,1/8W,0805VISHAY CRCW0805150KFR3RESISTOR,150K,1%,1/8W,0805VISHAY CRCW0805150KFR4RESISTOR,150K,1%,1/8W,0805VISHAY CRCW0805150KFR5RESISTOR,150K,1%,1/8W,0805VISHAY CRCW0805150KFR6RESISTOR,150K,1%,1/8W,0805VISHAY CRCW0805150KFR7RESISTOR,150K,1%,1/8W,0805VISHAY CRCW0805150KFR8RESISTOR,150K,1%,1/8W,0805VISHAY CRCW0805150KFR9RESISTOR,31.6,1%,1/8W,0805VISHAY CRCW080531R6F R10RESISTOR,15.0K,1%,1/8W,0805VISHAY CRCW080515K0FT1SIGNAL PATH HPOE MAGNETICS COILCRAFT ETH1-230LU1IC,POE INTERFACE,TSSOP-14EP NATIONAL SEMICONDUCTOR LM5073MHZ1ZENER,15V@50µA,SOD-123CENTRAL SEMICONDUCTOR CMHZ4702Z2ZENER,15V@50µA,SOD-123CENTRAL SEMICONDUCTOR CMHZ4702Z3ZENER,15V@50µA,SOD-123CENTRAL SEMICONDUCTOR CMHZ4702Z4ZENER,15V@50µA,SOD-123CENTRAL SEMICONDUCTOR CMHZ4702Z5ZENER,15V@50µA,SOD-123CENTRAL SEMICONDUCTOR CMHZ4702Z6ZENER,15V@50µA,SOD-123CENTRAL SEMICONDUCTOR CMHZ4702Z7ZENER,15V@50µA,SOD-123CENTRAL SEMICONDUCTOR CMHZ4702Z8ZENER,15V@50µA,SOD-123CENTRAL SEMICONDUCTOR CMHZ4702Z9DIODE,TVS,60V,SMA DIODES INC.SMAJ60A-139 SNVA355–July2008AN-1875LM5073HE Evaluation Board With Active Bridge Submit Documentation FeedbackCopyright©2008,Texas Instruments IncorporatedPrinted Circuit Layout 10AN-1875LM5073HE Evaluation Board With Active Bridge SNVA355–July2008Submit Documentation FeedbackCopyright©2008,Texas Instruments IncorporatedEVALUATION BOARD/KIT/MODULE(EVM)ADDITIONAL TERMSTexas Instruments(TI)provides the enclosed Evaluation Board/Kit/Module(EVM)under the following conditions:The user assumes all responsibility and liability for proper and safe handling of the goods.Further,the user indemnifies TI from all claims arising from the handling or use of the goods.Should this evaluation board/kit not meet the specifications indicated in the User’s Guide,the board/kit may be returned within30days from the date of delivery for a full refund.THE FOREGOING LIMITED WARRANTY IS THE EXCLUSIVE WARRANTY MADE BY SELLER TO BUYER AND IS IN LIEU OF ALL OTHER WARRANTIES,EXPRESSED,IMPLIED,OR STATUTORY,INCLUDING ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE.EXCEPT TO THE EXTENT OF THE INDEMNITY SET FORTH ABOVE,NEITHER PARTY SHALL BE LIABLE TO THE OTHER FOR ANY INDIRECT,SPECIAL,INCIDENTAL,OR CONSEQUENTIAL DAMAGES.Please read the User's Guide and,specifically,the Warnings and Restrictions notice in the User's Guide prior to handling the product.This notice contains important safety information about temperatures and voltages.For additional information on TI's environmental and/or safety programs,please visit /esh or contact TI.No license is granted under any patent right or other intellectual property right of TI covering or relating to any machine,process,or combination in which such TI products or services might be or are used.TI currently deals with a variety of customers for products,and therefore our arrangement with the user is not exclusive.TI assumes no liability for applications assistance,customer product design, software performance,or infringement of patents or services described herein.REGULATORY COMPLIANCE INFORMATIONAs noted in the EVM User’s Guide and/or EVM itself,this EVM and/or accompanying hardware may or may not be subject to the Federal Communications Commission(FCC)and Industry Canada(IC)rules.For EVMs not subject to the above rules,this evaluation board/kit/module is intended for use for ENGINEERING DEVELOPMENT, DEMONSTRATION OR EVALUATION PURPOSES ONLY and is not considered by TI to be a finished end product fit for general consumer use.It generates,uses,and can radiate radio frequency energy and has not been tested for compliance with the limits of computing devices pursuant to part15of FCC or ICES-003rules,which are designed to provide reasonable protection against radio frequency interference.Operation of the equipment may cause interference with radio communications,in which case the user at his own expense will be required to take whatever measures may be required to correct this interference.General Statement for EVMs including a radioUser Power/Frequency Use Obligations:This radio is intended for development/professional use only in legally allocated frequency and power limits.Any use of radio frequencies and/or power availability of this EVM and its development application(s)must comply with local laws governing radio spectrum allocation and power limits for this evaluation module.It is the user’s sole responsibility to only operate this radio in legally acceptable frequency space and within legally mandated power limitations.Any exceptions to this are strictly prohibited and unauthorized by Texas Instruments unless user has obtained appropriate experimental/development licenses from local regulatory authorities,which is responsibility of user including its acceptable authorization.For EVMs annotated as FCC–FEDERAL COMMUNICATIONS COMMISSION Part15CompliantCautionThis device complies with part15of the FCC Rules.Operation is subject to the following two conditions:(1)This device may not cause harmful interference,and(2)this device must accept any interference received,including interference that may cause undesired operation. Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.FCC Interference Statement for Class A EVM devicesThis equipment has been tested and found to comply with the limits for a Class A digital device,pursuant to part15of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.This equipment generates,uses,and can radiate radio frequency energy and,if not installed and used in accordance with the instruction manual,may cause harmful interference to radio communications.Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.FCC Interference Statement for Class B EVM devicesThis equipment has been tested and found to comply with the limits for a Class B digital device,pursuant to part15of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation.This equipment generates,uses and can radiate radio frequency energy and,if not installed and used in accordance with the instructions,may cause harmful interference to radio communications.However,there is no guarantee that interference will not occur in a particular installation.If this equipment does cause harmful interference to radio or television reception,which can be determined by turning the equipment off and on,the user is encouraged to try to correct the interference by one or more of the following measures:•Reorient or relocate the receiving antenna.•Increase the separation between the equipment and receiver.•Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.•Consult the dealer or an experienced radio/TV technician for help.For EVMs annotated as IC–INDUSTRY CANADA CompliantThis Class A or B digital apparatus complies with Canadian ICES-003.Changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment.Concerning EVMs including radio transmittersThis device complies with Industry Canada licence-exempt RSS standard(s).Operation is subject to the following two conditions:(1)this device may not cause interference,and(2)this device must accept any interference,including interference that may cause undesired operation of the device.Concerning EVMs including detachable antennasUnder Industry Canada regulations,this radio transmitter may only operate using an antenna of a type and maximum(or lesser)gain approved for the transmitter by Industry Canada.To reduce potential radio interference to other users,the antenna type and its gain should be so chosen that the equivalent isotropically radiated power(e.i.r.p.)is not more than that necessary for successful communication.This radio transmitter has been approved by Industry Canada to operate with the antenna types listed in the user guide with the maximum permissible gain and required antenna impedance for each antenna type indicated.Antenna types not included in this list,having a gain greater than the maximum gain indicated for that type,are strictly prohibited for use with this device.Cet appareil numérique de la classe A ou B est conformeàla norme NMB-003du Canada.Les changements ou les modifications pas expressément approuvés par la partie responsable de la conformitéont pu vider l’autoritédel'utilisateur pour actionner l'équipement.Concernant les EVMs avec appareils radioLe présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence.L'exploitation est autorisée aux deux conditions suivantes:(1)l'appareil ne doit pas produire de brouillage,et(2)l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi,même si le brouillage est susceptible d'en compromettre le fonctionnement.Concernant les EVMs avec antennes détachablesConformémentàla réglementation d'Industrie Canada,le présentémetteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal(ou inférieur)approuvépour l'émetteur par Industrie Canada.Dans le but de réduire les risques de brouillage radioélectriqueàl'intention des autres utilisateurs,il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonnéeéquivalente (p.i.r.e.)ne dépasse pas l'intensiténécessaireàl'établissement d'une communication satisfaisante.Le présentémetteur radio aétéapprouvépar Industrie Canada pour fonctionner avec les types d'antenneénumérés dans le manueld’usage et ayant un gain admissible maximal et l'impédance requise pour chaque type d'antenne.Les types d'antenne non inclus dans cette liste,ou dont le gain est supérieur au gain maximal indiqué,sont strictement interdits pour l'exploitation de l'émetteur.【Important Notice for Users of this Product in Japan】This development kit is NOT certified as Confirming to Technical Regulations of Radio Law of JapanIf you use this product in Japan,you are required by Radio Law of Japan to follow the instructions below with respect to this product:e this product in a shielded room or any other test facility as defined in the notification#173issued by Ministry of Internal Affairs andCommunications on March28,2006,based on Sub-section1.1of Article6of the Ministry’s Rule for Enforcement of Radio Law of Japan,e this product only after you obtained the license of Test Radio Station as provided in Radio Law of Japan with respect to thisproduct,ore of this product only after you obtained the Technical Regulations Conformity Certification as provided in Radio Law of Japan withrespect to this product.Also,please do not transfer this product,unless you give the same notice above to the transferee.Please note that if you could not follow the instructions above,you will be subject to penalties of Radio Law of Japan.Texas Instruments Japan Limited(address)24-1,Nishi-Shinjuku6chome,Shinjuku-ku,Tokyo,Japanhttp://www.tij.co.jp【ご使用にあたっての注】本開発キットは技術基準適合証明を受けておりません。