Re: CAN-EGT 8 channel thermocouple interface
Posted: Sat Dec 20, 2014 11:14 am
There has been some talk about using CAN as a kind of back haul for other remote devices. Are there any suggested CAN protocols that might allow others to develop modules that can be interfaced. I guess CANopen comes to mind. For example, if someone has PIC experience and motivation to build something, I'm all for supporting them. I'n the early stages of the effort, I'll comment about why I would choose ARM, but if someone chooses something different, I'll probably offer support in what ways I can. If we can choose a published back-haul, this would make it easier for people to interface with rusEFI.
So I wonder what CAN protocols should be considered and why should they be considered? Also is CAN the best back-haul for things like this EGT board?
Other boards I see needing a back-haul mechanism a need for include VR/hall for wheel speed sensing, PWM fuel pump controller, GPS, accelerometer data, transmission controller, ect. So we should consider a back-haul that can support other devices with various levels of packet priority.
So I wonder what CAN protocols should be considered and why should they be considered? Also is CAN the best back-haul for things like this EGT board?
Other boards I see needing a back-haul mechanism a need for include VR/hall for wheel speed sensing, PWM fuel pump controller, GPS, accelerometer data, transmission controller, ect. So we should consider a back-haul that can support other devices with various levels of packet priority.