Marcos, según Microchip todos estos micros tienen periférico CAN:
http://www.microchip.com/ParamChartSearch/chart.aspx?branchID=50&mid=10&lang=en&pageId=74
¿sabes si con ellos nos podemos ahorrar los transceptores?, ¿conoces la diferencia entre bus CAN y ECAN?
No conozco ningun micro de marca alguna que implemente al transceptor dentro del micro.
La razon es que ese transceptor es elemento de sacrificio ante brutalidades como que el BUS sea expuesto a tensiones o descargas que provoquen su destrucción, imaginate que si estuvieran incorporados al micro, en ese caso deberías cambiar el micro completo, mientras que de esta forma cambias el transceptor y asunto solucionado (luego de haber localizado la causa de la falla).
Por otro lado por las características del BUS CAN, se busca que aún en circunstancias de falla, cada componente tenga la mayor autonomía y control posibles, por lo tanto en transceptor incorporado tampoco cumple con ese precepto.
Se entiende??
Respecto a las diferencias entre BUS CAN y ECAN, creo que la nota de Microchip es mas explicativa de lo que yo sería, ademas no quiero pecar de sabelotodo, por eso prometo investigar y luego contestaré con más idea al respecto.
La NotaAquí algo de las diferencias, remarco en azul las mas importantes:
CAN INTERFACE CHARACTERISTICS• Implementation of the CAN protocols: CAN 1.2, CAN 2.0A and CAN 2.0B
• Standard and extended data frames
• 0-8 bytes data length
• Programmable bit rate up to 1 Mbit/sec
• Support for remote frames
• Double-buffered receiver with two prioritized received message storage buffers
• Six full (standard/extended identifier) acceptance filters; two associated with the high priority receive buffer and four associated with the low priority receive buffer
• Two full acceptance filter masks, one each associated with the high and low priority receive buffers
• Three transmit buffers with application specified prioritization and abort capability
• Programmable wake-up functionality with integrated low-pass filter
• Programmable Loopback mode supports self-test operation
• Signaling via interrupt capabilities for all CAN receiver and transmitter error states
• Programmable clock source
• Programmable link to timer module for time-stamping and network synchronization
• Low-power Sleep mode
ECAN INTERFACE CHARACTERISTICS• Implementation of the CAN protocols: CAN 1.2, CAN 2.0A and CAN 2.0B
• DeviceNet™ data bytes filter support• Standard and Extended data frames
• 0-8 bytes data length
• Programmable bit rate up to 1 Mbit/sec
• Fully backward compatible with PIC18XX8 CAN module
• Three modes of operation:
- Mode 0 – Legacy mode
- Mode 1 – Enhanced Legacy mode with DeviceNet support
- Mode 2 – FIFO mode with DeviceNet support• Support for remote frames with automated handling
• Double-buffered receiver with two prioritized received message storage buffers
• Six buffers programmable as RX and TX message buffers
• 16 full (standard/extended identifier) acceptance filters that can be linked to one of four masks• Two full acceptance filter masks that can be assigned to any filter
• One full acceptance filter that can be used as either an acceptance filter or acceptance filter mask
• Three dedicated transmit buffers with application specified prioritization and abort capability
• Programmable wake-up functionality with integrated low-pass filter
• Programmable Loopback mode supports self-test operation
• Signaling via interrupt capabilities for all CAN receiver and transmitter error states
• Programmable clock source
• Programmable link to timer module for time-stamping and network synchronization
• Low-power Sleep mode