Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Some extra features

Posted by osnwt, 04 January 2012 · 147 views

Quite often I am asked on forums: "Why don't you have this feature?". Some of requests can be handled using officially released firmware and software. But there are some which have strong demand, obvious reasons, but aren't addressed in the official OpenPilot firmware. Moreover, some of them will never be included into official builds because of many reasons...

What should we do? Sit and wait? No. The project is open, and and we are free to implement basically anything we want if we can, right? That's why I created this blog. It lists some features I'm working on, and which probably will be included in my unofficial software distributions (no promises).

os/features/advanced-camera-stabilization
Now in the "next" branch.
This branch adds advanced camera stabilization and control options with configuration GUI.

Spoiler

os/features/better-version-info-and-uav-export
Now in the "next" branch.
This branch is in fact a set of small but handy improvements for support: better UAV settings/data export, more detailed system info, more correct version mismatch reporting, and some internal code changes.

Spoiler

First, it changes the version mismatch message.

Here is the official one:

It is simply incorrect because:
- they might be compatible,
- user may want to downgrade and not upgrade (we should not tell him what to do),
- it is inconvenient because user has to look what his firmware (or GCS - what's older) version is.

What you'll have after this patch:

Why I think it is better? Because:
- it tells that versions are different (the main goal of the message),
- it does not tell that they are incompatible (they may be compatible even with different git hashes),
- it displays both firmware and GCS versions to user (no need to look somewhere else), which can be copy/pasted for support,
- it does not suggest to update exact part of the system (we don't know user's intentions, he may want to downgrade, for instance).

Second, this changes the format of UAV settings and data files. Now both settings and data (current system state) can be written to the same UAV file. So when the support needs to look at the system state, it can request only data file, not both. The file will contain both data and settings (what is useful since often data is useless w/o knowing of settings).

Third, the exported files now contain more detailed and better formatted system info:

<!DOCTYPE UAVObjects>
<uavobjects>
	<version>
		<hardware revision="1" serial="51ff6b064883545366621987" type="4"/>
		<firmware tag="os/import-export-improve+" date="20120102 22:22" hash="279a581b"/>
		<gcs tag="unofficial" date="20120104 13:55" hash="3a7e6dc6"/>
	</version>
	<data>
		<object id="0xC409985A" name="AccessoryDesired">
			<field values="0" name="AccessoryVal"/>
		</object>
		...
	</data>
	<settings>
		<object id="0xF2875746" name="ActuatorSettings">
			<field values="50,50,50,50" name="ChannelUpdateFreq"/>
			...
		</object>
		...
	</settings>
</uavobjects>

Of course, you still can import old settings files, this change provides full backward compatibility.

~~os/features/pid-defaults-button~~
Now in the "master" and "next" branches.
This small feature adds nice "Reset to Defaults" button to the PID settings page.

Spoiler

os/features/simple-gcscontroller-graphics
This is the simple old good GCS controller graphics. This is not a functional change, "just" a usability thing.

Spoiler

os/features/pid-tuning-from-transmitter
Now in the "master" and "next" branches.
Using this module, you can easily tune your PID settings using your transmitter spare channel with knob or slider. Moreover, you even can adjust PIDs depending on the Throttle channel input, lowering them when descending a quad or gliding a plane.

Spoiler

os/features/stick-deadband
Now in the "master" and "next" branches.
This feature was demanded by low-end radio (Turnigy 9X2 or similar) owners. The main problem is that such radios have some notable stick neutral drift (up to 5 percents). This makes impossible to tune the CopterControl for stable hovering. This patch enables to define Roll/Pitch/Yaw stick deadband to prevent this behavior.

Spoiler

2012/02/13.
Here is unofficial Windows build which is based on the most fresh public release from "master" and includes all extra features (except alternative controller image). It is not flight-tested, so be careful. It comes without warranty of any kind and without technical support (except questions about listed features). Use it on your own risk.
OpenPilot-20120213-ac122598-install.exe
Sorry, no Mac/Linux build available.

glikar

Jan 17 2012 02:27 AM

Exactly what I am looking for "os/features/advanced-camera-stabilization".
Thanks!

agrath

Jan 18 2012 11:14 PM

Hi Oleg, this is awesome
I know you said: "Due to lack of interest no more unofficial builds will be published. " but could you please please please produce a build that has all 6 above?
Are these features scheduled to be added into the trunk at some point in the future?

LeeS

Jan 20 2012 08:30 AM

I'm certainly glad you pointed out this PID tuning branch. I wouldn't have known it was in the repo otherwise. Thanks!

osnwt

Jan 21 2012 12:05 PM

could you please please please produce a build that has all 6 above?

Probably, except new GCS controller graphics which is replaced by new image. I prefer old simple, but seems that most of users like realistic ones.

Are these features scheduled to be added into the trunk at some point in the future?

I can't give exact answer because I don't know.

os/features/advanced-camera-stabilization - it is merged into the "next" and scheduled for the next release (not that which will be published in few days).

os/features/better-version-info-and-uav-export - might be, since it gives obvious advantages for technical support.

os/features/pid-defaults-button - might be.

os/features/simple-gcscontroller-graphics - replaced by another image. I am keeping this branch for purists, but see above.

os/features/pid-tuning-from-transmitter - probably, never unless there is a big enough demand on public forums. The "official" statement is that having too many such options (count also coming navigation on Revo), it will be a mess. I don't think so because anyone will tune stabilization first, and other options later. My implementation does not have few canned options to be tuned (like commercial systems), it allows to choose up to ANY 3 options (from a big list) to tune. So do we have a list of 10 or 20 options - it does not matter. But by now it is my only opinion, and not the official one. Might be the latter can be changed if there are some success stories on forums. But currently I am pessimistic about inclusion of this branch into any of official builds.

os/features/stick-deadband - probably, never unless there is a demand on public forums. The official statement is "it is not a problem" because some developers use Spektrum DX7 radios. I have DX7 and I also bought the Turnigy 9X reflashed to ER9X firmware to have more channels and flexible settings. I can confirm that there is a difference. I have no problems with Spektrum, and there are some with T9X. Again, it is my only opinion, and the official one is "Nobody asked".

After some experience in the past I decided to not push for inclusion of any of those features into official builds. But if many people will use them and like them, and report that on forums - might be some of them will be included, but that's not my decision.

osnwt

Jan 21 2012 12:51 PM

New Windows build published.

Please note that every field in my changed GCS screens has tooltip hint if you hover mouse over it. Many of them were added in my branches. Mostly this is applicable to camera stabilization.

agrath

Jan 27 2012 08:49 PM

Hi,
I've tested the build and it seems to work good.
My only comment is it's a bit misleading that the REV on the input tab is greyed out and you have to manually switch the values around to get it to "enable"

osnwt

Jan 28 2012 11:11 AM

My only comment is it's a bit misleading that the REV on the input tab is greyed out and you have to manually switch the values around to get it to "enable"

I completely agree with you.
Unfortunately, it is a trade-off in the official "master" branch (should be released very soon), and not my change. There was a problem with settings of throttle neutral point in the currently released firmware (if Rx sends inverted channel). In that case the throttle neutral was wrong. It should be fixed, but not done yet. so the whole calibration is replaced by input wizard where all checks are done.

We have an idea to provide even single channel calibration and rev option, but someone has to write the code for that.

PS. The wizard was required because we now support few Rxs simultaneously and GCS does not see inputs until configured. Wizard senses active channels and sets correct channel groups. I would prefer to configure groups by hand, but for most users wizard is easier to use.

sergyalta

Feb 22 2012 04:02 PM

Thank you very much, Oleg, for this opportunity!
Previously, it was not possible to set up my quad to hang with no appreciable drift.Today, it remains almost the same place. But the main thing is now clear the reasonfor the drift T9X with the official firmware.
I am one of those lucky people who no longer need to puzzle out how to get the modelto stay in position!
PID tuning is not a test, but in the near future and I think he will go to work.
Once again thank you for caring about us!

(Google translation).

← May 2013 →

M	T	W	T	F	S	S
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31

Some extra features

← May 2013 →

Recent Entries

Recent Comments

Some extra features

← May 2013 →

Recent Entries

Recent Comments

Sign In