Re: [Paparazzi-devel] Improving the Messages system, comments, thoughts welcome!

[Stephen Dwyer]

Hello,

Regarding the new messages, there are some concerns in the server
logging in the existing messages system. It could be a documentation
issue, or need to be fixed. More information in github issue 215:
https://github.com/paparazzi/paparazzi/issues/215

Any thoughts on this?

Thanks,
-Stephen Dwyer

On Mon, Jun 11, 2012 at 9:26 AM, Felix Ruess <address@hidden> wrote:
> Hi Christoph,
>
> yes, good idea.
> I actually did that quite a long time ago for some tests but never added
> it... Something like
> <message name=INFO_MSG" id="foo">
>   <field name="string" type="unit8[]"/>
> </message>
>
> Cheers, Felix
>
>
> On Mon, Jun 11, 2012 at 4:34 PM, Christoph Niemann
> <address@hidden> wrote:
>>
>> Hi everyone,
>>
>> what I would really like, would be the possibility to send arbritary
>> string. One could do something like printf() in the code, it would be out
>> into a Message of arbritary length (until 0x99 again). The text would the
>> appear as Message in the GCS. Would be very nice for some kind of "Hello
>> World" debugging or for custom navigation modules.
>> Or is there already something similar?
>>
>> Cheers
>>
>> Christoph
>>
>>
>> 2012/6/11 Balazs GATI <address@hidden>
>>>
>>> Hi,
>>>
>>> I don't have too much experience in paparazzi, but I would find a tool
>>> very useful, which can support the effective usage of the available
>>> bandwith. For example a bandwith calculator for a given telemetry config
>>> file, detection of lost packages, latency measurement, etc.
>>>
>>> Balazs
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> 2012.06.11. 11:59 keltezéssel, Felix Ruess írta:
>>>>
>>>> Hi all,
>>>>
>>>> Gautier's student Xavier Gibert is working on an improved messages
>>>> system for Paparazzi.
>>>> So far this is in the messages branch (github pull request
>>>> <https://github.com/paparazzi/paparazzi/pull/213>) where we want to
>>>>
>>>> clean up the messages, finalize new names, etc...
>>>>
>>>> The message definitions are now split up into several xml files under
>>>> conf/messages
>>>> <https://github.com/paparazzi/paparazzi/tree/messages/conf/messages>
>>>>
>>>>
>>>> http://paparazzi.enac.fr/wiki/DevGuide/CommunicationsNew
>>>> github issue 119: integrate mavlink
>>>> <https://github.com/paparazzi/paparazzi/issues/119>
>>>>
>>>>
>>>> Comments, questions, improvements and thoughts on how the messages are
>>>> split up into different files, message names, common message set, etc.
>>>> would be very much welcome!
>>>>
>>>> Cheers, Felix
>>>>
>>>>
>>>> _______________________________________________
>>>> Paparazzi-devel mailing list
>>>> address@hidden
>>>> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>>
>>>
>>> --
>>> Balazs GATI, PhD
>>>     Department of Aircraft and Ships
>>>     Budapest University of Technology and Economics
>>>
>>> Address:   Budapest
>>>          Stoczek u 6. J. ép. 423
>>>          1111
>>> Tel:       +(36)-1-463-1960
>>> Fax:       +(36)-1-463-3080
>>> Homepage: http://rht.bme.hu/~gatib/
>>>
>>> _______________________________________________
>>> Paparazzi-devel mailing list
>>> address@hidden
>>> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>
>>
>>
>> _______________________________________________
>> Paparazzi-devel mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>>
>
>
> _______________________________________________
> Paparazzi-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
>