I am making good progress on the HoTT telemetry support and am now at the
point where I want to send messages back to the receiver from the PX4 in
response to its poll requests.
The thing is, HoTT receivers use a single wire (@19200, 8N1). Up until now
I have had it connected to the RX port of the PX4 which works fine. Now I
want to connect the the TX port as well. This not surprisingly doesn't seem
to work straight off.
Any suggestions as to what I do I need to do to make this work? Do I need
to enable/disable transmit/receive modes somehow?
hi,
i have my hott system on my desk - nothing connected to it.
but you need to have an artificial delay between characters send.
not 19'200 baud - for the bits yes, but between bytes you have to wait 2ms
before you try to acces the bus again.
> I am making good progress on the HoTT telemetry support and am now at the
> point where I want to send messages back to the receiver from the PX4 in
> response to its poll requests.
> The thing is, HoTT receivers use a single wire (@19200, 8N1). Up until now
> I have had it connected to the RX port of the PX4 which works fine. Now I
> want to connect the the TX port as well. This not surprisingly doesn't seem
> to work straight off.
> Any suggestions as to what I do I need to do to make this work? Do I need
> to enable/disable transmit/receive modes somehow?
> You received this message because you are subscribed to the Google Groups
> px4users group. To post to this group, send email to
> px4users@googlegroups.com. To unsubscribe from this group, send email to
> px4users+unsubscribe@googlegroups.com. For more options, visit this group
> at https://groups.google.com/d/forum/px4users?hl=en-US
Yep, I have all of that implemented. The receiver polls twice per device
with a 200ms window each. On receiving a request a 5ms period of silence on
the line must be respected and after the byte stream can be returned with a
2-3ms delay in between each single byte.
I am just not sure how to make the hardware level stuff work. Just
connecting the wire to UART2's TX and RX port isn't enough as things just
hang.
Thanks,
Simon
On Sun, Nov 18, 2012 at 1:36 PM, Robert Bouwens <bouwens.m...@gmail.com>wrote:
> hi,
> i have my hott system on my desk - nothing connected to it.
> but you need to have an artificial delay between characters send.
> not 19'200 baud - for the bits yes, but between bytes you have to wait 2ms
> before you try to acces the bus again.
>> I am making good progress on the HoTT telemetry support and am now at the
>> point where I want to send messages back to the receiver from the PX4 in
>> response to its poll requests.
>> The thing is, HoTT receivers use a single wire (@19200, 8N1). Up until
>> now I have had it connected to the RX port of the PX4 which works fine. Now
>> I want to connect the the TX port as well. This not surprisingly doesn't
>> seem to work straight off.
>> Any suggestions as to what I do I need to do to make this work? Do I need
>> to enable/disable transmit/receive modes somehow?
>> You received this message because you are subscribed to the Google Groups
>> px4users group. To post to this group, send email to
>> px4users@googlegroups.com. To unsubscribe from this group, send email to
>> px4users+unsubscribe@googlegroups.com. For more options, visit this
>> group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups
> px4users group. To post to this group, send email to
> px4users@googlegroups.com. To unsubscribe from this group, send email to
> px4users+unsubscribe@googlegroups.com. For more options, visit this group
> at https://groups.google.com/d/forum/px4users?hl=en-US
> Yep, I have all of that implemented. The receiver polls twice per device
> with a 200ms window each. On receiving a request a 5ms period of silence on
> the line must be respected and after the byte stream can be returned with a
> 2-3ms delay in between each single byte.
> I am just not sure how to make the hardware level stuff work. Just
> connecting the wire to UART2's TX and RX port isn't enough as things just
> hang.
> Thanks,
> Simon
> On Sun, Nov 18, 2012 at 1:36 PM, Robert Bouwens <bouwens.m...@gmail.com>wrote:
>> hi,
>> i have my hott system on my desk - nothing connected to it.
>> but you need to have an artificial delay between characters send.
>> not 19'200 baud - for the bits yes, but between bytes you have to wait
>> 2ms before you try to acces the bus again.
>>> I am making good progress on the HoTT telemetry support and am now at
>>> the point where I want to send messages back to the receiver from the PX4
>>> in response to its poll requests.
>>> The thing is, HoTT receivers use a single wire (@19200, 8N1). Up until
>>> now I have had it connected to the RX port of the PX4 which works fine. Now
>>> I want to connect the the TX port as well. This not surprisingly doesn't
>>> seem to work straight off.
>>> Any suggestions as to what I do I need to do to make this work? Do I
>>> need to enable/disable transmit/receive modes somehow?
>>> You received this message because you are subscribed to the Google
>>> Groups px4users group. To post to this group, send email to
>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>> to px4users+unsubscribe@googlegroups.com. For more options, visit this
>>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups
>> px4users group. To post to this group, send email to
>> px4users@googlegroups.com. To unsubscribe from this group, send email to
>> px4users+unsubscribe@googlegroups.com. For more options, visit this
>> group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups
> px4users group. To post to this group, send email to
> px4users@googlegroups.com. To unsubscribe from this group, send email to
> px4users+unsubscribe@googlegroups.com. For more options, visit this group
> at https://groups.google.com/d/forum/px4users?hl=en-US
>> Yep, I have all of that implemented. The receiver polls twice per device
>> with a 200ms window each. On receiving a request a 5ms period of silence on
>> the line must be respected and after the byte stream can be returned with a
>> 2-3ms delay in between each single byte.
>> I am just not sure how to make the hardware level stuff work. Just
>> connecting the wire to UART2's TX and RX port isn't enough as things just
>> hang.
>> Thanks,
>> Simon
>> On Sun, Nov 18, 2012 at 1:36 PM, Robert Bouwens <bouwens.m...@gmail.com>wrote:
>>> hi,
>>> i have my hott system on my desk - nothing connected to it.
>>> but you need to have an artificial delay between characters send.
>>> not 19'200 baud - for the bits yes, but between bytes you have to wait
>>> 2ms before you try to acces the bus again.
>>>> I am making good progress on the HoTT telemetry support and am now at
>>>> the point where I want to send messages back to the receiver from the PX4
>>>> in response to its poll requests.
>>>> The thing is, HoTT receivers use a single wire (@19200, 8N1). Up until
>>>> now I have had it connected to the RX port of the PX4 which works fine. Now
>>>> I want to connect the the TX port as well. This not surprisingly doesn't
>>>> seem to work straight off.
>>>> Any suggestions as to what I do I need to do to make this work? Do I
>>>> need to enable/disable transmit/receive modes somehow?
>>>> You received this message because you are subscribed to the Google
>>>> Groups px4users group. To post to this group, send email to
>>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>>> to px4users+unsubscribe@googlegroups.com. For more options, visit this
>>>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>>> You received this message because you are subscribed to the Google
>>> Groups px4users group. To post to this group, send email to
>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>> to px4users+unsubscribe@googlegroups.com. For more options, visit this
>>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups
>> px4users group. To post to this group, send email to
>> px4users@googlegroups.com. To unsubscribe from this group, send email to
>> px4users+unsubscribe@googlegroups.com. For more options, visit this
>> group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups
> px4users group. To post to this group, send email to
> px4users@googlegroups.com. To unsubscribe from this group, send email to
> px4users+unsubscribe@googlegroups.com. For more options, visit this group
> at https://groups.google.com/d/forum/px4users?hl=en-US
I think my mail server ate an earlier reply - at any rate, if you hook this up, wire it to a device-specific IOCTL and we'll see if we can get NuttX to accept it upstream.
On Nov 18, 2012, at 3:11 PM, Simon Wilks <sjwi...@gmail.com> wrote:
> My logic probe is showing my data returning almost correctly...getting closer now :)
> On Sun, Nov 18, 2012 at 1:55 PM, Robert Bouwens <bouwens.m...@gmail.com> wrote:
> hi,
> now i am puzzled.
> from what i hear you do it right.
> i hope to activate my hott transmitter soon.
> will report when i am lucky...
> 2012/11/18 Simon Wilks <sjwi...@gmail.com>
> Hi,
> Yep, I have all of that implemented. The receiver polls twice per device with a 200ms window each. On receiving a request a 5ms period of silence on the line must be respected and after the byte stream can be returned with a 2-3ms delay in between each single byte.
> I am just not sure how to make the hardware level stuff work. Just connecting the wire to UART2's TX and RX port isn't enough as things just hang.
> Thanks,
> Simon
> On Sun, Nov 18, 2012 at 1:36 PM, Robert Bouwens <bouwens.m...@gmail.com> wrote:
> hi,
> i have my hott system on my desk - nothing connected to it.
> but you need to have an artificial delay between characters send.
> not 19'200 baud - for the bits yes, but between bytes you have to wait 2ms before you try to acces the bus again.
> i hope you have succes!
> best robert
> 2012/11/18 Simon Wilks <sjwi...@gmail.com>
> I am making good progress on the HoTT telemetry support and am now at the point where I want to send messages back to the receiver from the PX4 in response to its poll requests.
> The thing is, HoTT receivers use a single wire (@19200, 8N1). Up until now I have had it connected to the RX port of the PX4 which works fine. Now I want to connect the the TX port as well. This not surprisingly doesn't seem to work straight off.
> Any suggestions as to what I do I need to do to make this work? Do I need to enable/disable transmit/receive modes somehow?
> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
No problem. Forced me to dig into stuff and learn ;)
One other question: This protocol seems pretty sensitive to timing.
Currently I am using usleep() to pause between each byte sent (about 3ms is
the goal) but I am getting considerable variations from 1.5ms to 4.5ms.
What is the best way of improve the timing without hogging the CPU?
On Mon, Nov 19, 2012 at 12:32 AM, PX4 Developer <p...@purgatory.org> wrote:
> I think my mail server ate an earlier reply - at any rate, if you hook
> this up, wire it to a device-specific IOCTL and we'll see if we can get
> NuttX to accept it upstream.
> On Nov 18, 2012, at 3:11 PM, Simon Wilks <sjwi...@gmail.com> wrote:
> OK, after lots of reading and trying different things out I worked it out:
>>> Yep, I have all of that implemented. The receiver polls twice per device
>>> with a 200ms window each. On receiving a request a 5ms period of silence on
>>> the line must be respected and after the byte stream can be returned with a
>>> 2-3ms delay in between each single byte.
>>> I am just not sure how to make the hardware level stuff work. Just
>>> connecting the wire to UART2's TX and RX port isn't enough as things just
>>> hang.
>>> Thanks,
>>> Simon
>>> On Sun, Nov 18, 2012 at 1:36 PM, Robert Bouwens <bouwens.m...@gmail.com>wrote:
>>>> hi,
>>>> i have my hott system on my desk - nothing connected to it.
>>>> but you need to have an artificial delay between characters send.
>>>> not 19'200 baud - for the bits yes, but between bytes you have to wait
>>>> 2ms before you try to acces the bus again.
>>>>> I am making good progress on the HoTT telemetry support and am now at
>>>>> the point where I want to send messages back to the receiver from the PX4
>>>>> in response to its poll requests.
>>>>> The thing is, HoTT receivers use a single wire (@19200, 8N1). Up until
>>>>> now I have had it connected to the RX port of the PX4 which works fine. Now
>>>>> I want to connect the the TX port as well. This not surprisingly doesn't
>>>>> seem to work straight off.
>>>>> Any suggestions as to what I do I need to do to make this work? Do I
>>>>> need to enable/disable transmit/receive modes somehow?
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups px4users group. To post to this group, send email to
>>>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>>>> to px4users+unsubscribe@googlegroups.com. For more options, visit
>>>>> this group at https://groups.google.com/d/forum/px4users?hl=en-US
>>>> You received this message because you are subscribed to the Google
>>>> Groups px4users group. To post to this group, send email to
>>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>>> to px4users+unsubscribe@googlegroups.com. For more options, visit this
>>>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>>> You received this message because you are subscribed to the Google
>>> Groups px4users group. To post to this group, send email to
>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>> to px4users+unsubscribe@googlegroups.com. For more options, visit this
>>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups
>> px4users group. To post to this group, send email to
>> px4users@googlegroups.com. To unsubscribe from this group, send email to
>> px4users+unsubscribe@googlegroups.com. For more options, visit this
>> group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups
> px4users group. To post to this group, send email to
> px4users@googlegroups.com. To unsubscribe from this group, send email to
> px4users+unsubscribe@googlegroups.com. For more options, visit this group
> at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups
> px4users group. To post to this group, send email to
> px4users@googlegroups.com. To unsubscribe from this group, send email to
> px4users+unsubscribe@googlegroups.com. For more options, visit this group
> at https://groups.google.com/d/forum/px4users?hl=en-US
> No problem. Forced me to dig into stuff and learn ;)
> One other question: This protocol seems pretty sensitive to timing. Currently I am using usleep() to pause between each byte sent (about 3ms is the goal) but I am getting considerable variations from 1.5ms to 4.5ms. What is the best way of improve the timing without hogging the CPU?
> Thanks,
> Simon
> On Mon, Nov 19, 2012 at 12:32 AM, PX4 Developer <p...@purgatory.org> wrote:
> I think my mail server ate an earlier reply - at any rate, if you hook this up, wire it to a device-specific IOCTL and we'll see if we can get NuttX to accept it upstream.
> On Nov 18, 2012, at 3:11 PM, Simon Wilks <sjwi...@gmail.com> wrote:
>> OK, after lots of reading and trying different things out I worked it out:
>> My logic probe is showing my data returning almost correctly...getting closer now :)
>> On Sun, Nov 18, 2012 at 1:55 PM, Robert Bouwens <bouwens.m...@gmail.com> wrote:
>> hi,
>> now i am puzzled.
>> from what i hear you do it right.
>> i hope to activate my hott transmitter soon.
>> will report when i am lucky...
>> 2012/11/18 Simon Wilks <sjwi...@gmail.com>
>> Hi,
>> Yep, I have all of that implemented. The receiver polls twice per device with a 200ms window each. On receiving a request a 5ms period of silence on the line must be respected and after the byte stream can be returned with a 2-3ms delay in between each single byte.
>> I am just not sure how to make the hardware level stuff work. Just connecting the wire to UART2's TX and RX port isn't enough as things just hang.
>> Thanks,
>> Simon
>> On Sun, Nov 18, 2012 at 1:36 PM, Robert Bouwens <bouwens.m...@gmail.com> wrote:
>> hi,
>> i have my hott system on my desk - nothing connected to it.
>> but you need to have an artificial delay between characters send.
>> not 19'200 baud - for the bits yes, but between bytes you have to wait 2ms before you try to acces the bus again.
>> i hope you have succes!
>> best robert
>> 2012/11/18 Simon Wilks <sjwi...@gmail.com>
>> I am making good progress on the HoTT telemetry support and am now at the point where I want to send messages back to the receiver from the PX4 in response to its poll requests.
>> The thing is, HoTT receivers use a single wire (@19200, 8N1). Up until now I have had it connected to the RX port of the PX4 which works fine. Now I want to connect the the TX port as well. This not surprisingly doesn't seem to work straight off.
>> Any suggestions as to what I do I need to do to make this work? Do I need to enable/disable transmit/receive modes somehow?
>> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4users@googlegroups.com. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
I am not sure how strict it has to be. I guess for testing I could run just
this daemon and give it full priority and once it works start backing off
to see where its limits are.
By definition it should have a 5ms window (and no less) between receiving
the request and responding. The response should have 2-3ms pauses between
each byte.
There is a minimum that should not be undercut but I am not sure what the
upper limit is and if it is OK if it varies per byte. Right now I am just
working on the the receiver obtaining the message correctly (so I want
things as perfect as possible for now) and then I will see how it behaves
with less strict conditions.
Attaching some screenshots for fun. If it is not a timing issue then I just
have something small that needs tweaking and it all should work.
On Mon, Nov 19, 2012 at 1:56 AM, PX4 Developer <p...@purgatory.org> wrote:
> What are the constraints around timing? Reliable serial pacing is
> nontrivial.
> On Nov 18, 2012, at 4:43 PM, Simon Wilks <sjwi...@gmail.com> wrote:
> No problem. Forced me to dig into stuff and learn ;)
> One other question: This protocol seems pretty sensitive to timing.
> Currently I am using usleep() to pause between each byte sent (about 3ms is
> the goal) but I am getting considerable variations from 1.5ms to 4.5ms.
> What is the best way of improve the timing without hogging the CPU?
> Thanks,
> Simon
> On Mon, Nov 19, 2012 at 12:32 AM, PX4 Developer <p...@purgatory.org> wrote:
>> I think my mail server ate an earlier reply - at any rate, if you hook
>> this up, wire it to a device-specific IOCTL and we'll see if we can get
>> NuttX to accept it upstream.
>> On Nov 18, 2012, at 3:11 PM, Simon Wilks <sjwi...@gmail.com> wrote:
>> OK, after lots of reading and trying different things out I worked it out:
>>>> Yep, I have all of that implemented. The receiver polls twice per
>>>> device with a 200ms window each. On receiving a request a 5ms period of
>>>> silence on the line must be respected and after the byte stream can be
>>>> returned with a 2-3ms delay in between each single byte.
>>>> I am just not sure how to make the hardware level stuff work. Just
>>>> connecting the wire to UART2's TX and RX port isn't enough as things just
>>>> hang.
>>>> Thanks,
>>>> Simon
>>>> On Sun, Nov 18, 2012 at 1:36 PM, Robert Bouwens <bouwens.m...@gmail.com
>>>> > wrote:
>>>>> hi,
>>>>> i have my hott system on my desk - nothing connected to it.
>>>>> but you need to have an artificial delay between characters send.
>>>>> not 19'200 baud - for the bits yes, but between bytes you have to wait
>>>>> 2ms before you try to acces the bus again.
>>>>>> I am making good progress on the HoTT telemetry support and am now at
>>>>>> the point where I want to send messages back to the receiver from the PX4
>>>>>> in response to its poll requests.
>>>>>> The thing is, HoTT receivers use a single wire (@19200, 8N1). Up
>>>>>> until now I have had it connected to the RX port of the PX4 which works
>>>>>> fine. Now I want to connect the the TX port as well. This not surprisingly
>>>>>> doesn't seem to work straight off.
>>>>>> Any suggestions as to what I do I need to do to make this work? Do I
>>>>>> need to enable/disable transmit/receive modes somehow?
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups px4users group. To post to this group, send email to
>>>>>> px4users@googlegroups.com. To unsubscribe from this group, send
>>>>>> email to px4users+unsubscribe@googlegroups.com. For more options,
>>>>>> visit this group at
>>>>>> https://groups.google.com/d/forum/px4users?hl=en-US
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups px4users group. To post to this group, send email to
>>>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>>>> to px4users+unsubscribe@googlegroups.com. For more options, visit
>>>>> this group at https://groups.google.com/d/forum/px4users?hl=en-US
>>>> You received this message because you are subscribed to the Google
>>>> Groups px4users group. To post to this group, send email to
>>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>>> to px4users+unsubscribe@googlegroups.com. For more options, visit this
>>>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>>> You received this message because you are subscribed to the Google
>>> Groups px4users group. To post to this group, send email to
>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>> to px4users+unsubscribe@googlegroups.com. For more options, visit this
>>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups
>> px4users group. To post to this group, send email to
>> px4users@googlegroups.com. To unsubscribe from this group, send email to
>> px4users+unsubscribe@googlegroups.com. For more options, visit this
>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups
>> px4users group. To post to this group, send email to
>> px4users@googlegroups.com. To unsubscribe from this group, send email to
>> px4users+unsubscribe@googlegroups.com. For more options, visit this
>> group at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups
> px4users group. To post to this group, send email to
> px4users@googlegroups.com. To unsubscribe from this group, send email to
> px4users+unsubscribe@googlegroups.com. For more options, visit this group
> at https://groups.google.com/d/forum/px4users?hl=en-US
> You received this message because you are subscribed to the Google Groups
> px4users group. To post to this group, send email to
> px4users@googlegroups.com. To unsubscribe from this group, send email to
> px4users+unsubscribe@googlegroups.com. For more options, visit this group
> at https://groups.google.com/d/forum/px4users?hl=en-US
Good news for Graupner HoTT owners...it works! HoTT telemetry is on its way.
Attached is a photo of the MX-20 main screen showing battery voltage
(7.0V), altitude (320m) and baro temperature (31 deg). Not bad for starters
but of course there will be more to come.
I have also attached the logic probe readings from an Electric Air Module I
have and finally what got the PX4 to generate (the same only one of them is
zoomed out a bit more). It turns out even the EAM idle times vary but I
think keeping somewhere above a minimum is fine.
Time to clean up the code, do some more testing and get a first basic
version submitted.
On Mon, Nov 19, 2012 at 2:05 AM, Simon Wilks <sjwi...@gmail.com> wrote:
> I am not sure how strict it has to be. I guess for testing I could run
> just this daemon and give it full priority and once it works start backing
> off to see where its limits are.
> By definition it should have a 5ms window (and no less) between receiving
> the request and responding. The response should have 2-3ms pauses between
> each byte.
> There is a minimum that should not be undercut but I am not sure what the
> upper limit is and if it is OK if it varies per byte. Right now I am just
> working on the the receiver obtaining the message correctly (so I want
> things as perfect as possible for now) and then I will see how it behaves
> with less strict conditions.
> Attaching some screenshots for fun. If it is not a timing issue then I
> just have something small that needs tweaking and it all should work.
> Thanks,
> Simon
> On Mon, Nov 19, 2012 at 1:56 AM, PX4 Developer <p...@purgatory.org> wrote:
>> What are the constraints around timing? Reliable serial pacing is
>> nontrivial.
>> On Nov 18, 2012, at 4:43 PM, Simon Wilks <sjwi...@gmail.com> wrote:
>> No problem. Forced me to dig into stuff and learn ;)
>> One other question: This protocol seems pretty sensitive to timing.
>> Currently I am using usleep() to pause between each byte sent (about 3ms is
>> the goal) but I am getting considerable variations from 1.5ms to 4.5ms.
>> What is the best way of improve the timing without hogging the CPU?
>> Thanks,
>> Simon
>> On Mon, Nov 19, 2012 at 12:32 AM, PX4 Developer <p...@purgatory.org>wrote:
>>> I think my mail server ate an earlier reply - at any rate, if you hook
>>> this up, wire it to a device-specific IOCTL and we'll see if we can get
>>> NuttX to accept it upstream.
>>> On Nov 18, 2012, at 3:11 PM, Simon Wilks <sjwi...@gmail.com> wrote:
>>> OK, after lots of reading and trying different things out I worked it
>>> out:
>>>>> Yep, I have all of that implemented. The receiver polls twice per
>>>>> device with a 200ms window each. On receiving a request a 5ms period of
>>>>> silence on the line must be respected and after the byte stream can be
>>>>> returned with a 2-3ms delay in between each single byte.
>>>>> I am just not sure how to make the hardware level stuff work. Just
>>>>> connecting the wire to UART2's TX and RX port isn't enough as things just
>>>>> hang.
>>>>> Thanks,
>>>>> Simon
>>>>> On Sun, Nov 18, 2012 at 1:36 PM, Robert Bouwens <
>>>>> bouwens.m...@gmail.com> wrote:
>>>>>> hi,
>>>>>> i have my hott system on my desk - nothing connected to it.
>>>>>> but you need to have an artificial delay between characters send.
>>>>>> not 19'200 baud - for the bits yes, but between bytes you have to
>>>>>> wait 2ms before you try to acces the bus again.
>>>>>>> I am making good progress on the HoTT telemetry support and am now
>>>>>>> at the point where I want to send messages back to the receiver from the
>>>>>>> PX4 in response to its poll requests.
>>>>>>> The thing is, HoTT receivers use a single wire (@19200, 8N1). Up
>>>>>>> until now I have had it connected to the RX port of the PX4 which works
>>>>>>> fine. Now I want to connect the the TX port as well. This not surprisingly
>>>>>>> doesn't seem to work straight off.
>>>>>>> Any suggestions as to what I do I need to do to make this work? Do I
>>>>>>> need to enable/disable transmit/receive modes somehow?
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups px4users group. To post to this group, send email to
>>>>>>> px4users@googlegroups.com. To unsubscribe from this group, send
>>>>>>> email to px4users+unsubscribe@googlegroups.com. For more options,
>>>>>>> visit this group at
>>>>>>> https://groups.google.com/d/forum/px4users?hl=en-US
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups px4users group. To post to this group, send email to
>>>>>> px4users@googlegroups.com. To unsubscribe from this group, send
>>>>>> email to px4users+unsubscribe@googlegroups.com. For more options,
>>>>>> visit this group at
>>>>>> https://groups.google.com/d/forum/px4users?hl=en-US
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups px4users group. To post to this group, send email to
>>>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>>>> to px4users+unsubscribe@googlegroups.com. For more options, visit
>>>>> this group at https://groups.google.com/d/forum/px4users?hl=en-US
>>>> You received this message because you are subscribed to the Google
>>>> Groups px4users group. To post to this group, send email to
>>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>>> to px4users+unsubscribe@googlegroups.com. For more options, visit this
>>>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>>> You received this message because you are subscribed to the Google
>>> Groups px4users group. To post to this group, send email to
>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>> to px4users+unsubscribe@googlegroups.com. For more options, visit this
>>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>>> You received this message because you are subscribed to the Google
>>> Groups px4users group. To post to this group, send email to
>>> px4users@googlegroups.com. To unsubscribe from this group, send email
>>> to px4users+unsubscribe@googlegroups.com. For more options, visit this
>>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups
>> px4users group. To post to this group, send email to
>> px4users@googlegroups.com. To unsubscribe from this group, send email to
>> px4users+unsubscribe@googlegroups.com. For more options, visit this
>> group at https://groups.google.com/d/forum/px4users?hl=en-US
>> You received this message because you are subscribed to the Google Groups
>> px4users group. To post to this group, send email to
>> px4users@googlegroups.com. To unsubscribe from this group, send email to
>> px4users+unsubscribe@googlegroups.com. For more options, visit this
>> group at https://groups.google.com/d/forum/px4users?hl=en-US