I am not sure whether someone has already created this topic. If not, is there an app that doesn't use the commander app that will enable one to send PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on an oscilloscope connected to the servo output pin? I have a spektrum receiver which explains why I can't use the commander and px4io apps. I have tried the "tests servo" command which fails with device not found.
<dnovich...@hotmail.com> wrote:
> I am not sure whether someone has already created this topic. If not, is
> there an app that doesn't use the commander app that will enable one to send
> PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on
> an oscilloscope connected to the servo output pin? I have a spektrum
> receiver which explains why I can't use the commander and px4io apps. I have
> tried the "tests servo" command which fails with device not found.
> 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
In a recent push to master I added the currently undocumented 'px4io test' command which will set each of the PX4IO outputs to a measurable PWM value. (1000 - 1700us in 100us steps)
I can't actually promise that the outputs are behaving correctly yet - I'm working on that today - since there have been major code changes in the last couple of days. Keep an eye out for more commits tonight.
On Nov 4, 2012, at 4:39 AM, dnovich...@hotmail.com wrote:
> I am not sure whether someone has already created this topic. If not, is there an app that doesn't use the commander app that will enable one to send PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on an oscilloscope connected to the servo output pin? I have a spektrum receiver which explains why I can't use the commander and px4io apps. I have tried the "tests servo" command which fails with device not found.
> 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've verified that outputs 1-7 on PX4IO are working correctly. Note that the board must be armed (press & hold the safety switch for 1 second until the safety LED starts blinking).
Output zero (closest to the power connector) is being weird; it's probably a timer configuration issue. I'll push a fix when I have it.
> In a recent push to master I added the currently undocumented 'px4io test' command which will set each of the PX4IO outputs to a measurable PWM value. (1000 - 1700us in 100us steps)
> I can't actually promise that the outputs are behaving correctly yet - I'm working on that today - since there have been major code changes in the last couple of days. Keep an eye out for more commits tonight.
> On Nov 4, 2012, at 4:39 AM, dnovich...@hotmail.com wrote:
>> I am not sure whether someone has already created this topic. If not, is there an app that doesn't use the commander app that will enable one to send PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on an oscilloscope connected to the servo output pin? I have a spektrum receiver which explains why I can't use the commander and px4io apps. I have tried the "tests servo" command which fails with device not found.
>> 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
On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
> I've verified that outputs 1-7 on PX4IO are working correctly. Note that > the board must be armed (press & hold the safety switch for 1 second until > the safety LED starts blinking).
> Output zero (closest to the power connector) is being weird; it's probably > a timer configuration issue. I'll push a fix when I have it.
> On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
> In a recent push to master I added the currently undocumented 'px4io test' > command which will set each of the PX4IO outputs to a measurable PWM value. > (1000 - 1700us in 100us steps)
> I can't actually promise that the outputs are behaving correctly yet - I'm > working on that today - since there have been major code changes in the > last couple of days. Keep an eye out for more commits tonight.
> On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com <javascript:> wrote:
> I am not sure whether someone has already created this topic. If not, is > there an app that doesn't use the commander app that will enable one to > send PWM values to the PX4IO board which can be displayed on Qgroundcontrol > or on an oscilloscope connected to the servo output pin? I have a spektrum > receiver which explains why I can't use the commander and px4io apps. I > have tried the "tests servo" command which fails with device not found.
> You received this message because you are subscribed to the Google Groups > px4users group. To post to this group, send email to > px4u...@googlegroups.com <javascript:>. To unsubscribe from this group, > send email to px4users+u...@googlegroups.com <javascript:>. 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 > px4u...@googlegroups.com <javascript:>. To unsubscribe from this group, > send email to px4users+u...@googlegroups.com <javascript:>. For more > options, visit this group at > https://groups.google.com/d/forum/px4users?hl=en-US
I pushed a fix for pwm0 earlier tonight; there's a conflict with the flow control pins for USART2 that's fixed now.
I'm about to push a basic Spektrum decoder and the related support for enabling it. If you have the chance to test and debug it, that would be excellent. There are sure to be some minor issues.
I need to do some work on the serial driver before we are going to be able to handle S.bus properly.
On Nov 4, 2012, at 9:21 PM, dnovich...@hotmail.com wrote:
> I've also had output pins 1-7 working or outputting a constant PWM. Any news on the spektrum code? I can spend a day or two writing a barebone for it.
> On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
> I've verified that outputs 1-7 on PX4IO are working correctly. Note that the board must be armed (press & hold the safety switch for 1 second until the safety LED starts blinking).
> Output zero (closest to the power connector) is being weird; it's probably a timer configuration issue. I'll push a fix when I have it.
> On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
>> In a recent push to master I added the currently undocumented 'px4io test' command which will set each of the PX4IO outputs to a measurable PWM value. (1000 - 1700us in 100us steps)
>> I can't actually promise that the outputs are behaving correctly yet - I'm working on that today - since there have been major code changes in the last couple of days. Keep an eye out for more commits tonight.
>> On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com wrote:
>>> I am not sure whether someone has already created this topic. If not, is there an app that doesn't use the commander app that will enable one to send PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on an oscilloscope connected to the servo output pin? I have a spektrum receiver which explains why I can't use the commander and px4io apps. I have tried the "tests servo" command which fails with device not found.
>>> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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
On Monday, November 5, 2012 8:27:03 AM UTC+1, PX4 Developer wrote:
> I pushed a fix for pwm0 earlier tonight; there's a conflict with the flow > control pins for USART2 that's fixed now.
> I'm about to push a basic Spektrum decoder and the related support for > enabling it. If you have the chance to test and debug it, that would be > excellent. There are sure to be some minor issues.
> I need to do some work on the serial driver before we are going to be able > to handle S.bus properly.
> On Nov 4, 2012, at 9:21 PM, dnovi...@hotmail.com <javascript:> wrote:
> I've also had output pins 1-7 working or outputting a constant PWM. Any > news on the spektrum code? I can spend a day or two writing a barebone for > it.
> On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
>> I've verified that outputs 1-7 on PX4IO are working correctly. Note that >> the board must be armed (press & hold the safety switch for 1 second until >> the safety LED starts blinking).
>> Output zero (closest to the power connector) is being weird; it's >> probably a timer configuration issue. I'll push a fix when I have it.
>> On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
>> In a recent push to master I added the currently undocumented 'px4io >> test' command which will set each of the PX4IO outputs to a measurable PWM >> value. (1000 - 1700us in 100us steps)
>> I can't actually promise that the outputs are behaving correctly yet - >> I'm working on that today - since there have been major code changes in the >> last couple of days. Keep an eye out for more commits tonight.
>> On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com wrote:
>> I am not sure whether someone has already created this topic. If not, is >> there an app that doesn't use the commander app that will enable one to >> send PWM values to the PX4IO board which can be displayed on Qgroundcontrol >> or on an oscilloscope connected to the servo output pin? I have a spektrum >> receiver which explains why I can't use the commander and px4io apps. I >> have tried the "tests servo" command which fails with device not found.
>> You received this message because you are subscribed to the Google Groups >> px4users group. To post to this group, send email to >> px4u...@googlegroups.com. To unsubscribe from this group, send email to >> px4users+u...@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 >> px4u...@googlegroups.com. To unsubscribe from this group, send email to >> px4users+u...@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 > px4u...@googlegroups.com <javascript:>. To unsubscribe from this group, > send email to px4users+u...@googlegroups.com <javascript:>. For more > options, visit this group at > https://groups.google.com/d/forum/px4users?hl=en-US
On Nov 5, 2012, at 12:30 PM, Philipp Oettershagen wrote:
I'd be happy to support you in testing the Spektrum decoder... let me know as soon as you have pushed it!
On Monday, November 5, 2012 8:27:03 AM UTC+1, PX4 Developer wrote:
I pushed a fix for pwm0 earlier tonight; there's a conflict with the flow control pins for USART2 that's fixed now.
I'm about to push a basic Spektrum decoder and the related support for enabling it. If you have the chance to test and debug it, that would be excellent. There are sure to be some minor issues.
I need to do some work on the serial driver before we are going to be able to handle S.bus properly.
On Nov 4, 2012, at 9:21 PM, dnovi...@hotmail.com<javascript:> wrote:
I've also had output pins 1-7 working or outputting a constant PWM. Any news on the spektrum code? I can spend a day or two writing a barebone for it.
On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
I've verified that outputs 1-7 on PX4IO are working correctly. Note that the board must be armed (press & hold the safety switch for 1 second until the safety LED starts blinking).
Output zero (closest to the power connector) is being weird; it's probably a timer configuration issue. I'll push a fix when I have it.
On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
In a recent push to master I added the currently undocumented 'px4io test' command which will set each of the PX4IO outputs to a measurable PWM value. (1000 - 1700us in 100us steps)
I can't actually promise that the outputs are behaving correctly yet - I'm working on that today - since there have been major code changes in the last couple of days. Keep an eye out for more commits tonight.
On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com wrote:
I am not sure whether someone has already created this topic. If not, is there an app that doesn't use the commander app that will enable one to send PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on an oscilloscope connected to the servo output pin? I have a spektrum receiver which explains why I can't use the commander and px4io apps. I have tried the "tests servo" command which fails with device not found.
You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<javascript:>. 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<mailto:px4users@googlegroups.com>. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com<mailto:px4users+unsubscribe@googlegro ups.com>. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
> Use the IO console (connector designated BOOT in the manual) and/or FMU console to track down any remaining issues. If there are, they will be small.
> -Lorenz
> ------------------------------------------------------
> Lorenz Meier
> Institute for Visual Computing
> ETH Zurich
> http://www.inf.ethz.ch/personal/lomeier/
> On Nov 5, 2012, at 12:30 PM, Philipp Oettershagen wrote:
> I'd be happy to support you in testing the Spektrum decoder... let me know as soon as you have pushed it!
> On Monday, November 5, 2012 8:27:03 AM UTC+1, PX4 Developer wrote:
> I pushed a fix for pwm0 earlier tonight; there's a conflict with the flow control pins for USART2 that's fixed now.
> I'm about to push a basic Spektrum decoder and the related support for enabling it. If you have the chance to test and debug it, that would be excellent. There are sure to be some minor issues.
> I need to do some work on the serial driver before we are going to be able to handle S.bus properly.
> On Nov 4, 2012, at 9:21 PM, dnovi...@hotmail.com<javascript:> wrote:
> I've also had output pins 1-7 working or outputting a constant PWM. Any news on the spektrum code? I can spend a day or two writing a barebone for it.
> On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
> I've verified that outputs 1-7 on PX4IO are working correctly. Note that the board must be armed (press & hold the safety switch for 1 second until the safety LED starts blinking).
> Output zero (closest to the power connector) is being weird; it's probably a timer configuration issue. I'll push a fix when I have it.
> On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
> In a recent push to master I added the currently undocumented 'px4io test' command which will set each of the PX4IO outputs to a measurable PWM value. (1000 - 1700us in 100us steps)
> I can't actually promise that the outputs are behaving correctly yet - I'm working on that today - since there have been major code changes in the last couple of days. Keep an eye out for more commits tonight.
> On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com wrote:
> I am not sure whether someone has already created this topic. If not, is there an app that doesn't use the commander app that will enable one to send PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on an oscilloscope connected to the servo output pin? I have a spektrum receiver which explains why I can't use the commander and px4io apps. I have tried the "tests servo" command which fails with device not found.
> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<javascript:>. 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<mailto:px4users@googlegroups.com>. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com<mailto:px4users+unsubscribe@googlegro ups.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 actually think using px4io start rx_spektrum7 is a better approach. Hence I ended up modifying the code. Is it possible for you to add some code that supports Spektrum DX8? One can say that the only difference between the two is that DX8 has an additional channel. Somehow I tried modifying a code that supports DX8 to work with DX7 but could not get it to work. This might be the reason why I am not getting any data out or even see the printf statements in the px4io.cpp code.
On Tuesday, November 6, 2012 4:23:18 PM UTC+11, PX4 Developer wrote:
> That will probably need to be
> px4io start > px4io rx_spektrum7
> as start doesn't (currently) support options like that.
> Please let us know how you go.
> On Nov 5, 2012, at 7:09 AM, Meier Lorenz wrote:
> I have quickly hacked support for it into the FMU code. In theory you > should get Spektrum output now if you start IO with (don't forget to > upgrade):
> Use the IO console (connector designated BOOT in the manual) and/or FMU > console to track down any remaining issues. If there are, they will be > small.
> -Lorenz
> ------------------------------------------------------ > Lorenz Meier > Institute for Visual Computing > ETH Zurich > http://www.inf.ethz.ch/personal/lomeier/
> On Nov 5, 2012, at 12:30 PM, Philipp Oettershagen wrote:
> I'd be happy to support you in testing the Spektrum decoder... let me know > as soon as you have pushed it!
> On Monday, November 5, 2012 8:27:03 AM UTC+1, PX4 Developer wrote:
> I pushed a fix for pwm0 earlier tonight; there's a conflict with the flow > control pins for USART2 that's fixed now.
> I'm about to push a basic Spektrum decoder and the related support for > enabling it. If you have the chance to test and debug it, that would be > excellent. There are sure to be some minor issues.
> I need to do some work on the serial driver before we are going to be able > to handle S.bus properly.
> On Nov 4, 2012, at 9:21 PM, dnovi...@hotmail.com<javascript:> wrote:
> I've also had output pins 1-7 working or outputting a constant PWM. Any > news on the spektrum code? I can spend a day or two writing a barebone for > it.
> On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
> I've verified that outputs 1-7 on PX4IO are working correctly. Note that > the board must be armed (press & hold the safety switch for 1 second until > the safety LED starts blinking).
> Output zero (closest to the power connector) is being weird; it's probably > a timer configuration issue. I'll push a fix when I have it.
> On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
> In a recent push to master I added the currently undocumented 'px4io test' > command which will set each of the PX4IO outputs to a measurable PWM value. > (1000 - 1700us in 100us steps)
> I can't actually promise that the outputs are behaving correctly yet - I'm > working on that today - since there have been major code changes in the > last couple of days. Keep an eye out for more commits tonight.
> On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com wrote:
> I am not sure whether someone has already created this topic. If not, is > there an app that doesn't use the commander app that will enable one to > send PWM values to the PX4IO board which can be displayed on Qgroundcontrol > or on an oscilloscope connected to the servo output pin? I have a spektrum > receiver which explains why I can't use the commander and px4io apps. I > have tried the "tests servo" command which fails with device not found.
> You received this message because you are subscribed to the Google Groups > px4users group. To post to this group, send email to > px4u...@googlegroups.com. To unsubscribe from this group, send email to > px4users+u...@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 > px4u...@googlegroups.com. To unsubscribe from this group, send email to > px4users+u...@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 > px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, > send email to px4users+u...@googlegroups.com<javascript:>. 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 > px4u...@googlegroups.com <javascript:><mailto:px4u...@googlegroups.com<javascript:>>. > To unsubscribe from this group, send email to > px4users+u...@googlegroups.com <javascript:><mailto: > px4users+unsubscribe@googlegroups.com <javascript:>>. 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 > px4u...@googlegroups.com <javascript:>. To unsubscribe from this group, > send email to px4users+u...@googlegroups.com <javascript:>. For more > options, visit this group at > https://groups.google.com/d/forum/px4users?hl=en-US
I think to make your testing efficient you need to dig a bit deeper. Look at apps/px4io/mixer.c, the Spektrum parsing is there. Adding 8 Ch support there and in FMU should be straightforward. Also make sure to put some debugging output there, since it will tell you more than just measuring on the FMU side.
-Lorenz
dnovich...@hotmail.com hat geschrieben:
I actually think using px4io start rx_spektrum7 is a better approach. Hence I ended up modifying the code. Is it possible for you to add some code that supports Spektrum DX8? One can say that the only difference between the two is that DX8 has an additional channel. Somehow I tried modifying a code that supports DX8 to work with DX7 but could not get it to work. This might be the reason why I am not getting any data out or even see the printf statements in the px4io.cpp code.
On Tuesday, November 6, 2012 4:23:18 PM UTC+11, PX4 Developer wrote:
That will probably need to be
px4io start
px4io rx_spektrum7
as start doesn't (currently) support options like that.
Please let us know how you go.
On Nov 5, 2012, at 7:09 AM, Meier Lorenz wrote:
I have quickly hacked support for it into the FMU code. In theory you should get Spektrum output now if you start IO with (don't forget to upgrade):
On Nov 5, 2012, at 12:30 PM, Philipp Oettershagen wrote:
I'd be happy to support you in testing the Spektrum decoder... let me know as soon as you have pushed it!
On Monday, November 5, 2012 8:27:03 AM UTC+1, PX4 Developer wrote:
I pushed a fix for pwm0 earlier tonight; there's a conflict with the flow control pins for USART2 that's fixed now.
I'm about to push a basic Spektrum decoder and the related support for enabling it. If you have the chance to test and debug it, that would be excellent. There are sure to be some minor issues.
I need to do some work on the serial driver before we are going to be able to handle S.bus properly.
On Nov 4, 2012, at 9:21 PM, dnovi...@hotmail.com<javascript:> wrote:
I've also had output pins 1-7 working or outputting a constant PWM. Any news on the spektrum code? I can spend a day or two writing a barebone for it.
On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
I've verified that outputs 1-7 on PX4IO are working correctly. Note that the board must be armed (press & hold the safety switch for 1 second until the safety LED starts blinking).
Output zero (closest to the power connector) is being weird; it's probably a timer configuration issue. I'll push a fix when I have it.
On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
In a recent push to master I added the currently undocumented 'px4io test' command which will set each of the PX4IO outputs to a measurable PWM value. (1000 - 1700us in 100us steps)
I can't actually promise that the outputs are behaving correctly yet - I'm working on that today - since there have been major code changes in the last couple of days. Keep an eye out for more commits tonight.
On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com wrote:
I am not sure whether someone has already created this topic. If not, is there an app that doesn't use the commander app that will enable one to send PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on an oscilloscope connected to the servo output pin? I have a spektrum receiver which explains why I can't use the commander and px4io apps. I have tried the "tests servo" command which fails with device not found.
You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<javascript:>. 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 px4u...@googlegroups.com<mailto:px4u...@googlegroups.com>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<mailto: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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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
My apologies; the DSM/Spektrum parser I pushed recently was based on a mis-understanding of the protocol (and not having hardware to test with...). I'm about to push an updated version (still untested) that might come closer to actually DTRT.
It ought to work with most of the current protocols; you'll need to tell it whether you are using 10- or 11-bit data with
px4io rx_dsm_10bit
or
px4io rx_dsm_11bit
(this replaces the previous spektrum6/spektrum7 options)
> I have some printf statements in apps/px4io/mixer.c to tell me the channel values. None of those printf's get printed. If it shouldn't matter whether it is a DX8 or DX7, then I should get it working tonight. It just that from an old quadrotor project when we attempted using a DX7 in place of a DX8, our system didn't work.
> > I think to make your testing efficient you need to dig a bit deeper. Look at apps/px4io/mixer.c, the Spektrum parsing is there. Adding 8 Ch support there and in FMU should be straightforward. Also make sure to put some debugging output there, since it will tell you more than just measuring on the FMU side.
> > -Lorenz
> > dnovich...@hotmail.com hat geschrieben:
> > I actually think using px4io start rx_spektrum7 is a better approach. Hence I ended up modifying the code. Is it possible for you to add some code that supports Spektrum DX8? One can say that the only difference between the two is that DX8 has an additional channel. Somehow I tried modifying a code that supports DX8 to work with DX7 but could not get it to work. This might be the reason why I am not getting any data out or even see the printf statements in the px4io.cpp code.
> > On Tuesday, November 6, 2012 4:23:18 PM UTC+11, PX4 Developer wrote:
> > That will probably need to be
> > px4io start
> > px4io rx_spektrum7
> > as start doesn't (currently) support options like that.
> > Please let us know how you go.
> > On Nov 5, 2012, at 7:09 AM, Meier Lorenz wrote:
> > I have quickly hacked support for it into the FMU code. In theory you should get Spektrum output now if you start IO with (don't forget to upgrade):
> > Use the IO console (connector designated BOOT in the manual) and/or FMU console to track down any remaining issues. If there are, they will be small.
> > -Lorenz
> > ------------------------------------------------------
> > Lorenz Meier
> > Institute for Visual Computing
> > ETH Zurich
> > http://www.inf.ethz.ch/personal/lomeier/
> > On Nov 5, 2012, at 12:30 PM, Philipp Oettershagen wrote:
> > I'd be happy to support you in testing the Spektrum decoder... let me know as soon as you have pushed it!
> > On Monday, November 5, 2012 8:27:03 AM UTC+1, PX4 Developer wrote:
> > I pushed a fix for pwm0 earlier tonight; there's a conflict with the flow control pins for USART2 that's fixed now.
> > I'm about to push a basic Spektrum decoder and the related support for enabling it. If you have the chance to test and debug it, that would be excellent. There are sure to be some minor issues.
> > I need to do some work on the serial driver before we are going to be able to handle S.bus properly.
> > On Nov 4, 2012, at 9:21 PM, dnovi...@hotmail.com<javascript:> wrote:
> > I've also had output pins 1-7 working or outputting a constant PWM. Any news on the spektrum code? I can spend a day or two writing a barebone for it.
> > On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
> > I've verified that outputs 1-7 on PX4IO are working correctly. Note that the board must be armed (press & hold the safety switch for 1 second until the safety LED starts blinking).
> > Output zero (closest to the power connector) is being weird; it's probably a timer configuration issue. I'll push a fix when I have it.
> > On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
> > In a recent push to master I added the currently undocumented 'px4io test' command which will set each of the PX4IO outputs to a measurable PWM value. (1000 - 1700us in 100us steps)
> > I can't actually promise that the outputs are behaving correctly yet - I'm working on that today - since there have been major code changes in the last couple of days. Keep an eye out for more commits tonight.
> > On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com wrote:
> > I am not sure whether someone has already created this topic. If not, is there an app that doesn't use the commander app that will enable one to send PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on an oscilloscope connected to the servo output pin? I have a spektrum receiver which explains why I can't use the commander and px4io apps. I have tried the "tests servo" command which fails with device not found.
> > You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<javascript:>. 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 px4u...@googlegroups.com<mailto:px4u...@googlegroups.com>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<mailto: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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 topx4users+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 topx4users+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/px4users?hl=en-US
Hi Lorenz, I could not get it to work with Spektrum DX8 yesterday but however made modifications to the code and created a ppm signal using an arduino board. I was able to see the RC signal and any changes using qgroundcontrol. I'll do the DX8 testing and will tell you how it goes. Is there a special boot connector to connect to the IO board?
On Wednesday, 7 November 2012 21:47:11 UTC+11, PX4 Developer wrote:
> Moses,
> My apologies; the DSM/Spektrum parser I pushed recently was based on a > mis-understanding of the protocol (and not having hardware to test > with...). I'm about to push an updated version (still untested) that might > come closer to actually DTRT.
> It ought to work with most of the current protocols; you'll need to tell > it whether you are using 10- or 11-bit data with
> px4io rx_dsm_10bit
> or
> px4io rx_dsm_11bit
> (this replaces the previous spektrum6/spektrum7 options)
> On Nov 6, 2012, at 12:21 AM, Moses Bangura wrote:
> Hi Lorenz,
> I have some printf statements in apps/px4io/mixer.c to tell me the channel > values. None of those printf's get printed. If it shouldn't matter whether > it is a DX8 or DX7, then I should get it working tonight. It just that from > an old quadrotor project when we attempted using a DX7 in place of a DX8, > our system didn't work.
> > I think to make your testing efficient you need to dig a bit deeper. > Look at apps/px4io/mixer.c, the Spektrum parsing is there. Adding 8 Ch > support there and in FMU should be straightforward. Also make sure to put > some debugging output there, since it will tell you more than just > measuring on the FMU side.
> > -Lorenz
> > dnovi...@hotmail.com <javascript:> hat geschrieben: > > I actually think using px4io start rx_spektrum7 is a better approach. > Hence I ended up modifying the code. Is it possible for you to add some > code that supports Spektrum DX8? One can say that the only difference > between the two is that DX8 has an additional channel. Somehow I tried > modifying a code that supports DX8 to work with DX7 but could not get it to > work. This might be the reason why I am not getting any data out or even > see the printf statements in the px4io.cpp code.
> > On Tuesday, November 6, 2012 4:23:18 PM UTC+11, PX4 Developer wrote:
> > That will probably need to be
> > px4io start > > px4io rx_spektrum7
> > as start doesn't (currently) support options like that.
> > Please let us know how you go.
> > On Nov 5, 2012, at 7:09 AM, Meier Lorenz wrote:
> > I have quickly hacked support for it into the FMU code. In theory you > should get Spektrum output now if you start IO with (don't forget to > upgrade):
> > Use the IO console (connector designated BOOT in the manual) and/or FMU > console to track down any remaining issues. If there are, they will be > small.
> > -Lorenz
> > ------------------------------------------------------ > > Lorenz Meier > > Institute for Visual Computing > > ETH Zurich > > http://www.inf.ethz.ch/personal/lomeier/
> > On Nov 5, 2012, at 12:30 PM, Philipp Oettershagen wrote:
> > I'd be happy to support you in testing the Spektrum decoder... let me > know as soon as you have pushed it!
> > On Monday, November 5, 2012 8:27:03 AM UTC+1, PX4 Developer wrote:
> > I pushed a fix for pwm0 earlier tonight; there's a conflict with the > flow control pins for USART2 that's fixed now.
> > I'm about to push a basic Spektrum decoder and the related support for > enabling it. If you have the chance to test and debug it, that would be > excellent. There are sure to be some minor issues.
> > I need to do some work on the serial driver before we are going to be > able to handle S.bus properly.
> > On Nov 4, 2012, at 9:21 PM, dnovi...@hotmail.com<javascript:> wrote:
> > I've also had output pins 1-7 working or outputting a constant PWM. Any > news on the spektrum code? I can spend a day or two writing a barebone for > it.
> > On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
> > I've verified that outputs 1-7 on PX4IO are working correctly. Note that > the board must be armed (press & hold the safety switch for 1 second until > the safety LED starts blinking).
> > Output zero (closest to the power connector) is being weird; it's > probably a timer configuration issue. I'll push a fix when I have it.
> > On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
> > In a recent push to master I added the currently undocumented 'px4io > test' command which will set each of the PX4IO outputs to a measurable PWM > value. (1000 - 1700us in 100us steps)
> > I can't actually promise that the outputs are behaving correctly yet - > I'm working on that today - since there have been major code changes in the > last couple of days. Keep an eye out for more commits tonight.
> > On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com wrote:
> > I am not sure whether someone has already created this topic. If not, is > there an app that doesn't use the commander app that will enable one to > send PWM values to the PX4IO board which can be displayed on Qgroundcontrol > or on an oscilloscope connected to the servo output pin? I have a spektrum > receiver which explains why I can't use the commander and px4io apps. I > have tried the "tests servo" command which fails with device not found.
> > You received this message because you are subscribed to the Google > Groups px4users group. To post to this group, send email to > px4u...@googlegroups.com. To unsubscribe from this group, send email to > px4users+u...@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 > px4u...@googlegroups.com. To unsubscribe from this group, send email to > px4users+u...@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 > px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, > send email to px4users+u...@googlegroups.com<javascript:>. 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 > px4u...@googlegroups.com<mailto:px4u...@googlegroups.com>. To unsubscribe > from this group, send email to px4users+u...@googlegroups.com< > mailto:px4use...@googlegroups.com <javascript:>>. 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 > px4u...@googlegroups.com. To unsubscribe from this group, send email to > px4users+u...@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 > px4u...@googlegroups.com <javascript:>. To unsubscribe from this group, > send email to px4users+u...@googlegroups.com <javascript:>. 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 > px4u...@googlegroups.com <javascript:>. To unsubscribe from this group, > send email topx4users+u...@googlegroups.com <javascript:>. 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 > px4u...@googlegroups.com <javascript:>. To unsubscribe from this group, > send email topx4users+u...@googlegroups.com <javascript:>. For more > options, visit this group at > https://groups.google.com/d/forum/px4users?hl=en-US
On Nov 7, 2012, at 2:39 PM, dnovich...@hotmail.com<mailto:dnovich...@hotmail.com> wrote:
Hi Lorenz,
I could not get it to work with Spektrum DX8 yesterday but however made modifications to the code and created a ppm signal using an arduino board. I was able to see the RC signal and any changes using qgroundcontrol. I'll do the DX8 testing and will tell you how it goes. Is there a special boot connector to connect to the IO board?
Regards,
Moses.
On Wednesday, 7 November 2012 21:47:11 UTC+11, PX4 Developer wrote:
Moses,
My apologies; the DSM/Spektrum parser I pushed recently was based on a mis-understanding of the protocol (and not having hardware to test with...). I'm about to push an updated version (still untested) that might come closer to actually DTRT.
It ought to work with most of the current protocols; you'll need to tell it whether you are using 10- or 11-bit data with
px4io rx_dsm_10bit
or
px4io rx_dsm_11bit
(this replaces the previous spektrum6/spektrum7 options)
On Nov 6, 2012, at 12:21 AM, Moses Bangura wrote:
Hi Lorenz,
I have some printf statements in apps/px4io/mixer.c to tell me the channel values. None of those printf's get printed. If it shouldn't matter whether it is a DX8 or DX7, then I should get it working tonight. It just that from an old quadrotor project when we attempted using a DX7 in place of a DX8, our system didn't work.
> I think to make your testing efficient you need to dig a bit deeper. Look at apps/px4io/mixer.c, the Spektrum parsing is there. Adding 8 Ch support there and in FMU should be straightforward. Also make sure to put some debugging output there, since it will tell you more than just measuring on the FMU side.
> -Lorenz
> dnovi...@hotmail.com<javascript:> hat geschrieben:
> I actually think using px4io start rx_spektrum7 is a better approach. Hence I ended up modifying the code. Is it possible for you to add some code that supports Spektrum DX8? One can say that the only difference between the two is that DX8 has an additional channel. Somehow I tried modifying a code that supports DX8 to work with DX7 but could not get it to work. This might be the reason why I am not getting any data out or even see the printf statements in the px4io.cpp code.
> On Tuesday, November 6, 2012 4:23:18 PM UTC+11, PX4 Developer wrote:
> That will probably need to be
> px4io start
> px4io rx_spektrum7
> as start doesn't (currently) support options like that.
> Please let us know how you go.
> On Nov 5, 2012, at 7:09 AM, Meier Lorenz wrote:
> I have quickly hacked support for it into the FMU code. In theory you should get Spektrum output now if you start IO with (don't forget to upgrade):
> Use the IO console (connector designated BOOT in the manual) and/or FMU console to track down any remaining issues. If there are, they will be small.
> -Lorenz
> ------------------------------------------------------
> Lorenz Meier
> Institute for Visual Computing
> ETH Zurich
> http://www.inf.ethz.ch/personal/lomeier/
> On Nov 5, 2012, at 12:30 PM, Philipp Oettershagen wrote:
> I'd be happy to support you in testing the Spektrum decoder... let me know as soon as you have pushed it!
> On Monday, November 5, 2012 8:27:03 AM UTC+1, PX4 Developer wrote:
> I pushed a fix for pwm0 earlier tonight; there's a conflict with the flow control pins for USART2 that's fixed now.
> I'm about to push a basic Spektrum decoder and the related support for enabling it. If you have the chance to test and debug it, that would be excellent. There are sure to be some minor issues.
> I need to do some work on the serial driver before we are going to be able to handle S.bus properly.
> On Nov 4, 2012, at 9:21 PM, dnovi...@hotmail.com<javascript:> wrote:
> I've also had output pins 1-7 working or outputting a constant PWM. Any news on the spektrum code? I can spend a day or two writing a barebone for it.
> On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
> I've verified that outputs 1-7 on PX4IO are working correctly. Note that the board must be armed (press & hold the safety switch for 1 second until the safety LED starts blinking).
> Output zero (closest to the power connector) is being weird; it's probably a timer configuration issue. I'll push a fix when I have it.
> On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
> In a recent push to master I added the currently undocumented 'px4io test' command which will set each of the PX4IO outputs to a measurable PWM value. (1000 - 1700us in 100us steps)
> I can't actually promise that the outputs are behaving correctly yet - I'm working on that today - since there have been major code changes in the last couple of days. Keep an eye out for more commits tonight.
> On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com wrote:
> I am not sure whether someone has already created this topic. If not, is there an app that doesn't use the commander app that will enable one to send PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on an oscilloscope connected to the servo output pin? I have a spektrum receiver which explains why I can't use the commander and px4io apps. I have tried the "tests servo" command which fails with device not found.
> You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<javascript:>. 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 px4u...@googlegroups.com<mailto:px4u...@googlegroups.com>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<mailto:px4use...@googlegroups.com<javascript :>>. 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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<javascript:>. 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 px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, send email topx4users+u...@googlegroups.com<javascript:>. 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 px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, send email topx4users+u...@googlegroups.com<javascript:>. 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<mailto:px4users@googlegroups.com>. To unsubscribe from this group, send email to px4users+unsubscribe@googlegroups.com<mailto:px4users+unsubscribe@googlegro ups.com>. For more options,
...
On Nov 7, 2012, at 5:39 AM, dnovich...@hotmail.com wrote:
> I could not get it to work with Spektrum DX8 yesterday but however made modifications to the code and created a ppm signal using an arduino board. I was able to see the RC signal and any changes using qgroundcontrol. I'll do the DX8 testing and will tell you how it goes. Is there a special boot connector to connect to the IO board?
Moses,
I think by "boot connector" you mean the curiously-labelled serial console connector? That should be a standard 3-pin Hirose DF-13. You can cut the side tabs off a 3-pin Picoblade if you have spares and it will mate as well.
Do note that the console shares the same UART as the DSM/S.bus input. You should be OK sending output to it, but selecting S.bus mode will change the bit rate.
> On Wednesday, 7 November 2012 21:47:11 UTC+11, PX4 Developer wrote:
> Moses,
> My apologies; the DSM/Spektrum parser I pushed recently was based on a mis-understanding of the protocol (and not having hardware to test with...). I'm about to push an updated version (still untested) that might come closer to actually DTRT.
> It ought to work with most of the current protocols; you'll need to tell it whether you are using 10- or 11-bit data with
> px4io rx_dsm_10bit
> or
> px4io rx_dsm_11bit
> (this replaces the previous spektrum6/spektrum7 options)
> On Nov 6, 2012, at 12:21 AM, Moses Bangura wrote:
>> Hi Lorenz,
>> I have some printf statements in apps/px4io/mixer.c to tell me the channel values. None of those printf's get printed. If it shouldn't matter whether it is a DX8 or DX7, then I should get it working tonight. It just that from an old quadrotor project when we attempted using a DX7 in place of a DX8, our system didn't work.
>> > I think to make your testing efficient you need to dig a bit deeper. Look at apps/px4io/mixer.c, the Spektrum parsing is there. Adding 8 Ch support there and in FMU should be straightforward. Also make sure to put some debugging output there, since it will tell you more than just measuring on the FMU side.
>> > -Lorenz
>> > dnovi...@hotmail.com hat geschrieben:
>> > I actually think using px4io start rx_spektrum7 is a better approach. Hence I ended up modifying the code. Is it possible for you to add some code that supports Spektrum DX8? One can say that the only difference between the two is that DX8 has an additional channel. Somehow I tried modifying a code that supports DX8 to work with DX7 but could not get it to work. This might be the reason why I am not getting any data out or even see the printf statements in the px4io.cpp code.
>> > On Tuesday, November 6, 2012 4:23:18 PM UTC+11, PX4 Developer wrote:
>> > That will probably need to be
>> > px4io start
>> > px4io rx_spektrum7
>> > as start doesn't (currently) support options like that.
>> > Please let us know how you go.
>> > On Nov 5, 2012, at 7:09 AM, Meier Lorenz wrote:
>> > I have quickly hacked support for it into the FMU code. In theory you should get Spektrum output now if you start IO with (don't forget to upgrade):
>> > Use the IO console (connector designated BOOT in the manual) and/or FMU console to track down any remaining issues. If there are, they will be small.
>> > -Lorenz
>> > ------------------------------------------------------
>> > Lorenz Meier
>> > Institute for Visual Computing
>> > ETH Zurich
>> > http://www.inf.ethz.ch/personal/lomeier/
>> > On Nov 5, 2012, at 12:30 PM, Philipp Oettershagen wrote:
>> > I'd be happy to support you in testing the Spektrum decoder... let me know as soon as you have pushed it!
>> > On Monday, November 5, 2012 8:27:03 AM UTC+1, PX4 Developer wrote:
>> > I pushed a fix for pwm0 earlier tonight; there's a conflict with the flow control pins for USART2 that's fixed now.
>> > I'm about to push a basic Spektrum decoder and the related support for enabling it. If you have the chance to test and debug it, that would be excellent. There are sure to be some minor issues.
>> > I need to do some work on the serial driver before we are going to be able to handle S.bus properly.
>> > On Nov 4, 2012, at 9:21 PM, dnovi...@hotmail.com<javascript:> wrote:
>> > I've also had output pins 1-7 working or outputting a constant PWM. Any news on the spektrum code? I can spend a day or two writing a barebone for it.
>> > On Monday, November 5, 2012 9:08:27 AM UTC+11, PX4 Developer wrote:
>> > I've verified that outputs 1-7 on PX4IO are working correctly. Note that the board must be armed (press & hold the safety switch for 1 second until the safety LED starts blinking).
>> > Output zero (closest to the power connector) is being weird; it's probably a timer configuration issue. I'll push a fix when I have it.
>> > On Nov 4, 2012, at 1:21 PM, PX4 Developer wrote:
>> > In a recent push to master I added the currently undocumented 'px4io test' command which will set each of the PX4IO outputs to a measurable PWM value. (1000 - 1700us in 100us steps)
>> > I can't actually promise that the outputs are behaving correctly yet - I'm working on that today - since there have been major code changes in the last couple of days. Keep an eye out for more commits tonight.
>> > On Nov 4, 2012, at 4:39 AM, dnovi...@hotmail.com wrote:
>> > I am not sure whether someone has already created this topic. If not, is there an app that doesn't use the commander app that will enable one to send PWM values to the PX4IO board which can be displayed on Qgroundcontrol or on an oscilloscope connected to the servo output pin? I have a spektrum receiver which explains why I can't use the commander and px4io apps. I have tried the "tests servo" command which fails with device not found.
>> > You received this message because you are subscribed to the Google Groups px4users group. To post to this group, send email to px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com<javascript:>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<javascript:>. 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 px4u...@googlegroups.com<mailto:px4u...@googlegroups.com>. To unsubscribe from this group, send email to px4users+u...@googlegroups.com<mailto:px4use...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email to px4users+u...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email topx4users+u...@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 px4u...@googlegroups.com. To unsubscribe from this group, send email
