3 ms·

Error corrected, matched pair CAN bus maxes out at 500 Khz; this design has nothing with matched termination and different cable lengths, so is obviously going

Error corrected, matched pair CAN bus maxes out at 500 Khz; this design has nothing with matched termination and different cable lengths, so is obviously going to be much worse. If you're curious about how much worse, start here: https://en.wikipedia.org/wiki/Reflections_of_signals_on_conducting_lines https://en.wikipedia.org/wiki/Reflections_of_signals_on_cond... http://www.smar.com/en/technical-article/inductive-coupling-and-how-to-minimize-their-effects-in-industrial-installations http://www.smar.com/en/technical-article/inductive-coupling-... https://en.wikipedia.org/wiki/Distributed_element_model https://en.wikipedia.org/wiki/Distributed_element_model http://www.connectworld.net/cable-length.html http://www.connectworld.net/cable-length.html

monochr 11y ago
Again, I'm not seeing why it was 33kHz exactly. It sounds like OP just used the wrong prefix.
- tcas 11y ago
  I think it was just lowering the number by a few orders of magnitude to compensate for the effects and logic propagation delay (e.g. I think he said he's using a ripple adder which has a critical path dependent on the bit length), not a precise calculation exact number. My gut instinct says it's probably the right order of magnitude though. You could probably run the long stretches at a much higher clock rate or make the design run on asynchronous clock domains if you use good serialize/deserialize units.