View ACT3492_1112072.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

eroflex circuit t echnology ? data bus modules for the future ? scd3492 rev b 6/26/01 features dual low power monolithic bus tranceivers performs the complete dual-redundant remote terminal, bus controller protocol and passive monitor functions of mil-std-1553b automated self-test functions allows setting of the message error bit on illegal commands provides programmable control over terminal flag and subsystem flag status bits mil-prf-38534 compliant circuits available 250 mw typical power consumption small size available in ceramic plug-in package configuration 5v dc operation full military (-55c to +125c) temperature range desc smd# pending 1 general description the ACT3492 series is a monolithic implementation of the mil-std-1553b bus controller, remote terminal and passive monitor functions including dual low power bus tranceivers. all protocol functions of mil-std-1553b are incorporated and a number of options are included to improve flexibility. these features include programmi ng of the status word, illegalizing specific commands and an independent loop back self-test which is initiated by the subsystem. this unit is directly compatible with all microprocessor interfaces such as the ct1611 and ct1800 produced by aeroflex incorporated. encoder decoder "o" decoder "1" driver select & enable bus "0" bus "1" t/r hybrid t/r hybrid internal highway control interface unit program sub address & word count outputs discrete outputs control inputs terminal address inputs block diagram (with transformers) ACT3492 mil-std-1553b remote terminal, bus controller, or passive monitor hybrid with status word control ACT3492 series inputs status word control circuit technology www.aeroflex.com asic asic asic dual low power monolithic bus tranceivers
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 2 electrical performance characteristics absolute maximum ratings parameter min max units v cc -0.3 7.0 v input or output voltage at any pin -0.3 v cc + 0.3v v storage case temperature -65 +150 c load temperature (soldering 10 sec) +300 c digital protocol logic characteristics (over full temperature range) parameter test conditions min typ max unit notes v cc (logic) 4.5 5.0 5.5 v v ih vcc = 5.0v 2.2 v v il vcc = 5.0v 0.7 v v oh high level output voltage vcc = 4.5v 2.4 v 1a v ol low level output voltage vcc = 4.5v 0.4 v 1a i ih high level input current vcc = 5.5v, v in = 2.7v -200 -25 -700 -400 a a 2a 3a i l low level input current vcc = 5.5v, v in = 0.4v -400 -25 -900 -400 a a 2a 3a i cc (logic) vcc = 5.5v 20 ma 4a notes: 1a /i ol = 3ma maximum, i oh = -2 ma maximum for all outputs and bidirectionals. 2a / rtad 0, 1, 2, 3, 4 and rtadpar only. 3a / all inputs and bidirectionals other than those in note 2. 4a / input clock (running) = 6mhz, all remaining inputs are open and all outputs and bidirectionals have no load.
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 3 absolute maximum ratings (analog tranceiver) parameter min max units v cc -0.3 7.0 v receiver differential voltage 10 vp-p v receiver common-mode voltage -5.0 +5.0 vdc driver peak output current 800 ma analog transceiver recommended operating conditions parameter min max unit notes v cc (logic) 4.75 5.5 v receiver differential voltage (see point a figure 4) 4.0 vp-p receiver common-mode voltage (see figure 4) -1.75 +5 vdc driver peak output current 700 ma serial data rate 1.0 mhz case operating temperature -55 +125 c analog transceiver characteristics (over full temperature range) parameter min max unit notes differential input level -8 +8 vp-p 1,3 input common-mode voltage -1.75 +5 v 1,3 threshold voltage 0.6 1.1 v 4
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 4 analog transceiver characteristics (over full temperature range) parameter symbol test conditions min max unit notes differential output voltage v o 35 ohm load, point a 70 ohm load, point c figure 4 6.0 18 9.0 26 vp-p vp-p 1 differential output noise v on inhibited figure 4, point a 10 mvp-p 3 terminal input impedance z in transmitter off 1 mhz sine wave as measured from the 1553 bus (direct coupled). figure 4 point a 2.0 k ? 1 differential offset voltage vos 35 ohm load, point a 70 ohm load, point c figure 4 90 250 mv mv 1, 3, 5 1,5 rise time t r 35 or 70 ohm load figure 4, points a,c 100 300 nsec 1 fall time t f 35 or 70 ohm load figure 4, points a,c 100 300 nsec 1 analog transceiver power supply characteristics (each channel) parameter symbol test conditions min max unit notes supply current i cc 1 standby 25 ma 1,2 i cc 2 25% duty cycle 160 ma 1,2 i cc 3 50% duty cycle 290 ma 1,2 i cc 4 100% duty cycle 550 ma 1,2,3 notes: 1 / vcc = 5.0 volts dc +/-0.1 volts dc unless otherwise specified. 2 / all specifications and limits are for a single channel with no connections made to the other channel. 3 / parameters shall be tested as part of device initial characterization and after design and process changes. parameter shall be guaranteed to limits specified in above tables for all lots not specifically tested. 4 / threshold determined by first no response to a receive 32 word command. 5 / measured 2.5sec after the mid-bit zero crossing of the last parity bit of a 660sec transmission.
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 5 remote terminal operation receive data operation all valid data words associated with a valid receive data command word for the rt are passed to the subsystem. the rt examines all command words from the bus and w ill respond to valid (i.e. correct manchester, parity coding etc.) commands which have the correct rt address (or broadcast address if the rt broadcast option is enabled). when the data words are received, they are decoded and checked by the rt and, if valid, passed to the subsystem on a word by word basis at 20 s intervals. this applies to receive data words in both bus controller to rt and rt to rt messages. when the rt detects that the message has finished, it checks that the correct number of words have been received and if the message is fully valid, then a good block received signal is sent to the subsystem, which must be used by the subsystem as permission to use the data just received. the subsystem must therefore have a temporary buffer store up to 32 words long into which these data words can be placed. the good block received signal will allow use of the buffer store data once the message has been validated. if a block of data is not validated, then good block received will not be generated. this may be caused by any sort of message error or by a new valid command for the rt being received on another bus to which the rt must switch. transmit data operation if the rt receives a valid transmit data command addressed to the rt, then the rt will request the data words from the subsystem for transmission on a word by word basis. to allow maximum time for the subsystem to collect each data word, the next word is requested by the rt as soon as the transmission of the current word has commenced. it is essential that the subsystem should provide all the data words requested by the rt once a transmit sequence has been accepted. failure to do so will be classed by the rt as a subsystem failure and reported as such to the bus controller. control of data transfers this section describes the detailed operation of the data transfer mechanism between the rt and subsystems. it covers the operations of the signals dtrq , dtak , iustb, h/l , gbr , nbgt , tx/rx during receive data and transmit data transfers. figures 29 and 30 show typical interfacing logic. figures 5 and 15 shows the operation of the data handshaking signals during a receive command with one data word. when the rt has fully checked the command word, nbgt is pulsed low, which can be used by the subsystem as an initialization signal. tx/rx will be set low indicating a receive command. when the first data word has been fully validated, dtrq is set low. the subsystem must then reply within approximately 1.5 s by setting dtak low. this indicates to the rt that the subsystem is ready to accept data. the data word is then passed to the subsystem on the internal highway ih08-ih715 in two bytes using iustb as a strobe signal and h/l as the byte indicator (high byte first followed by low byte). data is valid about both edges of iustb. signal timing for this handshaking is shown in figure 15. also see figures 19 and 20. if the subsystem does not declare itself busy, then it must respond to dtrq going low by setting dtak low within approximately 1.5 us. failure to do so will be classed by the rt as a sub system failure and reported as such to the bus controller. it should be noted that iustb is also used for internal working in the rt. dtrq being low should be used as an enable for clocking data to the subsystem with iustb. once the receive data block has finished and been checked by the rt, gbr is pulsed low if the block is entirely correct and valid. this is used by the subsystem as permission to make use of the data block. if no gbr signal is generated, then an error has been detected by the rt and the entire data block is invalid and no data words in it may be used. if the rt is receiving data in an rt to rt transfer, the data handshaking signals will operate in an identical
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 6 fashion but there will be a delay of approx 70 s between nbgt going low and dtrq first going low. figures 6 and 15 show the operation of the data handshaking signals during transmit command with one data word. as with the receive command discussed previously, nbgt is pulsed low if the command is valid and for the rt. tx/rx will be set high indicating a transmit data command. while the rt is transmitting its status word, it requests the first data word from the subsystem by setting dtrq low. the subsystem must then reply within approximately 13.5 s by setting dtak low. by setting dtak low, the subsystem is indicating that it has the data word ready to pass to the rt. once dtak is set low by the subsystem, dtrq should be used together with h/l and tx/rx to enable first the high byte and then the low byte of the data word onto the internal highway ih08-ih715. the rt will latch the data bytes during iustb, and will then return dtrq high. data for each byte must remain stable until iustb has returned low. signal timing for this handshaking is shown in figure 15. additional data information signals at the same time as data transfers take place, a number of information signals are made available to the subsystem. these are incmd , the subaddress lines sa0-sa4, the word count lines wc0-wc4 and current word count lines cwc0-cwc4. use of these signals is optional. incmd will go active low while the rt is servicing a valid command for the rt. the subaddress, transmit/receive bit, and word count from the command word are all made available to the subsystem as sa0-sa4, tx/rx and wc0-wc4 respectively. they may be sampled when incmd goes low and will remain valid while incmd is low. see figure 11. the subaddress is intended to be used by the subsystem as an address pointer for the data block. subaddress 0 and 31 are mode commands, and there can be no receive or transmit data blocks associated with these. (any data word associated with a mode command uses different handshaking operations. if the subsystem does not use all the subaddresses available, then some of the subaddress lines may be ignored. the tx/rx signal indicates the direction of data transfer across the rt - subsystem interface. its use is described in the previous section. the word count tells the subsystem the number of words to expect to receive or transmit in a message, up to 32 words. a word count of all 0s indicates a count of 32 words. the current word count is set to 0 at the beginning of a new message and is incremented following each data word transfer across the rt - subsystem interface. (it is clocked on the falling edge of the second iustb pulse in each word transfer). it should be noted that there is no need for the subsystem to compare the word count and current word count to validate the number of words in a message. this is done by the rt. subsystem use of status bits and mode commands general description use of the status bits and the mode commands is one of the most confusing aspects of mil-std-1553b. this is because much of their use is optional, and also because some involve only the rt while others involve both the rt and the subsystem. the ACT3492 allows full use to be made of all the status bits, and also implements all the mode commands. external programming of the terminal flag and subsystem flag bits plus setting of the message error bit on reception of an illegal command when externally decoded is available. the subsystem is given the opportunity to make use of status bits, and is only involved in mode commands which have a direct impact on the subsystem. the mode commands in which the subsystem may be involved are synchronize, sychronize with data word, transmit vector word, reset and dynamic bus control acceptance. the status bits to which the subsystem has access, or control are service request, busy, dynamic bus control acceptance, terminal flag, subsystem flag, and message error bit. operation of each of these mode commands and of the status bits is described in the following sections.
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 7 all other mode commands are serviced internally by the rt. the terminal flag and message error status bits and bit word contents are controlled by the rt; however the subsystem has the option to set the message error bit and to control the reset conditions for the terminal flag and subsystem flag bits in the status word, and the transmitter timeout, subsystem handshake, and loop test fail bits in the bit word. synchronize mode commands once the rt has validated the command word and checked for the correct address, the sync line is set low. the signal wc4 will be set low for a synchronize mode command, and high for a synchronize with data word mode command (see figure 9). in a synchronize with data word mode command, sync remains low during the time that the data word is received. once the data word has been validated, it is passed to the subsystem on the internal highway ih08-ih715 in two bytes using iustb as a strobe signal and h/l as the byte indicator (high byte first followed by low byte). sync being low should be used on the enable to allow iustb to clock synchronize mode data to the subsystem. if the subsystem does not need to implement either of these mode commands, the sync signal can be ignored, since the rt requires no response from the subsystem. transmit vector word mode command figures 8 and 17 illustrates the relevant signal timings for an rt receiving a valid transmit vector word mode command. the rt requests data by setting vecten low. the subsystem should use h/l to enable first the high byte and then the low byte of the vector word onto the internal highway ih08-ih715. it should be noted that the rt expects the vector word contents to be already prepared in a latch ready for enabling onto the internal highway when vecten goes low. if the subsystem has not been designed to handle the vector word mode command, it will be the fault of the bus controller if the rt receives such a command. since the subsystem is not required to acknowledge the mode command, the rt w ill not be affected in any way by vector word circuitry not being implemented in the subsystem. it will however transmit a data word as the vector word, but this word will have no meaning. reset mode command figure 7 shows the relevant signal timings for an rt receiving a valid reset mode command. once the command word has been fully validated and serviced, the reset signal is pulsed low. this signal may be used as a reset function for subsystem interface circuitry. dynamic bus allocation this mode command is intended for use with a terminal which has the capability of configuring itself into a bus controller on command from the bus. the line dbcreq (see figure 7) cannot go true unless the dbcacc line was true at the time of the valid command, i.e. tied low. for terminals acting only as rts, the signal dbcacc should be tied high (inactive), and the signal dbcreq should be ignored and left unconnected. use of the busy status bit the busy bit is used by the subsystem to indicate that it is not ready to handle data transfers either to or from the rt. the rt sets the bit to logic one if the busy line from the subsystem is active low at the time of the second falling edge of inclk after incmd goes low. this is shown in figures 14 and 20. once the busy bit is set, the rt will stop all receive and transmit data word transfers to and from the subsystem. the data transfers in the synchronize with data word and transmit vector word mode commands are not affected by the busy bit and will take place even if it has been set. it should be noted that a minimum of 0.5 s subaddress decoding time is given to the subsystem before setting of status bits. this allows the subsystem to selectively set the busy bit if for instance one
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 8 subaddress is busy but others are ready. this option will prove useful when an rt is interfacing with multiple subsystems. use of the service request status bit the service request bit is used by the subsystem to indicate to the bus controller that an asynchronous service is requested. the timing of the setting of this bit is the same as the busy bit and is shown in figures 14 and 20. use of servreq has no effect on the rt apart from setting the service request bit. it should be noted that certain mode commands require that the last status word be transmitted by the rt instead of the current one, and therefore a currently set status bit will not be seen by the bus controller. therefore the user is advised to hold servreq low until the requested service takes place. use of the subsystem status bit this status bit is used by the rt to indicate a subsystem fault condition. if the subsystem sets sserr low at any time, the subsystem fault condition in the rt w ill be set, and the subsystem flag status bit will subsequently be set. the fault condition will also be set if a handshaking failure takes place during a data transfer to or from the subsystem. the fault condition is cleared on power-up or by a reset mode command. dynamic bus control acceptance status bit dbcacc , when set true, enables an rt to configure itself into a bus controller, if the subsystem has the capability, by allowing dbcreq to pulse true and bit time 18 to be set in the status response. if dynamic bus control is not required then dbcacc must be tied high. dbcacc tied high inhibits dbcreq and clears bit time 18 in the status response. optional status word control message error bit the ACT3492 monitors all receptions for errors and sets the message error bit as prescribed in mil-std-1553b. the subsystem designer may, however, exercise the option of monitoring for illegal commands and forcing the message error bit to be set. the word count and subaddress lines for the current command are valid when incmd goes low. the subsystem must then determine whether or not the word count or subaddress is to be considered illegal by the rt. if either of them is considered illegal, the subsystem must produce a positive-going pulse called mereq. the positive-going edge of mereq must occur within 500 nsec of the falling edge of incmd . subsystem flag and terminal flag bits the conditions that cause the subsystem flag and terminal flag bits in the status word to be reset may be controlled by the subsystem using the enable , bit decode , next statu s, and status update inputs. if enable is inactive (high), then the terminal flag and subsystem flag behavior is the same as described below: (i.e. the other three option lines are disabled). subsystem flag bit this bit is reset to logic zero by a power up initialization or the servicing of a legal mode command to reset the remote terminal (code 01000). this bit shall be set in the current status register if the subsystem error line, sserr , from the subsystem ever goes active low. this bit shall also be set if an rt/subsystem handshaking failure occurs. this bit, once set, shall be repeatedly set until the detected error condition is known to be no longer present.
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 9 terminal flag bit this bit is reset to logic zero by a power up initialization or the servicing of a legal mode command to reset the remote terminal (code 01000). this bit can be set to logic one in the current status register in four possible ways: a) if the rx detects any message encoding or content error in the terminals transmission. a loop test failure, ltfail, will be signalled which shall cause the terminal flag to be set and the transmission aborted. b) if a transmitter timeout occurs while the terminal is transmitting. c) if a remote terminal self test fails. d) if there is a parity error in the hard wired address to the rx chip. this bit, once set, shall be repeatedly set until the detected error condition is known to be no longer present. the transmission of this bit as a logic one can be inhibited by a legal mode command to inhibit terminal flag bit (code 00110). similarly, this inhibit can be removed by a mode command to override inhibit terminal flag bit (code 00111), a power up initialization or a legal mode command to reset remote terminal (code 01000). if enable is held low, then the three options described below are available and are essentially independent. any, all, or none may be selected. also, reporting of faults by the subsystem requires that sserr be latched (not pulsed) low until the fault is cleared. resetting ssf and tf on receipt of valid commands if enable is selected and the other three option lines are held high, then the status word register will be reset on receipt of any valid command with the exception of transmit status and transmit last command. note that in this mode, the tf will never be seen in the status word, and the ssf will only be seen if sserr is latched low. also note that the ssf will not be seen in response to transmit status or transmit last command if the preceding status word was clear, regardless of actions taken on the sserr line after the clear status transmission. status register update at fault occurrence if status update is selected (held low), then the tf or ssf will appear in response to a transmit status or transmit last command issued as the first command after the fault occurs. any other command (except as noted in the preserving the bit word section) will reset the tf and ssf. repeated transmit status or transmit last command immediately following the fault will continue to show the tf and/or ssf in the status word. note that this behavior may not meet the "letter-of-the-spec" as described in mil-std-1553b, but is considered the "preferred" behavior by some users. tf and ssf reporting in the next status word after the fault if next status is selected (held low), then the tf or ssf will appear in response to the very next valid command after the fault except for transmit status or transmit last command. the flag(s) will be reset on receipt of any valid command following the status transmission with the flag(s) set except for transmit status, transmit last command, or as noted in the following section on preserving the bit word. preserving the bit word in order to preserve the transmitter timeout flag, subsystem handshake failure, and loop test failure bits in the bit word, it is necessary to select bit decode (hold it low). this will prevent resetting those bits if the transmit bit word mode command immediately follows the fault or follows a transmit last command or transmit status immediately following the fault. it will also prevent resetting the tf and ssf bits in the status word. any other valid commands will cause those bit word bits and the status word bits to be reset.
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 10 bus control operation to enable its use in a bus controller the asic has additional logic within it. this logic can be enabled by pulling the pin labelled rt/bc low. once the asic is in bus control mode, all data transfers must be initiated by the bus control processor correctly commanding the asic via the subsystem interface. in bus control mode six inputs are activated which in rt mode are inoperative and four signals with dual functions exercise the second function (the first being for the rt operation). to use the ACT3492 as a 1553b bus control interface, the bus control processor must be able to carry out four basic bus-related functions. two inputs, bcopa and bcopb allow these four options to be selected. the option is then initiated by sending a negative-going strobe on the bcopstb input. bcopstb must only be strobed low when ndrq is high. this is particularly important when two options are required during a single transfer.see figure 28 and table 1. with these options all message types and lengths can be handled. normal bc/rt exchanges are carried out in option zero. this is selected by setting bcopa and bcopb to a zero and strobing bcopstb . on receipt of the strobe, the ACT3492 loads the command word from an external latch using cwen and h/l. the command word is transmitted down the bus. the tx/rx bit is, however, considered as being its inverse and so if a transmit command is sent to a rt (figure 21), the ACT3492 in bc mode believes it has been given a receive command. as the rt returns the requested number of data words plus its status, the bc carries out a full validation check and passes the data into the subsystem using dtrq , dtak , h/l , iustb and cwc as in rt operation. it also supplies gbr at the end of a valid transmission. conversely, a receive command sent down the bus is interpreted by the bc as a transmit command, and so the requisite data words are added to the command word. see figure 22. for mode commands, where a single command word is required, option one is selected by strobing bcopstb when bcopa is high and bcopb is low. on receiving the strobe, the command word is loaded from the external latch using cwen and h/l , the correct sync and parity bits are added and the word transmitted (see figure 23). mode commands followed by a data word requires option two. option two, selected by strobing bcopstb while bcopa is low and bcopb is high, loads a data word via dwen and h/l , adds sync and parity and transmits them to the bus (see figure 25). if the mode code transmitted required the rt to return a data word, then selecting option three by strobing bcopstb when bcopa and bcopb are both high will identify that data word and if validated, output it to the sub system interface using rmdstb and h/l. this allows data words resulting from mode codes to be identified differently from ordinary data words and routed accordingly (see figure 24). all received status words are output to the subsystem interface using statstb and h/l . in bc option three, if the signal pasmon is active, then all data appearing on the selected bus is output to the subsystem using statstb for command and status words or rmdstb for data words. see passive monitor. rt to rt transfers require the transmission of two command words. a receive command to one rt is contiguously followed by a transmit command to the other rt. this can be achieved by selecting option one followed by option zero for the second command. the strobe (bcopstb ) for option zero must be delayed until ndrq has gone low and returned high following the strobe for option one. the rt transmissions are checked and transferred in the subsystem interface to the bus control processor (see figure 26). bc must wait for rto to pulse before issuing subsequent messages. passive monitor the monitor mode may be utilized to analyze or collect all activities which occur on a selected bus. this is initiated by selecting a bus, placing the unit in bc option three and setting pasmon low. all data appearing on the selected bus is output to the subsystem using statstb for command and status words or rmdstb for data words. see figure 27. automated self-test the ACT3492 has been designed to fully support a wrap-around self-test which ensures a high degree of
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 11 fault coverage. the monolithic circuit includes all circuitry required to perform the self-test. self-test can be an on-line or off-line function which is initiated by simple subsystem intervention. the drvinh signal selects on-line or off-line testing. the circuit accomplishes the on-line test without accessing the mil-std-1553 data bus by providing an internal data path which connects the encoder circuitry directly to the decoder circuitry. the transceiver is inhibited during this on-line test. the off-line test is designed to include the transceiver as well as the protocol device. this mode will generally be useful as an off-line card test where no live bus is in use. to initiate the self-test a word is placed in the vector word latch, loop test enable (lten ) is held low, and the loop test trigger (lttrig ) signal is pulsed low. the primary bus will be tested with the word that resides in the vector word latch, encoded then looped back, decoded and presented to the subsystem as a normal data transfer would be accomplished. the secondary bus is sequentially tested after the primary bus is completed via request bus a (reqbusa) utilizing the same word residing in the vector word latch. upon completion of each test, pass/fail signals will be asserted reporting the results of the test. this test implementation verifies mil-std-1553 protocol compliance; proper sync character, 16 data bits, manchester ii coding, odd parity, contiguous word checking and a bit by bit comparison of the transmitted data. the self-test circuitry increases the fault coverage by insuring that the internal function blocks; encoder, decoder, and internal control circuitry are operating correctly. an effective data pattern to accomplish this is hex aa55 since each bit is toggled, (8 bit internal highway) on a high/low byte basis. the total time required to complete the self-test cycle is 89 microseconds. the loop test enable signal must remain in the low state throughout the diagnostic cycle.
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 12 pin description signal direction pin signal description rtad 0-4 input k6,k5 j5,h5 f4 rt address lines - these should be hardwired by the user. rtad4 is the most significant bit. rtadpar input j6 rt address parity line - this must be hardwired by the user to give odd parity. bit decode input j4 bitword decode - when held low, prevents resetting txto bit, hsfail bit, and ltfail bit in the bit word (as well as tf and ssf bits in the status word) upon receipt of a transmit bit word mode command. bcsten 1 input f5 broadcast command enable bus 1 - when low the recognition of broadcast command is prevented on bus 1. bcsten 0 input g5 broadcast command enable bus 0 - when low the recognition of broadcast command is prevented on bus 0. 6mck (clock) input e4 6 megahertz master clock. ih 08 (lsb) ih 19 ih 210 ih 311 ih 412 ih 513 ih614 ih715 (msb) bidir e9 d6 d7 a9 d8 b9 d9 c9 internal highway - bi-directional 8 bit highway on which 16 bit words are passed in two bytes. ih 715 is the most significant bit of each byte, the most significant byte being transferred first. the highway should only be driven by the subsystem when data is to be transferred to the rt. dtrq output k10 data transfer request - goes low to request a data transfer between the asic and subsystem. goes high at the end of the transfer. dtak input f6 data transfer acknowledge - goes low to indicate that the subsystem is ready for the data transfer. iustb output g6 interface unit strobe - this is a double pulse strobe used to transfer the two bytes of data h/l output j9 high/low - indicates which byte of data is on the internal highway. logic level "0" for least significant byte. gbr output j7 good block received - pulses low for 500ns when a block of data has been received by the asic and has passed all the validity and error checks. nbgt output g9 new bus grant - pulses low whenever a new command is accepted by the asic. mereq input e8 message error request - positive-going edge will cause message error bit in status word to be set.
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 13 tx/rx output h10 transmit/receive - the state of this line informs the subsystem whether it is to transmit or receive data. the signal is valid while incmd is low. incmd output k9 in command - goes low when the rt is servicing a valid command. the subaddress and word count lines are valid while the signal is low. wc0-wc4 output b7,c8 a6,b6 a4 word count - these five lines specify the requested number of data words to be received or transmitted. valid when incmd is low. sa0-sa4 output j10,k8 h7,k3 h2 sub address - these five lines are a label for the data being transferred. valid when incmd is low. cwc0-cwc4 output h4,h8 k4,j8 k1 current word count - these five lines define which data word in the message is currently being transferred. sync output g7 synchronize - goes low when a synchronize mode code is being serviced. vecten /dwen output g8 vector word enable/dataword enable - in the rt mode, this signal is provided to enable the contents of the vector word latch (which is situated in the subsystem) onto the asic?s internal highway. this signal, when in the bus controller mode, is used to enable mode code data from the subsystem onto the internal highway. reset output c4 reset - this line pulses low for 500ns on completion of the ser- vicing of a valid and legal mode command to reset remote ter- minal. sserr input a5 subsystem error - by taking this line low, the subsystem can set the subsystem flag in the status word. busy input c7 busy - this signal should be driven low if the subsystem is not ready to perform a data transfer to or from the asic. servreq input a3 service request - this signal should be driven low to request an asynchronous transfer and left low until the transfer has taken place. inclk output g10 internal clock (2 mhz) - this is made available for synchronization use by the subsystem if required. however, many of the outputs to the subsystem are asynchronous. eot output h9 end of transmission - goes low if a valid sync plus two data bits do not appear in time to be contiguous with preceding word. rtader output a1 remote terminal address error - this line goes low if an error is detected in the rt address parity of the selected receiver. any receiver detecting an error in the rt address will turn itself off. pin description (cont.) signal direction pin signal description
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 14 hsfail output b5 handshake failure - this line pulses low if the allowable time for dtak response has been exceeded during the asic/subsystem data transfer handshaking. lstcmd /cwen output d5 last command/command word enable - this line pulses low when servicing a valid and legal mode command to transmit last command. when in rt mode this line must not be used to enable data from the subsystem. this line also pulses low, when in the bus control mode, when a command word is required for transmission. staten / statstb output k7 status enable/status strobe - this line pulses low to enable the status word onto the internal highway for transmission. when in rt mode this line must not be used to enable data from the subsystem. this line also pulses high, when in the bus control mode, to strobe received status words into the subsystem. when pasmon is true this line pulses high for command and status words. stat update input e6 status update - when held low, causes tf or ssf to appear in status word response to transmit status or transmit last com- mand issued immediately after fault occurrence biten / rmdstb output c6 built in test enable/receive mode data strobe - this line pulses low when servicing a valid and legal mode command to transmit the internal bit word. this signal is for information only and must not be used to enable data from the subsystem. this line also pulses high when in the bus control mode when mode data is received to be passed to the subsystem and when data is passed to the subsystem during pasmon . dwsync output g3 data word sync - this line goes low if a data word sync and two manchester biphase bits are valid. enable input e7 enable - when held low, enables bit decode, next status, and status update program lines. cmsync output g4 command word sync - this line goes low if a command word sync and two manchester biphase bits are valid. ndrq output d10 no data required - this line goes low if the encoder transmit buffer is full i.e. another word is going to be transmitted. this signal is for information only and must not be used to enable data from the subsystem. next stat input a10 next status - when held low, causes tf or ssf to appear in very next status word after fault occurrence (except for transmit status or transmit last command). master reset input b8 master reset - a logic low on this input (100 nsec minimum) will reset the interface. pin description (cont.) signal direction pin signal description
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 15 pa s m o n input f8 passive monitor - when functioning as a bus controller this line acts as a passive monitor select. the active going edge of this line will cause the reqbus lines to be latched and that bus, now selected will be monitored so long as pasmon remains low. all traffic on the bus will be handed, after validation, to the subsystem via statstb for status and commands words, and rmdstb for data words. bcopstb input f7 bus controller operation strobe - when functioning as a bus controller a low going pulse on this line will initiate the selected bus controller operation on the requested bus, using bcopa&b and reqbusa&b. bcopa input b10 bus control operation a - least significant bit of the bus controller operation select lines. bcopb input c10 bus control operation b - most significant bit of the bus controller operation select lines. reqbus a bidir e5 request bus a - this line, when in rt mode, is the least significant bit of the bus request lines which specify the origin of the command, i.e. they are sources. when in bc mode these lines are sinks and specify which bus is to be used for the next command. reqbus b bidir h6 request bus b - most significant bit of the bus request lines. (see above for description.) rt/bc input b4 remote terminal/bus control - this line when high causes the asic to function as a remote terminal. when low the asic functions as a bus controller or passive monitor. dbcacc input b3 dynamic bus control accept - this line should be permanently tied low if a subsystem is able to accept control of the bus if offered. lt fa i l output e2 loop test fail - this line goes low if any error in the transmitted waveform is detected or if any parity error in the hardwired rt address is detected. error output f2 error - this line latches low if a manchester or parity error is detected. it is reset by the next cmsync (rt mode) and also by rto in the bc mode. rto output f3 reply time out - this signal will pulse low whenever the reply time for a transmitting terminal has been exceeded. this line is intended for the bus controller use. txto output c3 transmitter time ou t - this line latches low if the transmitter time out limits are exceeded. pa r e r output d3 parity error - this line will pulse low if a parity error is detected by the decoder. pin description (cont.) signal direction pin signal description
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 16 maner output e3 manchester error - this line will pulse low if a manchester error is detected by the decoder. dbcreq output c5 dynamic bus control request - this line will pulse low when the status reply for a mode code dynamic bus control has finished where the accept bit was set. vald output c2 valid data - this line will pulse low when a valid data word is received. drvinh input h3 driver inhibit - selects on-line or off-line testing during automated self test. when high self test is on-line. must be high when lten is high. lt e n input a7 loop test enable - enables automated self-test when low. normally high. lttrig input a8 loop test trigger - when pulsed low while lten is low automated self-test is initiated. lten pulse width should be 100ns < pw < 5s. tx/rx a1 tx/rx a2 bidir b2 b1 bus a transmit/receive - high output to the primary side of the coupling transformer that connects to the a channel of the 1553 bus. tx/ rx a1 tx/ rx a2 bidir d2 d1 bus a transmit/receive - low output to the primary side of the coupling transformer that connects to the a channel of the 1553 bus. tx/rx b1 tx/rx b2 bidir g1 g2 bus b transmit/receive - high output to the primary side of the coupling transformer that connects to the b channel of the 1553 bus. tx/ rx b1 tx/ rx b2 bidir j1 j2 bus b transmit/receive - low output to the primary side of the coupling transformer that connects to the b channel of the 1553 bus. +5vaa +5vab power e1 a2 +5v input power supply connection for the a channel tranceiver +5vba +5vbb power k2 f1 +5v input power supply connection for the b channel tranceiver +5vlogic power e10 +5v input power supply connection for the digital protocol section. gnd a power c1 power supply return for the a channel tranceiver. gnd b power h1 power supply return for the b channel tranceiver. diggnd 1 diggnd 2 power f9 f10 power supply return for the digital protocol section. case connected to diggnd1 and diggnd2 pin description (cont.) signal direction pin signal description
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 17 next controller to rt transfer receive command data word data word . . . . data word . . status word command word rt to controller tran sfe r next transmit command . . status word data word data word . . . . data word command word next rt to rt tran sfe r receive command tr a n s m i t command . . status word data word data word . . . . data word . . status word command word mode com- mand with- out data word next mode command . . status word command word mode com- mand with data word (transmit) next mode command . . status word data word command word mode com- mand with data word (receive) next mode command data word . . status word command word note: = intermessage gap . . = response time figure 1 ? typical message formats t/r bit mode code function associated data word broadcast command allowed 1 00000 dynamic bus control no no 1 00001 synchronize no yes 1 00010 transmit status word no no 1 00011 initiate self test no yes 1 00100 transmitter shutdown no yes 1 00101 override transmitter shutdown no yes 1 00110 inhibit terminal flag bit no yes 1 00111 override lnhibit terminal flag bit no yes 1 01000 reset remote terminal no yes 1 01001 reserved no tbd 1 01111 reserved no tbd 1 10000 transmit vector word yes no 0 10001 synchronize yes yes 1 10010 transmit last command yes no 1 10011 transmit bltword yes no 0 10100 selected transmitter shutdown yes yes 0 10101 override selected transmitter shutdown ye s ye s 1 or 0 10110 reserved yes tbd 1 or 0 11111 reserved yes tbd figure 2 ? assigned mode codes
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 18 bit times 1234567891011121314151617181920 command word 515 5 1 sync remote terminal address t/r subaddress/mode data word count/mode code p data word 16 1 sync data p 1 lsb 20 bit word 1514131211109876543210 p sync status word 5 111 3 11111 1 sync remote terminal address reserved note: t/r ? transmit/receive p ? parity transmitter timeout on bus 3 transmitter timeout on bus 2 transmitter timeout on bus 1 transmitter timeout on bus 0 bus 3 shutdown bus 2 shutdown bus 1 shutdown bus 0 shutdown broadcast transmit data received word count high word count low illegal mode command mode t/r bit wrong loop test failure subsystem handshake failure transmitter timeout flag message error instrumentation service request broadcast command received busy subsystem flag dynamic bus control acceptance terminal flag parity figure 3 ? word formats
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 19 1 : 2.12 55 ? notes: 55 ? 1 : 1.5 tx/rx 55 ? 55 ? 1 : 1.41 transformer coupled stubs direct coupled stubs c b zoi v cmt = 10 v pk zoi a a 1. point c, vo = 18 vpp minimum tx/rx tx/rx tx/rx 70 ? 35 ? 35 ? 2. transformer self impedance 3k ? at 1mhz 3. v cmt for transformer coupled stubs v cmd for direct coupled stubs v cmd dc to 2mh z stub isolation stub + - figure 4 ? tranceiver signal points
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 20 data status previous value previous value previous value previous value val id valid cwc = 00000 sa 3-4 sa 0-2 wc 0-4 cwc 0-4 tx/rx ih 08-715 dtrq ndrq vald nbgt staten iustb incmd h/l rto reqbus b reqbus a dwsync eot cmsync valid previous value gbr figure 5 ? rt receive 1 word (non mode) cwc = 00001 mid-sync mid-parity tresp td1 td1 mid-sync mid-sync td2 pw1 point a fig 4 cmd 16 data bits p data 16 data bits p stat 16 data bits p 3-state with pullup command hl hl hl (request bus 1) dtak = 0
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 21 data status previous value previous value previous value previous value valid val id cwc = 00000 sa 3-4 sa 0-2 wc 0-4 cwc 0-4 tx/rx ih 08-715 ndrq dtrq nbgt staten iustb incmd h/l rto reqbus b reqbus a dwsync eot cmsync valid previous value figure 6 ? rt transmit 1 word (non mode) cwc = 00001 mid-sync mid-parity tresp td1 mid-sync mid-parity td2 pw2 pw1 td1 pw1 3-state with pullup command hl hl hl cmd 16 data bits p data 16 data bits p stat 16 data bits p point a fig 4 dtak = 0
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 22 figure 7 ? rt transmit mode (no data) during ?sync no data? during ?reset remote terminal? td2 command status previous value 3-state with pullup previous value previous value previous value previous value val id valid valid cwc = 00000 sa 3-4 sa 0-2 wc 0-4 cwc 0-4 tx/rx ih 08-715 staten ndrq sync nbgt incmd iustb reset h/l rto reqbus b reqbus a dbcreq eot cmsync if dbcacc = 0 mid-parity td1 pw1 mid-sync mid-parity pw1 tresp hl hl stat 16 data bits p cmd 16 data bits p point a fig 4 (request bus 1)
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 23 data previous value previous value previous value previous value val id val id cwc = 00000 sa 3-4 sa 0-2 wc 0-4 cwc 0-4 tx/rx ih 08-715 biten ndrq vecten nbgt staten iustb incmd h/l rto reqbus b reqbus a dwsync eot cmsync active during ?transmit bit word? input during ?transmit vector? only active during ?transmit last command? val id previous value lstcmd figure 8 ? rt transmit mode (with data) mid-sync mid-parity tresp 3-state with pullup command hl hl hl status cmd 16 data bits p stat 16 data bits p data 16 data bits p point a fig 4 (request bus 0)
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 24 figure 9 ? rt receive mode (with data ) pw1 data status previous value 3-state with pullup previous value previous value previous value previous value val id val id val id cwc = 00000 sa 3-4 sa 0-2 wc 0-4 cwc 0-4 tx/rx ih 08-715 sync ndrq vald nbgt staten iustb incmd h/l rto reqbus b reqbus a dwsync eot cmsync command td1 mid-sync mid-parity tresp cmd 16 data bits p data 16 data bit s p stat 16 data bits p point a fig 4 hl hl hl (request bus 0)
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 25 figure 10 ? rt rt to rt transfer l 3 state with pullup h l h l h previous value valid previous value valid previous value valid gbr tx/rx dwsync cmsync eot rto nbgt ndrq dtrq dtak h/l iustb staten incmd sa(4:0) wc(4:0) cwc(4:0) reqbusa reqbusb ih(7:0) cmd1 16 data bits p fig 4 point a 4 to 12 s cmd2 16 data bits p stat2 16 data bits p tresp data 16 data bits p stat1 16 data bits p
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 26 figure 11 ? command word transfer (all) command iustb h/l incmd reqbus a reqbus b nbgt mid parity ? command word 1553 bus tdsulow pw2 data bits p td1 td2 pw1 td3 td4 cwc = 00000 previous state previous state previous state valid valid valid valid previous state previous state wc0?wc4 sa3?sa4 tx/rx cwc0?cwc4 sa0?sa2 ih08?715 lo hi 3 state with pullup pw2 tdhldhi td6 tdhldlo tdsuhi td5 td5 data word when required
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 27 figure 12 ? rt transmit command service (non-mode) figure 13 ? rt receive command service (non-mode) tx/rx cwc0?cwc4 ih08?715 iustb h/l incmd dtrq ndrq staten gbr cwc0?cwc4 ih08?715 iustb h/l incmd dtrq ndrq staten vald rx data 3 state with pullup low hi cwc = cwc + 1 cwc low hi status pw1 tied to dtak cwc = 00001 cwc = 00000 previous state command status tx data 3 state with pullup previous state low hi low hi low hi tdsulo tdsuhi td2 td3 td1 td4 pw1 td5 tdhldlo tied to dtak td1
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 28 sa4-sa0 nbgt 1.5s minimum valid valid valid previous command value previous command value previous command value busy latched here tx/rx wc4-wc0 cwc4-cwc0 incmd inclk figure 14 ? new command initialization
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 29 figure 15 ? data handshake transmit / receive cwc3-cwc4 ih08-ih715 cwc cwc=cwc+1 rx data l h iustb h/l h/l ih08-ih715 cwc3-cwc4 iustb dtak dtrq tdhs rx data cwc cwc=cwc+1 tdhshld transmit receive td1 tdsuhi tdhldhi tdhldlo tdsulo l h td2 tdsuhi tdhldhi tdhldlo tdsulo td1 td2
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 30 low hi low hi figure 16 ? rt transmit mode service (no data) incmd sync ndrq h/l iustb tx/rx cwc0-cwc4 staten command status previous state previous state 3 state with pullup cwc = 00000 td1 ih08-715 pw2 td2 pw1
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 31 incmd vecten ndrq staten h/l tx/rx iustb ih08-715 cwc0-cwc4 previous state previous state 3 state with pullup command status cwc = 00000 hi low low figure 18 ? rt receive mode service (with data) biten lstcmd incmd va ld sync h/l iustb ih08-715 3 state with pullup mode data status hi low hi low ndrq staten figure 17 ? rt transmit mode service (with data) td1 td4 pw1 pw2 td3 mode data hi low td2 hi tdsuhi tdhldhi tdhldlo tdsulo hi td3 td1 td2 tdsuhi tdhldhi tdsulo tdhldlo
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 32 parametrics test conditions: vcc = +5v 10%, vss = 0, r l ( pull - up ) = 1.6k ?, r l ( pull - down ) = 5k ?, c l = 20 pf (including test jig)} transmit (non mode) (see figure 6) symbol limits min max units tresp 10.5 11.75 s pw1 275 550 ns pw2 475 525 ns td1 6.5 7.0 s td2 18.5 19 s transmit command service (non mode) (see figure 12) symbol limits min max units pw1 1.4 1.6 s td1 6.7 6.9 s td2 10 75 ns td3 225 275 ns td4 1.7 1.8 s td5 700 800 ns receive (non mode) (see figure 5) symbol limits min max units tresp 9.0 10 s pw1 875 1325 ns td1 3.65 3.95 s td2 2.8 3.5 s receive command (non mode) service (see figure 13) symbol limits min max units pw1 400 600 ns td1 700 800 ns
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 33 command word transfer (all) (see figure 11) symbol limits min max units pw1 475 525 ns pw2 225 275 ns td1 3.0 3.4 s td2 275 350 ns td3 50 500 ns td4 450 550 ns td5 - 75 ns td6 50 - ns tdsuhi 400 - ns tdhldhi 150 - ns tdsulo 400 - ns tdhldlo 150 - ns transmit mode (with data) (see figure 8) symbol limits min max units tresp 9.5 10.5 s data handshake (see figure 15) symbol limits min max units transmit tdhs (tx) 0 13.5 s tdhshld 750 - ns tdsuhi 25 - ns tdhldhi 25 - ns tdsulo 25 - ns tdhldlo 25 - ns td1 675 800 ns td2 50 - ns receive tdhs (rx) 0 1.5 s tdhshld 750 - ns tdsuhi 400 - ns tdhldhi 150 - ns tdsulo 400 - ns tdhldlo 150 - ns td1 675 800 ns td2 50 - ns receive mode (with data) (see figure 9) symbol limits min max units tresp 9.0 10 s pw1 21.75 23.0 s td1 200 300 ns
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 34 transmit mode service (with data) (see figure 17) symbol limits min max units pw1 1.4 1.6 s pw2 1.4 1.6 s td1 6.2 6.3 s td2 400 600 ns td3 10 - s td4 700 800 ns tdsuhi - 100 ns tdhldhi 0 - ns tdsulo - 100 ns tdhldlo 0 - ns transmit mode (no data) (see figure 7) symbol limits min max units tresp 9.5 11 s pw1 400 600 ns td1 600 1000 ns td2 150 275 ns receive mode service (with data) (see figure 18) symbol limits min max units td1 725 825 ns td2 680 760 ns td3 375 825 ns tdsuhi 400 - ns tdhldhi 150 - ns tdsulo 400 - ns tdhldlo 150 - ns transmit mode service (no data) (see figure 16) symbol limits min max units pw1 2.45 2.55 s pw2 1.4 1.6 s td1 450 550 ns td2 700 800 ns
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 35 nbgt ndrq tx/rx iustb staten cwc(4:0) inclk clock gbr ih(7:0) dtrq dtak incmd ndrq h/l iustb staten cwc(4:0) incmd clock gbr ih(7:0) dtrq dtak sa(4:0) wc(4:0) figure 20 inclk timing ? transmit (dtak delayed) figure 19 inclk timing ? receive (dtak delayed) inclk h/l data lo data hi stat hi stat lo cmd hi cmd lo stat hi stat lo data hi data lo previous sa3,4 valid all valid busy sampled here (both transmit and receive) valid previous
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 36 rt/bc bcopa bcopb bcopstb reqbusa reqbusb vald tx/rx dwsync cmsync eot rto nbgt ndrq dtrq dtak h/l iustb statstb rmdstb cwen dwen incmd ih(7:0) gbr sa(4:0) wc(4:0) cwc(4:0) figure 21 ? bc transmit 1 word (non mode) 4 to 12 s hl command data status 3 state with pullup cmd 16 data bits p stat 16 data bits p data 16 data bits p point a fig 4 hl hl sa previous value wc = 00001 previous value cwc = 00000 cwc = cwc + 1
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 37 rt/bc bcopstb val d tx/rx dwsync cmsync eot rto nbgt ndrq dtrq dtak h/l iustb statstb rmdstb cwen dwen incmd ih(7:0) sa(4:0) wc(4:0) cwc(4:0) figure 22 ? bc receive 1 word (non mode) 4 to 12 s hl hl hl command data status 3 state with pullup cmd 16 data bits p stat 16 data bits p data 16 data bits p bcopa bcopb reqbusa reqbusb sa previous value wc = 00001 previous value cwc = 00000 cwc = cwc + 1 point a fig 4
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 38 4 to 12 s figure 23 ? bc transmit mode (no data) command status 3 state with pullup cmd 16 data bits p stat 16 data bits p hl hl fig 4 bcopstb val d tx/rx dwsync cmsync eot rto nbgt ndrq dtrq dtak h/l iustb statstb rmdstb cwen dwen incmd sa(4:0) wc(4:0) cwc(4:0) bcopa bcopb reqbusa reqbusb point a gbr ih(7:0) previous value previous value previous value rt/bc = 0
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 39 figure 24 ? bc transmit mode (with data) 4 to 12 s command status data 3 state with pullup cmd 16 data bits p hl hl hl fig 4 bcopstb val d tx/rx dwsync cmsync eot rto nbgt ndrq dtrq dtak h/l iustb statstb rmdstb cwen dwen incmd sa(4:0) wc(4:0) cwc(4:0) bcopa bcopb reqbusa reqbusb point a gbr ih(7:0) stat 16 data bits p data 16 data bits p rt/bc = 0 previous value previous value previous value
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 40 figure 25 ? bc receive mode (with data) command status 3 state with pullup cmd 16 data bits p data 16 data bits p hl hl hl fig 4 bcopstb val d tx/rx dwsync cmsync eot rto nbgt ndrq dtrq dtak h/l iustb statstb rmdstb cwen dwen incmd sa(4:0) wc(4:0) cwc(4:0) bcopa bcopb reqbusa reqbusb point a gbr ih(7:0) data previous value previous value previous value rt/bc = 0 stat 16 data bits p 4 to 12 s
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 41 figure 26 ? bc rt to rt transfer command cmd1 16 data bits p 3 state with pullup hl hl hl hl hl command status data status fig 4 bcopa vald tx/rx cmsync dwsync eot rto nbgt ndrq dtrq dtak h/l iustb statstb rmdstb cwen dwen incmd sa(4:0) wc(4:0) cwc(4:0) bcopb bcopstb reqbusa reqbusb point a gbr ih(7:0) previous value cwc = cwc + 1 previous value previous value sa = ? wc = ? rt/bc = 0 cmd2 16 data bits p stat2 16 data bits p data 16 data bits p stat1 16 data bits p 4 to 12 s 4 to 12 s
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 42 figure 27 monitor mode 3 state with pullup hl hl bcopa val d statstb pasmo n point a rmdstb ih(7:0) reqbusa bcopb rt/bc cmsync reqbusb tx/rx dmsync eot rto nbgt h/l csync data p dsync data p command or data word status word fig 4
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 43 first or only bcopstb second bcopstb transfer type bcop-b bcop-a bcop-b bcop-a normal data (bc to rt / rt to bc) 0 0 n/a n/a rt to rt 0100 mode codes (no data) [t/r = 0] 00h dynamic bus control 01h synchronize (no data) 02h transmit status 03h initiate self test 04h transmitter shutdown 05h override tx shutdown 06h inhibit tf flag 07h override inhibit tf flag 08h reset remote terminal 01n/an/a mode codes (data rt to bc) [t/r = 1] 10h transmit vector word 12h transmit last command 13h transmit bit word 0111 mode codes (data bc to rt) [t/r = 0] 11h synchronize (with data) 14h selected tx shutdown 15h override selected tx shutdown 0110 table 1 ? bcop sequences bcop-a,bcop-b bcopstb valid valid second first t 4 t 3 t 1 t 2 t 1 t 3 t 4 reqbus-a,reqbus-b 250ns < t 1 < 5s 7s < t 2 < 17s t 3 < 500ns t 4 > 1.5s limits: figure 28 ? bcop sequence timing
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 44 low byte data high data clock low data clock ih715 (c9) ACT3492 high byte data ih614 (d9) ih513 (b9) ih412 (d8) ih311 (a9) ih210 (d7) ih19 (d6) ih08 (e9) tx/rx (h10) vecten (g8) dtrq (k10) or h/l (j9) 18 17 14 13 8 7 4 3 11 1 10 19 16 15 12 9 6 5 2 +vcc 20 18 17 14 13 8 7 4 3 11 1 10 19 16 15 12 9 6 5 2 20 +vcc d7 d6 d5 d4 d3 d2 d1 d0 oe gnd q7 q6 q5 q4 q8 q2 q1 q0 vcc d7 d6 d5 d4 d3 d2 d1 d0 oe gnd q7 q6 q5 q4 q8 q2 q1 q0 vcc 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 figure 29 typical transmit data interface dtak may be connected to dtrq , ground or controlled
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 45 low byte data high byte enable low byte enable ih715 (c9) ACT3492 high byte data ih614 (d9) ih513 (b9) ih412 (d8) ih311 (a9) ih210 (d7) ih19 (d6) ih08 (e9) tx/rx (h10) iustb (g6) sync (g7) or h/l (j9) 18 17 14 13 8 7 4 3 1 19 16 15 12 9 6 5 2 20 +vcc d7 d6 d5 d4 d3 d2 d1 d0 oe gnd 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 figure 30 typical receive data interface q7 q6 q5 q4 q8 q2 q1 q0 vcc 11 10 18 17 14 13 8 7 4 3 1 19 16 15 12 9 6 5 2 20 +vcc d7 d6 d5 d4 d3 d2 d1 d0 oe gnd q7 q6 q5 q4 q8 q2 q1 q0 vcc 11 10 dtrq (k10) dtak may be connected to dtrq , ground or controlled
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 46 package pin out description by pin - ACT3492 pin # function pin # function pin # function a1 rtader d5 lstcmd /cwen g9 nbgt a2 +5vab d6 ih19 g10 inclk a3 servreq d7 ih210 h1 gndb a4 wc4 d8 ih412 h2 sa4 a5 sserr d9 ih614 h3 drvinh a6 wc2 d10 ndrq h4 cwc0 a7 lten e1 +5vaa h5 rtad3 a8 lttrig e2 ltfail h6 reqbusb a9 ih311 e3 maner h7 sa2 a10 nextstat e4 6mck h8 cwc1 b1 txrx a2 e5 reqbusa h9 eot b2 txrx a1 e6 statupdate h10 tx/rx b3 dbcacc e7 enable j1 txrx b1 b4 rt/bc e8 mereq j2 txrx b2 b5 hsfail e9 ih08 j3 pass b6 wc3 e10 +5v logic j4 bitdecode b7 wc0 f1 +5vbb j5 rtad2 b8 master reset f2 error j6 rtadpar b9 ih513 f3 rto j7 gbr b10 bcopa f4 rtad4 j8 cwc3 c1 gnda f5 bcsten 1 j9 h/l c2 vald f6 dtak j10 sa0 c3 txto f7 bcopstb k1 cwc4 c4 reset f8 pasmon k2 +5vba c5 dbcreq f9 dig gnd 1 / case k3 sa3 c6 biten /rmdstb f10 dig gnd 2 / case k4 cwc2 c7 busy g1 txrx b1 k5 rtad1 c8 wc1 g2 txrx b2 k6 rtad0 c9 ih715 g3 dwsync k7 staten /statstb c10 bcopb g4 cmsync k8 sa1 d1 txrx a2 g5 bcsten 0 k9 incmd d2 txrx a1 g6 iustb k10 dtrq d3 parer g7 sync d4 test g8 vecten /dwen
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 47 package pin out description by function - ACT3492 function pin # function pin # function pin # +5vaa e1 h/l j9 rtad4 f4 +5vab a2 hsfail b5 rtader a1 +5vba k2 ih08 e9 rtadpar j6 +5vbb f1 ih19 d6 rto f3 +5v logic e10 ih210 d7 sa0 j10 6mck e4 ih311 a9 sa1 k8 bcopa b10 ih412 d8 sa2 h7 bcopb c10 ih513 b9 sa3 k3 bcopstb f7 ih614 d9 sa4 h2 bcsten 0 g5 ih715 c9 servreq a3 bcsten 1 f5 inclk g10 sserr a5 bitdecode j4 incmd k9 staten /statstb k7 biten /rmdstb c6 iustb g6 statupdate e6 busy c7 lstcmd /cwen d5 sync g7 cmsync g4 lten a7 test d4 cwc0 h4 ltfail e2 tx/rx h10 cwc1 h8 lttrig a8 txrx a1 b2 cwc2 k4 maner e3 txrx a2 b1 cwc3 j8 master reset b8 txrx b1 g1 cwc4 k1 mereq e8 txrx b2 g2 dbcacc b3 nbgt g9 txrx a1 d2 dbcreq c5 ndrq d10 txrx a2 d1 dig gnd 1 / case f9 nextstat a10 txrx b1 j1 dig gnd 2 / case f10 parer d3 txrx b2 j2 drvinh h3 pasmon f8 txto c3 dtak f6 pass j3 vald c2 dtrq k10 reqbusa e5 vecten /dwen g8 dwsync g3 reqbusb h6 wc0 b7 enable e7 reset c4 wc1 c8 eot h9 rt/bc b4 wc2 a6 error f2 rtad0 k6 wc3 b6 gbr j7 rtad1 k5 wc4 a4 gnda c1 rtad2 j5 gndb h1 rtad3 h5
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 48 ceramic cofired pga package outline pin a1 & esd designator .100 typ .065 dia typ .065 sq .040 ref 45 . 900 1 2 3 4 5 6 7 8 9 10 abcdefghjk 1.060 sq .015 chamfer braze ring .020 ref 45 chamfer 4x .050 4x .050 .005 .018 .002 .160 max .180 .010 standoffs pins b2, j2, b9 & j9
aeroflex circuit technolo gy scd3492 rev b 6/26/01 plainview ny ( 516 ) 694-6700 49 ordering information model number desc part number package ACT3492 pending 1.06" x 1.06" ceramic plug in circuit technology specifications subject to change without notice. aeroflex circuit technology 35 south service road plainview new york 11803 telephone: (516) 694-6700 fax: (516) 694-6715 toll free inquiries: 1-(800)the-1553

▲Up To Search▲

Price & Availability of ACT3492

	To Download ACT3492 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .