UP TO DATE GUIDE IN 2nd POST. Cheers.
Hey Everyone,
As you know, the OpenLRS system is an open source long range system which also features telemetry.
As far as I know, the ezUHF and OpenLRS are the only legal long range systems in the UK.
I will constantly try to incorporate new stuff to the system in order to make it a complete FPV system ;D
Currently working on adding antenna tracker capability to the system.
As promised, here is my Crash Course Guide for the "UK version" of the OpenLRS system.
For some reason I can't attach the guide so here is the link for now:
http://www.multiupload.com/20GX6Q0F6J (http://www.multiupload.com/20GX6Q0F6J)
I tried to tidy the code a bit. Removed (hopefully) all my custom code so should work ok.
---------------------------------------------------------------------------------------------------
FIRMWARE MODS
---------------------------------------------------------------------------------------------------
Disclaimer: This mods have or have not been tested/ flown yet Use at your own risk!
-----------------
Super Simple RX Firmware
As the title says, this is a ultra stripped down version of the 1.10 UK firmware uploaded by Nigel (Devonian) on the Flytron repo.
Features:
- Uni-Directional/ NO TELEMETRY! (should get better range ?)
- Removed sensors and wii related stuff
-Proper RSSI Out :D - 0 to 2.6v nice and fluent RSSI output - TESTED!
- fw ahs been bench tested( left tx/rx on for 1h to see if it gets locks etc)
-------------------------------
thUndead's RSSI MOD
this section will show you how to add my RSSI MOD into your own firmware :D
Add this bits of code into your OpenLRS_Rx.pde file. My code is in bold. the rest is to show you where to add it:
-------------------------------------------------------------------------------------
failsafe_mode = 1; // Activate failsafe mode
load_failsafe_values(); // Load Failsafe positions from EEPROM
Direct_Servo_Drive(); // Set directly the channels form Servo buffer
Red_LED_ON;
//***************************************
//* thUndead's RSSI MOD
//* info: when packet lost, rssi voltage goes to 0
analogWrite(RSSI_OUT,0); // Convert the RSSı value to PWM signal
//***************************************
}
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
last_hopping_time = time;
//* thUndead's RSSI MOD
//* info: when fail-safe ON, rssi voltage goes to 0
analogWrite(RSSI_OUT,0); // Convert the RSSı value to PWM signal
//***************************************
#if (FREQUENCY_HOPPING==1)
Hopping(); //Hop to the next frequency
#endif
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
// Rx_RSSI = _spi_read(0x26); // Read the RSSI value
// analogWrite(RSSI_OUT,Rx_RSSI); // Convert the RSSı value to PWM signal
//***************************************
//* thUndead's RSSI MOD
//* info: RSSI voltage according to avg rssi value :D
Rx_RSSI = _spi_read(0x26); // Read the RSSI value
rssicounter++; //counter which resets after getting to 41
if (rssicounter <=40) rssipwm= rssipwm+ Rx_RSSI ; //adds values into temp buffer
else rssicounter =0;
if (rssicounter ==40)
{
rssipwm = rssipwm / 40; // averege 40 rssi values to get stable reading
rssibuf = map(rssipwm,40,120,10,250); //map value for pwm: MAX = 2.6v bad rssi unver 1 v
analogWrite(RSSI_OUT,rssibuf); //write the RSSI voltage
#if defined(Serial_RSSI)
Serial.print("RSSI:"); //some debugging
// Serial.println(rssipwm);
Serial.println(rssipwm);
Serial.println(rssibuf);
#endif
}
//***************************************
-------------------------------------------------------------------------------------
now go onto your config.h file and add this in the variable section:
//***************************************
//* thUndead's RSSI MOD
//* info: variable used for RSSI MOD
unsigned int rssipwm,rssibuf = 0;
unsigned short rssicounter = 0;
//***************************************
------------------------------------------------------------------------------------
TUNING THE RSSI:
uncomment #define serial_RSSI and check the first value (mine gives me about 100-120 with tx close )
modifi the value in bold accordingly:
rssibuf = map(rssipwm,40,120,10,250);
-------------------------------------
I've attached the unmodified UK firmware with the RSSI mod :)
Any questions, suggestions, mistakes are welcomed :thanx!: :flying:
Cheers,
Mihai.
-----------------
ATTACHMENTS
-----------------
can't upload files in my post for some reason so here are some links...
UK openLRS FW - ORIGINAL+RSSI MOD - http://www.multiupload.com/LV9OCONUD0 (http://www.multiupload.com/LV9OCONUD0)
SIMPLE Stripped FW - http://www.multiupload.com/REUWN7Z3FI (http://www.multiupload.com/REUWN7Z3FI)
UK OpenLRS Setup Guide
--------------------------------
Introduction
As we know, the UK legal frequency for long range RC control is 459 Mhz. The only legal UHF devices I know are the ezUHF (great piece of kit but very £££) and the newly found OpenLRS, an open source RC link from our Turkish friends, Flytron.com.
This is a crash course guide to get you start using your new and shiny LRS system
Please post any questions regarding this guide (maybe I missed something haha) in the UK OpenLRS Guide and Future Development thread found here: http://www.fpvuk.org/forum/index.php?board=9.0 (http://www.fpvuk.org/forum/index.php?board=9.0)
STUFF YOU NEED:
1. OpenLRS system - get it from www.Flytron.com (http://www.flytron.com)
2. FTDI Usb adaptor –
• http://www.flytron.com/multicopter-parts/117-3v-ftdi-for-arduino.html (http://www.flytron.com/multicopter-parts/117-3v-ftdi-for-arduino.html)
• http://www.skpang.co.uk/catalog/ftdi-cable-5v-p-319.html (http://www.skpang.co.uk/catalog/ftdi-cable-5v-p-319.html)
• Google is our friend :D
3. 4 wire cable - I used male pin headers on my LRS, FTDI cable etc and made myself a 4 wire female to female cable (See pic)
4. Soldering Iron + basic soldering skills – needed for header soldering on your Rx, Tx
5. Arduino SDK - http://www.arduino.cc/en/Main/Software (http://www.arduino.cc/en/Main/Software)
6. Custom OpenLRS Firmware – http://www.multiupload.com/EU1ZF0Q9X6 (http://www.multiupload.com/EU1ZF0Q9X6)
7. 20 mins of your time :)
(http://s2.postimage.org/1g6kqkztw/Stuff.jpg) (http://postimage.org/image/1g6kqkztw/)
Preparing the Arduino Environment
After unzipping the Arduino SDK, connect your FTDI cable to ur PC and let the drivers install. If for some reason (Bill Gates ?) windows doesn't find drivers, select manual install and navigate in the Arduino SDK folder and you will find needed drivers there.
In the SDK, selecd the default board as shown in the picture below
(http://s2.postimage.org/1g7g5sl7o/board_and_serial.jpg) (http://postimage.org/image/1g7g5sl7o/)
After that, select yout FTDI cable's Serial Port. If you see multiple ports listed, go into Device Manager – Com ports – Serial device something.
(http://s2.postimage.org/1g7rqk0o4/Clipboard01.jpg) (http://postimage.org/image/1g7rqk0o4/)
Uploading the code.
Now it's time to connect our OpenLRS and load up our custom firmware.
Let's start with the Receiver Board.
1. Load up the OpenLRS_RX.pde in the arduino SDK.
2. Just to be safer, be sure to change the HEADER to whatever you want:
(http://s2.postimage.org/1g7v1mpno/Change_header.jpg) (http://postimage.org/image/1g7v1mpno/)
So for example change from 'O', 'L', 'R', 'S' to 'L', 'M', 'A', 'O'.
BE SURE TO CHANGE THIS IN BOTH THE RX AND TX FIRMWARE !!!!!
3. Click on the Verify button (the play button) to compile your code. This should go without any errors.
4. Connect an ESC to your RX. Any channel will do . I usually use the throttle channel. BE SURE TO CONNECT THE SERVO WIRE CORRECTLY!!! (from top to bottom: WHITE ; RED ; BLACK)
5. Now connect your FTDI adapter and RX as shown in the CONNECTIONS section.
6. Have you LIPO close.
7. READ THE NEXT THREE STEPT CAREFULLY
8. Now press the UPLOAD button (button with arrow pointing right)
9. Wait for the "Binary sketch size bla bla" message to appear on the bottom of the SDK.
10. Now Connect your Lipo.
11. If you did all correctly, the LEDs on the FTDI adapter should go nuts.
12. You're done with the RX.
Now follow exactly the same steps for the TX module: Don't forget to check the connection DIAGRAM!! TX pins are different from the RX!!!! also you will load OpenLRS_TX.pde onto the transmitter module; Instead of connecting a LIPO, you will power the TX on when the "Binary sketch" message appears.
Now add some servos to the RX and see if everything is working properly.
If everything works, congrats! You now have a legal long range system muhaha :o
CONNECTION DIAGRAMS
Basic Rule of thumb:
• TX pin always to RX pin
• RX pin always to TX pin
• GND always to GND
• DO NOT CONNECT THE V+ WIRE !
(http://s2.postimage.org/1g8bl06lg/Connections.jpg) (http://postimage.org/image/1g8bl06lg/)
Modified my TX for easy port access :cooldance:
vvvvvvvvvvvvvvvvvvv
(http://s2.postimage.org/1g8i75kkk/tx_modif.jpg) (http://postimage.org/image/1g8i75kkk/)
Arduino Buttons Explained
(http://s2.postimage.org/1g8juox2c/instructions_2.jpg) (http://postimage.org/image/1g8juox2c/)
Project Poor Man's openLRS Antenna Tracker
Well to put it short, student + FPV equipment = :toiletbang:
Buut, me knows programming muhaha ;D
And building a 50quid DIY antenna tracker sounds pretty good.
Also the openLRS has telemetry so why not give it a shot.
(http://s2.postimage.org/1g93p52zo/Clipboard01.jpg) (http://postimage.org/image/1g93p52zo/)
-------------------------
Components used:
Arduino Mega 2560
2x Cheapo Turnigy Servos
Patch antenna (11 dbi I think)
Flytron GPS Module
2x Xbee for serial data from TX to Mega board
-------------------------
Currently Working:
- GPS latitude, longitude, altitude over telemetry protocol with max precision
- Pan/tilt apparently working good (bench tested with Google Maps coords)
-------------------------
Under development
- Data from TX to ground station via Xbee
- Add LCD to display info
- Implement voltage sensor (V divider) to display % battery life of video RX/Ground Station
- Button to set Home
- Go from breadbord and tonz of wires to DIY PCB
-------------------------
Will release code , PCB layout(mos likely Eagle file) etc when I have a usable version.
In the meantime I'm open to suggestions, adding additional features as I go :)
Also any support for my currently empty Beer/Project Fund are more than welcomed :pint:
GEEK Section - Technical stuff
This post will be updated as the project progresses.
So far:
GPS Telemetry
When it comes to gps coordinates, we need very accurate data.
NMEA stream is processed using the TinyGps library
Extracted data (latitude, longitude, altitude) is transmitted as 13 bytes encoded float variables:
4 bytes per parameter + 1 byte for valid data checking = no data loss to rounding, missing decimals etc.
-----------------------------
Pan/Tilt
My current setup uses 2 cheapo 9g servos that get software stretched to 180 degrees.
Current code covers 360 degrees of movement so we shouldn't worry about moving the antenna round when plane passes over.
The way I tried making it work is:
PAN: goes from 0 to 180;
TILT: goes from 0 to 90;
if plane flies over, PAN is reversed and TILT flips the antenna upside down.
EDIT: Video of the pan tilt system
Diy antenna tracker (http://www.youtube.com/watch?v=trgyQAYZNe4#)
-----------------------------
DIY PCB for the Mega
(http://s1.postimage.org/214cv729w/IMG_20110901_153908.jpg) (http://postimage.org/image/214cv729w/)
(http://s1.postimage.org/215ewk1ms/IMG_20110901_153950.jpg) (http://postimage.org/image/215ewk1ms/)
-----------------------
SPARE PARTS
http://proto-pic.co.uk/rfm22b-s2-smd-wireless-transceiver/ (http://proto-pic.co.uk/rfm22b-s2-smd-wireless-transceiver/)
------------------------
Excellent guide Mihai! Although I'm still a newbie it's great to know a guide like this exisits when the time comes!
Thanks
Fantastic! My OpenLRS, and programmer jobby, have arrived at our office in Yorkshire. I'm down in Brighton but as soon as the opportunity presents itself I will be getting up there and following your guide in earnest!
Thanks so much for spending the time writing the guide. That's really appreciated!
All the best
Simon
Quote from: Capello1986 on August 31, 2011, 01:38:37 PM
I really like the idea of this system but just worried that am not going to be able to get it going or set up 100% :-(.
Is it easy enough?
Martin
If you follow my guide you should be flying in 30 mins or so :)
The only lets say issue I see if soldering the pins but it's no rocket science. Watch the first post for a video showing basic soldering.
Cheers,
Mihai.
Mihai,
Good job on the basic guide.
Would it be worth starting a Google repository for UK only 459MHz firmware(s)?
Either that, or ask Melih (at Flytron) if we could make a sub section on the main Google OLRS site for UK firmware?
http://code.google.com/p/openlrs/downloads/list (http://code.google.com/p/openlrs/downloads/list)
Personally, I'd prefer it on the main site.
EDIT
I've asked Melih if it's possible to add a setion on the main Google firmware site for UK basic and development firmware(s).
This will be good for those who want a basic 'load n fly' firmware and those of us who like to experiment/hack ;)
/EDIT
Nigel.
That's a good idea. let me know what Melih replies and we can start organizing :D
Quote from: Devonian on September 01, 2011, 11:02:52 PM
Mihai,
Good job on the basic guide.
Would it be worth starting a Google repository for UK only 459MHz firmware(s)?
Either that, or ask Melih (at Flytron) if we could make a sub section on the main Google OLRS site for UK firmware?
http://code.google.com/p/openlrs/downloads/list (http://code.google.com/p/openlrs/downloads/list)
Personally, I'd prefer it on the main site.
EDIT
I've asked Melih if it's possible to add a setion on the main Google firmware site for UK basic and development firmware(s).
This will be good for those who want a basic 'load n fly' firmware and those of us who like to experiment/hack ;)
/EDIT
Nigel.
I see that the openLRS transmitter has a Futaba connection. Would it work ok on the Trainer port of a Spektrum DX8?
I believe so, as OLRS can also be driven from the trainer port with compatible PPM signals and suitable power connections.
I really don't know Spektrum Tx's, so check some more before commiting to the 'buy' button ;)
You will have to make some kind of adapter lead and suitable mount for your DX8, because, as you noted, it's for Futaba Tx with plug in module (or with the adapter PCB, for JR/Turnigy 9x).
You will need a varying degree of soldering/electronics/computer ability whatever way you decide to go.
OLRS is not a 'plug n go' system.
That said, there is a growing UK interest and wherever we can, we will help.
Nigel.
In the UK what video system would best work alongside this? I'm assuming it's 2.4GHZ? Thanks
In the UK, we are legally allowed to use 2.4GHz or 5.8GHz - either will work alongside 459MHz quite happily.
The worst, would be 1.3GHz (for our foreign friends) as thats a bit too close to the 3rd (and strongest) harmonic of the 434/459MHz systems.
Nigel.
Back on subject...
I found a UK supplier for the RF module, should anyone be unlucky enough to destroy theirs - or maybe you want to make a hack module for yourself?
http://proto-pic.co.uk/rfm22b-s2-smd-wireless-transceiver/ (http://proto-pic.co.uk/rfm22b-s2-smd-wireless-transceiver/)
Nigel.
Right, quick update:
Finished & tested PCB. it's now coding time yaay. I need to think of a serial protocol from the TX to the antenna tracker.
Was thinking of something like this: ![sttream of data bla bla bla]@. Do u think it's enough having a start and a stop bit or should I include maybe checksum.
Mihai.
Added the link in Spare parts section of the 3rd post.
Quote from: Devonian on September 02, 2011, 09:39:40 PM
Back on subject...
I found a UK supplier for the RF module, should anyone be unlucky enough to destroy theirs - or maybe you want to make a hack module for yourself?
http://proto-pic.co.uk/rfm22b-s2-smd-wireless-transceiver/ (http://proto-pic.co.uk/rfm22b-s2-smd-wireless-transceiver/)
Nigel.
Melih from Flytron has got back to me and is willing to upload files to the main Google repository.
However, as he points out, the files are really for developers as it's opensource after all, and doesn't want to have a sub section for 459 end users only.
I have started a new thread on Flytron forum dedicated to UK 459 users and have attached my version of basic 459MHz files.
I hope Melih will follow the new thread and as new versions of firmware are released and we ammend them for UK use, post them to the forum thread and he will then load them to the Google repository.
They can be downloaded from here and used to load into the Tx and Rx to get you running on 459MHz...
http://forum.flytron.com/viewtopic.php?f=7&t=134 (http://forum.flytron.com/viewtopic.php?f=7&t=134)
You use them at your own risk and I accept no responsibilty from the use of the files.
If anyone spots any errors in my files, let me know and I will ammend them.
Nigel.
Melih has now placed my 1.8 version of UK 459MHz firmware on the Google repository:
http://code.google.com/p/openlrs/downloads/list (http://code.google.com/p/openlrs/downloads/list)
Nigel.
I'm still a bit confused on this 459mhz stuff...
If it's not long range and only has about 2km range then why would I want to use it instead of my 2.4ghz system ?
Not being funny, I just can't see/understand the benefits ?
Well first you can use a 2.4 video system that will give you better range and the system probably can go much further than 2 km. no one has actually tested it yet. :)
Quote from: TeeJay on September 07, 2011, 03:17:02 PM
I'm still a bit confused on this 459mhz stuff...
If it's not long range and only has about 2km range then why would I want to use it instead of my 2.4ghz system ?
Not being funny, I just can't see/understand the benefits ?
Benefits of OLRS for me are:
1) Much less risk of being shot down by someone (as is possible on 35Mhz).
2) Gives me more freedom of choice for video link - I now have 2.4GHz and 5.8GHz
3) OLRS has the possibilty to be programmed to do many things, e.g. built in Rx stabilisation with IMU's, 2 way telemetry, etc.
4) It's open source as opposed to closed souce, so I have the freedom to add as much as can be developed for the system.
5) Potential of 'long range' - so far it has gone out to 4km, with probably more to be had with effecient antennas.
6) It's currently the cheapest and UK legal UHF system on the market.
7) I enjoy the challenge!
Nigel.
I think its a point some people miss being a 459 uk legal system.
Range really shouldnt matter at all, if the whole point of it is legal uk frequency then the user would of course be flying legally, so realisticly, anything over 2km is more than enough for Uk legal flying.
Its rolling along quite fast now, more brains make for lighter work :)
Quote from: Devonian on September 02, 2011, 09:01:29 PM
I believe so, as OLRS can also be driven from the trainer port with compatible PPM signals and suitable power connections.
I really don't know Spektrum Tx's, so check some more before commiting to the 'buy' button ;)
You will have to make some kind of adapter lead and suitable mount for your DX8, because, as you noted, it's for Futaba Tx with plug in module (or with the adapter PCB, for JR/Turnigy 9x).
You will need a varying degree of soldering/electronics/computer ability whatever way you decide to go.
OLRS is not a 'plug n go' system.
That said, there is a growing UK interest and wherever we can, we will help.
Nigel.
The plug in module does sound a good idea. I might look at getting a Futaba TX from eBay. Which model should I go for bearing in mind that I would be using it exclusively with the OpenLRS.
Trevor
Personally, I'd say a T9C - has all you will need and some.
Will also take the Spektrum 2.4GHz module, Frsky 2.4GHz module, OLRS UHF module + others and of course all the Futaba modules!
Another source is:
http://www.bmfaclassifieds.co.uk/ (http://www.bmfaclassifieds.co.uk/)
HTH
Nigel.
This is fascinating and I will be looking at this is a bit more detail.
Thanks very much for posting the information :)
Cheers,
New v2 Rx is due for release - read more...
http://forum.flytron.com/viewtopic.php?f=7&t=142&sid=a0e6eccd5f4a22f888327e4e64ed3904 (http://forum.flytron.com/viewtopic.php?f=7&t=142&sid=a0e6eccd5f4a22f888327e4e64ed3904)
Nigel.
Hi guys,
What is the score with antennas? Is there a commercial source of 459MHz antennas anywhere? Can the supplied antennas be modified in some way to be optimum for 459MHz?
Devonian: Do you know where we stand on transmitting telemetry from the air legally? I think I remember reading that 433MHz is OK for telemetry. I wonder what the other (JETI?) telemetry solutions use?
If it is the case that 433MHz is the allowed frequency is it possible to have the Rx receive on 459MHz and transmit telemetry on 433MHz (and vice versa on the transmitter) or am I dreaming?
Now to solder on the pin header to my OpenLRS and get stuck in!
All the best
Simon
Simon,
I make my own 1/4 wave antenna's using an SMA connector with a bit of wire @ 163mm inside a bit of pushrod tubing pushed into the SMA connector and then all of it is covered with heatshrink (Sander did a good tutorial on 'How To' somewhere on RCG).
Even better would be a 1/4 wave with radials for the RF ground return - this would provide maximum radiation/reception.
I haven't opened up the supplied 433MHz rubber ducks but guess they could be cut off a bit and re-tuned to 459MHz.
Others on UHF systems have used Ham whip antennas for 70cm (most are 1/2 wave and with a bit of tuning would work on 459MHz).
To be honest, I have no idea where we stand with transmitting telemetry back on 459MHz, but my gut feel says if it's not strictly in the rule book, it'll probably be a grey area.
I don't think it will be practical to programme the system to Tx and Rx at two differing frequencies.
I'm no programmer, but imagine there would be timing issues between the 2 components (when should one Tx and the other Rx and vice versa).
Some form of control must be implemented right now as the 2 components Tx & Rx on 459MHz - so maybe it's do-able on 2 different frequencies as well??? (although antenna matching comes into question...)
Nigel.
Interesting stuff. I'll see if I can turn up Sander's tutorial.
Good point on the multiple bands and antennas.
I just found this page regarding model control and telemetry: http://hoylakemodelboatclub.com/OFCOMINFORMATION.aspx (http://hoylakemodelboatclub.com/OFCOMINFORMATION.aspx)
It says: The 458/459 MHz band is also allocated to Industrial telemetry and telecommand devices between 458.5 and 458.95 MHz, and to specialised telemetry between 458.95 and 459.1 MHz. While the potential for mutual interference is minimal, model controllers should avoid the specialised telemetry part of this band.
It being a boat club website it doesn't go on to give any advice on airborne telemetry unfortunately.
All the best
Simon
I'm staying with the 459MHz and telemetry (for now at least).
Sander style UHF whip, ignore his dimensions as it's for 433MHz - I used 163mm...
http://www.rcgroups.com/forums/showthread.php?t=1413650 (http://www.rcgroups.com/forums/showthread.php?t=1413650)
Nigel.
Do you use Sander style antennas on your Tx and Rx? Any chance of a photo please?
I was thinking about removing the antenna from my Turnigy 9x and mounting an SMA connector where the antenna used to be, soldered to the 6th pin of the module connector (where the 35MHz antenna clearly used to go on the verson 1).
Then opening up the OpenLRS and soldering the coax from the antenna pad (where it is now) to the ANT pin on the module connector (Pin 6). Is that a silly idea I wonder?
As requested
Tx
(http://s3.postimage.org/1c81cbn5w/DSCN0536.jpg) (http://postimage.org/image/1c81cbn5w/)
(http://s3.postimage.org/1c84nec5g/DSCN0537.jpg) (http://postimage.org/image/1c84nec5g/)
Rx
(http://s3.postimage.org/1c8l6rt38/DSCN0542.jpg) (http://postimage.org/image/1c8l6rt38/)
I use SMA connector for CLF200 size coax as you can then use the inner part of a servo push rod tube to snug inside the connector (ignore the red bit of tube, it's just to show the pushrod tubing idea) and the antenna cable fits inside that and the pushrod tube stops the centre pin pushing back, pic should explain it but if you need more, ask away.
(http://s3.postimage.org/1c9ovo4xw/DSCN0543.jpg) (http://postimage.org/image/1c9ovo4xw/)
I have no experience of the Turnigy, but it sounds very logical.
Nigel
Thanks to Devonian and Thundead I now have 459MHz antennas and the 459MHz firmware flashed on!
One thing that confused me for a while when doing the flashing was that the pin order on the Tx is different to the Rx (the Tx and Rx pins are reversed). So for ages I was trying to update the Tx firmware with the cable I had made (which was wrong). All is well now though. I know this is clear if you look at the diagram, or in fact exercise proper caution and look at the board (which is obscured by the case on the Tx) but if they're anything like me people might assume that the cable is the same for both ends. Perhaps it would be worth mentioning that in the guide?
Also, Thundead, the (excellent) guide says "now repeat this with the Tx". It would be clearer if it said that you need to load the OpenLRS_TX.pde for the Tx side. I can see people trying to put OpenLRS_RX.pde on the Tx.
Time for a range check and hopefully a fly! Fingers crossed not a crash.
Thank you both for all of your help
All the best
Simon
I've updated my original post regarding the 2 different pinouts on the Tx and Rx boards (only required for programming).
http://www.fpvuk.org/forum/index.php?topic=2551 (http://www.fpvuk.org/forum/index.php?topic=2551)
If you look at my Tx & Rx modules, you can just about make out where I made a cutout to align with the programming pins.
No need to dismantle anything now for firmware changes (and I made a few in the beginning!).
Nigel.
I updated the guide with the missing bits on TX programming and Pin layouts.
Sorry took me this long but for some reason I got unsubscribed from the thread.
Cheers,
Mihai.
Quote from: simondale on October 03, 2011, 02:33:44 PM
Thanks to Devonian and Thundead I now have 459MHz antennas and the 459MHz firmware flashed on!
One thing that confused me for a while when doing the flashing was that the pin order on the Tx is different to the Rx (the Tx and Rx pins are reversed). So for ages I was trying to update the Tx firmware with the cable I had made (which was wrong). All is well now though. I know this is clear if you look at the diagram, or in fact exercise proper caution and look at the board (which is obscured by the case on the Tx) but if they're anything like me people might assume that the cable is the same for both ends. Perhaps it would be worth mentioning that in the guide?
Also, Thundead, the (excellent) guide says "now repeat this with the Tx". It would be clearer if it said that you need to load the OpenLRS_TX.pde for the Tx side. I can see people trying to put OpenLRS_RX.pde on the Tx.
Time for a range check and hopefully a fly! Fingers crossed not a crash.
Thank you both for all of your help
All the best
Simon
I've modified the v1.10 firmware and asked Flytron to post it on the Google download site (should run on v2 hardware - but needs someone to check it out for me/us)
http://code.google.com/p/openlrs/downloads/list (http://code.google.com/p/openlrs/downloads/list)
If you want to check it out right now, get it from here
http://forum.flytron.com/viewtopic.php?f=7&t=4&start=100 (http://forum.flytron.com/viewtopic.php?f=7&t=4&start=100)
I've also modded my 2nd post
http://www.fpvuk.org/forum/index.php?topic=2551.0 (http://www.fpvuk.org/forum/index.php?topic=2551.0)
so you can easily see the few lines of code that need changing for 459MHz use (highlighted in red so you could simply cut n paste into any firmware version you choose to try).
I haven't any v2 hardware to test it on as yet (Simon ;) )
Nigel.
Hey Nigel,
Had a quick look and seems ok :) You can test it on the v1 hardware by modifying this and should work.
//####### TX BOARD TYPE #######
//We have 2 option for OpenLRS TX, You can use original TX modules or just load the Tx firmware into the RX
// 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
#define TX_BOARD_TYPE 2
I'm going to give it a shot tomorrow and see if it works ok but on my v1 hardware
Regards,
Mihai.
Isn't his great we now have a UK legal dedicated RC uhf control..bravo..
I received my v2 TX and RX and plugged the TX into my 9X. It all works fine. I cannot find any documentation on the V2 RX board at all. There are no markings on the PCB to even say which is - + S. There is also no indication of which channels are for each pin.
I am missing something since I cannot seem to locate this documentation.
Can you read schematics?
If so,
Tx
http://www.flytron.com/pdf/openlrs-m2-module.pdf (http://www.flytron.com/pdf/openlrs-m2-module.pdf)
Rx
http://www.flytron.com/pdf/OpenLRS_RX2.pdf (http://www.flytron.com/pdf/OpenLRS_RX2.pdf)
Looking at the pics of the Rx, the Signal pin is nearest the chip (with the inline 1k resistors leading to the Atmega).
http://www.firstpersonview.co.uk/index.php?main_page=popup_image&pID=349&zenid=0feapkhsdliok08g46ah07j763 (http://www.firstpersonview.co.uk/index.php?main_page=popup_image&pID=349&zenid=0feapkhsdliok08g46ah07j763)
On my v1 board, the servo connections are, from left to right, 1 2 3 4 5 6 7 8 (when viewed as if you were plugging in a servo and the antenna to the top).
It follows that the connections will be like this...
1 2 3 4 5 6 7 8
S S . . . . . . .
+ + . . . . . . .
- - . . . . . . .
Please verify this for yourself and not take my guestimate as gospel!!
As this is open source hardware, you are free to programme whatever you want, hence the reason not to mark the board perhaps?
I see from the schematic, that Melih has now made the Tx and Rx programming pinouts the same, so only one programming cable is needed - on v1 boards, they were transposed.
HTH
Nigel.
Nigel,
Many thanks for your answer and please take this reply in good spirit as it was intended.
The documentation for OpenLRS seems to be totally non-existent. I have a degree in electronics and have been designing stuff for over 20 years. I am also a programmer and consider myself to be very competent. I do not expect anything to be delivered to me with this level of documentation.
The guys at Flytron and the people in the "community" have developed something that is truly groundbreaking. It is a fantastic product .. I used my multimeter to find out what the connections were and just plugged it into my 9X and it worked first time. Leaving 24 Ghz available for FPV is wonderful and I intend to use it. If you do lots of searching and exploring forums you will find that you can force the RX to deliver PPM on a single pin. This connects to a MultiWii installation and provides for a very neat installation.
OpenLRS is fantastic and I cannot believe that there is no "idiots guide". I will be producing this guide and hope that more people will take up this great product.
Sorry if I sound a but uptight about this. I have worked for so many years and have had so many ideas that have been wasted (I invented Cover Flow many, many years ago but did not patent). This project deserves to enter the mainstream and not be just a project that you enter at your own peril. There is some reference made to adding a Wii Motion+ and a Nunchuck thus giving you a complete control system and RX combined. When you add the possibility of 2 way serial communications and the advantages of Open Source the mind really starts to race....
I explored by plugging in servos and stuff according to how I see my receivers 1 - throttle, 2 ailerons etc. I should have thought this out better since I know PWM goes in a different order. By experimenting I have worked it all out.
I will produce the documentation as soon as possible and look forward to working much more with OpenLRS.
I quite agree that Melih doesn't do enough to sell this great bit of hardware, least of all by not producing any useful and basic documentation.
He is a very clever bloke, but like most clever blokes, he's more interested in the hardware/software than producing decent documentation.
Good to see you are embracing the open source concept and making your contribution by producing some documentation.
Doc's in PDF format would be fantastic.
When you have it done, post it on the Flytron forum as well and it will surely benefit a lot of followers.
As you say, this has the potential to do so much, but only if the end users can follow it without having to be uber geeks !
Just look at how AlexinParis' MultiWii went viral....
Nigel.
I know I've mentioned this before but can't recal getting an answer...
What's the point of the 459mh OLRS if it gives no more range than say a Futaba FASST or a 35mhz system ?
Not having a dig, just curious as to what the advantages are
On page 2, post #22, I mentioned...
Benefits of OLRS for me are:
1) Much less risk of being shot down by someone (as is possible on 35Mhz).
2) Gives me more freedom of choice for video link - I now have 2.4GHz and 5.8GHz
3) OLRS has the possibilty to be programmed to do many things, e.g. built in Rx stabilisation with IMU's, 2 way telemetry, etc.
4) It's open source as opposed to closed souce, so I have the freedom to add as much as can be developed for the system.
5) Potential of 'long range' - so far it has gone out to 4km, with probably more to be had with effecient antennas.
6) It's currently the cheapest and UK legal UHF system on the market.
7) I enjoy the challenge!
... more to come, I'm sure.
Nigel.
I would echo all of your points.
I plugged the OpenLRS module into the back of my FF9 (which arrived this morning) and powered up the RX. I twiddled the knobs and the servos moved. I am very impressed that it worked first time and all so simple.
Going to reprogram tonight to 459 and the latest release.
Quote from: Splashy on October 14, 2011, 11:17:48 PM
I would echo all of your points.
I plugged the OpenLRS module into the back of my FF9 (which arrived this morning)
This morning ?
It was sent for next day delivery several days ago
Yes, I know. And the tracking showed it went from Swansea to Birmingham to Milton Keynes to Taunton. Strange route.
I don't mind really. I am very pleased with the TX, it does have a nice feel to it. I am now thinking about trying to get my Spektrum DX8 working with the OpenLRS.
Many thanks for sorting out the FF9 for me.
I connected from the trainer port of my Spektrum DX8 to the OpenLRS TX and it worked first time. This is quite exciting for me since I can now just plug the 3.5mm jack into the trainer port (leaving the DX8 switched off). It loads the current model and offers full control over OpenLRS. Because something is plugged into the trainer port it does not transmit anything over 2.4Ghz. I powered the OpenLRS TX from a 2S LiPo and the trainer lead can be up to maybe 6ft long so could plug into your base station where you can mount the TX.
The next step for me is to add a Wii Motion+ gyro and an accelerometer onto the RX. I will also be adding a GPS which will communicate with the base station using the transparent serial comms.
The possibilities for OpenLRS are endless. This could be much more versatile and exciting than the MultiWii since it can offer everything that the MultiWii offers and a great UHF system built in and 2 way serial communications.
I nearly bout one of these from FPVUK, yesterday, I even put the stuff in my basket, but ended up leaving it, I'm thinking of one for my quad, how big is the aerial on thes, is it like 35mhs and as long as you like, and do you get one with it, there isn't one shown in the picketers on FPVUK.
:) G
G, the ones supplied are short 'rubber duck' ones and tuned for 433MHz so not ideal for 459MHz.
I made my own for the Tx and Rx and at full 1/4 wave, they are just 163mm (6.5") long !!
Go back a page and look at my post #33 to see physical sizes ;)
Nigel.
Thanks Nigel
that's not to bade a length, thanks.
:) G
I've just received my OpenLRS Tx and Rx from Flytron and I have a few questions for the UK community that I hope someone can shed some light on.
A stumpy aerial was packaged with the Tx and there was a longer aerial that was loose in the jiffy bag.
Now I assumed that because the stumpy aerial was packaged with the Tx that it was the Tx aerial, but looking at others stock setups it looks to be the Rx aerial (and also logically being small).
I have attached the stumpy aerial to the Rx and the longer aerial to the Tx and all seems well. Can someone confirm my findings please?
Neither unit came in any sort of protective case. I now notice that after ordering that a Futaba module case can be ordered as an extra, but they now appear to be out of stock. I've ordered an empty Futaba module case from Ebay, but it doesn't have that lump on the back meaning that I'll probably have to use a right angled SMA connector. Does anyone foresee an issue with this?
Also, how do you guys protect the receiver given that it has no hard casing? I noticed that one person was lucky enough to have a suitable Tx case lying around, but I'm not that fortunate. Any ideas?
:pleasantry:
The short rubber duck is for the Rx and the longer rubber duck is for the Tx.
Personally, I wouldn't fly too far out with them as they are tuned for 433MHz.
Make a couple of antennas for 459MHz, look on this thread and my thread for some guides.
http://www.fpvuk.org/forum/index.php?topic=2551.0 (http://www.fpvuk.org/forum/index.php?topic=2551.0)
I'd get on to Melih at Flytron as the Tx normally comes cased??
Maybe this is suitable...
http://www.giantcod.co.uk/frsky-module-case-futaba-p-405244.html (http://www.giantcod.co.uk/frsky-module-case-futaba-p-405244.html)
My Rx is now hard cased, as I had a suitable case and adapted it to fit, otherwise maybe some clear heatshrink?
Nigel.
Am I right in thinking you can change the firmware to and from 459 to 433 very easily, and does 433 have a longer range as per the Dragon link or is the range specific to this unit? (I spend alot of time abroad so could change to 433 when in Europe)
Hey there,
Yup you can easily change between 459 and 433 but you will need your pc/laptop to upload the fw.
In theory, 433 has longer range because the wave length is bigger per say. If you fly a lot in europe I'd suggest you go for another UHF system because openLRS has a low power output (100 mw) compared to the other long range systems (500 mw - 2w).
Regards,
Mihai.
Quote from: Ian F on November 07, 2011, 09:11:00 PM
Am I right in thinking you can change the firmware to and from 459 to 433 very easily, and does 433 have a longer range as per the Dragon link or is the range specific to this unit? (I spend alot of time abroad so could change to 433 when in Europe)
I noticed Flytron do a 7w booster anyone got feed back on that
Yes, it's uni-directional (it SHOUTS, but can't listen) so you lose the bi-directional useage when it's in circuit.
Plus it's up to 7 watts for goodness sake!
Nigel.
Plus it's up to 7 watts for goodness sake!
Nigel.
[/quote]
I take it thats quite alot!?!?!?
What kind of range could you get?
well, most UHF systems have up do 2w and manage roughly 40 km
doubling the power gives you 1.4 times better range so quick calculation gives me about 78km for 8w of power haha so 7w should be maybe 70km ?
would be very very tricky to get video on that range but it has been done:
Long Range Flying (One Way Record) (http://www.youtube.com/watch?v=LTClFTAfwMY#)
Trappy doind trappy stuff haha: 86.9 km
Quote from: Ian F on November 08, 2011, 11:31:35 AM
Plus it's up to 7 watts for goodness sake!
Nigel.
I take it thats quite alot!?!?!?
What kind of range could you get?
[/quote]
Have a treat for all the openLRS lovers out there : proper RSSI :P Check first post.
Regards,
Mihai.
Nice to see that someone is also developing the system.
I'm right now building an antenna tracker for the OpenLRS but still I got some problems...
I do also send the GPS data parsed to the ground station where an Arduino does Display
all the Stuff on a 2.8" Touchscreen like speed altitude etc with an update rate of 2Hz.
The GPS data will be sent with a beginning "B" and a ending "*" so without a Checksum
and had never a problem with that.
Right now the Servos aren't that precises to put the Antenna into the direction of
the plane. Will probably work with a compass to get more accurate pointing.
(http://www.ibrutech.ch/fpv/tft1.jpg)
Display shows from left to right:
strength of RSSI, distance to start coordinates, direction pointing of the plane in degrees (seen from north), altitude, speed, satellites, graph shows RSSi level
When max button is pressed it will show max values of altitude speed and distance from home.
(http://www.ibrutech.ch/fpv/tft2.jpg)
Would be nice to collaborate :)
(sorry for the bad english but I'm from Switzerland :))
wohoo great work gekoch,
Would love to collaborate :) I am currently focusing on improving the range and making the system booster compatible but after I finish the fw I'll see what we could do for telemetry.
As shown in my other posts, I attempted in creating an antenna tracker based on the system but stopped because I didn't like the idea of having my transmitter tethered to the antenna.
I managed to get the pan and tilt system to work properly ( I think ) so I'll dig up the old fw and drop you a PM. maybe you can use something from it.
Think the best approach is to use two systems, one for antenna tracker and the other for RC control. The more stuff you add onto the firmware, the more laggy the RC link becomes ( laggy servos etc)
Mihai.
Yes you're right telemetry is nice to have.
As soon as the weather gets better I do some tests with my firmware to see
how the system works.
How about the diversity capability of the the OpenLRS receiver/transmitter chip
can we do there something?
Keep up the good work thx,
Andy
thnk you saw this thread but here is the link anyway
http://www.fpvuk.org/forum/index.php?topic=3642.0 (http://www.fpvuk.org/forum/index.php?topic=3642.0)
that includes my current mods for the lrs system.
regarding diversity, my current fw uses a slave RX as a backup receiver but it's not compatible with telemetry yet.
Regards,
Mihai.
Quote from: gekoch on December 26, 2011, 05:22:28 PM
Yes you're right telemetry is nice to have.
As soon as the weather gets better I do some tests with my firmware to see
how the system works.
How about the diversity capability of the the OpenLRS receiver/transmitter chip
can we do there something?
Keep up the good work thx,
Andy