thUndeadMod v3.4 - openLRS S**T just got real :)

[thundead]

Today's the day you guys get the new fw :D stay tuned

[Coyote]

Ah :) Sounds good, did you discover the problems with V4 or is it the next upgrade to 3.5

[Coyote]

Ah my bad .6 :)

[thundead]

Sorry guys will need another day to tweak out rssi :) papa is right, 3.6 core, new GUI

[ghost2212]

Sorry guys will need another day to tweak out rssi :) papa is right, 3.6 core, new GUI

Will this new firmware have link quality RSSI?

If so could you explain how this will differ from what we had before? Will it display bad packets to good packets as a percentage basically or something more complicated?

Thanks

Brett

[thundead]

the way I'm trying to implement it is like so:

average (good/bad packet ratio + analog rssi )

so basically if you have good analog rssi but loads of blocked channels, your rssi reading will be low and vice versa.

any other ideas are more than welcomed :) Not sure what's the best approach to this.

[Technoweenie]

I personally like signal strength RSSI as the "cliff effect" of packet loss tends to catch one by surprise. This is the effect where packets are good until almost near the end of range and then suddenly things go bad very quickly at the limit of range. Averaging both together might be a good way to do it. I have not tried packet loss RSSI with OLRS but have experience with digital P25 radio systems. Others may have a different preference.

Perhaps a config setting in the GUI? A tick box for Analog RSSI, Packet Loss RSSI, or Averaging. This might complicate the ease of configuration for the GUI and will require 3 separate subroutines based on the variable setting. I have seen some config GUIs that have tabs for simple or advance settings. When in simple mode, it could assume basic settings (averaging combined RSSI, derived header from name or something, preset hopping channels etc.). If switching to advanced mode, the user could input more advanced info like custom header, custom channel hopping, number of hops, type of RSSI, etc. Just throwing out some ideas.

I think the software is awesome now. Any improvements only make it that much better! Thanks for all you do.

[thundead]

it has landed
http://www.fpvuk.org/forum/index.php/topic,7115.0.html :D

[simondale]

Hi guys,

I've spent a happy evening upgrading my firmware from a very old one, to the current (last) one.

The upshot is that it'll work fine if I have channel hopping turned off, but as soon as I turn that back on I get nothing between the Tx and Rx.

This is my Tx configuration file:

//###############################################################
//### Config.h Generated with thUndead's openLRS Configurator ###
//###############################################################

//####### TX BOARD TYPE #######
// 0 = Original M1 Tx Board
// 1 = OpenLRS Rx Board works as TX, reads your PPM signals from first servo port.
// 2 = Original M2 Tx Board
// 3 = OpenLRS Rx v2 Board works as TX, reads your PPM signals from first servo port.
#define TX_BOARD_TYPE 0

//####### BOOSTER #######
// 0 = No booster
// 1 = Booster
#define BOOSTER 0

//######### Band Select ##########
// 0 = 433Mhz
// 1 = 459Mhz
#define BAND 1

//######### TRANSMISSION VARIABLES ##########
#define CARRIER_FREQUENCY 459000  //  startup frequency

//####### Freq Hopping #######
// 1 = Enabled  0 = Disabled
#define FREQUENCY_HOPPING 1

//###### HOPPING CHANNELS #######
#define CHNO 4
static unsigned char hop_list[10] = {2,0,1,1};

//###### RF DEVICE ID HEADERS #######
// Change this 4 byte values for isolating your transmission, RF module accepts only data with same header
static unsigned char RF_Header[4] = {'5','I','A','a'};

//###### SERIAL PORT SPEED #######
#define SERIAL_BAUD_RATE 115200 //115.200 baud serial port speed

This is my Rx configuration file:

//###############################################################
//### Config.h Generated with thUndead's openLRS Configurator ###
//###############################################################

//####### RX BOARD TYPE #######
// 1 = Rx v1 Board
// 2 = Rx v2 Board
#define RX_BOARD_TYPE 1

//###### SERIAL PPM Type #######
// Plug a jumper between Ch1 and CH3 for switching your Rx to SerialPPM mode
// =Serial PPM Types=
// 0 is classic SerialPPM, disables parallel outputs and uses CH8 for serial PPM output.
// 1 is Mixed PPM, uses CH4 for serial PPM output and last 4 channels (CH5,CH6,CH7,CH8) works normally as ParallelPPM mode.
// 2 Standard SerialPPM on Pin9 (v2RX)
#define SERIAL_PPM_TYPE 0

//######### Band Select ##########
// 0 = 433Mhz
// 1 = 459Mhz
#define BAND 1

//######### TRANSMISSION VARIABLES ##########
#define CARRIER_FREQUENCY 459000  //  startup frequency

//####### Freq Hopping #######
// 1 = Enabled  0 = Disabled
#define FREQUENCY_HOPPING 1

//###### HOPPING CHANNELS #######
#define CHNO 4
static unsigned char hop_list[10] = {2,0,1,1};

//###### RF DEVICE ID HEADERS #######
// Change this 4 byte values for isolating your transmission, RF module accepts only data with same header
static unsigned char RF_Header[4] = {'5','I','A','a'};

//###### SERIAL PORT SPEED #######
#define SERIAL_BAUD_RATE 115200 //115.200 baud serial port speed

Can anyone help me please?!

Many thanks

Simon

[thundead]

PM sent :)

[simondale]

Hi Mihai,

I tried putting v4 on a further 2 or 3 times (on both the Tx and Rx) to no avail.

I put v3.6 on and it worked first time :-)

I wonder if v4 firmware and v1 hardware are not compatible in some way?

Thanks!

Simon

[simondale]

Its all working nicely now.  I love the failsafe setting functionality!  So much easier than the hour's I've spent trying to set the failsafe on a Corona receiver before! 

WELL DONE MIHAI!

All the best

Simon

[thundead]

glad you like it :) looking fw for some range test results :D

Its all working nicely now.  I love the failsafe setting functionality!  So much easier than the hour's I've spent trying to set the failsafe on a Corona receiver before! 

WELL DONE MIHAI!

All the best

Simon

[simondale]

Is there any problem with me being on 3.6?  Any big changes for v4?

Now I have my Naza's failsafe and GPS return to home set I'm a bit more confident going longer distances!  I need to get my FPV gear installed tomorrow though - now we just had 750 GoPro cables delivered I can get on with that!

All the best

Simon

[thundead]

4.0 only brings a more user friendly config interface. the firmware barebone is the same :) Be sure to use a dipole on the rx paired up with a 1/2 wave ant on the tx to further improve your range :)

Regards,
Mihai.

Is there any problem with me being on 3.6?  Any big changes for v4?

Now I have my Naza's failsafe and GPS return to home set I'm a bit more confident going longer distances!  I need to get my FPV gear installed tomorrow though - now we just had 750 GoPro cables delivered I can get on with that!

All the best

Simon