E and L居中板 BEA--250482-EN-14

PCD1.G2100-A10E-Line S-Serie RIO 8UIData sheetThe S-Serie E-Line RIO modules are controlled via the RS-485 serial communication protocols S-Bus and Modbus for decentralised automation using industrial quality components. The data point mix is specifically designed for building automation applications.The compact design according to DIN 43880 enables the use in electrical distributionboxes even in the most confined spaces. Installation and maintenance are facilitated by the local manual override for each output. Remote maintenance is also possible using the access to the manual override by the web interface in the Saia PCD® controller. Programming is very efficient and fast using a complete FBox library with web templates for S-Bus. Individual programs may directly access the data points via Registers and Flags, a complete documentation is available from this data sheet.f S-Bus protocol optimized for fast data exchangef Modbus protocol for integration in multi-vendor installations*f Local override operating level via web panel or buttons on the module f Easy programming using the FBox library and web templates f Industrial hardware in accordance with IEC EN 61131-2 f Pluggable terminal blocksf Bridge connectors for power supply and communication f Bus termination on boardf Configurable Bi-Colour LEDs and labelling for I/Os* B y default the module is working in S-Bus Data Mode with Autobaud detection. To configure Modbus the Windows based Application “E-LineApp” is required.On a 35 mm top-hat rail ( i n accordance with DIN EN 60715 TH35)Housing width 6 HP (105 mm)Compatible with electrical control cabinet (in accordance with DIN 43880, size 2 × 55 mm)Dimensions and installationFeaturesGeneral technical dataPower supply/DA+DB-GND+24VOpenClose For easy installation the power supply and communicationbus is available together at one connector. The push-in springterminals enable wiring as well support the connector bridge.Push-in spring terminals enable wiring with rigid or flexible wireswith a diameter up to 1.5 mm². A max. of 1 mm² is permitted withcable end sleeves.Terminal technologyConnection conceptOFF No PowerGreen Communication OKGreen blink Auto bauding in progressOrange No communicationRedE rrorRed/Green alternate B ooter mode(e.g. during Firmware download)Red blink Internal fatal errorStatus LEDThe module provides an active bus termination. It is switchedoff by factory default. To enable the termination, the switchneed to be in the “Close” position.Bus terminationThe USB interface provides access to the communicationprotocol configuration. Firmware updates can also be downloaded via Saia PG5® Firmware Download tool.Service interfaceReset buttonPushed over 20 seconds: The button needs to be pushed forminimum 20 seconds and released during the first minute afterpower up. All user settings are reset to factory default values.Pushed at power up: Power off the device and press thebutton. Power on and release the button before 5 seconds havepassed. The device stays in boot mode for further actions likefirmware download etc.Input/Output configurationUniversal InputsAnalogue input mode[2] R ange 0 … 300 kΩ must be used. The temperature for NTC are not standardised and may differ depending on the manufacturer.A CSV file can be used for the value generation with a linearisation FBox. The CSV file can be found on the support page (link, see last page).Digital input modeGND +24V/DA+DB–GND +24V/DA+DB–Assignment overviewPower supply and bus terminationConnection diagrams0 … 10 V0 … 300 kOhmUniversal inputsOFF No Power Green Communication OK Green blink Auto bauding in progress Orange No communication Red E rror Red/Green alternate B ooter mode (e.g. during Firmwaredownload)Red blink Internal fatal errorStatus LEDLED SignalisationUniversal inputThe Manual override LED is Off in automatic mode and orange in case of manual override is active.LED colour f Off (automatic)f Orange manual mode active LED blink codef No blink (local manual override)f Blinking 1 flash per second (remote manual override)Manual modef Data exchange for I/O via optimised S-Busf Configurable save state for bus interruption or timeoutf Direct generation of the symbolsf Reading and writing of the status of the manual override statusf Direct compatibility with web macrosThe modules are addressed and programmed with Saia PG5® Fupla FBoxes. Web templates are available for theoperation and visualisation of the manual override function.Further information, including which FBoxes are supported,Getting Started, etc., can be found on our support page.Web templates are available for the operation and visualisationof the manual override function.Communication FBoxWeb templatesProgrammingBy using the local override function, commissioning can takeplace independently of the master station.In addition, the manual operation can also be controlledremotely using a touch panel. If the bus line is cut off, the FuplaE-Line libraryE-Line RIOs support the device setup by a windows application program connected via USB. The installer is available for down-load from the SBC support page: E-Line RIO IO Modules.The Baudrate can be defined as automatic detection(default) or set to a specific value. The drop down choice willbe available when the check box “Automatic” is unchecked.TN delay and TS delay shall be left at their default values of 2.Create a new device configurationOpen an existing device configurationSave the current settings as device configurationUpload configuration from the deviceDownload settings to the deviceThe serial communication protocol can be defined either asS-Bus or Modbus. By default the modules are delivered fromfactory with S-Bus.S-Bus settingsThe station number can be set by the rotary switches at thedevice in the range of 0 … 98. If the rotary switches are set toposition 99 the station number can be defined by the deviceconfiguration in a range of 0 … 253.Modbus settingsThe Baudrate is set by default to 115 k. It can be defined aschoice of the list.For best interoperability the Parity Mode and number ofStop Bits can also be set.S-Bus communication is based on Saia PCD® S-Bus Data Mode. Only the set-up of a unique S-Bus address within the communi-cation line is required to establish a communication between Saia PCD® controllers and E-Line RIO modules. The address can be set by the rotary switches at the front of the module. The baud rate will be learned from the network by factory default. In addition a Windows based application is available for manual parameter setup. Configuration parameters as well as manual override state and value are saved non-volatile. A delay of about one second between a manual state change and none volatile saving has to be taken into consideration.Device address f 0 … 98 Address is taken from the rotary switchesf 99Address is taken from the device configuration. The address is settable with the E-Line configuration software.Start-up procedure f Reboot: All outputs are cleared (Off state) f < 1 sec.Output in manual operation are set according to the state before power down.f Outputs in automatic modeIs no telegram received after reboot within the “safe state power-on timeout” the module enters into the safe state mode and sets the outputs according to their configured values.On reception of a valid command telegram the outputs are controlled by the communication. When no communication update followed within the “safe state com. timeout” the module enters into safe state and sets the outputs according to their configured values.Usage of the E-Line module specific FBoxesThe usage of the E-Line module specific FBoxes from the E-Line S-Bus Fupla library allows an easy and efficient commis-sioning of the E-Line RIO.The FBox allow to define and configure all possible function-alities of the E-Line RIO like manual override permission, us-age of safe state mode, behaviour and colour of the LED’s and so on.In the background, the FBox does use the fast ‘E-Line S-Bus’ protocol for a high speed communication between the mas-ter and the RIO.The following chapter describes the media and parameter mapping to Registers and Flags for individual programming. For efficient PCD programming the E-Line RIO FBox family and templates are suitable for most applications. Only individual pro-gramming (e.g. Instruction List) require standard S-Bus communication.Mode Configuration Register:0 : 0 … 10 V (default) Value scaled within Range Min and Range Max 3 : 0 … 2500 Ω Value scaled within Range Min and Range Max 4 : Pt1000 Value in 1/10°C (23.4 °C → 234)5 : Ni1000 Value in 1/10°C (23.4 °C → 234)6 : Ni1000LS Value in 1/10°C (23.4 °C → 234)8 : 0 … 300 kΩ Value scaled within Range Min and Range Max 9 : Digital inputValue for Input open, <5 V = 0, Input >10 V, 24 VDC = 1Register format:1 byte for each analogue input status. (e.g. b yte 0: AI0byte 1: AI1 byte 2: AI2 byte 3: AI3)Bit 0 Analogue input over-range Bit 1 Analogue input under-rangeStatus is cleared when the input returns to normal stateAnalogue inputsDirect access to the RIO medias with standard S-Bus send and receive telegrams** Time in 0.1 ms (e.g. 2 means 200 us) before sending the first character after line driver activation (only used for S-Bus slave protocol)*** The four registers contain the ASCII characters of the product type.E.g. for PCD1.A2000-A20:0605: 50434431H 0606: 2E413230H 0607: 30302D41H 0608: 32300000HDevice InformationModbus fulfils the requirements for standard communication protocols. It is based on Modbus RTU. The Windows based configu-ration software is required to enable and set up the Modbus communication parameters. The device address can be set up with the rotary switches at the front of the module. Configuration parameters as well as manual override state and value are saved non-volatile. A delay of about one second between a manual state change and non-volatile saving has to be taken into consideration. Device addressf0 … 98 Address is taken from the rotary switchesf99 Address is taken from the device configuration. The address is settable with the E-Line configuration soft-ware.Start-up proceduref Reboot: All outputs are cleared (Off state)f<1 sec. Output in manual operation are set according to the state before power down.f Outputs in automatic modeIs no telegram received after reboot within the “safe state power-on timeout” the module enters as will intothe safe state mode and sets the outputs according to their configured values.On reception of a valid command telegram the outputs are controlled by the communication. When no com-munication update followed within the “safe state com. timeout” the module enters into safe state and setsthe outputs according to their configured values.The following chapter describes the media and parameter mapping to Registers and Flags (=Coils).Supported Modbus services:f Function code 1 (read outputs)f Function code 3 (read registers)f Function code 15 (write multiple outputs)f Function code 16 (write multiple registers)The CRC has to be calculated over all telegram bytes starting with address field up to the last data byte. The CRC has to be attached to the data. Please find an example at the appendix of this document. For more details, please refer the publicly available Modbus documentation .Mode Configuration Register:0 : 0 … 10 V (default) Value scaled within Range Min and Range Max 3 : 0 … 2500 Ω Value scaled within Range Min and Range Max 4 : Pt1000 Value in 1/10°C (23.4 °C → 234)5 : Ni1000 Value in 1/10°C (23.4 °C → 234)6 : Ni1000LS Value in 1/10°C (23.4 °C → 234)8 : 0 … 300 kΩ Value scaled within Range Min and Range Max 9 : Digital inputValue for Input open, <5 V = 0, Input >10 V, 24 VDC = 1Register format:1 byte for each analogue input status. (e.g. b yte 0: AI0byte 1: AI1 byte 2: AI2 byte 3: AI3)Bit 0 Analogue input over-range Bit 1 Analogue input under-rangeStatus is cleared when the input returns to normal stateAnalogue inputsE.g. for PCD1.A2000-A20:1210…1217: 5043H | 4431H | 2E41H | 3230H | 3030H | 2D41H | 3230H | 0000HDevice InformationCRC Generation Example(Source: /docs/PI_MBUS_300.pdf, the following content of this page is copied from the referenced document. In case of any questions, please check out the original source)The function takes two arguments: unsigned char *puchMsg; A pointer to the message buffer containing binary data to be used for generating the CRC unsigned short usDataLen; The quantity of bytes in the message buffer. The function returns the CRC as a type unsigned short.CRC Generation Functionunsigned short CRC16(puchMsg, usDataLen) ;unsigned char *puchMsg ; /* message to calculate CRC upon */unsigned short usDataLen ; /* quantity of bytes in message */{unsigned char uchCRCHi = 0xFF ; /* high byte of CRC initialized */unsigned char uchCRCLo = 0xFF ; /* low byte of CRC initialized */unsigned uIndex ; /* will index into CRC lookup table */while (usDataLen--) /* pass through message buffer */{uIndex = uchCRCHi ^ *puchMsgg++; /* calculate the CRC */uchCRCHi = uchCRCLo ^ auchCRCHi[uIndex];uchCRCLo = auchCRCLo[uIndex];}return (uchCRCHi << 8 | uchCRCLo);}High-Order Byte Table/* Table of CRC values for high-order byte */static unsigned char auchCRCHi[] = {0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40,0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40, 0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41,0x00, 0xC1, 0x81, 0x40, 0x01, 0xC0, 0x80, 0x41, 0x01, 0xC0, 0x80, 0x41, 0x00, 0xC1, 0x81, 0x40 }; Low-Order Byte Table/* Table of CRC values for low-order byte */static char auchCRCLo[] = {0x00, 0xC0, 0xC1, 0x01, 0xC3, 0x03, 0x02, 0xC2, 0xC6, 0x06, 0x07, 0xC7, 0x05, 0xC5, 0xC4, 0x04,0xCC, 0x0C, 0x0D, 0xCD, 0x0F, 0xCF, 0xCE, 0x0E, 0x0A, 0xCA, 0xCB, 0x0B, 0xC9, 0x09, 0x08, 0xC8,0xD8, 0x18, 0x19, 0xD9, 0x1B, 0xDB, 0xDA, 0x1A, 0x1E, 0xDE, 0xDF, 0x1F, 0xDD, 0x1D, 0x1C, 0xDC,0x14, 0xD4, 0xD5, 0x15, 0xD7, 0x17, 0x16, 0xD6, 0xD2, 0x12, 0x13, 0xD3, 0x11, 0xD1, 0xD0, 0x10,0xF0, 0x30, 0x31, 0xF1, 0x33, 0xF3, 0xF2, 0x32, 0x36, 0xF6, 0xF7, 0x37, 0xF5, 0x35, 0x34, 0xF4,0x3C, 0xFC, 0xFD, 0x3D, 0xFF, 0x3F, 0x3E, 0xFE, 0xFA, 0x3A, 0x3B, 0xFB, 0x39, 0xF9, 0xF8, 0x38,0x28, 0xE8, 0xE9, 0x29, 0xEB, 0x2B, 0x2A, 0xEA, 0xEE, 0x2E, 0x2F, 0xEF, 0x2D, 0xED, 0xEC, 0x2C,0xE4, 0x24, 0x25, 0xE5, 0x27, 0xE7, 0xE6, 0x26, 0x22, 0xE2, 0xE3, 0x23, 0xE1, 0x21, 0x20, 0xE0,0xA0, 0x60, 0x61, 0xA1, 0x63, 0xA3, 0xA2, 0x62, 0x66, 0xA6, 0xA7, 0x67, 0xA5, 0x65, 0x64, 0xA4,0x6C, 0xAC, 0xAD, 0x6D, 0xAF, 0x6F, 0x6E, 0xAE, 0xAA, 0x6A, 0x6B, 0xAB, 0x69, 0xA9, 0xA8, 0x68,0x78, 0xB8, 0xB9, 0x79, 0xBB, 0x7B, 0x7A, 0xBA, 0xBE, 0x7E, 0x7F, 0xBF, 0x7D, 0xBD, 0xBC, 0x7C,0xB4, 0x74, 0x75, 0xB5, 0x77, 0xB7, 0xB6, 0x76, 0x72, 0xB2, 0xB3, 0x73, 0xB1, 0x71, 0x70, 0xB0,0x50, 0x90, 0x91, 0x51, 0x93, 0x53, 0x52, 0x92, 0x96, 0x56, 0x57, 0x97, 0x55, 0x95, 0x94, 0x54,0x9C, 0x5C, 0x5D, 0x9D, 0x5F, 0x9F, 0x9E, 0x5E, 0x5A, 0x9A, 0x9B, 0x5B, 0x99, 0x59, 0x58, 0x98,0x88, 0x48, 0x49, 0x89, 0x4B, 0x8B, 0x8A, 0x4A, 0x4E, 0x8E, 0x8F, 0x4F, 0x8D, 0x4D, 0x4C, 0x8C,0x44, 0x84, 0x85, 0x45, 0x87, 0x47, 0x46, 0x86, 0x82, 0x42, 0x43, 0x83, 0x41, 0x81, 0x80, 0x40 };PCD1.G2100-A10PCD1.K0206-005PCD1.K0206-025Saia-Burgess Controls AGBahnhofstrasse 18 | 3280 Murten, Switzerland T +41 26 580 30 00 | F +41 26 580 34 ********************|Order detailsTerminal set 32304321-003-S。

Quick Start GuideSWRU425–December2015 Dual-Mode Bluetooth®CC2564Module With IntegratedAntenna Evaluation BoardThis quick-start guide offers an overview of the CC2564MODAEM evaluation board for the dual-mode Bluetooth CC2564module with integrated antenna(CC2564MODA),including required hardware and software tools and basic settings.For more information,see the Dual-Mode Bluetooth CC2564Module With Integrated Antenna Evaluation Board User Guide(SWRU427).Contents1Introduction (2)2CC2564MODAEM Kit Contents (2)3CC2564MODAEM Requirements (3)4CC2564MODAEM Board Overview (4)5CC2564MODAEM Board Settings (5)List of Figures1CC2564MODAEM Board (2)2Hardware Setup Examples (3)3CC2564MODAEM Front View (4)4CC2564MODAEM Back View (4)List of Tables1EM1Standard Pinout (5)2EM2Standard Pinout (5)3COM Connector Pinout (6)1 SWRU425–December2015Dual-Mode Bluetooth®CC2564Module With Integrated Antenna EvaluationBoard Submit Documentation FeedbackCopyright©2015,Texas Instruments IncorporatedIntroduction 1IntroductionThe CC2564MODAEM board is used to evaluate the TI CC2564MODA device,which supports classicBluetooth and Bluetooth low energy(LE)wireless technology.The CC2564MODAEM works with TI'shardware development kits(HDKs),such as the following:•MSP-EXP430F5529•MSP-EXP430F5438•DK-TM4C123G•DK-TM4C129XThe CC2564MODA device is a complete basic rate(BR),enhanced data rate(EDR),and LE hostcontroller interface(HCI)solution that reduces design effort and enables fast time to market.Based on TI’s seventh-generation core,the module brings a product-proven solution supporting Bluetooth4.1dual-mode protocols.Figure1shows the CC2564MODAEM board.2564MODAEM Board2CC2564MODAEM Kit ContentsThe CC2564MODAEM kit contains the following contents:•One CC2564MODAEM board,including the dual-mode Bluetooth CC2564module with integrated antenna•One block jumper for the MSP-EXP430F5438board•Four jumpers for the MSP-EXP430F5529board2Dual-Mode Bluetooth®CC2564Module With Integrated Antenna Evaluation SWRU425–December2015 Board Submit Documentation FeedbackCopyright©2015,Texas Instruments Incorporated CC2564MODAEM Requirements 3CC2564MODAEM RequirementsFor a complete evaluation,the CC2564MODAEM board requires hardware and software tools selected from the following list:•HardwareMSP430™experimenter board(sold separately)or TM4C development kit(sold separately):–MSP430experimenter board options•MSP-EXP430F5529•MSP-EXP430F5438–TM4C development kit options•DK-TM4C123G•DK-TM4C129X•Software•TI dual-mode Bluetooth stack•On MSP430MCUs:CC256XMSPBTBLESW•On TM4C MCUs:CC256XM4BTBLESW•Other MCUs•On STM32F4MCUs:CC256XSTBTBLESWFigure2shows example hardware setups for the CC2564MODAEM board using the MSP-EXP430F5529 and MSP-EXP430F5438experimenter boards.Figure2.Hardware Setup Examples3 SWRU425–December2015Dual-Mode Bluetooth®CC2564Module With Integrated Antenna EvaluationBoard Submit Documentation FeedbackCopyright©2015,Texas Instruments IncorporatedCC2564MODAEM Board Overview 4CC2564MODAEM Board OverviewThe CC2564MODAEM board has two different connectors:•EM(default):I/Os are at3.3V.•COM:I/Os are at1.8V.Figure3shows the connectors on the front side of the CC2564MODAEM board.2564MODAEM Front ViewFigure4shows the connectors on the back side of the CC2564MODAEM board.2564MODAEM Back View4Dual-Mode Bluetooth®CC2564Module With Integrated Antenna Evaluation SWRU425–December2015 Board Submit Documentation FeedbackCopyright©2015,Texas Instruments Incorporated CC2564MODAEM Board Settings 5CC2564MODAEM Board SettingsThis section describes the settings for the EM connector and the COM connector.5.1EM Connector SettingsThe EM connectors can be mounted on a wide variety of TI MCU platforms,such as the MSP430(MSP-EXP430F5529and MSP-EXP430F5438)and TM4C(DK-TM4C123G and DK-TM4C129X).All EM I/Os are at3.3-V levels.Pin assignments are described with respect to the front(CC2564MODA) side.For example,MODULE_UART_RX refers to the receiving UART RX pin on the CC2564MODAdevice that connects to the UART_TX pin on the MCU.Table1describes the standard pinout for EM1.Table1.EM1Standard PinoutPin EM Adapter Assignment(1)Pin EM Adapter Assignment(1)1GND2NC3MODULE_UART_CTS4NC5SLOW_CLK6NC7MODULE_UART_RX8NC9MODULE_UART_TX10NC11NC12NC13NC14NC15NC16NC17NC18NC19GND20NC(1)NC=not connectedTable2describes the standard pinout for EM2.Table2.EM2Standard PinoutPin EM Adapter Assignment(1)Pin EM Adapter Assignment(1)1NC2GND3NC4NC5NC6NC7 3.3V8MODULE_AUDIO_DATA_OUT9 3.3V10MODULE_AUDIO_DATA_IN11MODULE_AUDIO_FSINK12NC13NC14NC15NC16NC17MODULE_AUDIO_CLK18MODULE_UART_RTS19nSHUTD20NC(1)NC=not connected5 SWRU425–December2015Dual-Mode Bluetooth®CC2564Module With Integrated Antenna EvaluationBoard Submit Documentation FeedbackCopyright©2015,Texas Instruments IncorporatedCC2564MODAEM Board Settings 5.2COM Connector SettingsThe COM connector interfaces with TI's MPU platforms,such as the AM335x evaluation module(TMDXEVM3358).NOTE:•All I/Os for the COM connector are at1.8V.•Some components must not be installed(DNI)to use the COM connector.For moreinformation,see the Dual-Mode Bluetooth CC2564Module With Integrated AntennaEvaluation Board User Guide(SWRU427).Table3describes the COM connector pinout. Connector PinoutPin(1)Relevant COM Connector Pin Assignment1SLOW_CLK_EDGE81V8_IN52AUD_CLK_1V854AUD_FSYNC_1V856AUD_IN_1V858AUD_OUT_1V866HCI_TX_1V868HCI_RX_1V870HCI_CTS_1V872HCI_RTS_1V876TX_DEBUG_1V889nSHUTDOWN_1V83,9,19,37,47,63,77,83,87,GND95,972,6,18,22,42,60,64,92GND(1)Pins not listed are NC.6Dual-Mode Bluetooth®CC2564Module With Integrated Antenna Evaluation SWRU425–December2015 Board Submit Documentation FeedbackCopyright©2015,Texas Instruments IncorporatedIMPORTANT NOTICETexas Instruments Incorporated and its subsidiaries(TI)reserve the right to make corrections,enhancements,improvements and other changes to its semiconductor products and services per JESD46,latest issue,and to discontinue any product or service per JESD48,latest issue.Buyers should obtain the latest relevant information before placing orders and should verify that such information is current and complete.All semiconductor products(also referred to herein as“components”)are sold subject to TI’s terms and conditions of sale supplied at the time of order acknowledgment.TI warrants performance of its components to the specifications applicable at the time of sale,in accordance with the warranty in TI’s terms and conditions of sale of semiconductor products.Testing and other quality control techniques are used to the extent TI deems necessary to support this warranty.Except where mandated by applicable law,testing of all parameters of each component is not necessarily performed.TI assumes no liability for applications assistance or the design of Buyers’products.Buyers are responsible for their products and applications using TI components.To minimize the risks associated with Buyers’products and applications,Buyers should provide adequate design and operating safeguards.TI does not warrant or represent that any license,either express or implied,is granted under any patent right,copyright,mask work right,or other intellectual property right relating to any combination,machine,or process in which TI components or services are rmation published by TI regarding third-party products or services does not constitute a license to use such products or services or a warranty or endorsement e of such information may require a license from a third party under the patents or other intellectual property of the third party,or a license from TI under the patents or other intellectual property of TI.Reproduction of significant portions of TI information in TI data books or data sheets is permissible only if reproduction is without alteration and is accompanied by all associated warranties,conditions,limitations,and notices.TI is not responsible or liable for such altered rmation of third parties may be subject to additional restrictions.Resale of TI components or services with statements different from or beyond the parameters stated by TI for that component or service voids all express and any implied warranties for the associated TI component or service and is an unfair and deceptive business practice. TI is not responsible or liable for any such statements.Buyer acknowledges and agrees that it is solely responsible for compliance with all legal,regulatory and safety-related requirements concerning its products,and any use of TI components in its applications,notwithstanding any applications-related information or support that may be provided by TI.Buyer represents and agrees that it has all the necessary expertise to create and implement safeguards which anticipate dangerous consequences of failures,monitor failures and their consequences,lessen the likelihood of failures that might cause harm and take appropriate remedial actions.Buyer will fully indemnify TI and its representatives against any damages arising out of the use of any TI components in safety-critical applications.In some cases,TI components may be promoted specifically to facilitate safety-related applications.With such components,TI’s goal is to help enable customers to design and create their own end-product solutions that meet applicable functional safety standards and requirements.Nonetheless,such components are subject to these terms.No TI components are authorized for use in FDA Class III(or similar life-critical medical equipment)unless authorized officers of the parties have executed a special agreement specifically governing such use.Only those TI components which TI has specifically designated as military grade or“enhanced plastic”are designed and intended for use in military/aerospace applications or environments.Buyer acknowledges and agrees that any military or aerospace use of TI components which have not been so designated is solely at the Buyer's risk,and that Buyer is solely responsible for compliance with all legal and regulatory requirements in connection with such use.TI has specifically designated certain components as meeting ISO/TS16949requirements,mainly for automotive use.In any case of use of non-designated products,TI will not be responsible for any failure to meet ISO/TS16949.Products ApplicationsAudio /audio Automotive and Transportation /automotiveAmplifiers Communications and Telecom /communicationsData Converters Computers and Peripherals /computersDLP®Products Consumer Electronics /consumer-appsDSP Energy and Lighting /energyClocks and Timers /clocks Industrial /industrialInterface Medical /medicalLogic Security /securityPower Mgmt Space,Avionics and Defense /space-avionics-defense Microcontrollers Video and Imaging /videoRFID OMAP Applications Processors /omap TI E2E Community Wireless Connectivity /wirelessconnectivityMailing Address:Texas Instruments,Post Office Box655303,Dallas,Texas75265Copyright©2015,Texas Instruments IncorporatedMSP430is a trademark of Texas Instruments.Bluetooth is a registered trademark of Bluetooth SIG.。

EC600N_核心定位板”域”规格说明及使用指导手册EC600N_核心板“域”规格说明及使用指导手册日期：2021-08-18创建人：Bruce《EC600N_核心定位板“域”规格说明及使用指导手册》(以下简称本手册) 仅适用于使用移远CAT1 模组EC600系列进行二次layout的核心板，本手册不代表移远公司的任何立场以及观点，若由本手册指导而误操作产生的任何损失，与移远模组产品无关。

声明 (1)1、关于本文档 (3)1.1、修订历史 (3)2、核心板“域”规格 (4)2.1、外观尺寸 (4)2.2、器件型号 (4)2.3、电器特征 (4)2.4、“域”核心板引脚分配 (4)2.5、插针定义描述 (5)3、天线连接器要求 (6)4、机械尺寸和包装 (7)4.1、机械尺寸 (7)4.2、包装 (7)5、注意事项 (8)5.1、关于供电 (8)5.2、关于USB_BOOT (8)5.3、关于无法开机 (8)5.4、关于USB供电 (8)附录 (9)--相关原理图 (9)1、关于本文档1.1、修订历史版本修订人日期修订内容V1.0 Bruce 2021-07-03 创建文件V1.1 Bruce2021-08-18更新引脚定义V1.2 Bruce2021-09-26更新原理图2、核心板“域”规格2.1、外观尺寸（上图仅供参考，实际外观请参照实物）其中贴有EC600N 模块和天线连接器为正面，另一面为反面。

尺寸：长*宽3.0cm*3.0cm外观：绿油白字。

2.2、器件型号主模块：移远EC600NIPEX天线：村田一代射频座SIM卡座：Nano SIM 6 PIN插拔式卡座GNSS：L76K2.3、电器特征供电范围：5V-16V串口电平：3.3V2.4、“域”核心板引脚分配下图给出了EC600N“域”核心板插针引脚分配。

EC600N “域”核心板插针是标准的2.54mm 排针，下表给出了模块对应的20-pin 引脚功能定义及说明。