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

[Chilternflyer]

Hi Guys,
I'm considering an HK Orange system on 459.

There seems to be a lot of activity on here..
So how is it going?

Is a reflashed Orange combo reliable and safe on 459 or should I stick with my old Dragonlink?

[phibin]

i couldnt comment on the HK copy...

but my OLRS is working great now iv ironed out the bugs it seems.

however im still to do a serious range test with it.

look at flytron for the HW...

simon.

[WSWhitby]

Same comments as phibin some small tweeks to get it working on the bench nothing serious and Mihai (thUndead) is a great help by PM. He is involved at this moment in time in a University project and hence has to be careful allocating his time. I have done some testing so far, no serious range check done, with the HK copy, Rx only The HK Tx is on its way. The results are the same as the Flytron's Rx. I would not however make a final recommendation until the range check is complete. Meanwhile another Kid on the block http://www.rcgroups.com/forums/showthread.php?t=1782034&page=8 seems to be further developments of Mihai's code, may be worth a try. I will probably try it  in the next few weeks whilst waiting for a HK Orange Tx and a Turnigy 9x, ordered about 20 days ago and of course for some one to tell me its rubbish or may be not.

Regards


John

[phibin]

any one know if flytrons V3 tx will work on the old v3.6 code?

simon.

[WSWhitby]

Problem.  :'(   It don't seem possible to stay legal with Flytrons M3 (Latest Tx) in UK  :o. As far as I can see its not possible to "turn down the wick" to get 100mW out. Data sheet of M3's rf module RFM 23BP suggests that the lowest setting is 28dBm approx 450mW. I have emailed both Hope, the module suppliers and Flytron, also asked on Flytrons forum but as yet no answers. If any one has got an answer please let me know. It may be possible to put an external attenuator between the module and the antenna, not sure if this is practical and it would need to have a gain of -8dBm. perhaps one of our more rf savy members could comment. Not withstanding the power out problem I see no reason why it should not work as the rest of the hardware apart from the unit power supply seems to be the same, it certainly uses the same Atmega 328P processor. I can only assume the above is true as I have no way of staying legal and testing.

Regards

John

[WSWhitby]

Hi phibin,
Sorry about the delay in posting on your question "any one know if flytrons V3 tx will work on the old v3.6 code?"
I have been involved in testing another set of software, so far so good and posting on that forum. http://www.rcgroups.com/forums/showthread.php?t=1782034&page=6. Well to answer now, as I said it don't seem possible to turn down the Power to 100mW, if anyone knows how they are staying quite about it. I have however decided to use a SMA to SMA 10 dB attenuator at the attenuator base to stay legal. Yes theUndeadMod V 4 and V3.6 both work fine on the Flytron M3 module with both Orange Rx and Flytron Rx. In fact they also work in that combination with the software openLRSng. I have done limited range checks of about 2 Km LOS ground to ground with a further 20 dB of attenuation at the Tx base. RSSI output filtered unbuffered into my Eagle Tree OSD Pro showed a drop from 210 to 130 actual about 3v to 1.8 volts rms after the filter. Range check limited by weather and temperature will try latter. Next tests will be with Turnigy Orange Tx Legal at 100mW Orange and Rx, when Hobby King finally get them to me, then the best bits can start some actual flying.

Added below 04/02/2013.
Just had an email from Eagle Tree support and that tells me that their OSD Pro does not at this point in time support PWM input for RSSI, which I find interesting it means that the PWM signal which the OpenLRS Rx outputs does not give meaningfull information to OSD Pro. I am filtering my RSSI out from Rx using a CR low pass filter and a ferrite core. I seem to get understandable results but will now have to do more tests. It seems the more you look at OpenLRS the more it seems we don't know, makes it interesting if you are prepared to check things out and keep an open mind.

Regards

John

[ORCA]

Hi,
Been out of all things aeromodelling for a good bad year due to personal reasons. So, starting to make some small steps to hopefully get back again. Thought I would start by having a play with the current 'Open LRS' but I would like to check a few points out if you would be kind enough to advise.
Let me start by saying that I have no experience or knowledge of Arduino programming, so, if anyone has any links to online tutorial sites please let me know. I feel a lot of reading and large amounts of coffee coming my way!
Equipment required:-
Tx module Mk3 from Flytron(for Futaba FF9 Tx) http://www.flytron.com/openlrs/212-openlrs-m3-1w-tx-module-for-futaba.html
Rx from HK http://www.hobbyking.com/hobbyking/store/uh_viewItem.asp?idproduct=27096
(I've had a quick read of this and the RCGroups threads and believe that the units should work together, if not please say.)
3.3v FTDI for Arduino from Flytron http://www.flytron.com/connectors-cables/117-3v-ftdi-for-arduino.html
Is this all I need, do I need any other items, cables for programming etc please advise? Don't want to order bits and then have to go back and reorder.
Thanks in anticipation for your forbearance of my ignorance.

[Doofer]

Can't wait to join this crowd, having taken delivery of the HK Orange kit.
However, can't get serial comms to work to flash the darned things.

Arduino 1.0., set for 328 16MHz 5v as recommended. Code from thUndeadMod v4 - no compilation errors. USB to serial bridge installed OK on Com 21. But the upload process fails, with no reply from the Rx.

I've tried:
- Gnd, Rx & Tx, with OpenLRS 'wait until it's compiled then connect power' procedure, as well as crossing Rx & Tx.
- Gnd, Rx, Tx, 3.3v & DTR, tried crossing Rx & Tx, tried connecting from DSR on USB instead (equivalent to crossing this control line).

No luck. The best that happens is the Rx LED flashes about 2-3 times, then switches full on until Arduino times out and declares the error.

And I can't find anyone else losing hours over this step.
Anyone got any suggestions? It seems to me vanishingly likely it's a problem with the Receiver.

[phibin]

you need arduino that will do '.pde' files...

i think the the 1.0 version of arduino does the new '.ino' files?

try using arduino 0022 and see if you can flash it with that.

everything else looks good i think...

simon.

p.s.

tx-to-rx / rx-to-tx ;)

[Doofer]

Okay, still no luck here. Both Rx & Tx modules now don't flash any LEDs at all when I try programming them, unless I use the FTDI programmer (which I know works fine, as I use it to flash my 9X transmitter), but I fear this is the FTDI programmer flashing the LEDs, not a sign of life in the modules. For a while the transmitter module seemed to have flashed OK (although I couldn't test it as the Rx won't flash) but now it too seems dead, just beeping and lighting up the 'Warning' LED on switch-on.

I have ordered another transmitter/receiver pair from HK (sigh), but I remain in the dark. I write firmware using thUndead's nice utility (v4), compile it with Arduino v.1, but I can't seem to upload. Using a USB to serial board (Gnd, Rx,Tx,3.3v,DTR) Arduino reports the 'can't connect' error, and using the FTDI  I get the 'cannot set sck period' +/- 'verification error'.

I've reached the point - having Googled so much, and tried so many different variations -  of wondering if I'm going mad  (?). Yes, these things are usually the result of some small different thing I'm doing without realising it, and not a problem with the modules.

Would anyone who has successfully flashed their Tx & Rx to 459MHz consider having a go with my modules?

It would be nice to know it is the modules, and not me - and, of course, if you have more success, I'd be able to get on with the project in hand.

I wonder, would anyone be willing to have a go at flashing these for me -

[phibin]

such a shame you cant get it to work.... :/

are you verifying the sketch first in arduino?
the little button next to upload... it makes sure all is ok before you flash....

I have to say, again, im fairly certain you need an earlier version of arduino......

the file you are trying to write are '.PDE'
versions 1+ of arduino does '.INO' files.....

this will corrupt the FW and it wont work.

try down loading arduino 0022 if you can, and try flashing again.

I hope this helps a bit?

keep us posted...

simon.

[Jumpy07]

I have been using the Orange OpenLRS kit on my TBS..  got a Diamond antenna on the TX and Sander on the RX..

I have had it running on 459Mhz.. but only getting around 2km.. so I have been looking to see if I can improve the range..

After doing a bit more investigation.. and using the Chrome browser based spectrum analyser ..

Easy to use.. jumper pins 3 and 4 on rx..  attach your FTDI adapter..  and run the softwware: https://github.com/cTn-dev/openLRSng-spectrum-analyzer

This the output... with everything on the TBS on... (GoPro didnt make any difference)




As you can see .. there is a spike at 459.5... not sure what it is yet.. either OSD or FPV cam etc...  but whilst pondering this.. thought would look at the setup again...

I am using KHA's latest build which is based on thunundeads code..  Firmware: https://github.com/kh4/openLRSng

The Frequency band approved in U.K for RC Models I understand is - 458.5 to 459.5MHz.

This band is shared with other users, in particular between 458.95 and 459.1MHz. It is recommended that aircraft use frequencies above 459.1 MHz.


So using the above info then.. this looks like the following channels and freq are legal and recommended for UK..

Ch1 - 459.100
Ch2 - 459.125
Ch3 - 459.150
Ch4 - 459.175
Ch5 - 459.200
Ch6 - 459.225
Ch7 - 459.250
Ch8 - 459.275
Ch9 - 469.300
Ch10 -459.325
Ch11 -459.350
Ch12 -459.375
Ch13 -459.400
Ch14 -459.425
Ch15 -459.450
Ch16 -459.475

(From info sourced here: http://www.ukrcc.org/459mhz.html)


So translating this to the settings required to flash the Orange OpenLRS kit...


I think it should be this ...

#define DEFAULT_CARRIER_FREQUENCY 459100000 // Hz startup frequency

And freq hop channels should be 1-16 (assuming starts at 1 and not 0).. also assume Orange OpenLRS channel spacing is 0.025 (25khz)

Does this look right ?

Thanks

[Devonian]

@ Jumpy,

No.

The RF module can only be programmed in 10KHz steps, therfore you can only achieve 459.100, 459.150, 459.200 etc OR 459.125, 459.175, 459.225 etc depending on the startup frequency.

So, if you want 459.125, 459.175 etc, your startup frequency should be 459.125.

The reason I suggest starting above 459.100MHz is that below that, the band is available to other, non flying users, whereas from 459.100 to 459.500 is primary UK flying use only.

Don't forget that the last useable frequency should be 459.475 due to bandwidth.

http://www.ukrcc.org/459mhz.html

Nigel.

[Jumpy07]

Thanks Nigel.. I think I get it.. :-X

So starting at 459.100 these would be the channels ? (so I can set the freq hop channels within the range)

Ch1 - 459.100
Ch2 - 459.150
Ch3 - 459.200
Ch4 - 459.250
Ch5 - 469.300
Ch6 -459.350
Ch7 -459.400
Ch8 -459.450

[Devonian]

Yup, you got it  :)

Nigel.