// API callback
related_results_labels({"version":"1.0","encoding":"UTF-8","feed":{"xmlns":"http://www.w3.org/2005/Atom","xmlns$openSearch":"http://a9.com/-/spec/opensearchrss/1.0/","xmlns$blogger":"http://schemas.google.com/blogger/2008","xmlns$georss":"http://www.georss.org/georss","xmlns$gd":"http://schemas.google.com/g/2005","xmlns$thr":"http://purl.org/syndication/thread/1.0","id":{"$t":"tag:blogger.com,1999:blog-32882751"},"updated":{"$t":"2014-10-01T21:45:29.725-07:00"},"category":[{"term":"Protocol"},{"term":"VOIP"},{"term":"Voice Over Internet Protocol"},{"term":"Bluetooth"},{"term":"Internet"},{"term":"CAN"},{"term":"Bluetooth Technology"},{"term":"RS232"},{"term":"Bluetooth Application"},{"term":"Modbus"},{"term":"USB"},{"term":"VOIP Technology"},{"term":"Wireless"},{"term":"Wireless Networks"},{"term":"Basic Bluetooth"},{"term":"Bluetooth Devices"},{"term":"Bluetooth USB"},{"term":"CRC"},{"term":"Data Communication"},{"term":"Flash"},{"term":"Microcontroller"},{"term":"RS-485"},{"term":"VIDEO Solfware"},{"term":"VOIP Solfware"}],"title":{"type":"text","$t":"Communication and Protocal Data"},"subtitle":{"type":"html","$t":"Bluetooth,  Internet Protocol,VOIP,RS-232 Electrical Signal Characteristics, Modbus Communications Protocol and CAN BUS"},"link":[{"rel":"http://schemas.google.com/g/2005#feed","type":"application/atom+xml","href":"http:\/\/rs232-rs485.blogspot.com\/feeds\/posts\/default"},{"rel":"self","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/-\/CAN?alt=json-in-script\u0026max-results=10"},{"rel":"alternate","type":"text/html","href":"http:\/\/rs232-rs485.blogspot.com\/search\/label\/CAN"},{"rel":"hub","href":"http://pubsubhubbub.appspot.com/"}],"author":[{"name":{"$t":"kop"},"uri":{"$t":"http:\/\/www.blogger.com\/profile\/03199950917117732729"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"16","height":"16","src":"http:\/\/img2.blogblog.com\/img\/b16-rounded.gif"}}],"generator":{"version":"7.00","uri":"http://www.blogger.com","$t":"Blogger"},"openSearch$totalResults":{"$t":"5"},"openSearch$startIndex":{"$t":"1"},"openSearch$itemsPerPage":{"$t":"10"},"entry":[{"id":{"$t":"tag:blogger.com,1999:blog-32882751.post-5024714183618674035"},"published":{"$t":"2009-11-18T16:57:00.000-08:00"},"updated":{"$t":"2009-11-18T16:57:00.450-08:00"},"category":[{"scheme":"http://www.blogger.com/atom/ns#","term":"CAN"}],"title":{"type":"text","$t":"CAN BUS MESSAGE FRAMES - Overload Frame,Interframe Space"},"content":{"type":"html","$t":"\u003Ca href=\"http:\/\/3.bp.blogspot.com\/_ycHwJEosotY\/SvoMDJMGF7I\/AAAAAAAAA64\/3Ql4_UQnoBg\/s1600-h\/Overload+Frame.JPG\"\u003E\u003Cimg id=\"BLOGGER_PHOTO_ID_5402643951130122162\" style=\"DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 320px; CURSOR: hand; HEIGHT: 154px; TEXT-ALIGN: center\" alt=\"\" src=\"http:\/\/3.bp.blogspot.com\/_ycHwJEosotY\/SvoMDJMGF7I\/AAAAAAAAA64\/3Ql4_UQnoBg\/s320\/Overload+Frame.JPG\" border=\"0\" \/\u003E\u003C\/a\u003E\u003Cbr \/\u003E\u003Cspan style=\"font-family:arial;\"\u003EAn overload frame, shown in Figure 2-5, has the same\u003Cbr \/\u003Eformat as an active error frame. An overload frame,\u003Cbr \/\u003Ehowever, can only be generated during an interframe\u003Cbr \/\u003Espace. In this way, an overload frame can be differentiated\u003Cbr \/\u003Efrom an error frame (an error frame is sent during\u003Cbr \/\u003Ethe transmission of a message). The overload frame\u003Cbr \/\u003Econsists of two fields: an overload flag followed by an\u003Cbr \/\u003Eoverload delimiter. The overload flag consists of six\u003Cbr \/\u003Edominant bits followed by overload flags generated by\u003Cbr \/\u003Eother nodes (and, as for an active error flag, giving a\u003Cbr \/\u003Emaximum of twelve dominant bits). The overload\u003Cbr \/\u003Edelimiter consists of eight recessive bits. An overload\u003Cbr \/\u003Eframe can be generated by a node as a result of two\u003Cbr \/\u003Econditions:\u003Cbr \/\u003E1. The node detects a dominant bit during the\u003Cbr \/\u003Einterframe space, an illegal condition.\u003Cbr \/\u003EException: The dominant bit is detected during\u003Cbr \/\u003Ethe third bit of IFS. In this case, the receivers will\u003Cbr \/\u003Einterpret this as a SOF.\u003Cbr \/\u003E2. Due to internal conditions, the node is not yet\u003Cbr \/\u003Eable to begin reception of the next message. A\u003Cbr \/\u003Enode may generate a maximum of two\u003Cbr \/\u003Esequential overload frames to delay the start of\u003Cbr \/\u003Ethe next message.\u003Cbr \/\u003E\u003Cbr \/\u003E\u003Cstrong\u003ECAN BUS MESSAGE FRAMES - Interframe Space\u003C\/strong\u003E\u003Cbr \/\u003E\u003Cbr \/\u003EThe interframe space separates a preceding frame (of\u003Cbr \/\u003Eany type) from a subsequent data or remote frame.\u003Cbr \/\u003EThe interframe space is composed of at least three\u003Cbr \/\u003Erecessive bits called the Intermission. This allows\u003Cbr \/\u003Enodes time for internal processing before the start of\u003Cbr \/\u003Ethe next message frame. After the intermission, the\u003Cbr \/\u003Ebus line remains in the recessive state (bus idle) until\u003Cbr \/\u003Ethe next transmission starts.\u003Cbr \/\u003E\u003Cbr \/\u003Ehttp:\/\/ww1.microchip.com\/downloads\/en\/DeviceDoc\/21801d.pdf\u003C\/span\u003E"},"link":[{"rel":"edit","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/5024714183618674035"},{"rel":"self","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/5024714183618674035"},{"rel":"alternate","type":"text/html","href":"http:\/\/rs232-rs485.blogspot.com\/2009\/11\/can-bus-message-frames-overload.html","title":"CAN BUS MESSAGE FRAMES - Overload Frame,Interframe Space"}],"author":[{"name":{"$t":"kop"},"uri":{"$t":"http:\/\/www.blogger.com\/profile\/03199950917117732729"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"16","height":"16","src":"http:\/\/img2.blogblog.com\/img\/b16-rounded.gif"}}],"media$thumbnail":{"xmlns$media":"http://search.yahoo.com/mrss/","url":"http:\/\/3.bp.blogspot.com\/_ycHwJEosotY\/SvoMDJMGF7I\/AAAAAAAAA64\/3Ql4_UQnoBg\/s72-c\/Overload+Frame.JPG","height":"72","width":"72"}},{"id":{"$t":"tag:blogger.com,1999:blog-32882751.post-2319389249045217623"},"published":{"$t":"2009-11-14T16:54:00.000-08:00"},"updated":{"$t":"2009-11-14T16:54:00.525-08:00"},"category":[{"scheme":"http://www.blogger.com/atom/ns#","term":"CAN"}],"title":{"type":"text","$t":"CAN BUS MESSAGE FRAMES - Error Frame"},"content":{"type":"html","$t":"\u003Ca href=\"http:\/\/2.bp.blogspot.com\/_ycHwJEosotY\/SvoLkc6ElAI\/AAAAAAAAA6w\/FNJuhqeYdZg\/s1600-h\/Error+Frame.JPG\"\u003E\u003Cimg id=\"BLOGGER_PHOTO_ID_5402643423847289858\" style=\"DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 320px; CURSOR: hand; HEIGHT: 187px; TEXT-ALIGN: center\" alt=\"\" src=\"http:\/\/2.bp.blogspot.com\/_ycHwJEosotY\/SvoLkc6ElAI\/AAAAAAAAA6w\/FNJuhqeYdZg\/s320\/Error+Frame.JPG\" border=\"0\" \/\u003E\u003C\/a\u003E\u003Cbr \/\u003E\u003Cbr \/\u003E\u003Cbr \/\u003E\u003Cspan style=\"font-family:arial;\"\u003EAn error frame is generated by any node that detects a\u003Cbr \/\u003Ebus error. An error frame, shown in Figure 2-4, consists\u003Cbr \/\u003Eof two fields: an error flag field followed by an error\u003Cbr \/\u003Edelimiter field. There are two types of error flag fields.\u003Cbr \/\u003EThe type of error flag field sent depends upon the error\u003Cbr \/\u003Estatus of the node that detects and generates the error\u003Cbr \/\u003Eflag field. \u003C\/span\u003E\u003Cbr \/\u003E\u003Cspan style=\"font-family:arial;\"\u003E\u003Cbr \/\u003E2.4.1 ACTIVE ERRORS\u003Cbr \/\u003EIf an error-active node detects a bus error, the node\u003Cbr \/\u003Einterrupts transmission of the current message by\u003Cbr \/\u003Egenerating an active error flag. The active error flag is\u003Cbr \/\u003Ecomposed of six consecutive dominant bits. This bit\u003Cbr \/\u003Esequence actively violates the bit-stuffing rule. All other\u003Cbr \/\u003Estations recognize the resulting bit-stuffing error and, in\u003Cbr \/\u003Eturn, generate error frames themselves, called error\u003Cbr \/\u003Eecho flags.\u003Cbr \/\u003E\u003Cbr \/\u003EThe error flag field, therefore, consists of between six\u003Cbr \/\u003Eand twelve consecutive dominant bits (generated by\u003Cbr \/\u003Eone or more nodes). The error delimiter field (eight\u003Cbr \/\u003Erecessive bits) completes the error frame. Upon\u003Cbr \/\u003Ecompletion of the error frame, bus activity returns to\u003Cbr \/\u003Enormal and the interrupted node attempts to resend the\u003Cbr \/\u003Eaborted message.\u003Cbr \/\u003E\u003Cbr \/\u003E2.4.2 PASSIVE ERRORS\u003Cbr \/\u003EIf an error-passive node detects a bus error, the node\u003Cbr \/\u003Etransmits an error-passive flag followed by the error\u003Cbr \/\u003Edelimiter field. The error-passive flag consists of six\u003Cbr \/\u003Econsecutive recessive bits. The error frame for an errorpassive\u003Cbr \/\u003Enode consists of 14 recessive bits. From this it\u003Cbr \/\u003Efollows that, unless the bus error is detected by an erroractive\u003Cbr \/\u003Enode or the transmitting node, the message will\u003Cbr \/\u003Econtinue transmission because the error-passive flag\u003Cbr \/\u003Edoes not interfere with the bus.\u003Cbr \/\u003E\u003Cbr \/\u003EIf the transmitting node generates an error-passive flag,\u003Cbr \/\u003Eit will cause other nodes to generate error frames due\u003Cbr \/\u003Eto the resulting bit-stuffing violation. After transmission\u003Cbr \/\u003Eof an error frame, an error-passive node must wait for\u003Cbr \/\u003Esix consecutive recessive bits on the bus before\u003Cbr \/\u003Eattempting to rejoin bus communications.\u003Cbr \/\u003EThe error delimiter consists of eight recessive bits and\u003Cbr \/\u003Eallows the bus nodes to restart bus communications\u003Cbr \/\u003Ecleanly after an error has occurred.\u003Cbr \/\u003E\u003Cbr \/\u003Ehttp:\/\/ww1.microchip.com\/downloads\/en\/DeviceDoc\/21801d.pdf\u003C\/span\u003E"},"link":[{"rel":"edit","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/2319389249045217623"},{"rel":"self","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/2319389249045217623"},{"rel":"alternate","type":"text/html","href":"http:\/\/rs232-rs485.blogspot.com\/2009\/11\/can-bus-message-frames-error-frame.html","title":"CAN BUS MESSAGE FRAMES - Error Frame"}],"author":[{"name":{"$t":"kop"},"uri":{"$t":"http:\/\/www.blogger.com\/profile\/03199950917117732729"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"16","height":"16","src":"http:\/\/img2.blogblog.com\/img\/b16-rounded.gif"}}],"media$thumbnail":{"xmlns$media":"http://search.yahoo.com/mrss/","url":"http:\/\/2.bp.blogspot.com\/_ycHwJEosotY\/SvoLkc6ElAI\/AAAAAAAAA6w\/FNJuhqeYdZg\/s72-c\/Error+Frame.JPG","height":"72","width":"72"}},{"id":{"$t":"tag:blogger.com,1999:blog-32882751.post-6699851882820832653"},"published":{"$t":"2009-11-10T16:52:00.001-08:00"},"updated":{"$t":"2009-11-10T16:54:09.045-08:00"},"category":[{"scheme":"http://www.blogger.com/atom/ns#","term":"CAN"}],"title":{"type":"text","$t":"CAN BUS MESSAGE FRAMES - Remote Frame"},"content":{"type":"html","$t":"\u003Ca href=\"http:\/\/1.bp.blogspot.com\/_ycHwJEosotY\/SvoLBLV0alI\/AAAAAAAAA6o\/bjAQaSch3bM\/s1600-h\/Remote+Frame.JPG\"\u003E\u003Cimg id=\"BLOGGER_PHOTO_ID_5402642817836411474\" style=\"DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 320px; CURSOR: hand; HEIGHT: 121px; TEXT-ALIGN: center\" alt=\"\" src=\"http:\/\/1.bp.blogspot.com\/_ycHwJEosotY\/SvoLBLV0alI\/AAAAAAAAA6o\/bjAQaSch3bM\/s320\/Remote+Frame.JPG\" border=\"0\" \/\u003E\u003C\/a\u003E\u003Cbr \/\u003E\u003Cbr \/\u003E\u003Cspan style=\"font-family:arial;\"\u003ENormally, data transmission is performed on an\u003Cbr \/\u003Eautonomous basis by the data source node (e.g., a\u003Cbr \/\u003Esensor sending out a data frame). It is possible,\u003Cbr \/\u003Ehowever, for a destination node to request data from\u003Cbr \/\u003Ethe source. To accomplish this, the destination node\u003Cbr \/\u003Esends a remote frame with an identifier that matches\u003Cbr \/\u003Ethe identifier of the required data frame. The\u003Cbr \/\u003Eappropriate data source node will then send a data\u003Cbr \/\u003Eframe in response to the remote frame request.\u003Cbr \/\u003EThere are two differences between a remote frame\u003Cbr \/\u003E(shown in Figure 2-3) and a data frame. First, the RTR\u003Cbr \/\u003Ebit is at the recessive state and, second, there is no\u003Cbr \/\u003Edata field. In the event of a data frame and a remote\u003Cbr \/\u003Eframe with the same identifier being transmitted at the\u003Cbr \/\u003Esame time, the data frame wins arbitration due to the\u003Cbr \/\u003Edominant RTR bit following the identifier. In this way,\u003Cbr \/\u003Ethe node that transmitted the remote frame receives\u003Cbr \/\u003Ethe desired data immediately.\u003Cbr \/\u003E\u003Cbr \/\u003Ehttp:\/\/ww1.microchip.com\/downloads\/en\/DeviceDoc\/21801d.pdf\u003C\/span\u003E"},"link":[{"rel":"edit","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/6699851882820832653"},{"rel":"self","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/6699851882820832653"},{"rel":"alternate","type":"text/html","href":"http:\/\/rs232-rs485.blogspot.com\/2009\/11\/can-bus-message-frames-remote-frame.html","title":"CAN BUS MESSAGE FRAMES - Remote Frame"}],"author":[{"name":{"$t":"kop"},"uri":{"$t":"http:\/\/www.blogger.com\/profile\/03199950917117732729"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"16","height":"16","src":"http:\/\/img2.blogblog.com\/img\/b16-rounded.gif"}}],"media$thumbnail":{"xmlns$media":"http://search.yahoo.com/mrss/","url":"http:\/\/1.bp.blogspot.com\/_ycHwJEosotY\/SvoLBLV0alI\/AAAAAAAAA6o\/bjAQaSch3bM\/s72-c\/Remote+Frame.JPG","height":"72","width":"72"}},{"id":{"$t":"tag:blogger.com,1999:blog-32882751.post-4379188139424615953"},"published":{"$t":"2009-11-07T17:02:00.000-08:00"},"updated":{"$t":"2009-11-07T17:04:46.820-08:00"},"category":[{"scheme":"http://www.blogger.com/atom/ns#","term":"CAN"}],"title":{"type":"text","$t":"CAN BUS MESSAGE FRAMES - Extended Data Frame"},"content":{"type":"html","$t":"\u003Ca href=\"http:\/\/1.bp.blogspot.com\/_ycHwJEosotY\/SvYY7zul0jI\/AAAAAAAAA6A\/93mHqh7FV1s\/s1600-h\/Extended+Data+Frame.JPG\"\u003E\u003Cimg id=\"BLOGGER_PHOTO_ID_5401532218854462002\" style=\"DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 320px; CURSOR: hand; HEIGHT: 110px; TEXT-ALIGN: center\" alt=\"\" src=\"http:\/\/1.bp.blogspot.com\/_ycHwJEosotY\/SvYY7zul0jI\/AAAAAAAAA6A\/93mHqh7FV1s\/s320\/Extended+Data+Frame.JPG\" border=\"0\" \/\u003E\u003C\/a\u003E\u003Cbr \/\u003E\u003Cbr \/\u003E\u003Cspan style=\"font-family:arial;\"\u003EIn the extended CAN data frame, shown in Figure 2-2,\u003Cbr \/\u003Ethe SOF bit is followed by the arbitration field, which\u003Cbr \/\u003Econsists of 32 bits. The first 11 bits are the Most\u003Cbr \/\u003ESignificant bits (MSb) (Base-lD) of the 29-bit identifier.\u003Cbr \/\u003EThese 11 bits are followed by the Substitute Remote\u003Cbr \/\u003ERequest (SRR) bit, which is defined to be recessive.\u003Cbr \/\u003EThe SRR bit is followed by the lDE bit, which is\u003Cbr \/\u003Erecessive to denote an extended CAN frame.\u003Cbr \/\u003EIt should be noted that if arbitration remains unresolved\u003Cbr \/\u003Eafter transmission of the first 11 bits of the identifier,\u003Cbr \/\u003Eand one of the nodes involved in the arbitration is\u003Cbr \/\u003Esending a standard CAN frame (11-bit identifier), the\u003Cbr \/\u003Estandard CAN frame will win arbitration due to the\u003Cbr \/\u003Eassertion of a dominant lDE bit. Also, the SRR bit in an\u003Cbr \/\u003Eextended CAN frame must be recessive to allow the\u003Cbr \/\u003Eassertion of a dominant RTR bit by a node that is\u003Cbr \/\u003Esending a standard CAN remote frame.\u003Cbr \/\u003EThe SRR and lDE bits are followed by the remaining\u003Cbr \/\u003E18 bits of the identifier (Extended lD) and the remote\u003Cbr \/\u003Etransmission request bit.\u003Cbr \/\u003ETo enable standard and extended frames to be sent\u003Cbr \/\u003Eacross a shared network, the 29-bit extended message\u003Cbr \/\u003Eidentifier is split into 11-bit (most significant) and 18-bit\u003Cbr \/\u003E(least significant) sections. This split ensures that the\u003Cbr \/\u003ElDE bit can remain at the same bit position in both the\u003Cbr \/\u003Estandard and extended frames.\u003Cbr \/\u003EFollowing the arbitration field is the six-bit control field.\u003Cbr \/\u003EThe first two bits of this field are reserved and must be\u003Cbr \/\u003Edominant. The remaining four bits of the control field\u003Cbr \/\u003Eare the DLC, which specifies the number of data bytes\u003Cbr \/\u003Econtained in the message.\u003Cbr \/\u003EThe remaining portion of the frame (data field, CRC\u003Cbr \/\u003Efield, acknowledge field, end-of-frame and intermission)\u003Cbr \/\u003Eis constructed in the same way as a standard data\u003Cbr \/\u003Eframe\u003Cbr \/\u003E\u003Cbr \/\u003E\u003Cspan style=\"color:#009900;\"\u003Ehttp:\/\/ww1.microchip.com\/downloads\/en\/DeviceDoc\/21801d.pdf\u003C\/span\u003E\u003C\/span\u003E"},"link":[{"rel":"edit","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/4379188139424615953"},{"rel":"self","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/4379188139424615953"},{"rel":"alternate","type":"text/html","href":"http:\/\/rs232-rs485.blogspot.com\/2009\/11\/can-bus-message-frames-extended-data.html","title":"CAN BUS MESSAGE FRAMES - Extended Data Frame"}],"author":[{"name":{"$t":"kop"},"uri":{"$t":"http:\/\/www.blogger.com\/profile\/03199950917117732729"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"16","height":"16","src":"http:\/\/img2.blogblog.com\/img\/b16-rounded.gif"}}],"media$thumbnail":{"xmlns$media":"http://search.yahoo.com/mrss/","url":"http:\/\/1.bp.blogspot.com\/_ycHwJEosotY\/SvYY7zul0jI\/AAAAAAAAA6A\/93mHqh7FV1s\/s72-c\/Extended+Data+Frame.JPG","height":"72","width":"72"}},{"id":{"$t":"tag:blogger.com,1999:blog-32882751.post-4435790483703926145"},"published":{"$t":"2009-11-02T18:23:00.000-08:00"},"updated":{"$t":"2009-11-02T18:28:00.890-08:00"},"category":[{"scheme":"http://www.blogger.com/atom/ns#","term":"CAN"},{"scheme":"http://www.blogger.com/atom/ns#","term":"Protocol"}],"title":{"type":"text","$t":"CAN BUS MESSAGE FRAMES - Standard Data Frame"},"content":{"type":"html","$t":"\u003Cspan style=\"font-family:arial;\"\u003E\u003Cstrong\u003EStandard Data Frame\u003C\/strong\u003E\u003C\/span\u003E\u003Cbr \/\u003E\u003Cbr \/\u003E\u003Ca href=\"http:\/\/3.bp.blogspot.com\/_ycHwJEosotY\/Su-U5nqrxdI\/AAAAAAAAA5I\/lJi_F-HfQDI\/s1600-h\/Standard+Data+Frame.JPG\"\u003E\u003Cimg id=\"BLOGGER_PHOTO_ID_5399698195861980626\" style=\"DISPLAY: block; MARGIN: 0px auto 10px; WIDTH: 320px; CURSOR: hand; HEIGHT: 126px; TEXT-ALIGN: center\" alt=\"\" src=\"http:\/\/3.bp.blogspot.com\/_ycHwJEosotY\/Su-U5nqrxdI\/AAAAAAAAA5I\/lJi_F-HfQDI\/s320\/Standard+Data+Frame.JPG\" border=\"0\" \/\u003E\u003C\/a\u003E\u003Cbr \/\u003E\u003Cspan style=\"font-family:arial;\"\u003EThe CAN standard data frame is shown in Figure 2-1.\u003Cbr \/\u003EAs with all other frames, the frame begins with a Start-\u003Cbr \/\u003EOf-Frame (SOF) bit, which is of the dominant state and\u003Cbr \/\u003Eallows hard synchronization of all nodes.\u003Cbr \/\u003EThe SOF is followed by the arbitration field, consisting\u003Cbr \/\u003Eof 12 bits: the 11-bit identifier and the Remote\u003Cbr \/\u003ETransmission Request (RTR) bit. The RTR bit is used\u003Cbr \/\u003Eto distinguish a data frame (RTR bit dominant) from a\u003Cbr \/\u003Eremote frame (RTR bit recessive).\u003Cbr \/\u003EFollowing the arbitration field is the control field,\u003Cbr \/\u003Econsisting of six bits. The first bit of this field is the\u003Cbr \/\u003EIdentifier Extension (IDE) bit, which must be dominant\u003Cbr \/\u003Eto specify a standard frame. The following bit, Reserved\u003Cbr \/\u003EBit Zero (RB0), is reserved and is defined as a dominant\u003Cbr \/\u003Ebit by the CAN protocol. The remaining four bits of the\u003Cbr \/\u003Econtrol field are the Data Length Code (DLC), which\u003Cbr \/\u003Especifies the number of bytes of data (0 – 8 bytes)\u003Cbr \/\u003Econtained in the message.\u003Cbr \/\u003EAfter the control field is the data field, which contains\u003Cbr \/\u003Eany data bytes that are being sent, and is of the length\u003Cbr \/\u003Edefined by the DLC (0 – 8 bytes).\u003Cbr \/\u003EThe Cyclic Redundancy Check (CRC) field follows the\u003Cbr \/\u003Edata field and is used to detect transmission errors. The\u003Cbr \/\u003ECRC field consists of a 15-bit CRC sequence, followed\u003Cbr \/\u003Eby the recessive CRC Delimiter bit.\u003Cbr \/\u003EThe final field is the two-bit Acknowledge (ACK) field.\u003Cbr \/\u003EDuring the ACK Slot bit, the transmitting node sends\u003Cbr \/\u003Eout a recessive bit. Any node that has received an\u003Cbr \/\u003Eerror-free frame acknowledges the correct reception of\u003Cbr \/\u003Ethe frame by sending back a dominant bit (regardless\u003Cbr \/\u003Eof whether the node is configured to accept that\u003Cbr \/\u003Especific message or not). The recessive acknowledge\u003Cbr \/\u003Edelimiter completes the acknowledge field and may not\u003Cbr \/\u003Ebe overwritten by a dominant bit.\u003Cbr \/\u003E\u003Cbr \/\u003E\u003Cspan style=\"color:#009900;\"\u003Ehttp:\/\/ww1.microchip.com\/downloads\/en\/DeviceDoc\/21801d.pdf\u003C\/span\u003E \u003C\/span\u003E"},"link":[{"rel":"edit","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/4435790483703926145"},{"rel":"self","type":"application/atom+xml","href":"http:\/\/www.blogger.com\/feeds\/32882751\/posts\/default\/4435790483703926145"},{"rel":"alternate","type":"text/html","href":"http:\/\/rs232-rs485.blogspot.com\/2009\/11\/can-bus-message-frames-standard-data.html","title":"CAN BUS MESSAGE FRAMES - Standard Data Frame"}],"author":[{"name":{"$t":"kop"},"uri":{"$t":"http:\/\/www.blogger.com\/profile\/03199950917117732729"},"email":{"$t":"noreply@blogger.com"},"gd$image":{"rel":"http://schemas.google.com/g/2005#thumbnail","width":"16","height":"16","src":"http:\/\/img2.blogblog.com\/img\/b16-rounded.gif"}}],"media$thumbnail":{"xmlns$media":"http://search.yahoo.com/mrss/","url":"http:\/\/3.bp.blogspot.com\/_ycHwJEosotY\/Su-U5nqrxdI\/AAAAAAAAA5I\/lJi_F-HfQDI\/s72-c\/Standard+Data+Frame.JPG","height":"72","width":"72"}}]}});