Patent Application
20060161687
The present invention relates to a method of synchronizing operation of serially connected devices, a system of serially connected devices, a serially connectable device and a method of managing communications with serially connected devices.
Computer peripherals can be connected to computers by a number of different types of connections using a number of different protocols. Amongst such connections are connections that enable supply of power to the peripheral device such as USB ports and firewire ports.
We have developed a stackable media device, that is constructed so that a tower of stackable storage devices can be used to store a large quantity of CD-ROMS or other optical media and the entire tower can be serially connected to the same USB port. There is a need to control operation of such devices for example to control power usage in such a stack or of other serially connected devices and to manage communications with such devices.
In a first aspect of the invention there is provided a method of synchronising operation of at least one component of each of a plurality of serially connected devices connected to a common power source comprising:
sending cycles of serial interrupts to each of the serially connected devices;
allocating an operation time slot to each serially connected device corresponding to at least one interrupt of each cycle, each at least one allocated time slot being different; and
controlling operation of at least one component of each serially connected device to operate only during the time slot allocated to the serially connected device.
In a second broad aspect there is provided a synchronised system of serially connected devices comprising:
a plurality of serially connected devices;
a computer for sending a cycles of serial interrupts to each of the plurality of connected devices; and
allocation means for allocating operation time slots to each serially connected device corresponding to at least one interrupt, and wherein
each serially connected device comprises control means for monitoring said cycle of interrupts and controlling operation of at least one component to operate only during the time slot allocated to the serially connected device.
In a third broad aspect there is provided a serially connectable device configured to receive cycles of serial interrupts and to be allocated a time slot corresponding to at least one interrupt, said serially connectable device further comprising control means for monitoring said cycle of interrupts and controlling operation of at least one component to operate only during the time slot allocated to the serially connected device.
In a fourth broad aspect there is provided a method of managing communications with a plurality of serially connectable devices comprising a master device and a variable number of slave devices in serial data communication with one another, the method comprising:
a master device continually polling its serial output lines for slave devices; and
each time a new slave device is located until a predetermined maximum number of slave devices is reached, altering the polling in order to poll for additional slave devices, the polling passing through all located slave devices, whereby the master device can determine the current number of connected slave devices.
In a fifth broad aspect there is provided a serially connectable device configured to act as a master device, the serially connectable device comprising:
polling means for continually polling serial output lines of the master device for slave devices, the polling means configured to poll for additional slave devices each time a new slave device is located until a maximum number of slave devices is located, the polling passing through all located slave devices, whereby the master device can determine the current number of slave devices.
The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more embodiments of the present invention and, together with the detailed description, serve to explain the principles and implementations of the invention.
In the drawings:
Embodiments of the present invention are described herein in the context of a tower of stacked media storage devices. Those of ordinary skill in the art will realize that the following detailed description of the present invention is illustrative only and is not intended to be in any way limiting. Other embodiments of the present invention will readily suggest themselves to such skilled persons having the benefit of this disclosure. In particular, persons skilled in the art will appreciate that the invention can be applied to other serially connectable devices. Reference will now be made in detail to implementations of the present invention as illustrated in the accompanying drawings. The same reference indicators will be used throughout the drawings and the following detailed description to refer to the same or like parts.
Herein, the term “power input port” is used to refer to an input port of a serially connectable device via which the serially connectable device can be supplied with power and control signals, typically from an output port of a computer. Examples of such ports are USB ports and Firewire ports.
The terms “input” and “output” are used to explain the power direction, however communication will be bi directional.
Here the term “serially connectable device” refers to a device adapted to be connected with other devices to form a series of connected devices. Such series being referred to as a series of two or more devices. That is, there may be a minimum of two devices. The maximum number of devices will depend on a variety of parameters, and in the preferred embodiment is five devices. While the series of devices will typically be connected to a serial port, the term “serially connectable” is not intended to imply that the devices must be connected to a serial port.
In the interest of clarity, not all of the routine features of the implementations described herein are shown and described. It will, of course, be appreciated that in the development of any such actual implementation, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, such as compliance with application and business related constraints, and that these specific goals will vary from one implementation to another and from one developer to another. Moreover, it will be appreciated that such a development effort might be complex and time consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art having the benefit of this disclosure.
In accordance with one embodiment of the present invention, the components, process steps, and/or data structures may be implemented using various types of operating systems (OS), computing platforms, firmware, computer programs, computer languages, and/or general purpose machines. The method can be run as a programmed process running on processing circuitry. The processing circuitry can take the form of numerous combinations of processors and operating systems, or a stand-alone device. The process can be implemented as instructions executed by software running on such hardware, hardware alone, or any combination thereof. The software may be stored on a program storage device readable by a machine.
In addition, those of ordinary skill in the art will recognize that devices of a less general purpose nature, such as hardwired devices, field programmable logic devices (FPLDs), including field programmable gate arrays (FPGAs) and complex programmable logic devices (CPLDs), application specific integrated circuits (ASICs), or the like, may also be used without departing from the scope and spirit of the inventive concepts disclosed herein.
In accordance with one embodiment of the present invention, the method may be implemented on a data processing computer such as a personal computer, workstation computer, mainframe computer, or high performance server running an OS such as Mac OSX available from Apple of Cupertino, Microsoft® Windows® XP and Windows® 2000, Windows ME, Windows 98 SE, all available from Microsoft Corporation of Redmond, Washington, or various versions of the Unix operating system such as Linux available from a number of vendors. The method may also be implemented on a multiple-processor system, or in a computing environment including various peripherals such as input devices, output devices, displays, pointing devices, memories, storage devices, media interfaces for transferring data to and from the processor(s), and the like. In addition, such a computer system or computing environment may be networked locally, or over the Internet.
Those of ordinary skills in the art will recognize that the computer system 106 consists of at least one microcontroller (not shown), memory (not shown), a power source (not shown), and a motherboard (not shown) connected to a USB connection. The computer system will typically be a personal computer.
Each media storage device can physically store one or more optical storage medium such as CDs and DVDs. For example, each storage device may include a carousel (not shown) having slots to accommodate the CDs and DVDS. The carousel may be powered by a motor driver and controlled by a microcontroller. A slit opening in the storage device allows a CD or DVD to be inserted and removed. The hardware inside a storage device unit is illustrated and described in more detail in
The external power switches 210 switches power to the upper unit via upper stacking connector (USC) 206—i.e. the USC acts as a serial output power port and the external power switch controls whether power is supplied to the output port. The upper stacking connector 206 is electrically connected to the lower stacking connector (LSC) 208 of another unit stacked on top of the present unit. The upper stacking connector 206 has five conductive pins. In the upper units the power comes from the USC 206 of the next lower unit, into the LSC 208 and to the switches. It is only the master, or bottom unit, where the power comes from the USB port 204.
The internal power switches 212 switches power to the present unit from either the LSC or the USB depending on the source of the unit's power. In particular, the internal power switches 212 provides power to motor drivers 218, LED and Opto sensor 222, and Vpp Generation 224. The motor drivers 218 power the carousel motor(not shown) of the present unit. The carousel motor mechanically turns the carousel under the unit's control. The LED provides visual notification to a user whether the storage device unit is powered, and what its current status is. (Busy, idle, errored etc.) The opto sensor 222 senses any addition or removal of an optical disc (e.g. CD or DVD) to the present storage device. The opto sensor 22 also detects movement of the carousel in order to monitor which slot faces the front. The Vpp Generation 224 provides a higher voltage (12V) for the programming of the flash memory in the microcontroller. (Normal operation of the microcontroller and its memory is with a 5V supply.) To program or reprogram the internal flash memory the higher voltage is required. This is typically done when the user downloads a firmware upgrade from the internet and selects to program it into a unit.
The microcontroller 216 is either powered via the USB port 204 (in the case of the a storage device being a master device, in this embodiment the bottom one) or via a lower stacking connector 208 (in the case of a storage device being a slave device, in this embodiment stacked on top of another storage device). That is, the master device is the first device in the series and the only device to receive power directly from the USB port, all subsequent devices in the series of connected devices are slave devices. The microcontroller 216 of the master device control the power usage of the entire tower of storage devices in part by synchronising operation of some components of the storage devices so they do not occur concurrently. Further power control methods are disclosed in Australian patent application no. 2005200225 filed 19 Jan. 2005 the disclosure of which is incorporated herein by reference. The microcontroller of the master device also enables communication with all the devices by allocating addresses as described below. The allocated addresses are also used in the synchronisation method.
In the case where a storage device unit is not powered via USB connector 204, the lower stacking connector 208 provides power to the storage device unit (external power switches 210, internal power switches 212, microcontroller 216). The lower stacking connector 208 is electrically connected to the upper stacking connector of another storage device unit stacked below the present storage device unit. The lower stacking connector 208 has a set of conductive pins.
The stacking connectors also allow each unit to communicate with another. The serial peripheral interface (SPI) bus from the stacking connector may be used for serial communications within a tower of units. Only three data lines (SCK, MISO, MOSI) are required for the SPI connection, thereby minimizing the number of stacking connector pins.
In the preferred embodiment the bottom unit is the logical master and other units within the tower operate as slaves. The normal method of using SPI with multiple slaves (using slave select addressing lines) is not used in this system. Instead, the slaves are configured to listen to master communications and the system uses a layer 2 protocol to frame slave communications.
The master unit is in control of all communications. The master unit sends packets to the first unit then either waits for the response packet from this unit or times out. The master unit determines whether there are any additional slave units by a polling procedure that will be described in further detail below. In summary new slave devices that are attached to the stack have their processor running, but do not provide power to any unit above them in the stack, do not have an address, and do not participate in any serial communications. At specific intervals (in this embodiment, every 2 seconds) the master sends out a “set address” command which only slaves without addresses will interpret. The master knows a new slave has been added if subsequent “get_id” commands sent to the new address get a response. If there is no response, the master assumes there is no new slave and continues as normal. This process relies on the fact that there can only be one new slave unit on the stack at any time due to new units having their upper power connector turned off. Slave units are responsible for working out which eight bits of data comprise a byte, (i.e. synchronizing the byte framing). Slave units synchronise themselves to the byte framing by looking for gaps in the serial clock. Data is sent one bit at a time as a sequence of eight bits, generating eight closely spaced clock pulses. Then there is a gap before the next byte is sent. The slave units synchronise by looking for that gap and then turn on their serial hardware before the next data byte comes through.
The unique way in which SPI is used means that a number of precautions needed to be taken to ensure the physical layer of SPI operates correctly. This includes a system of identifying SPI traffic and adding slave data only when requested by the master, and a means of synchronizing slave communication with the master and/or other slaves. Slaves read all data coming from the master. Slaves know that when the master is talking to a another slave, the other slave is going to be using the shared slave line. They also know no-one else will be using the line when they have received a packet from the master.
A layer 2 ‘link layer transmission protocol’ for packet transmission has been designed as a means of controlling data transfer within the stack.
The data to be transferred in the link layer frames is formatted in packets. The format of the packets are to provide a consistent and expandable means of facilitating communications between the master unit and the slaves. The packet start and end are defined by packet delimiters 302 and 314 respectively. The packet contents comprise an address 304, sequence number 306, command 308, then between three and 12 data fields 310. Data fields are not always used, but at least three are always present. This packet format is the same for all packets. Inter-packet gaps are filled by slaves transmitting null bytes between packets, but only because the outputs are tri-stated and the master reads it as a low level. The master sends hex AA bytes as its inter packet gap fill, if a slave somehow misses a delimiter and gets its start and end of packet mixed up, it will see a delimiter followed by an AA, so know that it was out of sync and that was actually the end of a packet. The address field 304 from master to slave indicates which slave is supposed to interpret that packet. From slave to master the address field is used to ensure the correct slave is sending, otherwise discard the packet. When the slave is sending the sequence number field just mirrors whatever the sequence number was on the last command sent from the host PC. This allows the master to see when slaves have received the specified host command. The command field 308 from master to slave indicates an action the slave should take, or what the slave should do with any data bytes that came with that packet. Thus, the command field 308 determines how the data is interpreted. The packet may contain between zero and twelve data bytes. For master to slave communications there are between zero and five bytes used. For slave to master communications there are between three and twelve data bytes used. In a master transmitted packet these parameters completely describe the action required by the unit. For example, if the command was move, the parameters in the data fields 310 would be slot number of the carousel and an eject or retain parameter. In slave to master communications, the data fields return information about the slave status such as whether it is busy performing a command or the current slot number.
The combination of the link layer framing protocol and the packet format make a stable communication system capable of reliably passing commands within the tower and also a means of easily reformatting packets for USB transfer to the host computer. USB transfers are formatted in a very similar fashion to inter-unit SPI communications with the only differences to the data format being the removal of the delimiter bytes, (7E), and the addition of a USB ID field to the start of the packet. USB packets are also always 8 bytes long, so packets that are longer are not sent via USB to the host. There is only one such command which has this problem (the 12 byte return data from a get_id command). To get this data to the host, it has been split up into three separate commands, so that the host PC can retrieve the data as three separate segments.
Rungs 406 to 410 illustrates the sequence of events that occurs when there is no slaves present. At rung 406 the master 400 turns on its own output power connectors (the upper stacking connector) and sends a set address to one command on the output signal line. No response is received at this stage. At rung 408 the master 400 sends a get_id command on the output line. Having transmitted both the address and the id command allows the slave to reply to acknowledge that it is in address one and to reply with its id and the slave should be able to return the id at rung 410 and accordingly as no id is supplied to the master at rung 410, the master knows that no slave is present at this stage. Note that the next command from the master is to get the status of the slave. With respect to the address, the master's address is 0 and each additional slave's address will increase by one digit 1,2,3 etc. up to the maximum number of slaves, in this embodiment five slaves so the maximum address is 4.
Rungs 412 and 414 represent the master 400 beginning the process of looking for a slave again. This time at rung 416 the master receives an id from the first slave 402 with address 1 and including the id number of the unit. This starts a new cycle of the master 400 continually checking the status of the slave 402 so it sends another get status signal at rung 418. At rung 420 the master 400 starts looking for a second slave 404 and sends a set address command for the second address. The first slave 402 notes that this is not its address because it knows that its address is “1” and ignores the request. Similarly a get_id command is sent by the master 400 at rung 422 which is addressed to the second unit. The master 400 receives an id response at rung 424 and knows to add the second slave 404 to the stack at that point. The master 400 then continues to send status and/or command questions to each unit in turn. As indicated by rungs 426 and 428. The master 400 will also continue to attempt to add further units up to the maximum number of slave devices.
This process is illustrated further in the flow chart of
If there is at least one slave at step 511 the master 400 determines the next slave to communicate with at 512. At step 514 it transmits packets to a slave and receives the slave packets.
At step 516 it determines whether a slave response is received in time. If a slave response is not received when expected or the response starts but does not end correctly then the response times out and the packet is ignored and the process of looking for new units starts again. If a unit responds in time at step 518 the slave response is processed.
The addresses allocated to the slaves are used as part of the stack synchronisation protocol. The stack synchronisation protocol is used to ensure the light emitting diodes of the optical sensors of different devices are not on at the same time. Accordingly, it is necessary for each device to know when they can carry out their own optical sampling procedure. This acts to control power usage by the devices. Thus synchronising the optical sampling function avoids too much power being drawn from the shared power source at the same time.
The crystal resonators of each serially connectable device will have some frequency variation. Accordingly, if the devices were merely synchronised once, units would drift apart in time sufficiently to cause problems within a matter of milliseconds. Accordingly, the applicant has developed a method of constantly synchronising the units using the SPI interrupts as the SPI interrupts will occur between 170 and 220 ms intervals and all units within a stack receive the interrupt within a few microseconds of each other.
For the devices of the preferred embodiment, sampling the optical inputs takes up to 500 ms to complete and as there are a maximum of five devices that need separate 500 ms time slots to operate in it is necessary to have at least 2.5 ms time period between optical sampling for each unit. As the time taken for these interrupts to execute varies during normal operation a safety margin is added and accordingly the time allowed was set to a total of a 4 ms period and to build this 4 ms period ten separate serial interrupts were used. As illustrated in
Referring to
To ensure that each unit uses a different time slot for optical sampling each unit needs to know which time slot it is allowed to use. As discussed above when slave units are initialised they are allocated an address. At the same time, the master also advises the slave the current serial interrupt as far as the master is concerned. The slave then takes this number and adds its address multiplied by two to give it a different set of optical time slots to the master and stores this as its current time slot number. This results in each unit in the stack having a different set of two SPI interrupts in which to conduct the optical sensing. The units then use a counter to monitor cycles of interrupts in order to determine which interrupts belong to them and conduct their sensing during these interrupts.
In the above embodiment, each serially connectable stackable media storage device is of identical construction. While this has advantages—e.g. that each device is capable of acting as a master device or a slave device depending on its place in the series of devices and all devices can be manufactured to the same specification persons skilled in the art will appreciate that devices could be designed to operate specifically as master or slave units. In such an embodiment, the master units would not need a lower stacking connector. Such an embodiment would also allow the slave units to be of simpler construction, for example they would not need a USB connection and could be provided with a simpler micro controller.
While embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts herein. The invention, therefore, is not to be restricted except in the spirit of the appended claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2005/200225 | Jan 2005 | AU | national |
| 2005/200880 | Feb 2005 | AU | national |
