Direct Frsky telemtry data from MW FC

Re: Direct Frsky telemtry data from MW FC

Postby ezio » Wed Oct 15, 2014 8:45 pm

izeman wrote:
ezio wrote:Maybe someone can record with realterm ( http://realterm.sourceforge.net) or similar software couple minutes of FrSky telemetry traffic with working GPS?
There is a bug in EZ-GUI in position reporting and I want to fix it. Unfortunately I don't have required receiver to test with.
Bart

so you want someone to connect eg a serial2usb bridge to the serial configured in config.h for frsky telemetry and record that traffic? if yes, i can do this. i have working gps, but no telemetry data shown on my remote. maybe this will help me as well, as you can for sure see if the data itself present on serial3 is correct or not. should i send it? you will have to wait 10h as i just started work.

Not exactly. I need a data recorded from the frsky transmitter. So you have to connect ie FTDI cable via level converter to the frsky transmitter and then record a data at baud rate 9600.
User avatar
ezio
 
Posts: 827
Joined: Sun Apr 01, 2012 11:03 pm
Location: Paris

Re: Direct Frsky telemtry data from MW FC

Postby maik » Fri Oct 17, 2014 6:53 pm

Hi Bart,
I just send some captured FrSky data to your EMail.

Maik
User avatar
maik
 
Posts: 6
Joined: Tue Sep 16, 2014 7:26 pm

Re: Direct Frsky telemtry data from MW FC

Postby ezio » Fri Oct 17, 2014 8:00 pm

maik wrote:Hi Bart,
I just send some captured FrSky data to your EMail.

Maik

Thanks
User avatar
ezio
 
Posts: 827
Joined: Sun Apr 01, 2012 11:03 pm
Location: Paris

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Fri Oct 17, 2014 10:02 pm

ezio wrote:
maik wrote:Hi Bart,
I just send some captured FrSky data to your EMail.

Maik

Thanks

glad that maik did it, as i have no working level converter (as you could read in the past posts). thanks
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Postby ezio » Sat Oct 18, 2014 3:29 am

Thanks for help. The problem has been fixed. Beta version will be available in few hours.
User avatar
ezio
 
Posts: 827
Joined: Sun Apr 01, 2012 11:03 pm
Location: Paris

Re: Direct Frsky telemtry data from MW FC

Postby henfri » Sun Oct 26, 2014 9:26 pm

Hello,

thanks for the work on this!
Can you confirm, that this is the latest code?
http://code.google.com/p/multiwii-osd/s ... rsky_sport

And:
What's that about the S.Bus Host Mode?
https://code.google.com/p/multiwii-osd/wiki/Frsky_SPort
What's the difference?

Greetings,
Hendrik
henfri
 
Posts: 17
Joined: Wed Aug 27, 2014 10:12 pm

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Fri Nov 07, 2014 11:17 am

i got telemetry working now. seems there where two problems:

.) the level converter was broken
.) i had to set "serial protocol" from "none" to "hub" at my remote :)

if you never used telemetry before it's easy to overlook this very obvious but never used before parameter :oops:
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby SpeedBoy » Fri Nov 07, 2014 4:17 pm

izeman wrote:.) i had to set "serial protocol" from "none" to "hub" at my remote :)


What is your remote, bro? I don't see it at my taranis settings.
SpeedBoy
 
Posts: 7
Joined: Sun Oct 12, 2014 2:40 pm

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Fri Nov 07, 2014 5:29 pm

SpeedBoy wrote:
izeman wrote:.) i had to set "serial protocol" from "none" to "hub" at my remote :)

What is your remote, bro? I don't see it at my taranis settings.

turnigy 9xr with frsky mod and open-tx.
here is a pic:

IMG_0274.JPG
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby henfri » Sat Nov 08, 2014 9:15 am

Hello,

can someone confirm, that this code (FrskyTelemetry.zip 3344Byte) works with an X8R?
There were comments in this thread, that the X8R uses a different SPort Protocol (which sounds odd to me: Does FRSKY offer different Sensors for it?)

Besides: I use this inverter:
http://www.ebay.de/itm/115200bps-Stucke ... 3cc8fe732d

Unfortunately it gets very hot as soon as I connect voltage to it. I think I might have fried it, as my Board/BEC supplies around 5.9V, rather than 5V (I have fixed that now).
Anyway: I am also not sure about the wirering of this. Can someone upload a photo?

I thought:
Controller Side:
Serial TX connected to inward pointing arrow on TTL Side
5V connected to + on TTL Side
GND connected to - on TTL Side


X8R Side:
Serial TX connected to outward pointing arrow on RS232Side
+ on RS232 Side not connected
GND connected to - on RS232 Side


But also I read somewhere, that the Protocol uses RX and TX on one cable (half-duplex). But I might mistake that with SBus?

Greetings,
Hendrik
henfri
 
Posts: 17
Joined: Wed Aug 27, 2014 10:12 pm

Re: Direct Frsky telemtry data from MW FC

Postby henfri » Wed Nov 12, 2014 8:08 pm

No comments?
henfri
 
Posts: 17
Joined: Wed Aug 27, 2014 10:12 pm

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Wed Nov 12, 2014 8:14 pm

i don't know what code you are referring two, and i guess noone wants to search the whole thread to find the correct link. maybe you should post it.
i had the very same problem with the converter getting hot and posted that already. i guess they sell a lot of cheap sh*t. i bought three converters from 3 different ebay sellers and 2 of them work. my power source is 5v though.
the wiring as you described it is correct, but you can leave away the rs232 gnd as gnd is already connected. there are at least 3 pictures in this thread (included one post from me) where you can see the correct wiring.
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby ASAP » Mon Nov 17, 2014 7:25 pm

Hi all!
I have a FrSky Taranis and an X8R and I'm using a HK multiwii pro FC on my quadcopter. As soon as I realized the idea of sending telemetry datas from the FC to taranis by reading this post, I went mad !
Yet, I didn't understood if It is possible or not and I sincerely ask someone help !
Is there anything we can do? Any working code ? Do I need external circuits ?
ASAP
ASAP
 
Posts: 8
Joined: Mon Nov 17, 2014 6:51 pm

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Tue Nov 18, 2014 10:22 am

did you read ANY post here? doesn't look like. i suggest reading all from the very beginning. there are circuit and all info you need.
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby ASAP » Tue Nov 18, 2014 4:48 pm

So do you confirm me It is possible to do it (with Taranis and X8R)?
I started reading first pages, but right now I believe not; I will continue reading.
Thank you!
ASAP
 
Posts: 8
Joined: Mon Nov 17, 2014 6:51 pm

Re: Direct Frsky telemtry data from MW FC

Postby ASAP » Thu Nov 20, 2014 6:53 pm

Still no idea! I hope someone could help me. I have only read about the possibility to do it with other frsky rx, X8R excluded !!! Or I'm wrong ?
ASAP
 
Posts: 8
Joined: Mon Nov 17, 2014 6:51 pm

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Sat Nov 22, 2014 10:55 am

so telemetry is working. that's good. i can see ACCx, heading, gps data etc.
but i really struggle with VOLTAGE and CURRENT. if i connect it into A1 and A2 of my d8r-xp receiver is can see that data. but i'd like to feed voltage and amps to the fc and transmit it via serial protocol to the receiver (as the other data).
so i chose FAS as input and i can see values, but no matter to what analogue port (standard values A0 = vbatpin and A2 = psensorpin) i connect me sensing line i don't get reasonable values.
i guess i mix up some thing that don't go together, maybe someone can help:
is FAS meant to read regular voltage divider values and output from a acs758 sensor? or can this only read "original" FAS-40/100 data? is my only chance to use A[12] for that? or buy a FAS sensor?
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Sat Nov 22, 2014 9:43 pm

amp and voltage sensor connected to d8r receiver's A1 and A2 gives jumping values for current. the reading seems ok. resolution is quite low as this is a 200a sensor. i'd like to stop the jumping. any idea how to do it?

izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby bob195558 » Sat Nov 22, 2014 11:29 pm

Hi izeman,
With the values changing so quickly, maybe they are not real data values.
It maybe the sensor data is not getting through.
You may find help on the OpenRCforums being you are using er9x on your Turnigy9x.
Bob B.
bob195558
 
Posts: 38
Joined: Wed Jul 17, 2013 1:16 pm
Location: New England, USA

Re: Direct Frsky telemtry data from MW FC

Postby bob195558 » Sun Nov 23, 2014 12:24 am

ASAP wrote:Hi all! I have a FrSky Taranis and an X8R and I'm using a HK multiwii pro FC on my quadcopter.
As soon as I realized the idea of sending telemetry data from the FC to taranis by reading this post, I went mad !
Yet, I didn't understood if It is possible or not and I sincerely ask someone help !
Is there anything we can do? Any working code ? Do I need external circuits ?
ASAP
ASAP wrote:So do you confirm me It is possible to do it (with Taranis and X8R)?
I started reading first pages, but right now I believe not; I will continue reading.
Thank you!

Hi ASAP,
I do not know the details how to send MultiWii Telemetry Sensor Data through FrSky Receivers / Transmitters
and display it on our 9x Radio telemetry screens.
It is possible to do, I think some people have done it, but so far no one has completely documented how to do it yet.
Yes, I think you need additional circuits boards with firmware between your MultiWii board and the FrSky Receiver.
I am watching this subject, hoping someone will do a complete documentation of how to do this.
I know this dose not help much, I would like to do this also.

Bob B.
bob195558
 
Posts: 38
Joined: Wed Jul 17, 2013 1:16 pm
Location: New England, USA


Re: Direct Frsky telemtry data from MW FC

Postby izeman » Mon Nov 24, 2014 3:45 pm

thanks bob. this openXvario stuff sounds interesting. as always it's a LOT of reading before you have even the LIGHTEST idea what those guys are talking about. always nice to see a project with a wiki.
i guess that openXvario collects several telemetry data and sends them to the remote. maybe this is the more versatile solution. i guess i'll try it out.
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby bob195558 » Mon Dec 01, 2014 4:25 pm

bob195558
 
Posts: 38
Joined: Wed Jul 17, 2013 1:16 pm
Location: New England, USA

Re: Direct Frsky telemtry data from MW FC

Postby henfri » Wed Dec 31, 2014 2:57 pm

Hello,

izeman wrote:i don't know what code you are referring two, and i guess noone wants to search the whole thread to find the correct link. maybe you should post it.


Sorry. This is the Code I refered to:
viewtopic.php?f=7&t=1929&start=150#p43296
download/file.php?id=2497

The question is, whethter the code works for both the XR8 and the D-Series RX.

Greetings,
Hendrik
henfri
 
Posts: 17
Joined: Wed Aug 27, 2014 10:12 pm

Re: Direct Frsky telemtry data from MW FC

Postby Vertigo » Fri Jan 23, 2015 1:55 pm

Why do we need a hardware converter for frsky telemetry on a multiwii, when cleanflight/naze32 seems to do it with no additional hardware?
Does it have something to do with the "old" telemetry used in the D4R/D8R vs new in the X series? Id be happy with support for the old ones without needing an inverter.
Vertigo
 
Posts: 41
Joined: Mon Jul 08, 2013 6:58 pm

Re: Direct Frsky telemtry data from MW FC

Postby QuadBow » Fri Jan 23, 2015 3:11 pm

Vertigo wrote:Why do we need a hardware converter for frsky telemetry on a multiwii, when cleanflight/naze32 seems to do it with no additional hardware?
The Frsky protocol for the old receivers requires inverted signals. ATmega CPU does not support this inversion by hardware. So, either you have to use software serial (not recommended, since users have reported timing and performance issues) or you have to use a hardware connector, which consists basically of one transistor function. This is not necessary for Naze since that hardware is powerful enough to deal with software serial without performance issues.
QuadBow
 
Posts: 532
Joined: Fri Jan 04, 2013 10:06 am

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Sat Feb 21, 2015 4:23 pm

i must say this is the most frustrating and time consuming mission i try to accomplish.
so many different approaches, patch for different MW versions. i once got gps, altitude etc showing on my remote, but amp and voltage was wrong. no i can have (more or less) correct voltage readings but nothing else but ACC values. no altitude, no gps, no heading, no current..
i use the rc-timer 90a current/voltage sensor which works. i had to add some correction factor of /100 as current was showing 10A instead of 0.1A. now this works fine and quite accurate in multiwii gui. so i assume that my connections are all working well and i got voltage and current connected to the right analogue inputs of my crius aio.
has anyone got a COMPLETE up2date multwii directory working with ALL (available) flight data sent to the remote? i want to have capacity warning and low voltage warning on my remote, and also would like to log max altitude and max current drawn by the motors.
thanks in advance!

ps. i still don't understand why this doesn't find it's way into the official branch. does it add so much more complexity? frsky telemetry doesn't destroy any other features, and if you don't activate the code it's not even present in the firmware ...
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby QuadBow » Sat Feb 21, 2015 6:24 pm

izeman wrote:i still don't understand why this doesn't find it's way into the official branch. does it add so much more complexity? frsky telemetry doesn't destroy any other features, and if you don't activate the code it's not even present in the firmware ...

I agree with you. I don't understand neither, why this piece of well running software has not found its way into the official branch. I suggested it one year ago, when we discussed about the features for multiwii 2.4, but unfortunately without big success.
QuadBow
 
Posts: 532
Joined: Fri Jan 04, 2013 10:06 am

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Sat Feb 28, 2015 10:51 am

one week later, and nobody here is willing to put a working multiwii version online? wow.
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby QuadBow » Sun Mar 01, 2015 10:55 am

izeman wrote:one week later, and nobody here is willing to put a working multiwii version online?

I saw your point and took it into consideration...

Attached you can find my FRSKY telemetry extension to multiwii. Consider that you have to use a level converter between FC and FRSKY receiver as described earlier in this post.

Consider that I use a homebrew non-standard multiwii version with several additional features. So, I took me some time to seperate only the telemetry functions.
I have not had the possibility to test the attached version with your configuration.

So, you have to adapt config.h as usual. You should enable VBAT and POWERMETER and set the related definitions properly.
I have implemented a cells' voltage measuring. Of course, it only runs if you have connected all cells output via resistor deviders to the flight controller. If you want to use it, you have to define VCELLS in config.h and set the related definitions CELLxPIN and CELLxSCALE properly.
I have also implemented an estimation of the average speed of motors (rpm). For this you have to know the resistance of each motor in milliohm and the KV value and set the related definitions R_MOTOR and KV_MOTOR in config.h properly.

Furthermore, you have to set SERIALx_COM_SPEED (the serial used for telemetry) to 9600.

On the FLD-02 display you will see:
- arming time
- voltage
- temperature of the built-in sensor
- second temperatur of a second sensor (optional)
- RSSI
- number of satellites as fuel level
- motors' speed (rpm)
- distance to home
- course
- current
- capacity consumption (Ah)
- cell voltages (if enabled)
- acceleration
- longitude and latitude

Good luck!
Attachments
Multiwii2_3Telemetry.zip
FRSKY telemetry extension
(157.04 KiB) Downloaded 231 times
QuadBow
 
Posts: 532
Joined: Fri Jan 04, 2013 10:06 am

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Sun Mar 01, 2015 11:23 am

thanks a lot. i really appreciate your effort. having a (for you) working solutions makes it easier for me to determine the problems i have with my version. i will test and report back!
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Sun Mar 01, 2015 2:25 pm

quick testing: it's working. you seem to have modded voltage reading somehow. the voltage reported to multiwii_gui and sent to telemetry is around a factor 2 off. can that be? eg. it shows 12.2v (which is correct) on my console and 23.1v on my remote.
at least now i can see current, voltage, altitude, gps and others. thanks a lot again!
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby QuadBow » Sun Mar 01, 2015 4:44 pm

izeman wrote:is around a factor 2 off. can that be?

The FLD-02 device has to be configured, too.
Go to "Menu" at start-up and set the second value of the entry "Volt Ratio" to the ratio of the resistor devider for the accu voltage.
If you change that ratio to the half of the current value, it will show you the right voltage. In the worst case you could have to replace the resistors in order to get a more suitable volt ratio.
QuadBow
 
Posts: 532
Joined: Fri Jan 04, 2013 10:06 am

Re: Direct Frsky telemtry data from MW FC

Postby izeman » Sun Mar 01, 2015 7:30 pm

QuadBow wrote:
izeman wrote:is around a factor 2 off. can that be?

The FLD-02 device has to be configured, too.
Go to "Menu" at start-up and set the second value of the entry "Volt Ratio" to the ratio of the resistor devider for the accu voltage.
If you change that ratio to the half of the current value, it will show you the right voltage. In the worst case you could have to replace the resistors in order to get a more suitable volt ratio.

i don't have a FLD-02. i show the values directly on the 9XR remote. so i changed the Voltage Amperage section in telemetry.cpp to the "original" voltage calculation:

Code: Select all
// Voltage (Ampere Sensor)
void inline send_Voltage_ampere(void)
{
         uint16_t Data_Voltage_vBat_bp;
         uint16_t Data_Voltage_vBat_ap;
         uint16_t Data_Voltage_I_Motor;   
         uint16_t voltage;
         voltage = (analog.vbat * 110) / 22.5;         
         Data_Voltage_vBat_bp = voltage / 100;
         Data_Voltage_vBat_ap = ((voltage % 100) + 5) / 10; 
         Data_Voltage_I_Motor = analog.amperage / 100;

  sendDataHead(ID_Voltage_Amp_bp);
  write_FrSky16(Data_Voltage_vBat_bp);
  sendDataHead(ID_Voltage_Amp_ap);
  write_FrSky16(Data_Voltage_vBat_ap);   
  sendDataHead(ID_Current);
  write_FrSky16(Data_Voltage_I_Motor);   
}


i also had to enable several settings in "main function" section, as i didn't get "heading" and "GPS altitude" showing. i also set the "rpm" to the "real" number of satellites instead of a % setting.

Code: Select all
// Main function FrSky telemetry
void telemetry_frsky(void)
{
   static uint32_t lastTime;
   static uint8_t tele_loop;
   if ((millis() - lastTime) > 250) {
      // Data sent every 250ms
      lastTime = millis();
      tele_loop++;
      send_Voltage_ampere();
      send_Accel();
      // Data sent every 1s
      switch (tele_loop) {
         case 1:
         send_Num_Sat();
         send_GPS_longitude();
         break;
         case 2:
         send_Altitude();
         send_RPM();
                        send_GPS_altitude();
         send_GPS_speed();
         break;
         case 3:
         send_cell_volt();
         send_GPS_latitude();
                        break;
         case 4:
         send_Course();
         send_RPM();
         send_Time();
         tele_loop = 0;
         break;
         default:
         break;
      }
      sendDataTail();
   }
}
#endif
izeman
 
Posts: 57
Joined: Tue Sep 16, 2014 10:49 am

Re: Direct Frsky telemtry data from MW FC

Postby QuadBow » Mon Mar 02, 2015 7:24 pm

izeman wrote:so i changed the Voltage Amperage section in telemetry.cpp to the "original" voltage calculation:
It seems that FRSKY deviated for the voltage from the normal scheme of one integer before the dot and one after the dot.
QuadBow
 
Posts: 532
Joined: Fri Jan 04, 2013 10:06 am

Re: Direct Frsky telemtry data from MW FC

Postby Alexinparis » Tue Mar 03, 2015 12:51 am

QuadBow wrote:
izeman wrote:i still don't understand why this doesn't find it's way into the official branch. does it add so much more complexity? frsky telemetry doesn't destroy any other features, and if you don't activate the code it's not even present in the firmware ...

I agree with you. I don't understand neither, why this piece of well running software has not found its way into the official branch. I suggested it one year ago, when we discussed about the features for multiwii 2.4, but unfortunately without big success.


And honestly me too.
I remember it was initially suggested as a standalone extra file patch frsky.cpp or something like this. Not really the file structure I like to see.
So at this time, I decided to split Serial.cpp and Protocol.cpp to separate clearly all UART "low device" communication (Serial) and functional aspects like MSP (Protocol).
The purpose was also to use the new Protocol.cpp file to gather all functional communication aspects like telemetry.
Sebbi was involved in this process, but no news since. And I personally don't use any telemetry system, so can't offer the support it deserves.
So my suggestion:
After 2.4 release, are you ok to integrate and support frsky things in the main branch ?
Alexinparis
 
Posts: 1630
Joined: Wed Jan 19, 2011 9:07 pm

Re: Direct Frsky telemtry data from MW FC

Postby vpb » Tue Mar 03, 2015 3:52 pm

Alexinparis wrote:So my suggestion:
After 2.4 release, are you ok to integrate and support frsky things in the main branch ?

Its very good idea... :idea:
I still use Frsky Telemetry with r1739 in the old way, standalone file. And its still working good :mrgreen:
Image
vpb
 
Posts: 231
Joined: Mon Jul 23, 2012 4:09 pm

Re: Direct Frsky telemtry data from MW FC

Postby QuadBow » Tue Mar 03, 2015 10:22 pm

Alexinparis wrote:After 2.4 release, are you ok to integrate and support frsky things in the main branch ?
Hi Alex, I would be pleased to do so. The question would be how to integrate frsky telemetry into multiwii leaving some room for other telemetry protocols like hott, s.port, etc. My proposal would be to start with the proposed files telemetry.cpp/h. The section for frsky will be separated with the definition FRSKY_TELEMETRY. This would leave some room to add on further telemetry protocols. Maybe we could universalise some functions, even if the protocols differ from each other.
QuadBow
 
Posts: 532
Joined: Fri Jan 04, 2013 10:06 am

Re: Direct Frsky telemtry data from MW FC

Postby TheBum » Wed Mar 04, 2015 12:42 am

I'm already assuming this approach with the modifications I'm making to the old HoTT telemetry code, so merging it in should be somewhat simple.

The HoTT code is pretty large, so I'd still like to keep the bulk of it in a separate source file to keep from cluttering Protocol.cpp too much.
TheBum
 
Posts: 35
Joined: Wed Dec 03, 2014 9:53 pm

Re: Direct Frsky telemtry data from MW FC

Postby seikurou » Sat Mar 07, 2015 3:55 am

What am I doing wrong here?
I've checked the serial speed which should be 9600
Tried swapping the tx/rx wires
using QuadBow's code (thank you for that)
Image
Not even sure if i'm supposed to use that that level converter, or any at all.
Thanks
seikurou
 
Posts: 14
Joined: Mon Dec 08, 2014 5:37 am

Re: Direct Frsky telemtry data from MW FC

Postby QuadBow » Sat Mar 07, 2015 7:05 am

@seikuruo

You are using a cheap Promini/ATmega328-based flight controller. That type of controller has only one serial port. That serial0 is used for the connection to your computer. Frsky telemetry requires a second serial port-not an AUX port. Therefore you have to use a Mega/ATmega2560-based flight controller. All attempts to use software-serial (that means any port can act as a serial) on a promini failed due to performance issues.
QuadBow
 
Posts: 532
Joined: Fri Jan 04, 2013 10:06 am

Re: Direct Frsky telemtry data from MW FC

Postby baco » Thu Mar 19, 2015 2:56 am

MultiWii 2.4 Just Published and I wanted to implement telemetri FrSky with files of version 2.3, but does not work. Get an error in a variable that is not declared, "ACC_1G" but not that it is this variable. Any help, please?

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Acaba de salir multiwii 2.4, y he querido implementar la telemetri FrSky con los archivos de la version 2.3, pero no funciona. Sale un error en una variable que no esta declara, "ACC_1G", pero no se que es esta variable. Alguna ayuda, por favor?
User avatar
baco
 
Posts: 13
Joined: Thu Mar 12, 2015 11:47 pm

Re: Direct Frsky telemtry data from MW FC

Postby haydent » Thu Mar 19, 2015 6:24 am

QuadBow wrote:
Alexinparis wrote:After 2.4 release, are you ok to integrate and support frsky things in the main branch ?
Hi Alex, I would be pleased to do so. The question would be how to integrate frsky telemetry into multiwii leaving some room for other telemetry protocols like hott, s.port, etc. My proposal would be to start with the proposed files telemetry.cpp/h. The section for frsky will be separated with the definition FRSKY_TELEMETRY. This would leave some room to add on further telemetry protocols. Maybe we could universalise some functions, even if the protocols differ from each other.


not a bad idea having telemetry files, as there's quite alot that could go in there. with the various protocols around. i recently patched against shared the s.port addon into protocol files from alex's advice, but it hasnt been accepted yet.
User avatar
haydent
 
Posts: 583
Joined: Sun Jun 17, 2012 1:35 am
Location: NSW, AU

Re: Direct Frsky telemtry data from MW FC

Postby TheBum » Thu Mar 19, 2015 4:28 pm

Some possible common functions I can think of are a setup function (called from the MultiWii.cpp setup() function), an arm function, a disarm function, and a "check" function. Calls for the first three should be able to be placed in static locations in the code.

The "check" function's purpose would be to check for telemetry requests and get the ball rolling on sending the data to the receiver. If the protocol dictates that the telemetry data be sent unsolicited, it would only perform the second task. The function would be called from the control loop, but finding a location that fits every telemetry protocol might be tricky. In most cases, I would think that immediately after all the loop data is updated would be the place to call it, but I couldn't say that one or two protocols might not need it somewhere else.

The HoTT telemetry code I'm working would need to use the setup, arm, and "check" functions as a minimum. The only specialized code I'd have left is the code in the serial ISR to save a request timestamp, which is needed to support the timing constraints of the protocol.
TheBum
 
Posts: 35
Joined: Wed Dec 03, 2014 9:53 pm

Re: Direct Frsky telemtry data from MW FC

Postby baco » Fri Mar 20, 2015 6:50 pm

Ya lo he solucionado. Pongo el código nuevo.


Telemetria FrSky en MultiWii 2.4

https://mega.co.nz/#!8pVCzIRa!hCMJ5H5sgBP5540_GOYCd-C0Dpr8J4jSfSMTqdFikn8
User avatar
baco
 
Posts: 13
Joined: Thu Mar 12, 2015 11:47 pm

Re: Direct Frsky telemtry data from MW FC

Postby ardufriki » Mon Mar 23, 2015 2:34 pm

Hi there, I`m using 2.4 MW code, but also a MWOSD at SERIAL 3. Should I change the define:

#define TELEMETRY_FRSKY_SERIAL 3

to this?

#define TELEMETRY_FRSKY_SERIAL 1

It seems SERIAL 1 is not used in my CRIUS AIO PRO V2..
ardufriki
 
Posts: 88
Joined: Thu Dec 13, 2012 4:47 pm

Re: Direct Frsky telemtry data from MW FC

Postby ardufriki » Mon Mar 23, 2015 8:24 pm

I have the SERIAL 1 for Frsky, but I dont see anything in that port. I have tested with ftdi connector and terminal software, but no success. I have connected only TX line.

Does the Frsky protocol need both RX and TX lines or Multiwii transmittes information without being asked to?

Any clue?
ardufriki
 
Posts: 88
Joined: Thu Dec 13, 2012 4:47 pm

Postby baco » Mon Mar 23, 2015 9:33 pm

Tienes puesto el inversor?
User avatar
baco
 
Posts: 13
Joined: Thu Mar 12, 2015 11:47 pm

Re: Direct Frsky telemtry data from MW FC

Postby QuadBow » Mon Mar 23, 2015 9:38 pm

Hi ardufriki,

Are you talking about multiwii frsky telemetry or about openlrsng you mentioned in http://www.multiwii.com/forum/viewtopic.php?f=15&t=6262 ?

Have you connected the level converter (mentioned earlier in this thread) between your multiwii flight controller and the FRSKY receiver? You need only the TX line of multiwii to be connected to RX of the receiver.
QuadBow
 
Posts: 532
Joined: Fri Jan 04, 2013 10:06 am

Re: Direct Frsky telemtry data from MW FC

Postby ardufriki » Tue Mar 24, 2015 8:47 am

Hi Quadbow, Im talking about the same issue, but now it is solved :-)

I had to select SERIAL 1, and everything works now !! No need of RX line, as you said. Thanks.

I dont need level converter, cause Im using orangerx RX flashed with openlrsng as "frsky emulator", I connect TX1 from CRIUS FC to RX pin of my orangerx RX.

Now I have many values in the screen of my Turnigy 9x transmitter (hacked and flashed with er9x frsky option).

I have to check all, but it seems number of sats, amps, heading, altitude, throttle and other values works fine. I still dont have GPS position values displayed ok in the LCD screen (rare numbers and so on), and I cant get the voltage from MW (I see the internal battery of the transmitter instead), but it is a beggining.

I think I will have to flash another versión more compatible with all of this er9x or openTX in my transmitter

A hard work, but know I am getting something. :-)

PD: I have checked the Telemetry.cpp and I dont see any errors control (checksum or similar), so the bad packets could be dropped. I see many rare values in my LCD.
ardufriki
 
Posts: 88
Joined: Thu Dec 13, 2012 4:47 pm

PreviousNext

Return to Ideas

Who is online

Users browsing this forum: No registered users and 1 guest

cron