UAVCAN: Difference between revisions

From STorM32-BGC Wiki
Jump to navigation Jump to search
No edit summary
Line 7: Line 7:
== Uavcan Messages ==
== Uavcan Messages ==


In Uavcan speach this are "data types"
These Uavcan data types are supported:


==== NodeStatus (BC 341) ====
See [http://uavcan.org/Specification/7._List_of_standard_data_types/#nodestatus uavcan.protocol.NodeStatus].
==== GetNodeInfo (SR 1) ====
See [http://uavcan.org/Specification/7._List_of_standard_data_types/#getnodeinfo uavcan.protocol.GetNodeInfo].
==== RestartNode (SR 5) ====
See [http://uavcan.org/Specification/7._List_of_standard_data_types/#restartnode uavcan.protocol.RestartNode].
==== Param.ExecuteOpCode (SR 10) ====
See [http://uavcan.org/Specification/7._List_of_standard_data_types/#executeopcode uavcan.protocol.param.ExecuteOpcode].
==== Param.GetSet (SR 11) ====
See [http://uavcan.org/Specification/7._List_of_standard_data_types/#getset uavcan.protocol.param.GetSet].
==== GimbalStatus (BC 8300) ====
==== GimbalControl (BC 8301) ====
==== GimbalNodeSpecific (BC 8302) ====
==== GimbalNodeSpecificAck (BC 8303) ====


== Configuration ==
== Configuration ==

Revision as of 08:58, 29 July 2017

The information on this page refers to firmware v2.30 and higher.

The STorM32 gimbal controller supports UAVCAN. This allows communicating with the STorM32 board via a CAN bus, very similar to the communication through the serial interfaces or Wifi.

Uavcan Messages

These Uavcan data types are supported:

NodeStatus (BC 341)

See uavcan.protocol.NodeStatus.

GetNodeInfo (SR 1)

See uavcan.protocol.GetNodeInfo.

RestartNode (SR 5)

See uavcan.protocol.RestartNode.

Param.ExecuteOpCode (SR 10)

See uavcan.protocol.param.ExecuteOpcode.

Param.GetSet (SR 11)

See uavcan.protocol.param.GetSet.

GimbalStatus (BC 8300)

GimbalControl (BC 8301)

GimbalNodeSpecific (BC 8302)

GimbalNodeSpecificAck (BC 8303)

Configuration

The Uavcan related parameters are split into the "normal" and the "Uavcan" parameter sections. The parameters in the normal section are accessible like any other parameter, e.g. via the GUI. The parameters in the Uavcan section are however accessible only by using Uavcan's mechanism for Node configuration. The two sections are exclusive, that is, a parameter is found in one or the other section, but not in both. The single exception is the Uavcan Node ID parameter, which can be configured by both mechanisms.

GUI Parameters

The parameters in the normal section are found in the [GUI:Interfaces Tool] window, which is accessible via the [GUI:Tools] menu.

Uavcan Configuration:
Set to “normal” to activate the Uavcan communication. The STorM32 boards needs to be reset for a change to become active.

Uavcan Node ID:
Sets the node ID of the STorM32 controller (default = 71).

Uavcan Parameters

The parameters in the Uavcan section can be accessed e.g. using the UAVCAN GUI Tool, and a SLCAN adapter. A uc4h SLCAN adapter provides probably the cheapest solution.

NodeId:
Sets the node ID of the STorM32 controller (default = 71).

NodeStatus Rate:
Sets the rate with which the uavcan.protocol.NodeStatus message is emitted (default = 1000).

GimbalStatus Rate:
Sets the rate with which the storm32.GimbalStatus message is emitted (default = 500).