openrcforums

No, I have not built the sensor for tx yet, one step at a time so I know each part works properly.
But I wonder if it is the combination of the gy86 l and GPS causing trouble..
Note that is is a long time working before error occurs..

OH this afternoons first flight got gps lock very fast (on ground) and then was relatively trouble free so I imagine gps signal strength must vary and this was why I had less trouble, maybe later the gps strength was not so good and why I had more trouble..

openXsensor-master pitch roll yaw faster heading using accx y z.zip zip file with my version I'm using, so im using gy86 and gps at 5hz , I know its not the latest version but I did not see anything thats changed which would fix this problem. hope you can find something and its not just something i...

Will do , I am using 5v 16m arduino and recent version of osx but not sure if it's 7 or not, I will send it all

Flew for a couple of hours this afternoon, first hour I only lost the openxsensor telemetry once for about a minute, second hour after a battery change it did it about 5 times.. But wow those vario tones work really well now , I cored many thermals and it was faster and more precise and easy to do w...

Yes, RX volts and rssi etc still OK, just openxsensor data not there. This was done on s.port RX, I have tested on hub type but not in air and I never had the problem so I think it might be s.port related. Testing now with another RX is not easy as everything is now installed , also running opentx 2...

Tested today for real with the heads up display and it all worked great, the pitch and yaw levels did get thrown a little with g forces but still flyable and I returned to base many times just using the taranis display! The vario tones responded well too, I was definitely able to core thermals easie...

I tested it with opentx 2.0 and 2.1 and it worked OK just on the tx s.port pin or the RX s.port pin.
Sounds like you have a problem if it's flashing led and you get nothing from it..
Do you see it in sensor page if you discover new sensors?

I think I remember reading that there was a time limit for one id to send all its info, having loads of sensors on one id made it difficult to send all the data within that time limit and that was why there needed to be different ID used within the sensor?

Autocorrect. Lol Vario not various , I just mean we have pitch which could be used to some extent to compensate the vario tones, ie if nose pitch goes up and v.speed goes up then it's not real lift its just stick thermal... But if pitch stays the same and v.speed goes up its really lift... But to de...

Would defo be pos to compensate the various now though, we have yaw and pitch....

Gy521 is probably what you have, it has gyro ACC but no ms5611, but you can just add it to a gy63 to give same result.
We talked about using the angle of attack to compensate for vario but not implimented it yet, ATM the IMU just speeds up the response time any gives yaw pitch roll.

Yes gy86 has the ms5611 too..

Athertop, you need to use drawText for some reason...

Note in 2.1.7 that pilot-lat and pilot-lon are now available named as ive spelled them and used in the table same way as lat and lon..

I got the heading working in tx using the 6050 and s.port pin , needed to use termp1 in tx and acc values RX sensor as the acc values belong to same sensor and it would not work splitting them . To get the heading working I had to enable vario so code for ms5611 is in too, this did not seem to matte...

Just did a test to see how much drift there is just using the 6050, its a lot less then I expected, left it on for 20 mins and it drifted by only 6 degrees. So calibrating it will not be required very often and could even be done in my script by comparing it to plane heading when in same orientation...

To test the sensor connected to s.port on tx I connected a openxsensor with just vario to RX ( tried both d8r and x6r ) and then put my own s.port pitch roll sensor on the tx s.port pin, both vario and pitch roll worked at the same time. I know the heading thing could be done with ppm but doing GPS ...

Mstrens, I have ordered a compass board with 5883l like the one on gy-86 and intend to put it on the tx on s.port connector in order to give me my own compass heading so I can know which way I am facing in relation to the aircraft when flying by instruments display. once I upgrade to openxtx 2.1 I c...

an update on the response from opentx,
they admit the error and are considering the fix but note that other projects use the acc numbers as is now and so would need changing back in the other projects too ...
I will have to keep changing that line for now i guess. No big deal..

Can I connect a sensor, either s.port or hub direct to taranis and have data available as if it were connected via RX? Reason is for adding firstly a compass and maybe GPS later on. These would be in addition to the sensors in the plane. The first step of compass could just use any free sensor name ...

https://github.com/opentx/opentx/issues/3274

A link to my issue raised, no response yet.
Kilrah looks very busy..
If the problem is opentx and it sounds like it is then I will just change my code for now I guess and change it back if the problem gets fixed.

I have to change this line every time I test to get hub to be same as s.port, heard nothing from opentx on the difference in decimal place... I will probably change my code from using the temp1 and temp2 to accx,y,z to make more sense and to free up the temp in case of someone wanting them #elif def...

that looks same as x6r now.

OK I tried all combinations and no difference, even reverting back to sending all gps data in one go and still gps alt is lower on d8 then x6r, x6r reports higher then it should be but again this could be my gps reception. d8r reports about minus 5 and x6r reports plus 56 But thinking back now altit...

swapping between x6r and d8r the gps alt is off, x6r is plus 50 and d8r is minus 20 around....
I will experiment with sending alt data with lat and long,

a short test shows in logs -23 rather then old tests where alt was +47.
but this may not be conclusive as my gps lock is poor ( indoors as dark and raining outside...)

I will do a short test with logging enabled to see if its correct now in the Google maps as before this was wrong...

Could it be that GPS alt was wrong because of the bug just found?
Before I changed the counter reset line I was not getting any gps altitude ....I have it displayed now.

mstrens i am a little confused with the numbering of the split gps, not sure if i am understanding it wrong or if its a typo. but I dont see how the hubgpscount is reaching 4? I noticed it when thinking of sending the course more often. else if ( hubGpsCount == 4 ) { SendValue(FRSKY_USERDATA_GPS_CUR...

Ok I must be bored lol I tried spinning round and I don't think it will be a problem in flight...... ...I feel sick now !!!! :mrgreen: Sorry, couldn't help it :mrgreen: João I'm suprized it took you so long lol, I started to think that you were not following this thread ... I must be getting old th...