I'm trying the dev version r1317 because it has integrate GPS on serial port, suitable for the Crius All in one pro board - by the way the pos hold and baro hold are so good on this version.
The problem i have is if i include the #define FAILSAFE option then the board doesnt work properly, it will not arm and it will not read the correct throttle reading in the gui.
just FYI to anyone working on this dev version!
dev version r1317 issues
Re: dev version r1317 issues
Hi,
after updating from 2.1 i have issues in GPS modes PosHold and RTL, PosHold is quite exact but as soon GPS is engaged, my Copter shows small oscillations, in Acro and Stable Mode it flies very stable with no Oscillations at all...
with 2.1 there were no such issues...
is there some new paramter in the code to play with?
btw, all PIDs are stock value...
Flyduino Mega
FreeImu 0.43
GPS from flyduino
Frame Flyduino FCP HL with flyduino ESC and Tiger motors
Quad X configuration
greetings from Black Forest
Peter
after updating from 2.1 i have issues in GPS modes PosHold and RTL, PosHold is quite exact but as soon GPS is engaged, my Copter shows small oscillations, in Acro and Stable Mode it flies very stable with no Oscillations at all...
with 2.1 there were no such issues...
is there some new paramter in the code to play with?
btw, all PIDs are stock value...
Flyduino Mega
FreeImu 0.43
GPS from flyduino
Frame Flyduino FCP HL with flyduino ESC and Tiger motors
Quad X configuration
greetings from Black Forest
Peter
-
- Posts: 178
- Joined: Fri Apr 01, 2011 10:32 pm
- Location: Czech Republic, Prague
Re: dev version r1317 issues
scanman wrote:I'm trying the dev version r1317 because it has integrate GPS on serial port, suitable for the Crius All in one pro board - by the way the pos hold and baro hold are so good on this version.
The problem i have is if i include the #define FAILSAFE option then the board doesnt work properly, it will not arm and it will not read the correct throttle reading in the gui.
just FYI to anyone working on this dev version!
Hi!
Last devs have redesigned failsafe to be very strict about the pulse time: Everything which is under 1000 or above 2000 on any of first four RC channels causes failsafe activation. It's very sensitive, really 999microsecond pulse can be wrong!
I had the same problems and after readjusting radio it's now OK.
Try it!
Roman
-
- Posts: 19
- Joined: Fri Nov 23, 2012 10:30 pm
Re: dev version r1317 issues
Almost not worth mentioning but perhaps need to log it somewhere ... build fails when selecting LCD_CONF_AUX but you have no BUZZER, simple fix in LCD.ino
John
#if defined(BUZZER)
&lcd_param_text52, &conf.activate[BOXBEEPERON],&__AUX1,
&lcd_param_text52, &conf.activate[BOXBEEPERON],&__AUX2,
#ifndef SUPPRESS_LCD_CONF_AUX34
&lcd_param_text52, &conf.activate[BOXBEEPERON],&__AUX3,
&lcd_param_text52, &conf.activate[BOXBEEPERON],&__AUX4,
#endif
#endif
John
#if defined(BUZZER)
&lcd_param_text52, &conf.activate[BOXBEEPERON],&__AUX1,
&lcd_param_text52, &conf.activate[BOXBEEPERON],&__AUX2,
#ifndef SUPPRESS_LCD_CONF_AUX34
&lcd_param_text52, &conf.activate[BOXBEEPERON],&__AUX3,
&lcd_param_text52, &conf.activate[BOXBEEPERON],&__AUX4,
#endif
#endif
Re: dev version r1317 issues
good catch; noted.
-
- Posts: 19
- Joined: Fri Nov 23, 2012 10:30 pm
Re: dev version r1317 issues
Also Hambuger, I have made and tested a code change that moves the pre-compiled camera gimbal gains to the display so they can be changed at the field. I would like in next release to save keep adding it in, how would I go about that?
John
John
Re: dev version r1317 issues
start a new thread in software.development which contains
- a unified diff,
- state against which version,
- describe what it does.
Wait for discussion etc.
- a unified diff,
- state against which version,
- describe what it does.
Wait for discussion etc.
-
- Posts: 19
- Joined: Fri Nov 23, 2012 10:30 pm
Re: dev version r1317 issues
Done, thanks.