This is my understanding CAN vs USB,

USB wins for bulk and high speed data transfer.
USB wins for compatibility w/ standard hard/soft ware

USB as a control bus
    Complex driver developed for a different application suite
    Driver is often tweaked
    Millisecond latencies
    Hard latency bound is hard to come by
    Interrupts from node to host are almost unsupported

CAN wins for allowing daisy chaining
CAN wins for electrical reliability

> My question (before we jump into CAN or anything else) is, "What nodes
> need to talk to each other if the flight computer goes down?"
> If the flight computer is down, the goal should be to get the rocket
> to the ground safely.  I don't think there's much point in trying to
> use CAN to log data.  Given the goal of a safe landing, what nodes
> *really* need to talk to each other?
> If it turns out that only two nodes need to talk to each other, why
> bother with CAN?  Why not just run one serial connection between the
> two?  I'm concerned that we're adding too much complexity for what
> should be a really simple backup system.

psas-avionics mailing list

Reply via email to