• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 21 subscribers
  • Views 1232 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RS485 or CAN ?

jchoo235

hi all,

RS-485 is very low level embedded micro's network, but easy to implement with 9 bit Master-slave protocol, first implemented by our Father of Micros, Intel, as Bitbus in 70s.

CAN is robust protocol with its own hardware standard and automatic error detections, originated in 90s by BOSCH for in car communication, but needs upper level application support or firmware library such as CAN-Open or CAN-Kingdom for its full and efficient utilization.

Is any one has ready made source codes for above 485 and CAN to try with micros?

Thanks in advance,

Regards,

Parents
  • 0

    RS485 or CAN ?
    ...
    CAN is robust protocol with its own hardware standard and automatic error detections
    The difference between 485 and CAN basically is that CAN is 485 with a standard protocol.

    There is notrhing hindering that you make a "robust protocol" yourself for 485 I do it all the time.

    CAN ... needs upper level application support
    which often is the reason to use a "homebrew" protocol.

    There is no answer to "should I use CAN or my own protocol" it is totally dependent on the application.

    Is any one has ready made source codes for above 485 and CAN to try with micros?
    For CAN uy a SILabd f04x devkit ($145 if I recall), you get two CAN protoboards and software that makes them 'talk' (the f04x is a '51 derivative).

    Erik

Reply
  • 0

    RS485 or CAN ?
    ...
    CAN is robust protocol with its own hardware standard and automatic error detections
    The difference between 485 and CAN basically is that CAN is 485 with a standard protocol.

    There is notrhing hindering that you make a "robust protocol" yourself for 485 I do it all the time.

    CAN ... needs upper level application support
    which often is the reason to use a "homebrew" protocol.

    There is no answer to "should I use CAN or my own protocol" it is totally dependent on the application.

    Is any one has ready made source codes for above 485 and CAN to try with micros?
    For CAN uy a SILabd f04x devkit ($145 if I recall), you get two CAN protoboards and software that makes them 'talk' (the f04x is a '51 derivative).

    Erik

Children
No data