sensor conflict: how to change SPort AppId ?

Development & General Chat for the superb openxvario project.

Moderator: rainer

Post Reply
strgaltdel
Posts: 8
Joined: Thu Jan 05, 2017 6:48 pm
Country: -

sensor conflict: how to change SPort AppId ?

Post by strgaltdel »

Hi,

i'm using oXs with "GPS number of sats & hdop" configured
So these sensors occupy appId 0x400 resp. 0x410.


Now i'm using an YGE ESC which is using 0x400 for temperature too.
Tx is announcing sensor conflict every x seconds ))-:
There is no chance to change anything on YGE side.
So i wanted to change the appId of my oXs but can't figure out how to do.

I can see some appId ranges in the oXs_out_frsky.h file, but these parameters don't influence the effective oXs config.
even changing alt ID's didn't work

Code: Select all

#define ALT_FIRST_ID            0x0100
#define ALT_LAST_ID             0x010f
...
#define T1_FIRST_ID             0x0400
#define T1_LAST_ID              0x040f
#define T2_FIRST_ID             0x0410
#define T2_LAST_ID              0x041f
can someone point me into the right direction ?

thanks & regards

udo

strgaltdel
Posts: 8
Joined: Thu Jan 05, 2017 6:48 pm
Country: -

Re: sensor conflict: how to change SPort AppId ?

Post by strgaltdel »

found a way to change the appid into a completely other diy range
...Frsky.cpp file:
fieldID

Code: Select all

const uint8_t fieldId[24] = { 0x10 , 0x11 , 0x30 , 0x30 , 0x30 , 0x21 , 0x20 , 0x60 ,0x90, 0x91 , 0x80, 0x80 , 0x82 , 0x83 , 0x84 , 0x85, 0x85, 0x50 , 0x40 , 0x41 , 0xA0 , 0x70 , 0x71 , 0x72 } ; //fieldID to send to Tx (to shift 4 bits to left
So i can change the appid into 0x0430

Any idea how to get an id like 0x0415 ?
Post Reply

Return to “OpenXVario - an open source vario supported by the open source firmwares!!”