Firewire IEEE
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
computer science crazy
Super Moderator

Posts: 3,048
Joined: Dec 2008
20-09-2009, 03:57 PM


The article discusses about the IEEE 1394 networking standards also called as Firewire. Firewire was designed to link the personal computers, digital cameras, televisions, DVD players, printers and other electronic equipments. Another competing technology for Firewire called the universal serial bus(USB) which promised to do nearly the same work. Both Firewire and the USB arrived at almost the same time hence the hardware and software vendors had to make a choice as to which technology to develop and support.Like Firewire,USB also connects multiple peripherals to a single port behind our computers. But the USB is designed to be simpler, slower interface that is less expensive to manufacture. USB got a nod in the Wintel world with Windows driver support for USB peripherals as early as October 1996 but it was not until windows 98 that consumers got full support for USB. Early support on the Wintel platform , however, could account for the large number of USB components that have become popular over past two years, such as joysticks, speakers, printers, video cameras and all of which have made it to market much more quickly than Firewire based technology


FireWire is Apple Inc.â„¢s name for the IEEE 1394 High Speed Serial Bus. It was initiated by Apple and developed by the IEEE P1394 Working Group, largely driven by contributions from Apple, although major contributions were also made by engineers from Texas Instruments, Sony, Digital Equipment Corporation, IBM, and INMOS/SGS Thomson (now STMicroelectronics). Apple intended FireWire to be a serial replacement for the parallel SCSI (Small Computer System Interface) bus while also providing connectivity for digital audio and video equipment. Appleâ„¢s development began in the late 1980s, later presented to the IEEE,[2] and was completed in 1995. As of 2007, IEEE 1394 is a composite of four documents: the original IEEE Std. 1394-1995, the IEEE Std. 1394a-2000 amendment, the IEEE Std. 1394b- 2002 amendment, and the IEEE Std. 1394c-2006 amendment. On June 12, 2008, all these amendments as well as errata and some technical updates were incorporated into a superseding standard IEEE Std. 1394-2008.[3]

4-circuit (left) and 6-circuit (right) FireWire 400 alpha connectors The IEEE 1394 interface is a serial bus interface standard for high-speed communications and isochronous realtime data transfer, frequently used by personal computers, as well as in digital audio, digital video, automotive, and aeronautics applications. The interface is also known by the brand names of FireWire (Apple Inc.), i.LINK (Sony), and Lynx (Texas Instruments). IEEE 1394 replaced parallel SCSI in many applications, because of lower implementation costs and a simplified, more adaptable cabling system. The 1394 standard also defines a backplane interface, though this is not as widely used. IEEE 1394 has been adopted as the High Definition Audio-Video Network Alliance (HANA) standard connection interface for A/V (audio/visual) component communication and control.[1] FireWire is also available in wireless, fiber optic, and coaxial versions using the isochronous protocols. Since the mid 1990s, consumer grade camcorders had included a fourcircuit 1394 interface, though, except for premium models, this is becoming less common. It remains the primary transfer mechanism for almost all high end professional audio and video equipment. Since 2003 many computers intended for home or professional audio/video use have built-in FireWire/i.LINK ports, especially prevalent with Sony and Appleâ„¢s computers and the older iPods. The legacy (alpha) 1394 port is also available on premium retail motherboards. Sonyâ„¢s implementation of the system, known as i.LINK used a smaller connector with only the four signal circuits, omitting the two circuits which provide power to the device in favor of a separate power connector.

a pair of 6-circuit alpha connectors on the edge of an expansion card The system is commonly used for connection of data storage devices and DV (digital video) cameras, but is also popular in industrial systems for machine vision and professional audio systems. It is preferred over the more common USB for its greater effective speed and power distribution capabilities, and because it does not need a computer host. Perhaps more importantly, FireWire makes full use of all SCSI capabilities and has high sustained data transfer rates, a feature especially important for audio and video editors. Benchmarks show that the sustained data transfer rates are higher for FireWire than for USB 2.0, especially on Apple Mac OS X with more varied results on Microsoft Windows.[4][5] However, the royalty which Apple Inc. and other patent holders initially demanded from users of FireWire and the more expensive hardware needed to implement it, both of which have since been dropped, have prevented FireWire from displacing USB in lowend mass-market computer peripherals, where product cost is a major constraint.[2]


FireWire can connect up to 63 peripherals in a tree topology (as opposed to Parallel SCSI™s electrical bus topology). It allows peer-to-peer device communication ” such as communication between a scanner and a printer ” to take place without using system memory or the CPU. FireWire also supports multiple hosts per bus. It is designed to support Plug and play and hot swapping. The copper cable it uses (1394™s most common implementation) can be up to 4.5 metres (15 ft) long and is more flexible than most Parallel SCSI cables. In its six-circuit or nine-circuit variations, it can supply up to 45 watts of power per port at up to 30 volts, allowing moderate-consumption devices to operate without a separate power supply. FireWire devices implement the ISO/IEC 13213 configuration ROM model for device configuration and identification, to provide plug-andplay capability. All FireWire devices are identified by an IEEE EUI-64 unique identifier (an extension of the 48-bit Ethernet MAC address format) in addition to well-known codes indicating the type of device and the protocols it supports. 2.1 Operating system support Full support for IEEE 1394a and 1394b is available for Microsoft Windows XP, FreeBSD[6], Linux[7], Apple Mac OS 8.6 through to Mac OS 9[8], and Mac OS X as well as NetBSD and Haiku. Historically, performance of 1394 devices may have decreased after installing Windows XP Service Pack 2, but were resolved in Hot fix 885222[9] and in SP3. Some FireWire hardware manufacturers also provide custom device drivers which replace the Microsoft OHCI host adapter driver stack, enabling S800-capable devices to run at full 800 Mbit/s transfer rates on older versions of Windows (XP SP2 w/o Hot fix 885222) and Windows Vista. At the time of its release, Microsoft Windows Vista supported only 1394a, with assurances that 1394b support would come in the next service pack.[10] Service Pack 1 for Microsoft Windows Vista has since been released, however the addition of 1394b support is not mentioned anywhere in the release documentation.

2.2 Cable TV system

support Cable TV providers (in the US, with digital systems) must, upon request of a customer, provide a high-definition capable cable box with a functional FireWire interface. This applies only to customers leasing high-definition capable cable boxes from said cable provider after April 1, 2004. The relevant law is CFR 76.640 Section 4 Subsections i and ii.[14] The interface can be used to display or record Cable TV, including HDTV programming.[15]
2.3 Node hierarchy

FireWire devices are organized at the bus in a tree topology. Each device has a unique self-id. One of the nodes is elected root node and always has the highest id. The self-ids are assigned during the self-id process, which happens after each bus reset. The order in which the self-ids are assigned is equivalent to traversing the tree in a depth-first, post-order manner.

The previous standards and its three amendments are now incorporated into a superseding standard, IEEE 1394-2008[3]. The feature individually added gives a good history on the development path.
3.1 FireWire 400 (IEEE 1394-1995)

A 6-circuit FireWire 400 alpha connector The original release of IEEE 1394- 1995[16] specified what is now known as FireWire 400. It can transfer data between devices at 100, 200, or 400 Mbit/s half-duplex data rates (the actual transfer rates are 98.304, 196.608, and 393.216 Mbit/s, i.e. 12.288, 24.576 and 49.152 megabytes per second respectively)[2]. These different transfer modes are commonly referred to as S100, S200, and S400. Cable length is limited to 4.5 meters (14.8 ft), although up to 16 cables can be daisy chained using active repeaters; external hubs, or internal hubs are often present in FireWire equipment. The S400 standard limits any configurationâ„¢s maximum cable length to 72 meters (240 ft). The 6- circuit connector is commonly found on desktop computers, and can supply the connected device with power. The 6-circuit powered connector, now referred to as an alpha connector, adds power output to support external devices. Typically a device can pull about 7 to 8 watts from the port; however, the voltage varies significantly from different devices.[17] Voltage is specified as unregulated and should nominally be about 25 volts (range 24 to 30). Appleâ„¢s implementation on laptops is typically related to battery power and can be as low as 9 V and more likely about 12 V.
3.2 Enhancements

(IEEE 1394a-2000) An amendment IEEE 1394a was released in 2000[18], which both clarified and enhanced the original specification. It added in support for asynchronous streaming, quicker bus reconfiguration, packet concatenation, and a power saving suspend mode. 1394a also standardized the 4-circuit alpha connector developed by Sony and already widely in use. The 4- circuit version is used on many consumer devices such as camcorders, laptops, and other small FireWire devices. Though fully data compatible with 6-circuit alpha interfaces, it lacks power connectors.
3.3 FireWire 800 (IEEE 1394b-2002)

A 9-circuit beta connector. IEEE 1394b-2002[19] introduced FireWire 800 (Appleâ„¢s name for the 9- circuit S800 bilingual version of the IEEE 1394b standard) This specification and corresponding products allow a transfer rate of 786.432 Mbit/s full-duplex via a new encoding scheme termed beta mode. It is backwards compatible to the slower rates and 6-circuit alpha connectors of FireWire 400. However, while the IEEE 1394a and IEEE 1394b standards are compatible, FireWire 800â„¢s connector, referred to as a beta connector, is different from FireWire 400â„¢s alpha connectors, making legacy cables incompatible. A bilingual cable allows the connection of older devices to the newer port. In 2003, Apple was the first to introduce commercial products with the new connector. The full IEEE 1394b specification supports data rates up to 3200 Mbit/s over beta-mode or optical connections up to 100 meters (110 yd) in length. Standard Category 5e unshielded twisted pair supports 100 meters (330 ft) at S100. The original 1394 and 1394a standards used data/strobe (D/S) encoding (renamed to alpha mode) on the circuits, while 1394b adds a data encoding scheme called 8B10B referred to as beta mode. FireWire S1600 and S3200 In December 2007, the 1394 Trade Association announced that products will be available before the end of 2008 using the S1600 and S3200 modes that, for the most part, had already been defined in 1394b and was further clarified in IEEE Std. 1394-2008[3]. The 1.6 Gbit/s and 3.2 Gbit/s devices use the same 9- circuit beta connectors as the existing FireWire 800 and will be fully compatible with existing S400 and S800 devices. It will compete with the forthcoming USB 3.0.[20].
3.4 FireWire S800T (IEEE 1394c-2006)

FireWire is enhanced to share gigabit Category 5e cable IEEE 1394c-2006 was published on June 8 2007.[21] It provided a major technical improvement, namely new port specification that provides 800 Mbit/s over the same RJ45 connectors with Category 5e cable, which is specified in IEEE 802.3 clause 40 (gigabit Ethernet over copper twisted pair) along with a corresponding automatic negotiation that allows the same port to connect to either IEEE Std 1394 or IEEE 802.3 (Ethernet) devices. Though the potential for a combined Ethernet and FireWire RJ45 port is intriguing, as of November 2008, there are no products or chipsets which include this capability.
Although high-speed USB 2.0 nominally runs at a higher signaling rate (480 Mbit/s) than FireWire 400, data transfers over S400 FireWire interfaces generally outperform similar transfers over USB 2.0 interfaces. Typical USB PC-hosts rarely exceed sustained transfers of 280 Mbit/s, with 240 Mbit/s being more typical. This is likely due to USBâ„¢s reliance on the host-processor to manage low-level USB protocol, whereas FireWire delegates the same tasks to the interface hardware. For example, the FireWire host interface supports memory-mapped devices, which allows high-level protocols to run without loading the host CPU with interrupts and buffer-copy operations.[4] Besides throughput, other differences are that it uses simpler bus networking, provides more power over the chain, more reliable data transfer, and uses less CPU resources.[23] FireWire 800 is substantially faster than Hi-Speed USB, both in theory and in practice.[24]

Aircraft IEEE 1394b is used in military aircraft, where weight savings are desired. Developed for use as the data bus on the F-22 Raptor, it is also used on the F-35 Lightning II.[25] NASAâ„¢s Space Shuttle also uses IEEE 1394b to monitor debris (foam, ice) which may hit the vehicle during launch.[25] This standard should not be confused with the unrelated MIL-STD-1394B, which is concerned with the construction quality of hats.
5.2 Automobiles IDB-1394

Customer Convenience Port (CCP) is the automotive version of the 1394 standard. [26]
5.3 Networking over FireWire FireWire

can be used for ad-hoc (terminals only, no routers except where a FireWire hub is used) computer networks. Specifically, RFC 2734 specifies how to run IPv4 over the FireWire interface, and RFC 3146 specifies how to run IPv6. Mac OS X, Linux, FreeBSD, Windows ME, Windows 2000, Windows XP, and Windows Server 2003 all include support for networking over FireWire[27]. A network can be set up between two computers using a single standard FireWire cable, or by multiple computers through use of a hub. This is similar to Ethernet networks with the major differences being transfer speed, circuit length, and the fact that standard FireWire cables can be used for point-to-point communication. On December 4, 2004, Microsoft announced[28] that it would discontinue support for IP networking over the FireWire interface in all future versions of Microsoft Windows. Consequently, support for this feature is absent from both Windows Vista and Windows Server 2008.[29][30] The PlayStation 2 console had an i.LINK-branded 1394 connector. This was used for networking until the release of an Ethernet adapter late in the consoleâ„¢s lifespan, but very few software titles supported the feature.

(Instrumentation & Industrial Digital Camera) is the FireWire data format standard for live video, and is used by Appleâ„¢s iSight A/V camera. The system was designed for machine vision systems,[31] but is also used for other computer vision applications and for some webcams. Although they are easily confused since they both run over FireWire, IIDC is different from, and incompatible with, the ordinary DV (Digital Video) camcorder protocol.
5.5 DV Digital Video

(DV) is a standard protocol used by some digital camcorders. Formerly, all DV cameras had a FireWire interface (usually a 4-circuit), but recently many consumer brands have switched to USB. Labeling of the port varies by manufacturer, with Sony using either its i.LINK trademark or the letters ËœDVâ„¢. Many digital video recorders have a DV-input FireWire connector (usually an alpha connector) which can be used to record video from a directlyconnected DV camcorder (computerfree). The protocol also allows remote control (play, rewind, etc.) of connected devices.
5.6 Security issues

Devices on a FireWire bus can communicate by direct memory access, where a device can use hardware to map internal memory to FireWireâ„¢s Physical Memory Space. The SBP-2 (Serial Bus Protocol 2) used by FireWire disk drives uses this capability to minimize interrupts and buffer copies. In SBP-2, the initiator (controlling device) sends a request by remotely writing a command into a specified area of the targetâ„¢s FireWire address space. This command usually includes buffer addresses in the initiatorâ„¢s FireWire Physical Address Space, which the target is supposed to use for moving I/O data to and from the initiator. [32] On many implementations, particularly those like PCs and Macs using the popular OHCI, the mapping between the FireWire Physical Memory Space and device physical memory is done in hardware, without operating system intervention. While this enables high-speed and lowlatency communication between data sources and syncs without unnecessary copying (such as between a video camera and a software video recording application, or between a disk drive and the application buffers), this can also be a security risk if untrustworthy devices are attached to the bus. For this reason, high-security installations will typically either purchase newer machines which map a virtual memory space to the FireWire Physical Memory Space (such as a Power Mac G5, or any Sun workstation), disable the OHCI hardware mapping between FireWire and device memory, physically disable the entire FireWire interface, or do not have FireWire at all. This feature can also be used to debug a machine whose operating system has crashed, and in some systems for remote-console operations. On FreeBSD, the dcons driver provides both, using gdb as debugger. Under Linux, firescope[33] and fireproxy[34] exist
Use Search at wisely To Get Information About Project Topic and Seminar ideas with report/source code along pdf and ppt presenaion
project topics
Active In SP

Posts: 2,492
Joined: Mar 2010
05-04-2010, 10:31 PM

please read topicideashow-to-firewire-ieee and topicideashow-to-firewire-seminar and presentation-report for getting more about FireWire
Use Search at wisely To Get Information About Project Topic and Seminar ideas with report/source code along pdf and ppt presenaion

Important Note..!

If you are not satisfied with above reply ,..Please


So that we will collect data for you and will made reply to the request....OR try below "QUICK REPLY" box to add a reply to this page

Quick Reply
Type your reply to this message here.

Image Verification
Please enter the text contained within the image into the text box below it. This process is used to prevent automated spam bots.
Image Verification
(case insensitive)

Possibly Related Threads...
Thread Author Replies Views Last Post
  sniffer for detecting lost mobiles ieee paper pdf jaseelati 0 311 21-01-2015, 03:17 PM
Last Post: jaseelati
  sniffer for detecting lost mobiles ieee paper pdf jaseelati 0 303 16-12-2014, 04:05 PM
Last Post: jaseelati
  ZigBee/IEEE 802.15.4 Summary pdf study tips 0 343 05-06-2013, 12:29 PM
Last Post: study tips
  GHz IEEE 802.15.4 / ZigBee-ready RF Transceiver project girl 0 326 18-12-2012, 06:19 PM
Last Post: project girl
  Achieving per-flow and weighted fairness for uplink and downlink in IEEE 802.11 WLANs project girl 0 357 17-12-2012, 06:33 PM
Last Post: project girl
  Dynamic admission control and bandwidth reservation for IEEE 802.16e mobile WiMAX project girl 0 430 17-12-2012, 06:33 PM
Last Post: project girl
  Firewire ppt seminar tips 0 321 16-11-2012, 05:48 PM
Last Post: seminar tips
  IEEE Transactions on Power Apparatus and Systems, seminar tips 0 475 09-11-2012, 06:06 PM
Last Post: seminar tips
  Comparison of the IEEE 802.11, 802.15.1, 802.15.4 and 802.15.6 wireless standards seminar flower 0 551 24-08-2012, 03:05 PM
Last Post: seminar flower
  WiMAX: IEEE 802.16 - Wireless MANs seminar flower 0 459 26-07-2012, 10:49 AM
Last Post: seminar flower