1193:
to see an dominant bit (binary zero - active) within that slot. Each node that receives a valid CAN frame is required to send a dominant bit (actively drive a binary zero on the CAN wires) within the ACK slot. The active zero overrides the passive one and the transmitting node will see an ACK. Since the transmitting node sees an ACK it knows that the frame was received by at least one node. If the transmitting node does not see an ACK it immediately re-sends the frame. If only one node is operating on the network, the first frame it sends will not be ACKed and it will immediately resend it, over and over. This will saturate the network with CAN traffic. This synchronizing ensures that the CAN receiver (who is transmitting the ACK) generates the ACK in a position that the transmitter sees it and does not rebroadcast the frame.
1197:
on every recessive to dominant transition after that. For the receiver to resync, the bits being transmitted must change value. Since the data being transmitted could be all zeros or all ones, CAN 2.0 and ISO11898-1 call for bit stuffing. When the transmitter detects five consecutive bits with the same value (including a stuffed bit) it "stuffs" a complimentary bit into the data stream. The receiver must then "unstuff" the bit from the incoming data stream. Bosch's CAN 2.0B specification does indeed state that "The maximum length between two transitions which can be used for resynchronization is 29 bit times". I don't know why since the same spec also calls for bit stuffing at five bits meaning that there will be at most ten bits between two recessive to dominant transitions.
2698:
on systems that send proprietary data around cars on CAN bus; but we never referred to it as
Controller Area Network, which is the origin of the CAN name, but essentially generic in itself. Even the course link that Greg gives uses the term only once, in introducing the acronym. A few sources actually introduce the acronym with lowercase controller area network, suggesting that they specifically wanted to avoid giving the impression that Controller Area Network is the name. As for the first RM above, it was fix a bizarre mis-punctuation; the change to lowercase was done back in 2008.
1180:. On the other hand the CAN2.0 spec and ISO11898-1 discuss bit synchronization, which is what probably causes many, including the CiA in Kevin's link above, to call it synchronous. The key difference between CAN and what I call synchronous is that CAN transceivers do not synchronize their data reception by the means of a clock edge, but derive a clock by the data transmission edge. The synchronization is bit level synchronization between nodes where each node monitors the data edges and can adjust the point within the bit that it samples the data.
3674:
being their preferred way of naming it. This mess revolves around the original group not choosing a better name that didn't have an acronym that is identical as another common word. I'm not 100% opposed to renaming the article, but I am opposed to renaming it every couple of years. That why I'd rather have a longer discussion about the pro's and con's of each name, then try to flush out which one is best. Once we are done, then we could vote on it, and archive the entire discussion for future reference when someone wants to rename it again. â˘
1978:"Time constraints require efficient use of test processes, available resources and tools to ensure the highest levels of product quality are delivered at the conclusion of the integration testing phase. Testing teams must possess a means for identification and isolation of faults, along with the experience needed for quickly assessing possible root causes. The time required for actually tracking down and solving the root failure mode can often be extremely difficult and not time effective in widely distributed processes."
583:
777:
756:
562:
488:
787:
1981:"Testing tools must be scalable, flexible, and integrate able to provide test coverage for all pertinent levels of the OSI model. The ideal test tools themselves must provide the knowledge and know-how of skilled engineers by identifying questionable conditions, and then using reasoning to guide the test engineer in solving the issue. The tool should also be easily configurable, comprehensive, include predefined test libraries, and provide extremely reliable measurements.."
357:
330:
4617:
222:
478:
457:
253:
243:
191:
688:
667:
3781:
425:
593:
945:
905:
865:
1990:
for efficient use of test processes? What processes are those, and which apply to CAN systems integration versus other systems integration scenarios?), "Testing teams must possess a means for identification and isolation of faults" (please enlighten me; how is THAT supposed to be achieved in the context of CAN systems integration? Do you actually know how? Please say so!)
2562:, and more, among those with lowercase usage and free PDFs online. The real proper name is CAN; there is no evidence that I can find that what CAN stands for is also a proper name. There is plenty of precedent in reliable sources to treat "controller area network" like "local area network" and "wide area network": things one makes acronyms of, but not proper nouns.
1923:
Freescale, Renesas, you-name-it, has to pay. This includes also any implementation in ASIC or FPGA. Because, e.g. Altera, does not distribute a CAN implementation, but I do so, if I implement CAN in one of the Altera chips. So I would have to pay. But anybody who uses the chips, including the one I distribute based on the Altera, does not has to pay anything.
2403:. The plural in particular suggests that "controller area network" can be considered a common noun. I'm not an expert on this topic and this article is badly referenced so I can't rely on usage in the article's sources to determine whether or not it's used as a common noun. Just like ISO style, Knowledge style can differ from general usage. For example,
4891:
When separate power supply is required to power a device (eg full beam bulbs) is a separate plug/socket used to connect the device to power?, or do some manufacturers combine a power cable with the bus and use a beefier plug/socket so that each device only requires one male and one female connector?
4825:
There is no limit from the protocol. There is a limit by the transceiver used, bacause a choosen transceiver can drive only a certain amount of current and such only a certain number of nodes can be connected. The weakest transceiver defines the usable nodes in a network. There may is also limitation
3692:
That sounds reasonable but it doesn't appear anyone took the initiative to start that discussion. I read through the previous discussion before opening this RM and I decided to take a different approach and I encourage you to not get caught up in the means and support the move if you believe it is an
2810:
First one's a training house, who endemically over-capitalise because it makes things sound More
Important. Second one is German, and German sources also have an inherent tendency to capitalise nouns, particularly compound nouns. You'll note from Bosch though that for every full version of the name,
2224:
The digital canbus codes are transmitted along a two wire canbusnetwork referred to as a BUS hence the word CANBus or CAN BUS. There are other interfaces used to get CAN codes as most manufactures will not share this information easily, if you are requiring a product that will bridge your device with
1196:
Since CAN data is NRZ, there are only transition edges for the receiver to synchronize to. I.e. when the value of the current bit being transmitted is different than the value of the previous bit (zero-to-one, or one-to-zero). Hard synchronization occurs at the start bit and resynchronization occurs
1131:
say "The bus consists of a single channel that carries bits. From this data resynchronization information can be derived." I'm new to serial protocols, and to
Knowledge... just making sure that "asynchronous" is the correct classification of CAN... please let me know. If so, I'll figure out how to
2697:
I would be the first to agree to capitalization if the sources all did that. As I pointed about above the defining standard does not, and I linked several books and papers that do not, from among the ones visible on the web; I can link more. And for the record, I am not incompetent; I have worked
1778:
In its place I'm adding a new table with the ID bits and contention resolution described in the text. This is my first shot at a wiki table, and I'm not very happy with it. I would be happy if someone who knows tables would improve it. Specifically, the ID10, ID9, etc. needs to have a label above
1250:
Any message in CAN is always transmitted in broadcast. Because the transmitter does not have any knowledge about the receivers. Any receiver have to decide by itself, if it is interested in a certain message. The filtering can be done in software or in hardware. If the filtering is done in hardware,
1192:
The second is that there is definitely an ACK (Sorry Kevin but you're wrong, see Bosch's CAN 2.0 spec in the link at the start of this section). Towards the end of the CAN data frame is the ACK field. The transmitting node sends two recessive bits (binary one - passive) in the ACK slot and expects
1095:
Is it plesiochronous ? The data is sent at a rate with a tolerance of within say 50 ppm of a standard bit rate and since the other end is reading data, it looks for frames and bytes. The receiver then recovers the clock rate which was implicit in the received data (from the voltage transitions and
1012:
Agreed. NMEA 2000 is definitely derived from CAN, since the marine engine and electrical people, rather than the more electronic (navigation, communications, etc.) seemed to drive it. Having been through the IEEE 802.4 Token Bus for manufacturing, which was eventually overtaken by 802.3, using fiber
2927:
has SI purity and achieves consistency across the project (and we are a publishing house and can have our own house manual of style, yadda yadda). This violation of
Technical Writing 101 is amazing to me because the entire discipline of gravimetryâfrom NASA and their satellite measurements to boots
1271:
I presume you have basically four equal ECUs that you wish to selectively talk to. Unless you have software control of the ECUs to put in place some kind of addressing in the identifier (such as reserving the first two bits as an ECU address) then you can't do it without isolating each ECU on it's
1203:
To answer Julian's questions, a transition is when the next bit transmitted changes value from the previous bit. Two transitions means when the bit value changes then changes back. A "bit time" is the length of time to transmit a single bit, and is the reciprocal of the bit rate. A 125k bit rate
995:
States Intel developed the first silicone for CAN bus in 1987... also states that CAN Bus developed by Bosch in 1986 probably the 1989 date of the BMW technical document is when it was first used / implemented and or the standard finalized. However the above PPT does not cite any source I will only
1993:
The last quote is really a jewel: it is an utopian tool that is supposed to do the work of the test engineer so s/he does not have to. Does it actually exist, or it is just a figment of someone's imagination? In absence of concrete examples of such tool, I would go for the latter rather than the
1989:
Flags for platitudes vs real knowledge are phrases such as "to eliminate all causes of system behavior which may negatively impact the manufactured products reliability" (that is a general quality goal that is not specific of CAN), "efficient use of test processes" (tell me, where is there NO need
3820:
capitalize when forming acronyms. That and the common appearance in titles and headings and tables explain much of the caps usage. The rest is by people who think of it as a proper name or prefer to capitalize it for emphasis, but that doesn't make a case that we should do the same, in light of
3673:
uhhhhh, naming of other articles certaining does have bearing, otherwise there wouldn't be numerous guidelines on
Knowledge about the topic. I've seen numerous variations for "CAN" in magazine articles, datasheets, online articles, blogs. No matter what you pick, someone will whine about it not
3659:
Naming used by other articles has little bearing. What's of primary concern here is what is the name the technology is most commonly known by in the references. If it is CAN or
Controller Area Network, the article should be "Controller Areas Network". If it is CAN bus, CAN Bus or CANbus, then the
1922:
As with any patent someone holds, in the whole producer/user-chain only one pays for the licence, depending on whom is infringhing the patent. Bosch has decided that anybody who distributes CAN in some kind of implementation has to pay the licence. That means, any chipmanufacturer, like
Infineon,
1162:
in CAN specB2.0, it said "Clocking information may be derived from transitions from one bit value to the other. The property that only a fixed maximum number of successive bits have the same value provides the possibility of resynchronizing a bus unit to the bit stream during a frame. The maximum
2767:
I'm in the industry. I stopped capitalising it when I realised I was copying the name from official specs and having to add the capitalisation myself. The reason "anyone in the industry" capitalises it is only because no-one ever calls it "controller area network", it's always called CANbus (and
1475:
Can soemone explain and then fix the table in the article (copied below for reference. I understand CAN, I understand dominant and recessive, I understand the AND function. I don't understand the table - what are the columns what are the rows, why is one cell empty, why are some entries bold? --
1175:
CAN does not include a clock in the data transmission. All nodes on the CAN network must operate at the same bit rate, and the error between each node's internal clocks must be within tolerance, for the nodes on the network to communicate. This is the same as a PC's RS-232 serial port which is
3805:
that's interesting but in the references I examined, the first incidence is spelled out ("Controller Area
Network (CAN)") and the references following use the acronym ("CAN"). The articles that use "CAN bus" use it repeatedly. If you look up "CAN" in the Ngram viewer you find that it is a giant
2415:. The blogs that used "Universal Serial Buses" were referring to multiple versions of the USB standard. I also haven't seen a respectable sources treat "Universal Serial Bus" as a generic thing (a bus), but rather as describing a connector, or in the redundant form "USB bus." Also in Knowledge,
3838:
I think you may have missed my point. Sources that use "CAN bus" use that phrase for all instances. Sources that use "Controller Area
Network" use that once and then use "CAN" for further instances. My point is that n-gram viewer blindly counts instances and is not necessarily going to give an
3503:
Independent of how specific it is, the official protocol name seems to be CAN bus, and many sources, and especially better edited sources like books, interpret "controller area network" as generic, and set it in lower case. That's usually all the evidence we need to conclude that caps are not
1997:
These platitudes are, in fact, not constrained to CAN system integration; it is common to ANY systems integration. They add no value to this article (or any other). I propose to strike them out and simply describe the systems integration process, if the author has no real knowledge of how to
1884:
Indeed, the CAN protocol license on the Bosch website doesn't cover use of existing CAN controllers, but is intended for ASIC developers or FPGA programmers. I can see no limitation on the use of CAN in NXP's LPC2129 microcontroller, for example, but I expect that NXP had to pay a license fee.
1327:
You need a CAN controller (e.g., MCP2510 by
Microchip) and a CAN transceiver (e.g., PCA82C250 by Philips). The controller gets you a logical interface and transceiver gives you physical interface. Plus the software to interface with the controller. You can get microcontrollers with built-in
3819:
Certainly you wouldn't want to use n-grams to look at just CAN. But it does show that "CAN bus" is much more common than "Controller Area Network", and also that the lower-case form is not uncommon. I agree with you that "Controller Area Network (CAN)" is very common, since people typically
1284:(used for heavy trucks and buses) which uses 29-bit addresses, has a method of sending messages selectively to one ECU. using 8-bit ECU addresses. There is no room for that in the 11-bit addresses normally used for passenger cars. When wished, this must be placed in the payload data.--
2157:
is used for a range between numbers and should not be used to hyphenate or compound words/titles. (In this response, I use the en-dash after the word "support" to lead into my paragraph and before signing.) The en-dash is 100% being used incorrectly in the name of the article. â
1381:
Since I am affiliated with the company Softing I should not add this link. Instead, I would like to ask you as a neutral editor to evaluate this link and to add this link to the external link section of the Controller Area Network article if you think the link provides valuable
1016:
That ISO and NMEA standards are expensive to purchase may be a factor. IEEE seems to be moving to more of an open publication model, which the IETF always has been used. One of the reasons for the failure of OSI protocols was the cost of the documents, just to evaluate
1403:
I found some misinformation in the site: "Remark: CAN Specification 2.0 B passive implementations canât store or transmit Extended Data Frames; CAN Specification 2.0 B active implementations can store and transmit Standard Data Frames as well as Extended Data Frames"
2650:
The job of any good encyclopedia is to educate its readership on a particular subject and properly prepare them for their continuing studies elsewhere. We do no reader a favor by mangling the spelling from the way all industry insiders and experts always spell the
4887:
What items on a vehicle are typically controlled by the CANbus? What items are typically not controlled by the bus? Do the power lines in the D plugs only power the transceivers+controllers, or do they power electrical consumers too (eg indicator light)?
1396:
Selket, I find the content behind the link interesting and valuable - I don't see a problem with the fact that it comes from a company. It's good practice of capable companies to contribute content and make it accessable for everyone. This is a good example.
2624:
Specific type. It is a particular standard for a particular microcontroller bus. My best friend is an Ăźber expert in this stuff and has done it since the dawn of the digital controller age (back before the 8051). The term refers to *a particular one* and is
1144:
It's synchronous and broadcast (no ACKing, a message is fully sent once it's emitted). The leading edge of the synchronization bit begins automatic re-synchronization. Bits after that are counted out by time sequence, not by a seperate reference signal.
4964:
I don't know what happened there. I had no intention of making that revert. All I can guess is the pointer just happened to be sitting on revert and something fell on the mouse. It has been one of those days. Anyway, I reverted my revert. Cheers.
2419:
was recently moved to the uncapitalized form (though I don't think I'd have supported that move). "Open source" is rarely hyphenated in English-language sources, but it's hyphenated as a compound adjective in Knowledge. Linguists (!) don't hyphenate
4946:
You didn't explain why you reverted me. I thought I gave an adequate explanation of what I was doing im my edit summary. The edit that added the clarification needed tag actually succeeded in making the whole passage far less clear to the reader.
2541:
That's why I suggested we follow the ISO standard instead; that would seem to be the "most reliable" for an article on the standard. Other reliables sources that use lowercase, thereby suggesting that term is not accepted as a proper name, include
1975:"The integration testing phase requires that the âliveâ ECUâs be interconnected for the first time and the ultimate goal of this phase is to eliminate all causes of system behavior which may negatively impact the manufactured products reliability."
1926:
As normally, nobody implements CAN but uses it like any other serial connection, like RS232 or Ethernet, it is free of charge. Almost nobody implements RS232 or Ethernet by himself but uses available controller chips. The very same applies for CAN.
1072:
I used a binary division algorith with the data of 000000010100000000100000001b (data from the image) with a polynomial 1100010110011001b (0xC599), as descibed in the CAN standard and got 111011101010011b (0x7753), which confirms your observation.
4707:
The article starts out with defining a CAN bus as a vehicle bus. IMHO, that's overly specific: It was developed by Bosch who certainly had vehicle applications in mind. However, it's also used e.g. in control cabinets for industrial machinery.
1013:
rather than coax to get around noise problems, I do take it with a grain of salt. In marine applications, I am seeing Ethernet for some of the more general purpose computer interaction, while NMEA 2000 is more for the dedicated microprocessors.
5008:
As I understand it, the article confuses frames (the basic units of transmission) with messages (information being communicated, via a Data Frame). Lots of references to messages should be changed to frames, among other clarifications.
2554:. It's actually harder to find books that capitalize it for an ordinary use is a sentence; almost all capitalized uses are in paper titles, headings, and acronym definition. Similarly there's no shortage of scholarly articles like
1308:
Are these two bus's compatible with each other? I have seen PCI instrument cluster receiving messages on a CAN PCM. I'm not sure if the instrument cluster was compatible with both PCI and CAN or if PCI and CAN are mostly compatible.
2658:
changed it. Wrong; the article had been correct from when it was first created in 2003 (by editors who understand this stuff) through 2009 when those two editors at the RM patted each other on the back and said âGood showâby all
1880:
The article states that CAN is often used due to the low cost of CAN controllers, but then goes on to state that official uses of CAN must pay license fees to Bosch. The article does not state what constitutes an official usage.
3414:
5023:
2864:
2827:
Sorry if my statement "uses the term only once, in introducing the acronym" was slightly misleading as to the form; but I'll stick to it for the principle of why they capitalized. Ah, but you weren't talking to me; sorry.
2342:
is the closest I can think of. Title case is appropriate for the subject of this article as it is a proper noun, the name of a particular, standardized implementation of a network for controllers. A google survey confirmed
1004:
I don't know anything about CAN, but I was looking into NMEA, which has recently evolved from its serial carrier roots (see NMEA 0183) to NMEA 2000, which appears to use CAN. I'd have thought that was worth recognising.
1842:
Does anyone have a reference for this? I've added the text to the page on the basis that what I've added has to be better than simply overloading the acronym without explanation, but there should probably be a citation.
1220:
I found that I had a number of misunderstandings of this subject and have edited my previous comments to correct the most glaring errors. I hope to use my new (miss?)understanding to expand the Bit timing section soon
4925:
2522:
1; yes, the originator of the term, Bosch, wants it to be capitalized; no surprise there. But it became an official standard, which is what the article is about, and the official standard does not capitalize
153:
2257:
Although the original patents on the 1980's implementations are obviously expired, what part of the new patents still forces people to license them? It seems that you could just not use the new features?
1985:
The above quotes from this article shows a statement of goals or how things ought to be, with no indication whatsoever of how to achieve it given the difficulties faced in the CAN integration process.
2526:
2; if you download the PDF and look, it includes "Controller Area Networks" and a heading "Controller area network." Certainly not much support for a proper noun interpretation of a protocol name here.
2496:
for the standard they created. It is not within the purview of mere wikipedians to second-guess how the real world applies or misapplies the English language nor endeavor to lead by example in hopes of
2464:. If it's a specific standard, it's OK to respect the capitalization in the standard, which is lower case. It is not unusual to find it lower case in books, and very common in scholarly articles.
2424:. Applying style guidelines is a tricky matter. I'd be interested in revisiting the question when this article is well enough referenced to give a good sampling of reliable, high-quality sources. â
3810:. The Ngram viewer just counts total instances and is not intelligent enough to give accurate results given the way "Controller Area Network" and "CAN" is used in the references I've examined. ~
1047:
I noticed the same thing. When I transmit the same packet from an STM32, I get a very different CRC than what's depicted in the diagram. According to the hardware, the correct CRC is 0x7753.
738:
2210:
1607:
OK I've sussed it. The left column and top row are the inputs and the bottom right 2*2 is the result. I'll change the table so I can understand it and if you others dislike it, revert it. --
3227:
In the physical layer diagram nodes are labeled SG1 SG2 .. SGn. What is "SG"? Is this a German acronym? Should we replace it with ECU or Node (the terms used elsewhere in the article).
2719:
Usually, the document writes of âCAN.â But âController Area Networkâ is written three times. This is by Bosch now, and all three times it is all uppercase. This is exactly like Intelâs
3354:. Previous lengthy discussion about how the subject is or is not capitalized in sources is not directly relevant. If you don't like the caps, please provide justification for CAN as a
2221:
Data communications protocol (digital codes) to control and monitor functions on most modern canbus vehicles are identified using diagnostic tools only available to trusted Dealers.
4862:
What is meant (if any)? That the CRC value is invalid for the example CAN message (resulting in an error frame)? Where does bit stuffing come in (it also happens in the CRC field)?
4653:
1888:
I suspect that the statement on the page is partially incorrect. I have no citation to back this up, but there is also no citation backing up the full scope of the existing text.
4783:
1200:
To me, this means that CAN data is transmitted in an asynchronous format, but all of the nodes on the CAN network are "synchronized" to sample the transmitted data at same time.
5106:
4736:
as a wl in the lead. It needs to keep that. I've no objection to anything expanding on this with non-vehicle applications, but it should keep vehicle bus in the prime position.
4702:
2682:
that something be different in the world, does not make it incumbent that Knowledge allow itself to be exploited as a vehicle to change reality to what some think is better.
1864:
1303:
4777:
2666:
is editors who are active in how the English language should properly do this or that but who have next-to-zero experience in this particular discipline. And, like always,
4751:
3641:- because need more discussion and analysis of other "bus" article naming methods before a vote, instead of playing "article name" Ping-Pong. See the template below. â˘
2950:
was, but the pure SI units would also probably confuse me. Not that I'm arguing for (ft/sec/sec)/ft, but some us grew up on that, too. Hey, that would also be 3.1E-06.
1317:
my question is what components both hardware and software would it take to create a CAN BUS between several microcontrollers or FPGAs. Where can I find such Information?
4921:
2407:(a common noun IMO) is uncapitalized in Knowledge, despite many American-English sources using capitals. I've never seen a respectable English-language source pluralize
1947:
From the article: "Interframe spacing between frames is normally 96 bits. It provides time for machines on an Ethernet network to listen and have a chance to send data"
1364:
A representative of a company that maintains a CAN tutorial website asked me to add them to the external links section. He or she did not to so his/her self because of
1243:
In my application 4 ECUs are connected to the CAN bus.Can I send messages selectively to one ECU and not to other ECUs using CAN?How to use mask or filters to do this?
2132:
1832:
1627:
3259:
Can you provide a background as to why the extended identifiers were added to the standard frame, making it extended frame? Was it that 11 bits were not sufficient?
1235:
1081:
2848:
in that case? That would avoid both the ambiguity of this being a specific kind of bus/network and the, as usually little more than time-wasting, spelling debate. â
1374:
1176:
considered asynchronous. Many engineers (well at least this engineer) consider CAN to be asynchronous data transmission. Freescale calls it asynchronous in this
1061:
147:
5037:
2237:
434:
340:
2519:
Greg, you are mistaken about those sources. I agree that it is important not to stray too far from sources; but look more carefully at those external links:
1413:
544:
312:
5101:
3342:â Most commonly known as CAN or Controller Area Network and secondarily as CAN bus, CAN Bus or CANbus. CAN is normally expanded in technical documents and
2272:
AFAICT, the distinction will become irrelevant soon: a patent based on documents published in 1991 must also be close to expiring, if not already expired.
2245:
1107:
439:
1894:
1844:
2904:
discipline if none truly exists. I just have no patience for wikipedians who seek cross-project consistency and try to push Good IdeasŠâ˘ÂŽ, like how our
843:
415:
1858:
1186:
The first is that for the CAN arbitration scheme to work, all of the nodes need to be synchronized so that they send or receive bits at the same time
3271:
2233:
1902:
1421:
1020:
To what extent should NMEA 2000 be integrated into this article? The lead starts off with respect to automobiles, but is not the applicability wider?
4929:
4671:
1268:. Instead, it has message identifiers that say "this is what's in this packet" and each & every node has to decide to process it or discard it.
3472:
by saying "Use lowercase, except for proper names." "Controller area network" is not a proper name, though the name of the protocol, CAN, may be.
2735:
4806:
1812:
While I can accept that ECU can stand for electronic control unit. DaimlerChrysler (as was) always used ECU to refer to the Engine Control Unit!
1312:
649:
5136:
4791:
1916:
639:
1172:
This section has not been updated in years, but it is so full of wrong information and unanswered questions that I just can't leave it as is.
5096:
1951:
1908:
1794:
1780:
1222:
1207:
1255:
3267:
5126:
5076:
4612:
Interfaces are listed by their speed in the (roughly) ascending order, so the interface at the end of each section should be the fastest.
3577:, then I'm happy to have this move proposal rejected. I've reviewed the references and external links cited in the article and find that
3304:
Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a
986:
534:
302:
4726:
5161:
5091:
4760:
specification (no mention in Knowledge, at the time of writing), specifies a Single Wire (plus ground) physical layer for the CAN bus.
4057:
2023:
I'm helping reduce the platitudes and improve the knowledge density in other sections of this article. If I step on toes, let me know.
833:
405:
79:
2281:
5111:
5081:
4585:
1463:
4214:
3660:
existing title ("CAN bus") is good. (This is not to be confused with the capitalization use in the references. Capitalization is a
3449:
1821:-I always understand ECU to mean engine control unit in the context of automotives. BMW calls it "DME" Digital Motor Electronics.
2777:
1332:
886:
5166:
5151:
5131:
4818:
4077:
2854:
2678:. In short, this RM is properly settled not by nose count, but by the strength and weight of the arguments. Just because someone
2456:
728:
3557:
3539:
2167:
1375:
http://www.softing.com/home/en/industrial-automation/products/can-bus/more-can-bus/communication/broadcast.php?navanchor=3010076
4766:
3884:
3724:
2619:
2068:
510:
279:
4711:
I'd like to update the article by saying just that: designed mainly as a vehicle bus but now also used in other environments.
3087:
3069:
3060:
We seem to have converged nearly on CAN bus. Either move it that, reopen it to see if we agree, or make a new one for that.
3055:
2820:
2805:
2724:
2473:
2384:
1950:
This is obviously incorrect. The correct interframe spacing is something like 6 bits, and Ethernet has nothing to do with it.
1157:
2932:
We always do our readers a service by using the vernacular truly used in the field without prejudice against the true facts.
2880:
2338:â This request follows the example of other wikipedia articles on technical standards and specifications for network busses.
85:
4835:
4745:
3793:
3756:
3405:
2514:
1459:
by 24.91.109.193 to TekNewell, which seems to be nothing more than a commercial software suite for interfacing with CAN? --
1276:
1119:
5121:
5071:
4912:
4799:
Is there some reasonable limit? 70 requires 6+ bits (i.e. 7 or more). Is there something else that constrains this to 70?
4688:
4265:
3936:
3654:
3434:
2691:
2258:
2131:â An n-dash between controller and area doesn't make grammatical sense. A hyphen would be an option grammatically, but the
1828:
1623:
1090:
809:
381:
4920:
For new students of CAN Bus, this could be very confusing. CAN Bus itself cannot take any input nor process informations.
2959:
2941:
2837:
2753:
2707:
2589:
2571:
2186:
1936:
5156:
5141:
5086:
5003:
3181:
2990:
2538:
6 uses it in text only as "Controller Area Networks"; this can't be the name of a protocol, and suggests a generic usage.
2447:, which Knowledge lowercases. Anyways, this is the proper name of a specific protocol, regulated by a specific entity. --
2433:
1115:
1077:
926:
3971:
3843:
3833:
3814:
3774:
3697:
3687:
3668:
3517:
3498:
3481:
3460:
2445:
2400:
2393:
4318:
4157:
4087:
3216:
Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.
3114:
Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.
3018:
Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.
2305:
Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.
2273:
2204:
Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.
2094:
Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.
1293:
1057:
274:
on Knowledge. If you would like to participate, you can choose to edit the article attached to this page, or visit the
30:
1907:
It is my understanding as well that FPGA/ASIC developers pay a license fee to Bosch. Users of CAN controllers do not.
168:
4147:
3548:. Leaving it at CAN bus is a fine alternative; I was just saying where it would go "if we don't like the acronym".
1230:
1215:
704:
501:
462:
275:
266:
227:
3625:
3601:
3447:
is what's directly applicable here. Examples of how capitalization is handled for similar topics can be found here:
3198:
1640:
This table is so confusing (and pointless) that I'm deleting it. If you are interested in what is was, here it is.
135:
5146:
4245:
3491:
3254:
3243:
2675:
2241:
966:
615:
2266:
5116:
4696:
1354:
800:
761:
364:
335:
99:
44:
5018:
4995:
4979:
3279:
2485:
1127:
My first question about CAN is: is it asynchronous, synchronous, or both? It seems it is asynchronous -- the
4814:
4037:
2946:
True, such cases need to include alternative forms in parens. Not being into gravimetry, I didn't know what a
1631:
104:
20:
3132:
2893:
truly and most authoritatively handle it. If there are multiple ways, it wouldnât hurt to be up front and say
1416:
4589:
4240:
4209:
2529:
3 has it only in title and in acronym definition; no significant support here for proper name interpretation.
2366:
2322:
2032:
1187:
891:
74:
3862:
2117:
5056:
4874:
4187:
3041:
2013:
1959:
1128:
990:
695:
672:
202:
4658:
I have no idea what is the cause, but the links to other languages are gone. I see them just fine on e.g.
3377:
3326:
2144:
4917:"The CAN bus also takes inputs from the rain sensor to trigger the rear windscreen wiper when reversing"
4907:
4513:
4452:
4307:
3275:
2791:
2783:
2713:
2638:
2493:
2124:
2017:
1611:
1480:
1085:
606:
567:
129:
65:
3163:
2489:
2441:
The capitalization in ISO standards depends of who writes. For example, this other standard capitalizes
1836:
1373:
Question: Could you please evaluate the following link that leads to a very comprehensive CAN tutorial?
1065:
4984:
Thanks, no problem. I've made my own fair share of stupid mistakes on Knowledge so I can't complain.
4692:
4659:
4112:
3877:
2788:
A full-day hands-on training class about the Controller Area Network (also known as CAN bus or CANbus).
2646:
A full-day hands-on training class about the Controller Area Network (also known as CAN bus or CANbus).
2064:
1942:
1802:
1788:
1341:
1177:
4482:
1852:
1391:
1024:
4167:
3386:- generally we avoid acronyms unless the acronym is actually better known than the spelled-out form (
3295:
2421:
2252:
1368:. I said that it should be discused rather than giving me the sole decision, so I'm posting it here.
1189:. All nodes in arbitration must sample both their own and the other nodes ID bits at the same time.
1149:
1135:
Its a little of both. All nodes synchronise their clocks to the last message that went over the bus.
3490:. My argument is that Controller Area Network is a specific and singular network technology akin to
2930:
The gravity gradient (variation with height) above Earthâs surface is about 3.1Â ÂľGal per centimeter.
1467:
Great software provides productivity and efficiency on the factory floors. We should keep the link.
1427:
Various tools are available for developing CAN systems using these high level protocol. For example:
1096:
line codes? ), without being separate start/stop bits or an explicit Signal Element Timing circuit.
125:
4958:
4884:
This article contains much technical information, but hardly any practical information on usage.
4841:
4757:
4676:
3286:
3024:
2555:
2287:
2262:
2076:
1967:
1816:
1272:
own bus and putting a "switch" connecting all four buses that understands some addressing method.
872:
808:
on Knowledge. If you would like to participate, please visit the project page, where you can join
703:
on Knowledge. If you would like to participate, please visit the project page, where you can join
614:
on Knowledge. If you would like to participate, please visit the project page, where you can join
509:
on Knowledge. If you would like to participate, please visit the project page, where you can join
380:
on Knowledge. If you would like to participate, please visit the project page, where you can join
4990:
4953:
4620:
4595:
4487:
4142:
3712:
3527:
3422:
3338:
3138:
2416:
2334:
2329:
2163:
2128:
1779:
them saying Node ID bit, then each column below the Node ID bit should simply be the bit number.
1412:
If everybody is OK, let's list this external link as a second source for a CAN educational page.
1111:
109:
3247:
964:
on 2015-06-08. For the contribution history and old versions of the redirected page, please see
924:
on 2015-04-27. For the contribution history and old versions of the redirected page, please see
884:
on 2015-04-27. For the contribution history and old versions of the redirected page, please see
5052:
4741:
4177:
3720:
3535:
2816:
2773:
2499:
Showing the World a New and Better World Order For English-Language Application of Proper Nouns
2277:
1898:
1848:
1470:
377:
175:
4975:
4644:
4441:
4394:
4250:
4022:
3870:
3305:
3128:
2551:
2547:
2543:
2452:
2060:
1359:
208:
1166:
I don't know what is the meaning of "29 bit times" and "two transitions", who can teach me.
4903:
4879:
4810:
4802:
4684:
4437:
4290:
4172:
3741:
3618:
3263:
3239:
3231:
3083:
3051:
2610:
2408:
2404:
2362:
2353:
2339:
2318:
2229:
2056:
2028:
2001:
1824:
1619:
1154:
1103:
1053:
931:
5024:
Describe DBC files, simple databases for defining message formats, purposes, contents etc.
1251:
then the manual for the filtering is the documentation of the according CAN controller. --
8:
4667:
4349:
3904:
3400:
2654:
I note that this article originally used the correct spelling and an RM attended by just
2111:
2105:
1972:
This article have some content that passes for knowledge but are really just platitudes:
1163:
length between two transitions which can be used for resynchronization is 29 bit times."
912:
190:
55:
2670:
who has an opinion has a voice on Knowledge. That observation may offend, but Knowledge
4985:
4948:
4870:
4831:
4788:
It looks like the nodes are connected randomly, sometimes h to l and sometimes h to h.
4681:
ISO 11898-2:2016 now exists. And from what I heard, it supports up to 12 Mbps CAN FD.
3893:
3829:
3789:
3768:
3681:
3648:
3553:
3513:
3487:
3477:
3430:
3177:
3065:
3037:
2955:
2876:
2833:
2703:
2606:
2567:
2469:
2442:
2380:
2225:
a CANbus system on a vehicle you should have a look at what is already availabe first
2215:
CANBus (controller area network) alarm and tracking system infomation is availabe from
2159:
1932:
996:
consider it to be anecdotal evidence I will continue to search for a trustable source.
258:
70:
1041:
could they tell me why please ? Is the koopman paper incorrect ? (I somehow doubt it)
5048:
5033:
5014:
4737:
4339:
3961:
3897:
3731:
3716:
3531:
3368:
3322:
2812:
2769:
2182:
2140:
1351:
1265:
1030:
957:
917:
877:
278:, where you can join the project and see a list of open tasks. Leave messages at the
141:
51:
2559:
4966:
4941:
4934:
4895:
I could ask similar questions for use in elevators, escalators, and travelators.
4072:
3124:
2937:
2900:. We donât have to have perfect consistency and crystal clear, zero-ambiguity even
2801:
2749:
2687:
2585:
2510:
2448:
2009:
1955:
1912:
1798:
1784:
1226:
1211:
1021:
999:
952:
792:
4796:"may have as many as 70 electronic control units (ECU) for various subsystems.[7"
161:
4899:
4202:
4052:
4032:
3907:
3784:
is some pretty good evidence for the predominance of CAN bus being most common.
3235:
3157:
3079:
3047:
2984:
2811:
there's a dozen where it's CAN. Could one imagine IBM ever doing the same thing?
2358:
2349:
2314:
2024:
1807:
1451:
3544:
No, but if you want to call it that, at least don't over-capitalize; stick with
2975:; in that case, if/when expanded in the article text, it should be lower-cased.
4772:
4722:
4663:
4503:
4197:
4122:
4047:
3951:
3926:
3840:
3811:
3753:
3694:
3665:
3622:
3598:
3495:
3465:
3457:
3440:
3395:
3374:
3347:
2850:
2615:
971:
4848:
4643:
Subsequent comments should be made in a new section on this talk page or in a
5065:
4866:
4827:
4575:
4462:
4354:
4302:
4285:
4067:
3966:
3956:
3931:
3892:
3825:
3800:
3785:
3762:
3749:
3675:
3661:
3642:
3608:
3568:
3549:
3509:
3473:
3426:
3343:
3194:
3189:. Doen't solve the capitalization question, but solves the title question. â
3173:
3061:
3033:
2951:
2872:
2829:
2699:
2563:
2465:
2429:
2376:
1928:
1813:
1608:
1477:
1460:
1365:
1329:
1289:
1273:
1252:
582:
561:
2914:
The gravity gradient (variation with height) above Earthâs surface is about
1204:
is 8uS of time per bit. 29 bit times at 125kbit is 29 times 8uS, or 232uS.
5029:
5010:
4634:
4312:
4255:
4107:
4012:
3664:
issue not a naming issue and does not necessarily follow the references.) ~
3364:
3318:
3207:
3105:
3009:
2296:
2195:
2178:
2136:
2085:
1793:
Never mind, I eventually figured it out. I'm now happy with the new table
786:
776:
755:
598:
4763:
Single Wire CAN bus driver ICs and devices are already widespread in use.
4733:
4580:
4559:
4477:
4322:
4260:
4235:
4162:
3946:
3941:
3355:
3351:
3222:
2933:
2797:
2745:
2739:
2683:
2637:, which is a particular one. If you take a class or seminar on CAN, like
2581:
2506:
2412:
2154:
2005:
1644:
1489:
1388:
493:
271:
4826:
by the higher layer protocol used like 64 in DeviceNet, 127 in CANopen.
4399:
2042:
Can someone tell me what differs CAN 2.x from previous (CAN) standards?
1616:
The table is non-intuitive; Dominant is a 0 and recessive is a 1. Why?
991:
http://age-web.age.uiuc.edu/faculty/qzhang/teaching/ABE425/CAN%20Bus.ppt
804:, a collaborative effort to improve the coverage of articles related to
4778:
Single Wire CAN Network for Vehicle Applications â SAE J2411 â Standard
4433:
4132:
3921:
3150:
2977:
2947:
2907:
2734:
doesnât mean that we should latch onto that as an excuse because it is
506:
5028:
CAN DBC files seem to be important for working with CAN bus messages.
3425:
if we don't like the acronym. Please review previous move requests.
1410:
Recommendation: List this link as a second source for CAN information:
1407:
Question: Could you please be more specific about the misinformation?
1260:
To follow that up. CAN is broadcast only. It has no addressing like
270:, an attempt to provide a standard approach to writing articles about
4718:
4457:
4447:
4414:
4409:
4344:
4219:
4007:
3992:
3987:
1647:
for dominant/recessive, logical or, and logical and (for comparison)
1350:
section to go with the diagram, but it needs a lot more text adding.
1281:
805:
373:
4784:
the diagram titled Low-Speed Fault-Tolerant CAN Network. ISO 11898-3
4467:
4404:
4137:
3997:
3821:
3545:
3505:
3469:
3444:
3418:
3190:
2425:
1285:
1261:
369:
356:
329:
252:
242:
221:
4857:"An incorrect is CRC used for bit stuffing illustration purposes."
3078:. This allows everyone to weigh-in on that title specifically. --
1304:
DaimlerChrysler Programmable Communication Interface (PCI) and CAN
5047:. It's the layer above this article, which is the physical layer.
5044:
4600:
4554:
4538:
4364:
4182:
4127:
4062:
4017:
3523:
3417:, lowercase is common, and caps are not necessary, therefore per
3333:
3148:
Seems like the best option on the basis of the discussion above.
3142:
2868:
2860:
1446:
1438:
1434:
961:
921:
881:
477:
456:
24:
4752:
Add section describing Single Wire CAN Physcal Layer (SAE J2411)
1857:- ISO11898-2 lists this in the Abbreviations Table (Section 4).
4533:
4424:
4389:
4384:
4379:
4374:
4192:
4082:
4042:
4002:
2889:
we do, we should make sure we take the time to look at how the
2845:
4518:
4429:
2211:
Companies that provide vehicle CanBus products and information
4528:
4419:
4359:
4297:
4270:
4152:
4102:
4027:
3486:
I gather you are thinking controller area network is akin to
700:
687:
666:
2928:
on the ground with spring-based gravimetersâalways write it
1457:
1442:
4523:
4508:
4369:
4280:
4275:
4117:
1566:
1503:
1484:
424:
2505:
consistently. Knowledge must go with the flow of the RSs.
1035:
Hi in the koopman paper he gives the canbus crc as 0x62cc
4472:
4097:
4092:
3807:
3391:
3387:
2720:
2634:
2216:
1430:
611:
4654:
Links to other Languages absent (Wikidata) - Please help
3294:
The following discussion is an archived discussion of a
3104:
The following discussion is an archived discussion of a
3074:
The cleanest thing will be for someone to open an RM to
2295:
The following discussion is an archived discussion of a
2084:
The following discussion is an archived discussion of a
2037:
3032:
Why was this closed during so much active discussion?--
5107:
C-Class Computer networking articles of Mid-importance
3346:
discourages acronyms in titles in these cases. As per
1183:
Synchronizing the nodes is important for two reasons:
160:
4633:
The above discussion is preserved as an archive of a
3206:
The above discussion is preserved as an archive of a
3008:
The above discussion is preserved as an archive of a
2194:
The above discussion is preserved as an archive of a
3046:
Would you like me to revert the close and reopen? --
2392:. The standards body doesn't capitalize the name in
980:
782:
699:, a collaborative effort to improve the coverage of
610:, a collaborative effort to improve the coverage of
588:
505:, a collaborative effort to improve the coverage of
483:
368:, a collaborative effort to improve the coverage of
248:
15:
3308:. No further edits should be made to this section.
2786:writes (and this is the whole and reliable truth):
4846:This seems to be incomprehensible (in sub section
4647:. No further edits should be made to this section.
3573:If the technology is most commonly referred to as
4703:Definition as 'Vehicle bus' seems overly specific
2633:invented by Boschâjust like Intelâs invention of
1236:Is selective data transmission possible with CAN?
5063:
33:for general discussion of the article's subject.
4215:Coherent Accelerator Processor Interface (CAPI)
3350:we capitalize the title if the subject is is a
1891:Can anyone who knows more about CAN elaborate?
2863:, whichever is more common or more standard.
2629:properly uppercase because the term refers to
1998:achieve such integration in the CAN context.
3878:
3384:Support (in principle, no worries about caps)
174:
1865:"On the other hand any official use of CAN "
1328:controllers and so just need a transceiver.
5102:Mid-importance Computer networking articles
3761:Can you provide evidence that it's not? â˘
3744:. The links from the article indicate that
2135:name for the protocol just uses a space. --
1642:
970:; for the discussion at that location, see
930:; for the discussion at that location, see
890:; for the discussion at that location, see
3885:
3871:
989:comment regarding Intel I found this PPT:
2790:And Boschâs specification for CAN 2.0 is
2613:)? The lead is a bit ambiguous on this. â
2484:of the reliable sources mentioned in our
1422:Advertisement material moved from article
1038:Someone has changed this to another CRC.
3613:directly above here is my evidence that
2605:Is this a generic class of networks (as
2052:erbÄnoiu 15:03, 20 December 2010 (UTC)
3597:acknowledge that both terms are used. ~
2535:5 has it only in an acronym definition.
2532:4 has it only in an acronyn definition.
2488:uses allâuppercase. That list includes
1313:what components (hardware and software)
188:
5064:
4792:How many control units can it support?
2859:I think that would be a good idea; or
1654:Bus state with two nodes transmitting
1492:for dominant/recessive and logical AND
5137:Low-importance bus transport articles
4922:2003:E5:DF11:9800:71E6:AD9A:BF7D:B57A
3866:
3715:would be particularly inappropriate.
2723:. Notwithstanding that even RSs like
2712:Boschâs specification for CAN 2.0 is
2045:AFAIK CAN 2.0 introduced 29 bit IDs.
1500:Bus state with two nodes transmitting
5097:C-Class Computer networking articles
3693:improvement to the existing title. ~
3313:The result of the move request was:
3119:The result of the move request was:
2501:ÂŽâ˘ÂŠ. The mostâreliable RSs spell it
2310:The result of the move request was:
939:
899:
859:
798:This article is within the scope of
693:This article is within the scope of
604:This article is within the scope of
499:This article is within the scope of
362:This article is within the scope of
184:
3839:accurate comparison in this case. ~
3748:is more common (see my response to
2099:The result of the move request was
207:It is of interest to the following
23:for discussing improvements to the
13:
5127:Low-importance Automobile articles
5077:Low-importance electronic articles
4662:, but not here. Can anybody help?
1994:former: such tool does not exist.
423:
14:
5178:
5162:Low-importance Transport articles
5092:Low-importance Computing articles
3450:All pages with titles containing
2898:, also known as CAN bus or CANbus
2768:variants) with the acronym form.
2312:No consensus to move to new title
519:Knowledge:WikiProject Automobiles
287:Knowledge:WikiProject Electronics
5112:All Computer networking articles
5082:WikiProject Electronics articles
5004:Distinguish messages from frames
4616:
4615:
3492:Fiber Distributed Data Interface
2609:) or a specific type of bus (as
943:
903:
863:
785:
775:
754:
686:
665:
591:
581:
560:
522:Template:WikiProject Automobiles
486:
476:
455:
355:
328:
290:Template:WikiProject Electronics
251:
241:
220:
189:
45:Click here to start a new topic.
2736:properly âUniversal Serial Busâ
2580:See my below response to Ruud.
2356:) 01:37, 26 December 2011 (UTC)
838:This article has been rated as
818:Knowledge:WikiProject Transport
733:This article has been rated as
644:This article has been rated as
539:This article has been rated as
410:This article has been rated as
390:Knowledge:WikiProject Computing
307:This article has been rated as
5167:WikiProject Transport articles
5152:Low-importance Trucks articles
5132:C-Class bus transport articles
3736:can you provide evidence that
2744:can get it right on occasion.
2642:from Embedded Systems Academy,
2486:the articleâs âExternal linksâ
1456:Should we also remove the link
821:Template:WikiProject Transport
393:Template:WikiProject Computing
1:
5038:18:19, 30 December 2023 (UTC)
5019:18:16, 30 December 2023 (UTC)
4908:11:31, 12 November 2021 (UTC)
4210:Intel Ultra Path Interconnect
3746:Controller Area Network (CAN)
3615:Controller Area Network (CAN)
3583:Controller Area Network (CAN)
3248:16:15, 18 December 2011 (UTC)
2967:. But I don't mind a move to
2503:Controller Area Network (CAN)
2457:23:24, 29 December 2011 (UTC)
2434:05:58, 19 December 2011 (UTC)
2385:15:01, 18 December 2011 (UTC)
2367:14:41, 18 December 2011 (UTC)
2282:19:06, 18 December 2011 (UTC)
2033:14:52, 18 December 2011 (UTC)
1837:12:25, 24 November 2007 (UTC)
1803:17:34, 31 December 2014 (UTC)
1789:00:59, 22 November 2014 (UTC)
1333:22:30, 31 December 2006 (UTC)
812:and see a list of open tasks.
707:and see a list of open tasks.
618:and see a list of open tasks.
513:and see a list of open tasks.
432:This article is supported by
384:and see a list of open tasks.
42:Put new text under old text.
4996:08:48, 11 October 2022 (UTC)
4980:01:07, 11 October 2022 (UTC)
4959:23:42, 10 October 2022 (UTC)
4913:CAN Bus can not process data
4875:19:56, 12 October 2021 (UTC)
4819:16:25, 8 December 2020 (UTC)
4746:11:45, 21 January 2019 (UTC)
4727:08:58, 21 January 2019 (UTC)
4697:08:10, 11 January 2018 (UTC)
4188:Intel QuickPath Interconnect
4178:Direct Media Interface (DMI)
3806:because it is also used for
3133:06:24, 10 January 2012 (UTC)
2730:sometimes goof and spell it
2187:18:37, 18 October 2009 (UTC)
2168:21:09, 12 October 2009 (UTC)
2145:20:44, 12 October 2009 (UTC)
2118:10:14, 20 October 2009 (UTC)
1817:20:58, 6 November 2007 (UTC)
1400:Sonia Trier, s.trier@web.de
1392:18:32, 2 February 2007 (UTC)
1387:What does everyone think? --
1158:13:33, 7 November 2005 (UTC)
1120:12:30, 22 October 2014 (UTC)
1091:Synchronous or Asynchronous?
1025:01:02, 2 December 2007 (UTC)
713:Knowledge:WikiProject Trucks
7:
5122:C-Class Automobile articles
5072:C-Class electronic articles
4672:12:21, 18 August 2015 (UTC)
3199:19:44, 6 January 2012 (UTC)
3182:16:13, 6 January 2012 (UTC)
3164:00:40, 3 January 2012 (UTC)
3088:00:00, 3 January 2012 (UTC)
3070:23:37, 2 January 2012 (UTC)
3056:23:33, 2 January 2012 (UTC)
3042:23:27, 2 January 2012 (UTC)
2991:01:31, 2 January 2012 (UTC)
2960:01:13, 2 January 2012 (UTC)
2942:00:40, 2 January 2012 (UTC)
2881:00:25, 2 January 2012 (UTC)
2855:00:22, 2 January 2012 (UTC)
2838:00:25, 2 January 2012 (UTC)
2821:00:40, 2 January 2012 (UTC)
2806:00:20, 2 January 2012 (UTC)
2778:00:11, 2 January 2012 (UTC)
2754:00:09, 2 January 2012 (UTC)
2708:23:57, 1 January 2012 (UTC)
2692:23:35, 1 January 2012 (UTC)
2620:23:11, 1 January 2012 (UTC)
2590:23:35, 1 January 2012 (UTC)
2572:21:45, 1 January 2012 (UTC)
2515:20:15, 1 January 2012 (UTC)
2474:18:15, 1 January 2012 (UTC)
2323:22:59, 2 January 2012 (UTC)
1937:14:19, 20 August 2008 (UTC)
1464:18:47, 4 October 2007 (UTC)
1355:11:11, 9 January 2007 (UTC)
1294:21:56, 1 January 2015 (UTC)
1231:16:03, 1 January 2015 (UTC)
1132:add it to the CAN article.
716:Template:WikiProject Trucks
624:Knowledge:WikiProject Buses
50:New to Knowledge? Welcome!
10:
5183:
5157:C-Class Transport articles
5142:WikiProject Buses articles
5087:C-Class Computing articles
5057:10:38, 26 April 2024 (UTC)
4836:19:39, 25 April 2021 (UTC)
4660:de:Controller Area Network
4173:Compute Express Link (CXL)
3411:Oppose over-capitalization
3371:) 13:12, 3 July 2014 (UTC)
2925:reciprocal seconds squared
2844:Shouldn't we move this to
2635:Universal Serial Bus (USB)
2492:on the subject as well as
2479:Strongest possible support
2018:04:04, 1 August 2008 (UTC)
1632:12:25, 1 August 2011 (UTC)
1277:01:02, 10 March 2006 (UTC)
1066:18:36, 17 March 2017 (UTC)
844:project's importance scale
650:project's importance scale
627:Template:WikiProject Buses
545:project's importance scale
416:project's importance scale
313:project's importance scale
4609:
4568:
4547:
4496:
4410:IEEE-1284 (parallel port)
4332:
4325:logical device interface)
4228:
3980:
3914:
3725:00:15, 27 June 2014 (UTC)
3698:14:35, 27 June 2014 (UTC)
3688:23:59, 26 June 2014 (UTC)
3669:14:19, 26 June 2014 (UTC)
3655:09:02, 26 June 2014 (UTC)
3602:20:32, 27 June 2014 (UTC)
3558:16:48, 27 June 2014 (UTC)
3540:16:27, 27 June 2014 (UTC)
3518:15:24, 27 June 2014 (UTC)
3499:14:35, 27 June 2014 (UTC)
3482:23:49, 26 June 2014 (UTC)
3461:14:19, 26 June 2014 (UTC)
3435:00:02, 26 June 2014 (UTC)
3406:23:43, 25 June 2014 (UTC)
3378:18:31, 25 June 2014 (UTC)
3327:13:08, 11 July 2014 (UTC)
3280:06:15, 12 June 2013 (UTC)
2891:insiders in this industry
2422:word sense disambiguation
2267:05:00, 19 June 2011 (UTC)
2246:10:56, 4 March 2010 (UTC)
2049:
1960:13:25, 22 July 2008 (UTC)
1917:13:25, 22 July 2008 (UTC)
1903:06:35, 10 July 2008 (UTC)
1853:06:19, 10 July 2008 (UTC)
1612:19:36, 31 July 2007 (UTC)
1487:
1481:19:32, 31 July 2007 (UTC)
1417:17:59, 4 April 2007 (UTC)
1256:19:27, 9 March 2006 (UTC)
1216:02:13, 12 July 2014 (UTC)
1086:15:08, 5 March 2018 (UTC)
837:
770:
732:
681:
643:
576:
538:
471:
431:
409:
350:
306:
236:
215:
80:Be welcoming to newcomers
4640:Please do not modify it.
3844:13:45, 9 July 2014 (UTC)
3834:03:21, 9 July 2014 (UTC)
3815:14:10, 8 July 2014 (UTC)
3794:03:51, 8 July 2014 (UTC)
3775:21:49, 7 July 2014 (UTC)
3757:17:12, 7 July 2014 (UTC)
3626:14:10, 8 July 2014 (UTC)
3301:Please do not modify it.
3255:Why extended data frame?
3213:Please do not modify it.
3111:Please do not modify it.
3015:Please do not modify it.
2784:Embedded Systems Academy
2411:and do think of it as a
2302:Please do not modify it.
2201:Please do not modify it.
2091:Please do not modify it.
1008:Carry on the good work.
873:Terminating bias circuit
264:This article is part of
5147:C-Class Trucks articles
4930:08:26, 6 May 2022 (UTC)
3713:Controller area network
3528:controller area network
3522:So because the name is
3423:Controller area network
3339:Controller Area Network
3139:Controller area network
2896:Controller Area Network
2782:Itâs not as you write.
2490:this scholarly treatise
2417:Internet protocol suite
2335:Controller Area Network
2330:Controller area network
2129:Controller area network
2125:Controllerâarea network
502:WikiProject Automobiles
267:WikiProject Electronics
5117:All Computing articles
3972:List of bus bandwidths
3530:? Typical wikipedia.
2676:Competence is required
630:bus transport articles
428:
378:information technology
197:This article is rated
75:avoid personal attacks
2912:article ought to say
2885:Thatâs fine with me.
2674:have a policy called
2494:Boschâs specification
1441:Teknewell Engineering
950:The contents of the
910:The contents of the
870:The contents of the
801:WikiProject Transport
435:Networking task force
427:
365:WikiProject Computing
100:Neutral point of view
4415:IEEE-1394 (FireWire)
4153:PCI Extended (PCI-X)
3526:, we should call it
2732:universal serial bus
2721:Universal Serial Bus
2662:What weâve got here
2611:Universal Serial Bus
2409:Universal Serial Bus
2405:Storage area network
2340:Universal Serial Bus
1429:CANopen Configurator
105:No original research
4773:SAE J2411 reference
4732:At present, it has
4256:Parallel ATA (PATA)
1737:
1696:
1655:
1648:
1022:Howard C. Berkowitz
525:Automobile articles
293:electronic articles
4163:PCI Express (PCIe)
3488:local area network
2607:local area network
2443:Local area network
1943:interframe spacing
1735:
1694:
1653:
1643:
1564:
1501:
1433:X-Analyser for CAN
1342:Bit Timing Diagram
1099:-- Midnight Hour
824:Transport articles
696:WikiProject Trucks
429:
396:Computing articles
259:Electronics portal
203:content assessment
86:dispute resolution
47:
4805:comment added by
4699:
4687:comment added by
4627:
4626:
4613:
4340:Apple Desktop Bus
4317:PCI Express (via
4276:Serial ATA (SATA)
3962:Network on a chip
3372:
3283:
3266:comment added by
3251:
3234:comment added by
2357:
2253:Patent licensing?
2249:
2232:comment added by
2073:
2059:comment added by
2020:
2004:comment added by
1839:
1827:comment added by
1776:
1775:
1772:
1771:
1731:
1730:
1690:
1689:
1622:comment added by
1605:
1604:
1601:
1600:
1562:
1558:
1557:
1499:
1266:Internet Protocol
1141:--Kevin Schostek
1123:
1106:comment added by
1068:
1056:comment added by
978:
977:
938:
937:
898:
897:
858:
857:
854:
853:
850:
849:
749:
748:
745:
744:
660:
659:
656:
655:
607:WikiProject Buses
555:
554:
551:
550:
450:
449:
446:
445:
323:
322:
319:
318:
280:project talk page
183:
182:
66:Assume good faith
43:
5174:
4945:
4842:Incomprehensible
4821:
4682:
4677:ISO 11898-2:2016
4642:
4619:
4618:
4611:
4073:HP Precision Bus
3887:
3880:
3873:
3864:
3863:
3804:
3771:
3765:
3735:
3684:
3678:
3651:
3645:
3612:
3572:
3504:"necessary" per
3455:
3398:
3359:
3341:
3303:
3287:Requested move 4
3282:
3260:
3250:
3228:
3215:
3162:
3160:
3155:
3113:
3025:Requested move 3
3017:
2989:
2987:
2982:
2931:
2922:
2921:
2919:
2899:
2789:
2733:
2647:
2631:a particular bus
2504:
2482:Every single one
2344:
2337:
2304:
2288:Requested move 2
2248:
2226:
2203:
2116:
2114:
2108:
2093:
2077:Requested move 1
2072:
2061:Iulian.serbanoiu
2053:
2051:
1999:
1968:Just platitudes!
1877:
1876:
1872:
1859:User:d_rock_naut
1822:
1738:
1734:
1697:
1693:
1656:
1652:
1649:
1634:
1567:
1504:
1485:
1122:
1100:
1051:
969:
947:
946:
940:
929:
907:
906:
900:
889:
867:
866:
860:
826:
825:
822:
819:
816:
795:
793:Transport portal
790:
789:
779:
772:
771:
766:
758:
751:
750:
739:importance scale
721:
720:
717:
714:
711:
690:
683:
682:
677:
669:
662:
661:
632:
631:
628:
625:
622:
601:
596:
595:
594:
585:
578:
577:
572:
564:
557:
556:
527:
526:
523:
520:
517:
496:
491:
490:
489:
480:
473:
472:
467:
459:
452:
451:
398:
397:
394:
391:
388:
359:
352:
351:
346:
343:
332:
325:
324:
295:
294:
291:
288:
285:
261:
256:
255:
245:
238:
237:
232:
224:
217:
216:
200:
194:
193:
185:
179:
178:
164:
95:Article policies
16:
5182:
5181:
5177:
5176:
5175:
5173:
5172:
5171:
5062:
5061:
5043:That's part of
5026:
5006:
4939:
4937:
4915:
4882:
4844:
4800:
4794:
4786:
4769:
4754:
4705:
4679:
4656:
4651:
4638:
4628:
4623:
4605:
4564:
4543:
4492:
4405:IEEE-488 (GPIB)
4328:
4224:
4203:Infinity Fabric
4033:Europe Card Bus
3976:
3910:
3891:
3798:
3769:
3763:
3729:
3682:
3676:
3649:
3643:
3606:
3589:refer to it as
3581:refer to it as
3566:
3448:
3421:, it should be
3396:
3337:
3299:
3289:
3261:
3257:
3229:
3225:
3220:
3211:
3158:
3151:
3149:
3109:
3027:
3022:
3013:
2985:
2978:
2976:
2929:
2917:
2915:
2913:
2894:
2787:
2731:
2656:two individuals
2645:
2502:
2333:
2300:
2290:
2255:
2227:
2213:
2208:
2199:
2112:
2106:
2104:
2089:
2079:
2054:
2040:
1970:
1945:
1878:
1874:
1870:
1868:
1867:
1810:
1617:
1473:
1424:
1401:
1362:
1346:I have added a
1344:
1315:
1306:
1238:
1155:Julian Morrison
1139:
1101:
1093:
1069:
1045:
1033:
1002:
985:In response to
983:
965:
944:
925:
913:CAN bus monitor
904:
885:
864:
823:
820:
817:
814:
813:
791:
784:
764:
719:Trucks articles
718:
715:
712:
709:
708:
675:
629:
626:
623:
620:
619:
597:
592:
590:
570:
524:
521:
518:
515:
514:
492:
487:
485:
465:
395:
392:
389:
386:
385:
344:
338:
292:
289:
286:
283:
282:
257:
250:
230:
201:on Knowledge's
198:
121:
116:
115:
114:
91:
61:
12:
11:
5:
5180:
5170:
5169:
5164:
5159:
5154:
5149:
5144:
5139:
5134:
5129:
5124:
5119:
5114:
5109:
5104:
5099:
5094:
5089:
5084:
5079:
5074:
5060:
5059:
5025:
5022:
5005:
5002:
5001:
5000:
4999:
4998:
4936:
4933:
4914:
4911:
4881:
4878:
4860:
4859:
4843:
4840:
4839:
4838:
4793:
4790:
4785:
4782:
4781:
4780:
4775:
4768:
4765:
4753:
4750:
4749:
4748:
4714:Any opinions?
4704:
4701:
4689:62.119.168.113
4678:
4675:
4655:
4652:
4650:
4649:
4635:requested move
4629:
4625:
4624:
4614:
4610:
4607:
4606:
4604:
4603:
4598:
4593:
4583:
4578:
4572:
4570:
4566:
4565:
4563:
4562:
4557:
4551:
4549:
4545:
4544:
4542:
4541:
4536:
4531:
4526:
4521:
4516:
4514:Intel HD Audio
4511:
4506:
4504:ADAT Lightpipe
4500:
4498:
4494:
4493:
4491:
4490:
4485:
4480:
4475:
4470:
4465:
4460:
4455:
4450:
4445:
4427:
4422:
4417:
4412:
4407:
4402:
4397:
4392:
4387:
4382:
4377:
4372:
4367:
4362:
4357:
4352:
4347:
4342:
4336:
4334:
4330:
4329:
4327:
4326:
4315:
4310:
4305:
4300:
4295:
4294:
4293:
4288:
4278:
4273:
4268:
4263:
4258:
4253:
4248:
4243:
4238:
4232:
4230:
4226:
4225:
4223:
4222:
4217:
4212:
4207:
4206:
4205:
4198:HyperTransport
4195:
4190:
4185:
4180:
4175:
4170:
4165:
4160:
4155:
4150:
4145:
4140:
4135:
4130:
4125:
4120:
4115:
4110:
4105:
4100:
4095:
4090:
4085:
4080:
4075:
4070:
4065:
4060:
4055:
4050:
4045:
4040:
4035:
4030:
4025:
4020:
4015:
4010:
4005:
4000:
3995:
3990:
3984:
3982:
3978:
3977:
3975:
3974:
3969:
3964:
3959:
3954:
3952:Bus contention
3949:
3944:
3939:
3934:
3929:
3927:Front-side bus
3924:
3918:
3916:
3912:
3911:
3908:computer buses
3890:
3889:
3882:
3875:
3867:
3861:
3860:
3859:
3858:
3857:
3856:
3855:
3854:
3853:
3852:
3851:
3850:
3849:
3848:
3847:
3846:
3808:other purposes
3711:- COMMONNAME.
3706:
3705:
3704:
3703:
3702:
3701:
3700:
3636:
3635:
3634:
3633:
3632:
3631:
3630:
3629:
3628:
3604:
3564:
3563:
3562:
3561:
3560:
3408:
3332:
3330:
3311:
3310:
3296:requested move
3290:
3288:
3285:
3256:
3253:
3224:
3221:
3219:
3218:
3208:requested move
3202:
3201:
3184:
3136:
3117:
3116:
3106:requested move
3100:
3099:
3098:
3097:
3096:
3095:
3094:
3093:
3092:
3091:
3090:
3026:
3023:
3021:
3020:
3010:requested move
3004:
3003:
3002:
3001:
3000:
2999:
2998:
2997:
2996:
2995:
2994:
2993:
2842:
2841:
2840:
2824:
2823:
2762:
2761:
2760:
2759:
2758:
2757:
2756:
2741:even Microsoft
2600:
2599:
2598:
2597:
2596:
2595:
2594:
2593:
2592:
2539:
2536:
2533:
2530:
2527:
2524:
2520:
2476:
2459:
2436:
2387:
2328:
2326:
2308:
2307:
2297:requested move
2291:
2289:
2286:
2285:
2284:
2259:71.196.246.113
2254:
2251:
2212:
2209:
2207:
2206:
2196:requested move
2190:
2189:
2171:
2170:
2123:
2121:
2097:
2096:
2086:requested move
2080:
2078:
2075:
2039:
2036:
1984:
1969:
1966:
1964:
1944:
1941:
1940:
1939:
1924:
1866:
1863:
1829:64.238.175.105
1809:
1806:
1774:
1773:
1770:
1769:
1766:
1763:
1759:
1758:
1755:
1752:
1748:
1747:
1744:
1741:
1732:
1729:
1728:
1725:
1722:
1718:
1717:
1714:
1711:
1707:
1706:
1703:
1700:
1691:
1688:
1687:
1684:
1681:
1677:
1676:
1673:
1670:
1666:
1665:
1662:
1659:
1624:147.177.201.37
1603:
1602:
1599:
1598:
1595:
1592:
1588:
1587:
1584:
1581:
1577:
1576:
1573:
1570:
1559:
1556:
1555:
1548:
1543:
1537:
1536:
1531:
1524:
1518:
1517:
1512:
1507:
1495:
1494:
1472:
1471:Puzzling table
1469:
1466:
1450:
1448:
1444:
1440:
1436:
1432:
1428:
1426:
1423:
1420:
1414:68.236.126.218
1411:
1399:
1385:
1384:
1378:
1361:
1358:
1343:
1340:
1338:
1336:
1335:
1314:
1311:
1305:
1302:
1301:
1300:
1299:
1298:
1297:
1296:
1269:
1237:
1234:
1137:
1126:
1092:
1089:
1071:
1049:
1043:
1032:
1029:
1028:
1027:
1018:
1014:
1001:
998:
982:
979:
976:
975:
948:
936:
935:
908:
896:
895:
868:
856:
855:
852:
851:
848:
847:
840:Low-importance
836:
830:
829:
827:
810:the discussion
797:
796:
780:
768:
767:
765:Lowâimportance
759:
747:
746:
743:
742:
735:Low-importance
731:
725:
724:
722:
705:the discussion
691:
679:
678:
676:Lowâimportance
670:
658:
657:
654:
653:
646:Low-importance
642:
636:
635:
633:
616:the discussion
603:
602:
586:
574:
573:
571:Lowâimportance
565:
553:
552:
549:
548:
541:Low-importance
537:
531:
530:
528:
511:the discussion
498:
497:
481:
469:
468:
466:Lowâimportance
460:
448:
447:
444:
443:
440:Mid-importance
430:
420:
419:
412:Low-importance
408:
402:
401:
399:
382:the discussion
360:
348:
347:
345:Lowâimportance
333:
321:
320:
317:
316:
309:Low-importance
305:
299:
298:
296:
263:
262:
246:
234:
233:
231:Lowâimportance
225:
213:
212:
206:
195:
181:
180:
118:
117:
113:
112:
107:
102:
93:
92:
90:
89:
82:
77:
68:
62:
60:
59:
48:
39:
38:
35:
34:
28:
9:
6:
4:
3:
2:
5179:
5168:
5165:
5163:
5160:
5158:
5155:
5153:
5150:
5148:
5145:
5143:
5140:
5138:
5135:
5133:
5130:
5128:
5125:
5123:
5120:
5118:
5115:
5113:
5110:
5108:
5105:
5103:
5100:
5098:
5095:
5093:
5090:
5088:
5085:
5083:
5080:
5078:
5075:
5073:
5070:
5069:
5067:
5058:
5054:
5050:
5046:
5042:
5041:
5040:
5039:
5035:
5031:
5021:
5020:
5016:
5012:
4997:
4994:
4993:
4989:
4988:
4983:
4982:
4981:
4977:
4973:
4972:
4971:
4963:
4962:
4961:
4960:
4957:
4956:
4952:
4951:
4943:
4935:Clarification
4932:
4931:
4927:
4923:
4918:
4910:
4909:
4905:
4901:
4896:
4893:
4889:
4885:
4877:
4876:
4872:
4868:
4863:
4858:
4855:
4854:
4853:
4851:
4850:
4837:
4833:
4829:
4824:
4823:
4822:
4820:
4816:
4812:
4808:
4804:
4797:
4789:
4779:
4776:
4774:
4771:
4770:
4764:
4761:
4759:
4747:
4743:
4739:
4735:
4731:
4730:
4729:
4728:
4724:
4720:
4715:
4712:
4709:
4700:
4698:
4694:
4690:
4686:
4674:
4673:
4669:
4665:
4661:
4648:
4646:
4641:
4636:
4631:
4630:
4622:
4608:
4602:
4599:
4597:
4594:
4591:
4587:
4584:
4582:
4579:
4577:
4576:Multidrop bus
4574:
4573:
4571:
4567:
4561:
4558:
4556:
4553:
4552:
4550:
4546:
4540:
4537:
4535:
4532:
4530:
4527:
4525:
4522:
4520:
4517:
4515:
4512:
4510:
4507:
4505:
4502:
4501:
4499:
4495:
4489:
4486:
4484:
4483:External PCIe
4481:
4479:
4476:
4474:
4471:
4469:
4466:
4464:
4463:Parallel SCSI
4461:
4459:
4456:
4454:
4451:
4449:
4446:
4443:
4439:
4435:
4431:
4428:
4426:
4423:
4421:
4418:
4416:
4413:
4411:
4408:
4406:
4403:
4401:
4398:
4396:
4393:
4391:
4388:
4386:
4383:
4381:
4378:
4376:
4373:
4371:
4368:
4366:
4363:
4361:
4358:
4356:
4355:Commodore bus
4353:
4351:
4348:
4346:
4343:
4341:
4338:
4337:
4335:
4331:
4324:
4320:
4316:
4314:
4311:
4309:
4306:
4304:
4303:Fibre Channel
4301:
4299:
4296:
4292:
4289:
4287:
4284:
4283:
4282:
4279:
4277:
4274:
4272:
4269:
4267:
4264:
4262:
4259:
4257:
4254:
4252:
4249:
4247:
4244:
4242:
4239:
4237:
4234:
4233:
4231:
4227:
4221:
4218:
4216:
4213:
4211:
4208:
4204:
4201:
4200:
4199:
4196:
4194:
4191:
4189:
4186:
4184:
4181:
4179:
4176:
4174:
4171:
4169:
4166:
4164:
4161:
4159:
4156:
4154:
4151:
4149:
4146:
4144:
4141:
4139:
4136:
4134:
4131:
4129:
4126:
4124:
4121:
4119:
4116:
4114:
4111:
4109:
4106:
4104:
4101:
4099:
4096:
4094:
4091:
4089:
4086:
4084:
4081:
4079:
4076:
4074:
4071:
4069:
4066:
4064:
4061:
4059:
4056:
4054:
4051:
4049:
4046:
4044:
4041:
4039:
4036:
4034:
4031:
4029:
4026:
4024:
4021:
4019:
4016:
4014:
4011:
4009:
4006:
4004:
4001:
3999:
3996:
3994:
3991:
3989:
3986:
3985:
3983:
3979:
3973:
3970:
3968:
3967:Plug and play
3965:
3963:
3960:
3958:
3957:Bus mastering
3955:
3953:
3950:
3948:
3945:
3943:
3940:
3938:
3935:
3933:
3932:Back-side bus
3930:
3928:
3925:
3923:
3920:
3919:
3917:
3913:
3909:
3906:
3902:
3900:
3895:
3888:
3883:
3881:
3876:
3874:
3869:
3868:
3865:
3845:
3842:
3837:
3836:
3835:
3831:
3827:
3823:
3818:
3817:
3816:
3813:
3809:
3802:
3797:
3796:
3795:
3791:
3787:
3783:
3780:
3779:
3778:
3777:
3776:
3772:
3766:
3760:
3759:
3758:
3755:
3751:
3747:
3743:
3742:WP:COMMONNAME
3739:
3733:
3728:
3727:
3726:
3722:
3718:
3714:
3710:
3707:
3699:
3696:
3691:
3690:
3689:
3685:
3679:
3672:
3671:
3670:
3667:
3663:
3658:
3657:
3656:
3652:
3646:
3640:
3637:
3627:
3624:
3620:
3619:WP:COMMONNAME
3616:
3610:
3605:
3603:
3600:
3596:
3592:
3588:
3584:
3580:
3576:
3570:
3565:
3559:
3555:
3551:
3547:
3543:
3542:
3541:
3537:
3533:
3529:
3525:
3521:
3520:
3519:
3515:
3511:
3507:
3502:
3501:
3500:
3497:
3493:
3489:
3485:
3484:
3483:
3479:
3475:
3471:
3467:
3464:
3463:
3462:
3459:
3454:
3453:
3446:
3442:
3438:
3437:
3436:
3432:
3428:
3424:
3420:
3416:
3412:
3409:
3407:
3404:
3403:
3399:
3393:
3389:
3385:
3382:
3381:
3380:
3379:
3376:
3370:
3366:
3362:
3357:
3353:
3349:
3345:
3340:
3335:
3329:
3328:
3324:
3320:
3316:
3309:
3307:
3302:
3297:
3292:
3291:
3284:
3281:
3277:
3273:
3269:
3265:
3252:
3249:
3245:
3241:
3237:
3233:
3217:
3214:
3209:
3204:
3203:
3200:
3196:
3192:
3188:
3185:
3183:
3179:
3175:
3171:
3168:
3167:
3166:
3165:
3161:
3156:
3154:
3146:
3144:
3140:
3135:
3134:
3130:
3126:
3122:
3115:
3112:
3107:
3102:
3101:
3089:
3085:
3081:
3077:
3073:
3072:
3071:
3067:
3063:
3059:
3058:
3057:
3053:
3049:
3045:
3044:
3043:
3039:
3035:
3031:
3030:
3029:
3028:
3019:
3016:
3011:
3006:
3005:
2992:
2988:
2983:
2981:
2974:
2970:
2966:
2963:
2962:
2961:
2957:
2953:
2949:
2945:
2944:
2943:
2939:
2935:
2926:
2911:
2909:
2903:
2897:
2892:
2888:
2884:
2883:
2882:
2878:
2874:
2870:
2866:
2862:
2858:
2857:
2856:
2853:
2852:
2847:
2843:
2839:
2835:
2831:
2826:
2825:
2822:
2818:
2814:
2809:
2808:
2807:
2803:
2799:
2796:
2794:
2785:
2781:
2780:
2779:
2775:
2771:
2766:
2763:
2755:
2751:
2747:
2743:
2742:
2737:
2729:
2728:
2722:
2718:
2716:
2711:
2710:
2709:
2705:
2701:
2696:
2695:
2694:
2693:
2689:
2685:
2681:
2677:
2673:
2669:
2665:
2660:
2657:
2652:
2643:
2641:
2636:
2632:
2628:
2623:
2622:
2621:
2618:
2617:
2612:
2608:
2604:
2601:
2591:
2587:
2583:
2579:
2578:
2577:
2576:
2575:
2574:
2573:
2569:
2565:
2561:
2557:
2553:
2549:
2545:
2540:
2537:
2534:
2531:
2528:
2525:
2521:
2518:
2517:
2516:
2512:
2508:
2500:
2495:
2491:
2487:
2483:
2480:
2477:
2475:
2471:
2467:
2463:
2460:
2458:
2454:
2450:
2446:
2444:
2440:
2437:
2435:
2431:
2427:
2423:
2418:
2414:
2410:
2406:
2402:
2399:
2398:pluralizes it
2395:
2394:this abstract
2391:
2388:
2386:
2382:
2378:
2374:
2371:
2370:
2369:
2368:
2364:
2360:
2355:
2351:
2347:
2341:
2336:
2331:
2325:
2324:
2320:
2316:
2313:
2306:
2303:
2298:
2293:
2292:
2283:
2279:
2275:
2271:
2270:
2269:
2268:
2264:
2260:
2250:
2247:
2243:
2239:
2235:
2231:
2222:
2219:
2218:
2205:
2202:
2197:
2192:
2191:
2188:
2184:
2180:
2176:
2173:
2172:
2169:
2165:
2161:
2160:Keraunoscopia
2156:
2152:
2149:
2148:
2147:
2146:
2142:
2138:
2134:
2130:
2126:
2120:
2119:
2115:
2109:
2102:
2095:
2092:
2087:
2082:
2081:
2074:
2070:
2066:
2062:
2058:
2046:
2043:
2035:
2034:
2030:
2026:
2021:
2019:
2015:
2011:
2007:
2003:
1995:
1991:
1987:
1982:
1979:
1976:
1973:
1965:
1962:
1961:
1957:
1953:
1948:
1938:
1934:
1930:
1925:
1921:
1920:
1919:
1918:
1914:
1910:
1905:
1904:
1900:
1896:
1892:
1889:
1886:
1882:
1873:
1862:
1861:25 July 2008
1860:
1855:
1854:
1850:
1846:
1840:
1838:
1834:
1830:
1826:
1819:
1818:
1815:
1805:
1804:
1800:
1796:
1791:
1790:
1786:
1782:
1767:
1764:
1761:
1760:
1756:
1753:
1750:
1749:
1745:
1742:
1740:
1739:
1733:
1726:
1723:
1720:
1719:
1715:
1712:
1709:
1708:
1704:
1701:
1699:
1698:
1692:
1685:
1682:
1679:
1678:
1674:
1671:
1668:
1667:
1663:
1660:
1658:
1657:
1651:
1650:
1646:
1641:
1638:
1635:
1633:
1629:
1625:
1621:
1614:
1613:
1610:
1596:
1593:
1590:
1589:
1585:
1582:
1579:
1578:
1574:
1571:
1569:
1568:
1565:
1560:
1554:
1553:
1549:
1547:
1544:
1542:
1539:
1538:
1535:
1532:
1530:
1529:
1525:
1523:
1520:
1519:
1516:
1513:
1511:
1508:
1506:
1505:
1502:
1497:
1496:
1493:
1491:
1486:
1483:
1482:
1479:
1468:
1465:
1462:
1458:
1454:
1453:
1447:
1443:
1439:
1435:
1431:
1419:
1418:
1415:
1408:
1405:
1398:
1394:
1393:
1390:
1383:
1379:
1377:
1376:
1371:
1370:
1369:
1367:
1360:External Link
1357:
1356:
1353:
1349:
1339:
1334:
1331:
1326:
1325:
1324:
1321:
1318:
1310:
1295:
1291:
1287:
1283:
1280:
1279:
1278:
1275:
1270:
1267:
1263:
1259:
1258:
1257:
1254:
1249:
1248:
1247:
1246:Thanks Pearl
1244:
1241:
1233:
1232:
1228:
1224:
1218:
1217:
1213:
1209:
1205:
1201:
1198:
1194:
1190:
1188:
1184:
1181:
1179:
1173:
1170:
1167:
1164:
1160:
1159:
1156:
1151:
1150:
1148:Details here
1146:
1142:
1138:-- Robin48gx
1136:
1133:
1130:
1124:
1121:
1117:
1113:
1109:
1108:Midnight Hour
1105:
1097:
1088:
1087:
1083:
1079:
1078:77.94.130.182
1074:
1067:
1063:
1059:
1055:
1048:
1044:-- Robin48gx
1042:
1039:
1036:
1026:
1023:
1019:
1015:
1011:
1010:
1009:
1006:
997:
993:
992:
988:
973:
972:its talk page
968:
963:
959:
955:
954:
949:
942:
941:
933:
932:its talk page
928:
923:
919:
915:
914:
909:
902:
901:
893:
892:its talk page
888:
883:
879:
875:
874:
869:
862:
861:
845:
841:
835:
832:
831:
828:
811:
807:
803:
802:
794:
788:
783:
781:
778:
774:
773:
769:
763:
760:
757:
753:
752:
740:
736:
730:
727:
726:
723:
706:
702:
698:
697:
692:
689:
685:
684:
680:
674:
671:
668:
664:
663:
651:
647:
641:
638:
637:
634:
617:
613:
609:
608:
600:
589:
587:
584:
580:
579:
575:
569:
566:
563:
559:
558:
546:
542:
536:
533:
532:
529:
512:
508:
504:
503:
495:
484:
482:
479:
475:
474:
470:
464:
461:
458:
454:
453:
441:
438:(assessed as
437:
436:
426:
422:
421:
417:
413:
407:
404:
403:
400:
383:
379:
375:
371:
367:
366:
361:
358:
354:
353:
349:
342:
337:
334:
331:
327:
326:
314:
310:
304:
301:
300:
297:
281:
277:
273:
269:
268:
260:
254:
249:
247:
244:
240:
239:
235:
229:
226:
223:
219:
218:
214:
210:
204:
196:
192:
187:
186:
177:
173:
170:
167:
163:
159:
155:
152:
149:
146:
143:
140:
137:
134:
131:
127:
124:
123:Find sources:
120:
119:
111:
110:Verifiability
108:
106:
103:
101:
98:
97:
96:
87:
83:
81:
78:
76:
72:
69:
67:
64:
63:
57:
53:
52:Learn to edit
49:
46:
41:
40:
37:
36:
32:
26:
22:
18:
17:
5049:Alexceltare2
5027:
5007:
4991:
4986:
4969:
4968:
4954:
4949:
4938:
4919:
4916:
4897:
4894:
4890:
4886:
4883:
4880:Applications
4864:
4861:
4856:
4849:Bit stuffing
4847:
4845:
4801:â Preceding
4798:
4795:
4787:
4762:
4755:
4738:Andy Dingley
4716:
4713:
4710:
4706:
4683:â Preceding
4680:
4657:
4639:
4632:
4108:TURBOchannel
3898:
3745:
3737:
3732:Andy Dingley
3717:Andy Dingley
3708:
3638:
3614:
3594:
3590:
3586:
3582:
3578:
3574:
3532:Andy Dingley
3451:
3415:book sources
3410:
3401:
3383:
3360:
3331:
3314:
3312:
3300:
3293:
3262:â Preceding
3258:
3230:â Preceding
3226:
3212:
3205:
3186:
3169:
3152:
3147:
3137:
3120:
3118:
3110:
3103:
3075:
3014:
3007:
2979:
2972:
2968:
2964:
2924:
2905:
2901:
2895:
2890:
2886:
2849:
2813:Andy Dingley
2792:
2770:Andy Dingley
2764:
2740:
2726:
2714:
2679:
2671:
2667:
2663:
2661:
2655:
2653:
2649:
2639:
2630:
2626:
2614:
2602:
2498:
2481:
2478:
2461:
2438:
2397:
2389:
2372:
2345:
2327:
2311:
2309:
2301:
2294:
2274:212.159.69.4
2256:
2223:
2220:
2214:
2200:
2193:
2174:
2150:
2122:
2100:
2098:
2090:
2083:
2055:â Preceding
2048:Iulian-Nicu
2047:
2044:
2041:
2022:
1996:
1992:
1988:
1983:
1980:
1977:
1974:
1971:
1963:
1949:
1946:
1906:
1895:JacobBramley
1893:
1890:
1887:
1883:
1879:
1869:"": -->
1856:
1845:JacobBramley
1841:
1820:
1811:
1792:
1777:
1736:Logical and
1645:Truth tables
1639:
1636:
1618:â Preceding
1615:
1606:
1561:
1551:
1550:
1545:
1540:
1533:
1527:
1526:
1521:
1514:
1509:
1498:
1490:Truth tables
1488:
1474:
1455:
1425:
1409:
1406:
1402:
1395:
1386:
1382:information.
1380:
1372:
1363:
1352:Rocketmagnet
1347:
1345:
1337:
1322:
1319:
1316:
1307:
1245:
1242:
1239:
1219:
1206:
1202:
1199:
1195:
1191:
1185:
1182:
1174:
1171:
1168:
1165:
1161:
1152:
1147:
1143:
1140:
1134:
1125:
1102:â Preceding
1098:
1094:
1075:
1070:
1058:73.11.30.201
1052:â Preceding
1046:
1040:
1037:
1034:
1007:
1003:
994:
984:
951:
911:
871:
839:
799:
734:
694:
645:
605:
599:Buses portal
540:
500:
433:
411:
363:
308:
276:project page
265:
209:WikiProjects
171:
165:
157:
150:
144:
138:
132:
122:
94:
19:This is the
4942:Constant314
4734:vehicle bus
4645:move review
4581:CoreConnect
4560:ExpressCard
4488:Thunderbolt
4478:Camera Link
4261:Bus and Tag
3947:Address bus
3942:Control bus
3937:Daisy chain
3356:common noun
3352:proper noun
3306:move review
3125:Vegaswikian
2902:within this
2725:Microsoft,
2449:Enric Naval
2413:proper noun
2359:Hobson Lane
2228:âPreceding
2025:Hobson Lane
2000:âPreceding
1823:âPreceding
1695:Logical or
1563:Logical AND
1320:Thank you,
1129:Bosh spec's
967:its history
927:its history
887:its history
516:Automobiles
507:automobiles
494:Cars portal
463:Automobiles
284:Electronics
272:electronics
228:Electronics
148:free images
31:not a forum
5066:Categories
4900:FreeFlow99
4767:References
4434:ACCESS.bus
4333:Peripheral
4133:InfiniBand
4128:HP GSC bus
3922:System bus
3236:Hobsonlane
3121:page moved
3080:Mike Cline
3048:Mike Cline
2948:Gal (unit)
2908:Gravimetry
2375:, do it.--
2350:Mike Cline
2315:Mike Cline
2234:Gregmelson
2217:link title
2113:barbarian
2101:page moved
1686:Recessive
1680:Recessive
1664:Recessive
1348:Bit Timing
1050:-- Omega
956:page were
916:page were
876:page were
341:Networking
5030:â
NealMcBâ
5011:â
NealMcBâ
4758:SAE J2411
4664:Tony Mach
4395:Lightning
4345:Atari SIO
4220:SpaceWire
4053:Zorro III
3993:S-100 bus
3988:SS-50 bus
3981:Standards
3901:standards
3894:Technical
3752:above). ~
3468:supports
3315:not moved
2765:lowercase
2552:this book
2548:this book
2544:this book
2177:per nom.
2107:Skomorokh
1675:Dominant
1669:Dominant
1552:recessive
1541:recessive
1515:recessive
1445:CANalyzer
1282:SAE J1939
1031:Can CRC =
987:user:ajn1
953:ISO 11898
815:Transport
806:Transport
762:Transport
387:Computing
374:computing
370:computers
336:Computing
88:if needed
71:Be polite
21:talk page
4987:Spinning
4967:Constant
4950:Spinning
4898:Thanks.
4867:Mortense
4828:MisterTS
4815:contribs
4807:WithGLEE
4803:unsigned
4685:unsigned
4621:Category
4596:Wishbone
4569:Embedded
4548:Portable
4468:Profibus
4400:DMX512-A
4286:Parallel
4138:Ethernet
4048:Zorro II
3998:Multibus
3899:de facto
3826:Dicklyon
3822:MOS:CAPS
3801:Dicklyon
3786:Dicklyon
3764:Sbmeirow
3750:Dicklyon
3677:Sbmeirow
3644:Sbmeirow
3609:Sbmeirow
3569:Dicklyon
3550:Dicklyon
3546:MOS:CAPS
3510:Dicklyon
3506:MOS:CAPS
3474:Dicklyon
3470:MOS:CAPS
3452:protocol
3445:MOS:CAPS
3439:I think
3427:Dicklyon
3419:MOS:CAPS
3361:Relisted
3276:contribs
3264:unsigned
3244:contribs
3232:unsigned
3174:Dicklyon
3062:Dicklyon
3034:Asher196
2952:Dicklyon
2923:because
2887:Whatever
2873:Dicklyon
2867:suggest
2830:Dicklyon
2700:Dicklyon
2668:everyone
2603:Question
2564:Dicklyon
2560:this one
2556:this one
2466:Dicklyon
2401:this one
2377:Asher196
2346:relisted
2242:contribs
2230:unsigned
2133:ISO spec
2069:contribs
2057:unsigned
2014:contribs
2002:unsigned
1929:MisterTS
1825:unsigned
1814:TinyMark
1683:Dominant
1672:Dominant
1661:Dominant
1620:unsigned
1609:SGBailey
1546:dominant
1534:dominant
1528:dominant
1522:dominant
1510:dominant
1478:SGBailey
1461:Symmetry
1449:CANsniff
1330:Cburnett
1274:Cburnett
1262:ethernet
1253:MisterTS
1178:app note
1116:contribs
1104:unsigned
1076:-- Yuni
1054:unsigned
1000:NMEA CAN
56:get help
29:This is
27:article.
5045:CANopen
4601:SLIMbus
4555:PC Card
4539:TOSLINK
4229:Storage
4183:RapidIO
4063:FASTBUS
4018:STD Bus
3915:General
3740:is the
3738:CAN bus
3709:CAN bus
3617:is the
3591:CAN Bus
3575:CAN bus
3524:CAN bus
3466:WP:NOUN
3441:WP:NOUN
3365:Jenks24
3348:WP:NOUN
3334:CAN bus
3319:Jenks24
3187:Support
3143:CAN bus
3076:CAN bus
2973:CAN bus
2869:CAN bus
2865:N-grams
2861:CAN bus
2680:desires
2659:means.â
2439:Support
2373:I agree
2179:Tevildo
2175:Support
2155:en-dash
2151:Support
2137:Ed Brey
2038:CAN 2.x
1808:ECUÂ ???
1452:CANgate
1323:Jerome
1264:or the
962:CAN bus
922:CAN bus
882:CAN bus
842:on the
737:on the
648:on the
543:on the
414:on the
311:on the
199:C-class
154:WPÂ refs
142:scholar
25:CAN bus
4534:S/PDIF
4425:1-Wire
4390:RS-485
4385:RS-423
4380:RS-422
4375:RS-232
4236:ST-506
4193:NVLink
4043:STEbus
4003:Unibus
3662:WP:MOS
3639:Oppose
3413:â Per
3344:WP:NCA
3159:(talk)
2986:(talk)
2969:CANbus
2965:Oppose
2934:Greg L
2846:CANbus
2798:Greg L
2746:Greg L
2684:Greg L
2644:it is
2627:always
2582:Greg L
2550:, and
2507:Greg L
2462:Oppose
2390:Oppose
2343:this..
2153:â The
2006:Lamp90
1952:Brolin
1909:Brolin
1795:EE JRW
1781:EE JRW
1389:Selket
1366:WP:COI
1223:EE JRW
1208:EE JRW
958:merged
918:merged
878:merged
710:Trucks
701:trucks
673:Trucks
376:, and
205:scale.
126:Google
4992:Spark
4955:Spark
4529:McASP
4497:Audio
4442:SMBus
4438:PMBus
4420:UNI/O
4360:HP-IL
4313:SATAe
4298:ESCON
4271:HIPPI
4103:NuBus
4058:CAMAC
4028:Q-Bus
4023:SMBus
4008:VAXBI
3905:wired
3402:Slash
3268:Pc 07
2651:term.
1437:CANoe
981:INTEL
960:into
920:into
880:into
621:Buses
612:buses
568:Buses
169:JSTOR
130:books
84:Seek
5053:talk
5034:talk
5015:talk
4976:talk
4926:talk
4904:talk
4871:talk
4832:talk
4811:talk
4756:The
4742:talk
4723:talk
4719:Wrev
4693:talk
4668:talk
4586:AMBA
4524:MADI
4509:AES3
4370:MIDI
4323:NVMe
4319:AHCI
4281:SCSI
4266:DSSI
4241:ESDI
4118:SBus
4078:EISA
4013:MBus
3903:for
3896:and
3841:KvnG
3830:talk
3812:KvnG
3790:talk
3782:Here
3770:Talk
3754:KvnG
3721:talk
3695:KvnG
3683:Talk
3666:KvnG
3650:Talk
3623:KvnG
3599:KvnG
3593:and
3554:talk
3536:talk
3514:talk
3496:KvnG
3478:talk
3458:KvnG
3443:not
3431:talk
3397:Red
3375:KvnG
3369:talk
3323:talk
3272:talk
3240:talk
3195:talk
3178:talk
3153:Tony
3129:talk
3084:talk
3066:talk
3052:talk
3038:talk
2980:Tony
2956:talk
2938:talk
2920:10Â s
2877:talk
2871:. â
2851:Ruud
2834:talk
2817:talk
2802:talk
2793:here
2774:talk
2750:talk
2738:and
2727:here
2715:here
2704:talk
2688:talk
2672:does
2648:NowâŚ
2640:here
2616:Ruud
2586:talk
2568:talk
2511:talk
2470:talk
2453:talk
2430:talk
2396:and
2381:talk
2363:talk
2354:talk
2319:talk
2278:talk
2263:talk
2238:talk
2183:talk
2164:talk
2141:talk
2065:talk
2029:talk
2010:talk
1956:talk
1933:talk
1913:talk
1899:talk
1871:edit
1849:talk
1833:talk
1799:talk
1785:talk
1637:---
1628:talk
1290:talk
1227:talk
1212:talk
1169:---
1112:talk
1082:talk
1062:talk
162:FENS
136:news
73:and
4970:314
4852:):
4717:--
4637:.
4590:AXI
4519:I²S
4473:USB
4458:D²B
4453:SPI
4448:I3C
4430:I²C
4365:HIL
4350:DCB
4321:or
4308:SSA
4291:SAS
4251:SMD
4246:IPI
4168:AGP
4158:PXI
4148:PCI
4143:UPA
4123:VLB
4113:MCA
4098:VPX
4093:VXS
4088:VXI
4083:VME
4068:LPC
4038:ISA
3824:.
3621:. ~
3508:.
3494:. ~
3392:DVD
3388:USB
3223:SG?
3210:.
3191:Pnm
3170:Yes
3012:.
2971:or
2916:3.1
2664:now
2523:it.
2426:Pnm
2198:.
1286:BIL
1240:Hi
1153:--
1017:it.
834:Low
729:Low
640:Low
535:Low
406:Low
303:Low
176:TWL
5068::
5055:)
5036:)
5017:)
4978:)
4928:)
4906:)
4873:)
4865:--
4834:)
4817:)
4813:â˘
4744:)
4725:)
4695:)
4670:)
4440:,
4436:,
3832:)
3792:)
3773:â˘
3767:â˘
3723:)
3686:â˘
3680:â˘
3653:â˘
3647:â˘
3585:,
3579:11
3556:)
3538:)
3516:)
3480:)
3433:)
3394:)
3390:,
3363:.
3358:.
3336:â
3325:)
3317:.
3298:.
3278:)
3274:â˘
3246:)
3242:â˘
3197:)
3180:)
3172:â
3145:â
3141:â
3131:)
3123:.
3108:.
3086:)
3068:)
3054:)
3040:)
2958:)
2940:)
2879:)
2836:)
2819:)
2804:)
2776:)
2752:)
2706:)
2690:)
2588:)
2570:)
2558:,
2546:,
2513:)
2472:)
2455:)
2432:)
2383:)
2365:)
2348:--
2332:â
2321:)
2299:.
2280:)
2265:)
2244:)
2240:â˘
2185:)
2166:)
2143:)
2127:â
2110:,
2103:.
2088:.
2071:)
2067:â˘
2031:)
2016:)
2012:â˘
1958:)
1935:)
1927:--
1915:)
1901:)
1851:)
1835:)
1801:)
1787:)
1768:1
1762:1
1757:0
1751:0
1746:1
1727:1
1721:1
1716:1
1710:0
1705:1
1630:)
1597:1
1586:0
1575:1
1292:)
1229:)
1214:)
1118:)
1114:â˘
1084:)
1064:)
442:).
372:,
339::
156:)
54:;
5051:(
5032:(
5013:(
4974:(
4944::
4940:@
4924:(
4902:(
4869:(
4830:(
4809:(
4740:(
4721:(
4691:(
4666:(
4592:)
4588:(
4444:)
4432:(
3886:e
3879:t
3872:v
3828:(
3803::
3799:@
3788:(
3734::
3730:@
3719:(
3611::
3607:@
3595:2
3587:2
3571::
3567:@
3552:(
3534:(
3512:(
3476:(
3456:~
3429:(
3373:~
3367:(
3321:(
3270:(
3238:(
3193:(
3176:(
3127:(
3082:(
3064:(
3050:(
3036:(
2954:(
2936:(
2918:Ă
2910:â
2906:â
2875:(
2832:(
2815:(
2800:(
2795:.
2772:(
2748:(
2717:.
2702:(
2686:(
2584:(
2566:(
2509:(
2468:(
2451:(
2428:(
2379:(
2361:(
2352:(
2317:(
2276:(
2261:(
2236:(
2181:(
2162:(
2139:(
2063:(
2050:Č
2027:(
2008:(
1954:(
1931:(
1911:(
1897:(
1875:]
1847:(
1831:(
1797:(
1783:(
1765:0
1754:0
1743:0
1724:1
1713:0
1702:0
1626:(
1594:0
1591:1
1583:0
1580:0
1572:0
1288:(
1225:(
1210:(
1110:(
1080:(
1060:(
974:.
934:.
894:.
846:.
741:.
652:.
547:.
418:.
315:.
211::
172:¡
166:¡
158:¡
151:¡
145:¡
139:¡
133:¡
128:(
58:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.