Feature/sw 48 can servo feature addition

[Pradeep-Carbonix]

1. Update uavcan.equipment.power.CircuitStatus
2. update uavcan.equipment.device.Temperature

[robertlong13]

We should extend the onboard log message instead of adding new messages. If you check the CSRV message in master, it has voltage, current, and temperatures now. We should match master's message.

[Pradeep-Carbonix]

We should extend the onboard log message instead of adding new messages. If you check the CSRV message in master, it has voltage, current, and temperatures now. We should match master's message.

• Telemetry on MKS servos are sent as different messages. This needs to be handled separately:
  • uavcan.equipment.power.CircuitStatus
  • uavcan.equipment.device.Temperature

Thanks for suggesting to make these messages independent. The new generic names will not limit them to only mean servo/actuator logs

[loki077]

For tracking
These are the below 2 CAN packet we are trying to log:

For future reference:
There is a different method of the temperature logging implementation ArduPilot/ardupilot#25993 but as it will make a lot of code change to merge this we will stick to our current implementation for now.

[loki077]

Code structure looks good. Just please confirm in the comments it is been tested on a hardware as I don't have to test on. Also, @Pradeep-Carbonix if you have any test report put a link here which will be good for reference.

[loki077]

@robertlong13 do you have any comments on this PR? or good to go ahead and merge?

[Pradeep-Carbonix]

Check the logs here : \Dropbox (Carbonix Company)\Carbonix Engineering Team Folder\07_Test_Results\MKS HBL3850