openrcforums

Maybe the 'Protocol' field should change to read just:

Protocol:
-> FRSKY HUB
-> FRSKY SPORT
-> JETI XBUS
-> ANALOG VOLTAGE

Not sure if there would be enough space on-board to compile all the protocols as standard!

Rob

Rob Thomson wrote:Maybe the 'Protocol' field should change to read just:

Protocol:
-> FRSKY HUB
-> FRSKY SPORT
-> JETI XBUS
-> ANALOG VOLTAGE

Not sure if there would be enough space on-board to compile all the protocols as standard!

Rob

In fact the protocol field should be removed from the configurator.
In the new version of oXs there is no need anymore to choice between hub and sport protocols. This version supports both protocols simultanously.
At power on, it checks for a signal from the Rx. If a signal is found, then oXs activates sport protocol, otherwise it activates hub protocol.
Configurator has still to be adapted to remove the choice between the 2 protocols.
In both cases, analog voltage can be activated (optional). This is controlled by another parameter.

This version of oXs does not support the Jeti protocol. The Jeti protocol is supported only by an old version of openxvario (which contains less functionalities than the last oXs).
It is difficult for me to add the Jeti protocol to the last version of oXs because I have no hardware to test it.

Note: as said in the oXs_C_readme.txt the current version of the configurator does not yet support the new functionalities provided by v2 of oXs (airspeed, compensated vario, ...). Davx will adapt the configurator asap.

Hi,

Some News !

OXS Configurator v2.1 can now be used to set all the new functionalities of openXsensor v2.5 !
The Wiki has been updated for the occasion

Bye.

You Rock Davx, Thank you

João

+1

Thanx a lot ...

@davx.

Could it be, that I found a small issue with OpenXsensor Configurator 2.1 in combination with openXsensor_v2.5?

OFFSET was changed, but NOT DIVIDER ... Not a big thing, can do it manually.
br KH

Hi,

@kalle123,
I'm not sure what you mean, but if you're talking about differences between "Divider factor" in the Configurator and "MVOLT_PER_STEP" in the config file, it's normal, they are not the same value. When you enter a divider factor, it is then converted to mV/step in the config file.

Furthermore, it seems you're using internal reference (1.1V) for voltages, that's why the values are so close (but not equal and shouldn't be).

However, if your Arduino is correctly powered (>5V), I recommend you use VCC reference, it should be more accurate.

Bye.

davx wrote:... if your Arduino is correctly powered (>5V), I recommend you use VCC reference, it should be more accurate...

and you can omit the divider for the 1st cell ...

Klaus

Try to be a big more specific

I have a preset file in openXsensor Configurator 2.1.

The oXs_config.h in openXsensor_v2.5 with time stamp
has those values

#define OFFSET_1 117 // offset in mV
#define MVOLT_PER_STEP_1 4.58
#define OFFSET_2 252 // offset in mV
#define MVOLT_PER_STEP_2 8.25
#define OFFSET_3 -6 // offset in mV
#define MVOLT_PER_STEP_3 14.25



I walked the dog for an hour ...

Now I am back at my desk.

Opened openXsensor Configurator 2.1 again.

Loaded that preset file again with THOSE DIVIDER FACTORS
Proceeded to that screen here and pressed OK.
The oXs_config.h has been renewed in openXsensor_v2.5 now with new time stamp
But DIVIDER values stay unchanged ....

#define OFFSET_1 117 // offset in mV
#define MVOLT_PER_STEP_1 4.58
#define OFFSET_2 252 // offset in mV
#define MVOLT_PER_STEP_2 8.25
#define OFFSET_3 -6 // offset in mV
#define MVOLT_PER_STEP_3 14.25

davx, that is, what is puzzling me.

The GUI tells me OK, the file has obviously been renewed, but looking inside, the old values are still there ....

br KH (It is on a linux machine ...)

KAL wrote:

davx wrote:... if your Arduino is correctly powered (>5V), I recommend you use VCC reference, it should be more accurate...

and you can omit the divider for the 1st cell ...

Klaus

Hi Klaus.

That is not the point.

The issue is, that the Conf GUI ist telling me, it generated a new config file (time stamp), but the DIVIDER values are NOT changed in that new config file.

I am supplying an arduino uno (and RX) with 5.0 V DC, so the internal ref voltage is a little less than those 5.0V. In that case the recommendation is to use 1.1V Ref.

br KH

I think that the values written in the config file are consistent with the dividers set in configurator.

Take care that dividers in configurator are not the same as MVOLT_PER_STEP in configurator even if both are related.

In fact, configurator calculates MVOLT_PER_STEP based on divider and on reference voltage using this formula:
MVOLT_PER_STEP = DIVIDER * ( reference voltage in volt ) * 1000 / 1023
So if divider = 13.26 and reference = 1.1 volt : 13.26 * 1.1 * 1000 /1023 = 14.25 (MVOLT_PER_STEP).
So I think that configurator is OK even if for the first divider (4.25), I do not get exactly the expected result (perhaps a rounding issue).

The issue that this is not yet explained in the configurator documentation.
Personnally I regret that oXs and configurator are not using the same variables for set up. This can create some confusion.

Hi mstrens.

THAT EXPLAINS IT!!

Thanx a lot - KH

For people like me that is not that good with math, mV per step can be quite confusing. while a diver is easier to understand as we don't have to deal with the digital side of the things. It is easier to calculate the divider ratio and let the configurator calculate the digital part of it.. We don't have to know that.. In fact for some people it would be even better to give some fixed resistor values at 1% for each cell, or for a given battery pack, and not even make them calculate divider ratios.. I'm sure they would appreciate it Something like, you chose in the configurator which pack type (LiPo, LiFe, NiMh) you use, and how many cells, and then the configurator would generate some resistor values for the given setup..
But still have the possibility of just insert the divider ratio as well in case other people want to use other resistors.. I don't know how difficult it would be to implement this, but here is the idea..

João

It would be very easy to propose resistors for dividers. Those values are already documented in the explanation file when using the internal reference.
* Notes: You must use voltage dividers to scale down the voltages on each pin of the lipo balance plug
* If you use the 1.1 internal reference, you can set all R1 = 10 kOhm. Then R2 could best be
* 33 kOhm for Voltage1, 68 kOhm for Voltage2, 120 kOhm for Voltage3 and 150 kOhm for voltage4

One issue using divider instead of calibration is that when you use the internal reference 1.1 volt, the datasheet of MCU says that there can be 10% deviation.
If you do not take care of this, the returned voltages could be 10% wrong.
It is not easy to measure the internal ref.

Therefore the method explained in the description file (based on measurements with a voltmeter) is still the most accurate from my point of view.

Hi João.

As I can not understand, that there is not much response in German rc forums about openXsensor, I started a thread in rcline.

http://www.rclineforum.de/forum/board49 ... ndex2.html

Hoping to get more people interested in that great project. As I myself had some problems with understanding calibration, divider, offset, I even made a hand drawn!! sketch trying to explain. (Old saying is, a drawing says more than 100 words ... )

KH

@mstrens. We will have M-Link supported in the next GUI?

Normally Davx will make a new version of configurator in order to be able to use the configurator for FRSKY or MLINK protocols.
Still I do not know when Davx will be ready with this.
It will be a version 3.x

mstrens wrote: Personnally I regret that oXs and configurator are not using the same variables for set up. This can create some confusion.

I don't think mV per step is a user friendly unit and divider factor seems more simple to understand IMHO.

kalle123 wrote: THAT EXPLAINS IT!!

That's already what I had wrote in response at your post...

I may add that it's better to redone the preset files between different OXSC version because of internal changes.

mstrens wrote:It would be very easy to propose resistors for dividers.

I'm working on a tool integrated to the Configurator which will calculate the divider factor from resistors values.

kalle123 wrote:@mstrens. We will have M-Link supported in the next GUI?

Yes, it will be there.


Generally speaking, the Configurator is meant to facilitate the configuration for average people and/or those who like a GUI.
Nothing prevents you to view and edit the config file directly if you wish.

Bye.

davx wrote: I'm working on a tool integrated to the Configurator which will calculate the divider factor from resistors values.

That is great, thank you. Could you please also include the max voltage that the divider can handle to avoid people destroying the arduino?

Thanks

João

question, in the configurator I don't seem to be able to select the number of blades for RPM.. Or is it done on the radio? Can this be used with IC powered mopdels, opr only electric? Thanks

João

@jhsa
Number of blades is defined on TX side (at least for OpenTx or similar).
It could be that I have to add it in Multiplex protocol.

RPM can be use for all kind of motors. It requires that an external sensor is connected to oXs. OXs needs to get logical pulses (so with a level nearly between 0 and Vcc) .
External sensor could be an optical or a Hall effect sensor.

Thanks, that is what I needed to know. Helpful as always.. We are making a good reference to oXs on the new er9x manual.. I searched the google code project page for a good description but couldn't really find one. If someone wants to point me to it in case I've missed it, or contribute with one, is very welcome and certainly appreciated..

Thank you

João

Hi,

jhsa wrote: I searched the google code project page for a good description but couldn't really find one.

What particular description are you looking for ?

Bye.

A general description, like if you were selling it What it does, what can connect to it, configurator, etc.. Whatever you think people need to know about it.. compatibilities, etc.. Space is no problem. we have plenty. Pictures? if ity doesn't fit in the telemetry section, it will have it's own place in the manual.. I think the oXs project must be included as it is definitely a fantastic project and crucial for our hobby.. So, be creative

And thank you

João

Hi,

For the moment you have the infos from the home page https://code.google.com/p/openxsensor/ and pictures there https://code.google.com/p/openxsensor/w ... gs_how-tos.

I'm currently working on the Multiplex protocol for the Configurator and as I want to do it correctly, it will need quite some time...

Bye.

Hi Guys!
i haven't been active for quite some time on the oXs coding, but it's really good to see it still growing.
Even though i do not have the time for coding these days, i had an idea already quite some time ago, and maybe somebody wants to pick it up..

Most of the config is still done in the way of editing the config file manually or though the great configurator tool.

It would be a great feature to change this in a way to store all of the configurable values in the eeprom of the arduino and create some commands that could be received via the uplink or a serial connection to influence these. This would make it possible to change the config without having to reflash...

It could theoretically even be possible to add functionality to the transmitter to remotely configure the oXs.

Just an idea...

Cheers,

Rainer

Wow, excellent idea.. Thanks Rainer..

João

Makes sense, would this mean calibrating the voltages for cells could be done live, I have not set up my cells yet so don't know if this is already doable .
Ie connect a meter and make adjustments to the config to match them.

Yep, I think that's it.
Also you could configure the vario, adjust the current sensor, etc..
It's a wonderful idea.

João

Doing the adjustments like that would be a great idea ...