| Electronic Components Datasheet Search |
|
LTC6820 Datasheet(PDF) 34 Page - Analog Devices |
|
|
|||||||||||||||||||||||||||||
LTC6820 Datasheet(HTML) 34 Page - Analog Devices |
|
34 / 80 page ![]() LTC2949 34 Rev A For more information www.analog.com Commands Compatible with LTC68xx Cell Monitors (RDCV, ADCV) The LTC2949 supports several RDCV and ADCV style commands compatible with LTC68xx Cell Monitors. RDCVA-RDCVF,RDAUXA-RDAUXD,RDCFGA,RDCFGB(all referred as RDCV commands in this document), ADCV, ADOW, ADOL, ADAX, ADAXD, ADCVAX and ADCVSC (all referred as ADCV commands in this document) are sup- portedasbroadcastandaddressedcommands.Addressed commands are used to address LTC2949 exclusively. To trigger actions on LTC2949 and LTC68xx Cell Monitors simultaneously, broadcast commands are used. This is for example useful to initiating ADC conversions of several devices at the same time. No matter if LTC2949 is con- nected parallel to or on top of a daisy chain, addressed ADCV commands can trigger measurements on LTC2949 only and broadcast ADCV commands can perform syn- chronous ADC conversions on all devices connected to the SPI / isoSPI bus. The conversion starts at the end of the PEC for all devices. In cases where LTC2949 is connected parallel to a daisy chain, direct read commands (DCMD) must be used to read register data and addressed RDCV commands (with RDCVCONF=1) must be used to read the last fast conversion results. If LTC2949 is connected on top of a daisy chain, broadcast RDCV commands must be used to read register data (RDCVCONF=0) or to read the last fast conversion results (RDCVCONF=1) depending on setting of REGSCTRL.RDCVCONF. Write to LTC2949’s register map is always done with direct write commands (DCMD) independent of the bus topology. See Table 10 (Communication with LTC2949) for a summary of all possible communication scenarios. Before LTC2949 can react on ADCV commands it must be runninginslowcontinuousmeasurementmode(bitCONT in OPCTRL), at least one fast measurement channel must be selected via the Fast Control Register (FACTRL) and optionally, to make also fast BAT conversions via one of the power ADCs (P1 or P2 in voltage mode), P1ASV and/ or P2ASV in the ADC configuration register (ADCCONF) must be set. If LTC2949 is running in fast continuous mode (FACONV=1) any ADCV command is ignored and SERIAL INTERFACES acquired samples can be read from the FIFO registers (FI- FOI1, FIFOI2, FIFOBAT, FIFOAUX). Still, also in this mode, it is possible to read the last fast conversion results via RDCV(RDCVCONF=1).Iffastcontinuousmodeisdisabled (FACONV=0), any ADCV command will clear all FIFOs. If needed, samples within FIFOs should be read before sending an ADCV command while FACONV is cleared. In the configuration where LTC2949 is on top of a daisy chain, after a broadcast RDCV command, the stacked LTC68xxCellMonitorsturnintoacascadedshiftregister,in whichdataisshiftedthrougheachdevicetothenextdevice in the stack. In this scenario, LTC2949 responds to RDCV commands only if the Broadcast Read Enable bit (BCREN) in the Register Control Register (REGSCTRL) is set. In the scenario where LTC2949 is placed in parallel to a daisy chain of LTC68xx Cell Monitors, the bit BCREN must be cleared (default) to avoid bus collisions. Still, any broadcast RDCV may clear LTC2949's internal HS byte (see below) if the bit RDCVCONF is set, no matter if BCREN is set or not. For this reason, it is recommended to read LTC2949’s fast conversion results before reading from the LTC68xx Cell Monitors. Or, if for software tim- ing reasons it is necessary to read from the LTC68xx Cell Monitors first, the bit RDCVCONF must be cleared before (it must be set again afterwards to read fast conversion data from LTC2949). The last results of any fast conversion can be read out by the RDCV command, providing sequentially the results of I1, I2, BAT and AUX (least significant bytes first to be compatible with LTC68xx Cell Monitors) followed by one or more hand shake (HS) bytes, indicating if the data is new (0x0F) or old (0x00). Once LTC2949 sends the HS byte, it will continue sending it as long as the master is reading bytes. Still, a PEC will always be send for every 6 data bytes. Per transaction, the HS byte may only change from 0x00 to 0x0F, once it is 0x0F it won’t change. This allows the master to poll for conversion results being ready by checking for a transition of the HS byte from 0x00 to 0x0F. If the first HS byte is 0x0F the conversion data received with that command is already new and valid. If the first HS byte is 0x00 the data received in the same transaction was not yet updated. A subsequent RDCV |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |