CAN Bus Signalling

settings for configuring can bus signalling can be found here can termination terminating the can properly ensures signal integrity during operation it is recommended that each end of the can network be terminated, this usually means that termination is enabled on the unit farthest away from the flight computer the can termination resistor can be enabled on the nanodrive 4lpi using the can term pads on the underside of the unit, consult the integration guide for more detailed instructions dronecan the units support the dronecan protocol over can bus connection over dronecan allows for motor drive, telemetry, configuration and firmware updating the motor controller can be connected to hargrave configurator through dronecan for an improved configuration and firmware updating experience more information about the dronecan protocol can be found at the dronecan docs forcing node id the units support dynamic node allocation (dna) within the dronecan ecosystem, allowing quick connection to an existing network the downside is that on any given power up event, the unit may change the node id it is assigned while on the network this makes it difficult to review data and may even result in units not connecting if dna is not operating if all devices are known on the network then it is recommended to force the node ids to a known value, when enabled the preferred node id is forced this ensures a given unit will connect using only the given id however, duplication of ids should be avoided forcing a node id can reduce the time taken for the unit to be on the dronecan network from start up base id the preferred node id (and the node id that will be forced if force node id is enabled) on nano drive 4lpi units is calculated from a configurable base id the individual node ids are enumerated from the base id based on the device index of the motor controller esc index the esc index determines which throttle command a motor controller will respond to, each motor controller must have a unique esc index to be driven separately over dronecan on nanodrive 4lpi motor controllers the esc index is offset based on the device index of that motor controller by default arming dronecan supports an additional mechanism through the 1100 armingstatus message by default this message is required to drive using dronecan signalling the unit must receive a dronecan arming packet with the ‘status fully armed’ status within the configured armed message timeout (1s default duration) to remain armed or driving