search

Syzygyx / DroneWidgets

QtWidgets for Drones
2 stars 1 forks source link

Attach servo output to vehicle gauges #16

Closed dcmcshan closed 9 years ago

dcmcshan commented 9 years ago

For illustration purposes, connect servo1_raw - servo4_raw to our gauges in vehicle widget and scale appropriately. Obviously as the data is only 4 servos, and we have 7 gauges, you will need to use some more than once. It doesn't much matter, I just want for illustration.

BojanKverh commented 9 years ago

OK, I prepared the basis communication, but I will need some help, because I am not sure what is the exact format of text messages MAVLinkDecoder will send out containing these servoX_raw values. MAVLinkDecoder will now write SERVO_MSG: + message to the standard output, whenever it has to emit these message. Is it possible to compile the latest commit and run it with real system and copy/paste me the output lines beginning with SERVO_MSG?

dcmcshan commented 9 years ago

Unfortunately, we don’t have a real system. However, the log file we were using is populating the four servos, so we should see that…

On Jun 10, 2015, at 11:25 AM, BojanKverh notifications@github.com wrote:

OK, I prepared the basis communication, but I will need some help, because I am not sure what kind of text messages MAVLinkDecoder will send out containing these servoX_raw values. MAVLinkDecoder will now write SERVO_MSG: + message to the standard output, whenever it has to emit these message. Is it possible to compile the latest commit and run it with real system and copy/paste me the output lines beginning with SERVO_MSG?

— Reply to this email directly or view it on GitHub https://github.com/Syzygyx/DroneWidgets/issues/16#issuecomment-110843496.

dcmcshan commented 9 years ago

servo1_raw - servo4_raw are active in our log file. They "zero" at 1131 and "max" at about 1650. scale accordingly. if you can also update the digital readout with the raw value, that might be cool as well. again is just for demonstration.

dcmcshan commented 9 years ago

FWIW, it’s not printing out values: (but see other messages - we just want to wire up servo1-4 for now)

SERVO-MSG: "port0_SERVO_OUTPUT_RAW.servo1_raw" SERVO-MSG: "port0_SERVO_OUTPUT_RAW.servo2_raw" SERVO-MSG: "port0_SERVO_OUTPUT_RAW.servo3_raw" SERVO-MSG: "port0_SERVO_OUTPUT_RAW.servo4_raw" SERVO-MSG: "port0_SERVO_OUTPUT_RAW.servo5_raw" SERVO-MSG: "port0_SERVO_OUTPUT_RAW.servo6_raw" SERVO-MSG: “port0_SERVO_OUTPUT_RAW.servo7_raw”

On Jun 10, 2015, at 11:25 AM, BojanKverh notifications@github.com wrote:

OK, I prepared the basis communication, but I will need some help, because I am not sure what kind of text messages MAVLinkDecoder will send out containing these servoX_raw values. MAVLinkDecoder will now write SERVO_MSG: + message to the standard output, whenever it has to emit these message. Is it possible to compile the latest commit and run it with real system and copy/paste me the output lines beginning with SERVO_MSG?

— Reply to this email directly or view it on GitHub https://github.com/Syzygyx/DroneWidgets/issues/16#issuecomment-110843496.

BojanKverh commented 9 years ago

Good observation, thanks, this is what I needed.

BojanKverh commented 9 years ago

This is now done with the latest commit, I connected both, temperature and RPM with different formulas to servo_raw values.