trouble using latest GCS_MAVLink with minimOSD-extra

361 views
Skip to first unread message

André Kjellstrup

unread,
Nov 23, 2014, 11:41:59 AM11/23/14
to drones-...@googlegroups.com
I got latest GCS_MAVLink from arduplot, copied to Arduino folder to make a new MinimOSD-extra build with some mavlink data that are not supported in the old mavlink library used by MinimOSD.

on compilation, I get this:

In file included from MinimOSD_Extra_Plane_Pre_release_Beta.ino:72:
/home/andre/Arduino/libraries/GCS_MAVLink/GCS_MAVLink.h:54: error: ‘AP_HAL’ has not been declared
/home/andre/Arduino/libraries/GCS_MAVLink/GCS_MAVLink.h:54: error: expected initializer before ‘*’ token
/home/andre/Arduino/libraries/GCS_MAVLink/GCS_MAVLink.h:57: error: ‘AP_HAL’ has not been declared
/home/andre/Arduino/libraries/GCS_MAVLink/GCS_MAVLink.h:57: error: expected initializer before ‘*’ token
/home/andre/Arduino/libraries/GCS_MAVLink/GCS_MAVLink.h: In function ‘void comm_send_ch(mavlink_channel_t, uint8_t)’:
/home/andre/Arduino/libraries/GCS_MAVLink/GCS_MAVLink.h:76: error: ‘mavlink_comm_0_port’ was not declared in this scope
/home/andre/Arduino/libraries/GCS_MAVLink/GCS_MAVLink.h:79: error: ‘mavlink_comm_1_port’ was not declared in this scope
MinimOSD_Extra_Plane_Pre_release_Beta.ino: In function ‘void setup()’:
MinimOSD_Extra_Plane_Pre_release_Beta:113: error: ‘mavlink_comm_0_port’ was not declared in this scope

Question;  what changed with AP_HAL and the comm ports ?  / what do I need to change ?

André Kjellstrup

unread,
Nov 23, 2014, 1:25:28 PM11/23/14
to drones-...@googlegroups.com
What is the proper method of getting current "GCS_MAVLink" for Arduino ?
I tried to get sources from github, and run "python mavgenerate.py"  - but I am not sure which xml to select as input

Dario Lindo Adres

unread,
Nov 23, 2014, 6:27:22 PM11/23/14
to drones-...@googlegroups.com
Hi André,

Current GCS_Mavlink library files do not support MinimOSD due it depends on Ardupilot chip and sensor board. You need use a diferent GCS_Mavlink library. It not differs in message definitions or data options...just in technical calls to main board sensors.

I have a legacy Remzibi OSD that uses a custom ported MinimOSD firmware. I have attached my GCS_Mavlink folder below so you can try to adapt it for you. It works well with last Ardupilot codes (copter, rover and airplane last version).
This is not a plug and play for you, because my main code is wrote in pure "C+" code and original MinimOSD software is wrote in "Wiring" language, i.e for Arduino IE.

If you want, please, attach for me your current MinimOSD code, and indicates what version of Arduino IE are you using and what type of Atmega chip has your MinimOSD board. I will try to update your Mavlink libraries.

Regards from Spain,
Dario.
GCS_MAVLink.rar

André Kjellstrup

unread,
Nov 24, 2014, 4:25:46 AM11/24/14
to drones-...@googlegroups.com
Hi.
Thanks for the feedback.
I did not modify the MInimOSD code yet,it's still the trunk version of
MinimOSD_Extra_Plane_Pre_release_Beta

All I want to do is to replace the (barometer-onboard) temperature
from MAVLINK_MSG_ID_SCALED_PRESSURE , with the pitot air temperature
from MAVLINK_MSG_ID_HIL_SENSOR

So the current GCS_MAVLink is basically missing
GCS_MAVLink/include/mavlink/v1.0/common/mavlink_msg_hil_sensor.h
I think maybe the simplest solution would be to add that file
manually. - this way it would be easy to get it pulled into the
project as well.

The reason for this change is simple; monitoring and warning for
freezing condition of pitot is much more more important than the
Pixhawk PCB temperature :)
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "drones-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/drones-discuss/ccz9DgWi3T4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> drones-discus...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages