openrcforums

I'll change the bit rate and the volume, although if that would be a problem I should get a lot of noise. Will make the adjustment anyway.
I am playing them from SF.
Will report if something change after the modifications.

I have created or modified several sound files to play as track files both in the companion 2.2.1 and the Opentx 2.2.1 in the transmitter. I checked file sizes and naming length, but I cannot understand why some of them work and some don't, in either radio nor companion (which makes a lot of sense)....

Got you. Thank you for the link and suggestion.
Don't know if I will end up making the modification, but if I do, after testing I will let you know.

jtaylor, would you give me a link to the code, please?

I confirmed jtaylor's change to the log file header. I guess that was a miss when assigning units to Cels in the code.

missing pictures

I read this thread, and it looks I have a slightly different issue also related to the voltages. My problem is with the LiPo voltage sensor information. The two values I cannot see in the simulation are Cels and Vmin. However, they work on the transmitter and also I can see both in the Log viewer. I...

A expected the bin file has nothing to do with the GE not opening the kml file.

Well, here are the news. I reset the file association for klm, and was able to open the file from the explorer. I reset the file path in Companion, I copied the path from the 2.0, I restarted the computer, and still the GE opens but the kml file does not show. I am out of ammo. Well, the only thing ...

Kilrah, as usual, you hit the nail. Here is what I got so far: 1) As expected the kml file was where you said it should be. 2) When I tried to open it with GE, GE started but although the task manager showed it as active it was nowhere to be seen. Kind in the limbo. 3) I opened the GE from the start...

Ray, I am also using GE pro, and I had set DirectX. I bet that in the attached screenshot you have something under Temporary Places. I have nothing, as you can see. Now, there is another variable that I wonder if it doesn't make the difference, which is the bin that I am using. Below is the one I am...

Ok, Ray, That's weird too. I think the GE having a problem is 80%, the other 20% is my companion. Unfortunately, I don't know how GE manages the cvs file, but what is very strange to me, is that the log files from 2.0 and 2.2 have a major difference right at the sector where the coordinates are stor...

File

Hello Ray.
The file has not been manipulated. However, I am sending you now the file downloaded straight from the transmitter SD.
I did not have any problem on opening the one I sent you before, as shown in the screenshot I just did.

Sorry, Ray.
Since I posted those logs, I made some corrections to the Telemetry settings and following Kilrah suggestion I deleted all sensors and readquired back again.
As per the new suggestion from Kilrah, here is the last log I got.

Well Ray, the fact that the GE showed me in the middle of the Atlantic, did not mean that the coordinates were wrong. I entered the coordinates in Google Maps, and it showed me exactly were the plane was at the time of the log. In other words, there is no problem with the log itself, as it shows cor...

Well, I opened the log in Companion 2.1, and I got a track in GE. However the location was near the coast of Africa rather in the East Coast of US.
I think only a magician can fix this problem. I am done with ideas.

Bad news gents. I deleted all the logs 2.0 and 2.2. Did not work
Uninstalled GE and re-installed. Rebooted the PC. Did not work
Uninstalled Companion 2.2.1 and re-installed. Did not work

Now I am frustrated. I don't know any other trick.

Suggestions please!!!!

Hi, Ray
Thank you for your suggestion.
I will take the shot right now.

Good news and bad news. As per Kirlah suggestion I deleted all sensors and after waiting for 30 seconds, I make a sensor discovery. All sensors were up and reporting as expected. The altitude issue returned to normal (almost no differences between the GPS and the Vario). The bad news is that I am st...

OMG, Well, let's what happens tomorrow after the delete/discover.
Thank for your response. I hope then, that the altitude and the GE track issues are both related to Sensors discovery.

OK, Will try that tomorrow at the field. Thanks a lot. One other weird thing I found out related to Carbo observation is that I had set the Vario Source to RSSI instead of Alt. That should fix the altitude issue. I verified with other config and the log shows similar GAlt as Alt, but still the track...

Wow, you'r right. I thought it was GSpeed. Will Check that out. In most of my logs they are pretty close one to the other. Regardless, I cannot even see neither a piece of the track. I think I need help form one of the 2.2 developers. Like you, I am using 2.2.1. No reason not to get the same track t...

Carbo, please, check the screens I am getting (attached). I think the problem I may have is for some reason when I hit the GEarth icon, the software module that is activated is the one used for 2.0 instead of the one for 2.2. I can try to make the log to "look like" the 2.0 and double chec...

I have set the bario Alt to Auto-offset, but not the GPS Alt and Speed.

I am not able to transfer the logs into Google Earth. I can see the log into the Companion Viewer, but when I click on the Google Earth icon, it opens the program, but does not show the track. I checked differences between the 2.0 and 2.2 logs, and I found out that in the 2.2 latitude and longitude ...

Got it. Thank you

Thank you guys. I found the response here: viewtopic.php?t=8724
Kind regards

I just upgraded to OpenTX 2.2.1, and I cannot find the way to display in the screen the lowest cell value. In 2.0 I just have a Cell parameter that showed the minimum value, but in 2.2 cannot figure out how to obtain that value. Is anywhere where the new values/calculations are explained for 2.2? Th...

Thank you. The video https://www.youtube.com/watch?v=DsbaftCHpHs shows the right way to do that.