Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revisionLast revisionBoth sides next revision | ||
| can_faq [2011/12/23 12:21] – created heinz | can_faq [2014/12/16 12:05] – new qa heinz | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| This [[CAN_FaqLinks]] page contains a collection of other FAQs on the web. | This [[CAN_FaqLinks]] page contains a collection of other FAQs on the web. | ||
| + | * What is CAN? | ||
| + | * try to answer it here or see http:// | ||
| * What is the future of CAN ? | * What is the future of CAN ? | ||
| - | * CAN with flexible data rate - CanFd - will be introduced by Bosch in March 2012 on th 13th international CAN Conference | + | * [[can_fd |CAN with flexible data rate - CAN FD]] - was introduced by Bosch in March 2012 on the 13th international CAN Conference |
| * Why maintaining it this way? | * Why maintaining it this way? | ||
| * Because if many experts are contributing, | * Because if many experts are contributing, | ||
| - | * What is CAN? | + | * What is [[can_fd | CAN with flexible Data Rate]] CAN FD |
| - | * try to answer it here or see http:// | + | |
| * Where is CAN used? | * Where is CAN used? | ||
| * http:// | * http:// | ||
| - | * When was CAN invented? | + | * When was CAN invented? |
| * http:// | * http:// | ||
| + | * [[who_is_who | Who is Who]] in CAN ? | ||
| * Where do I get the standards from? | * Where do I get the standards from? | ||
| * The only place is http:// | * The only place is http:// | ||
| * How does CAN work? | * How does CAN work? | ||
| - | * http:// | + | * http:// |
| * An older CiA presentation describing the physical layer, can be found at http:// | * An older CiA presentation describing the physical layer, can be found at http:// | ||
| * Another CiA presentation describing the data link layer DLL http:// | * Another CiA presentation describing the data link layer DLL http:// | ||
| - | * Different CAN implementions | + | * Different CAN implementations |
| * CAN application fields http:// | * CAN application fields http:// | ||
| * What kind of physical layer is used? | * What kind of physical layer is used? | ||
| - | * http:// | + | * [[http:// |
| * Why is my CAN not working ? Here are some [[Problem Solving Questions]] | * Why is my CAN not working ? Here are some [[Problem Solving Questions]] | ||
| * What are Error Active, Error Passive, and Bus off of CAN Bus? | * What are Error Active, Error Passive, and Bus off of CAN Bus? | ||
| - | * read more: CanFaqErrors: | + | * read more: [[can_faq_erors | Can Errors]] |
| + | * What is the purpose of delimiters in CAN frame? HZ: The recessive formated delimiter bits are needed for resynchronization purpose of the nodes in one network by means of a falling edge. They surround the ACK bit which is send in recessive state by the transmitter and is overwritten by a dominant state by all receiving nodes that have sucessfully checked the CRC. | ||
| * What are commonly used bit rates? | * What are commonly used bit rates? | ||
| - | * read more: CanFaqBitrates | + | * read more: [[can_bitrates | CAN FAQ Bitrates]] |
| * Can a CAN Transceiver blow-up when connected to RS232? | * Can a CAN Transceiver blow-up when connected to RS232? | ||
| - | * read more: CanFaqBlowUpRS 232 | + | * read more: [[can_faq_blowUpRS232 | Blow UP RS232]] |
| * What is the difference between Basic CAN and Full CAN? | * What is the difference between Basic CAN and Full CAN? | ||
| - | * read at CanFaqBasicFullCAN | + | * read at [[can_faq_basic_full | CAN FAQ Basic-Full-CAN]] |
| * What is TTCAN | * What is TTCAN | ||
| - | * Time Triggered CAN - to make CAN more predictable. All you need to know at a first glance can be found at the [[http:// | + | * Time Triggered CAN - to make CAN more predictable. All you need to know at a first glance can be found at the [[http:// |
| - | * What connectors are used ? See CanConnectors | + | * What connectors are used ? See [[can_connectors | CAN Connectors]] |
| * depends of the suggestions made in higher layer protocols. The most different kind of connectors and there pinning are described in the CiA paper CiA DR 303-1 V 1.1.1 part 1: CANopen Cabling and Connector Pin Assignment. Version 1.0 can be found at: http:// | * depends of the suggestions made in higher layer protocols. The most different kind of connectors and there pinning are described in the CiA paper CiA DR 303-1 V 1.1.1 part 1: CANopen Cabling and Connector Pin Assignment. Version 1.0 can be found at: http:// | ||
| * Some can also be found directly here: http:// | * Some can also be found directly here: http:// | ||
| * Beware! Some manufacturers use proprietary pinning! | * Beware! Some manufacturers use proprietary pinning! | ||
| - | * WhatIsWrongWithRTR | + | * [[can_higher_layer_protocols: |
| - | * What is CanMessageFiltering | + | * What is [[can_message_filtering | CAN message filtering]] |
| - | * How is the BusOff handled by the CAN controllers? | + | * How is the [[can_bus_off | BusOff]] handled by the CAN controllers? |
| - | * What is the maximum | + | * What is the maximum |
| - | * What is GMLAN ? General Motors CAN protocol. | + | * What is GMLAN ? General Motors CAN protocol. |
| * Is the filter for CAN messages before or after the receiver/ | * Is the filter for CAN messages before or after the receiver/ | ||
| * jk: ACK is always sent by all enabled nodes receiving a valid frame that are not the transmitter of the frame. Filtering only determines whether or not the received message gets stored in a mailbox, and for controllers with multiple filters, which mailbox. Filtering comes after the ACK is sent. | * jk: ACK is always sent by all enabled nodes receiving a valid frame that are not the transmitter of the frame. Filtering only determines whether or not the received message gets stored in a mailbox, and for controllers with multiple filters, which mailbox. Filtering comes after the ACK is sent. | ||
