openrcforums

Hi Mike,
I updated eePSkye (Revision: 411 May 8, 2015)
and my Taranis-B-x9d with erSky9x-x9d (VERS:V.682-Mike / DATE: 08.05.2015 / MOD: X9D).
Still no model image and I tried several other model images still no work.
I am using the model images that came with my Taranis SD card, folder named "BMP"
and created a copy and changed the name of this new folder to "IMAGES".
Here is a copy of my Taranis SD card directory IMAGES folder: Here is a copy of my eeprom model list and for testing model images I used 700 TEST: Bob B.

I think I have a fix for the "trailing spaces" problem.
Bob: I'll have a look at your problem, it may be the same problem. Try the LONG UP LEFT LEFT and see if you have any spaces before the .bmp on the bottom line.

Mike.

MikeB wrote: It's why these are "test" versions!

Mike.

Yes I'm fully aware of that. Im just letting you know of any kind of issue, so you can see if it's a bug or my mishandling.

MikeB wrote:I think I have a fix for the "trailing spaces" problem.
Bob: I'll have a look at your problem, it may be the same problem. Try the LONG UP LEFT LEFT and see if you have any spaces before the .bmp on the bottom line.

Mike.

I thought about unwanted spaces and moved the cursor to the end and deleted everything to write again, but to no avail.

Just posted a new test version (Taranis and plus only), with the trailing spaces of the image filename removed.

Bob: I just loaded your EEPROM into eepskye, and transferred the 700 TEST model into a Taranis Plus and the quad image (from my IMAGES folder, loaded OK. I have yet to copy the quad.bmp file from your zip file above.

Mike.

Hi Mike,
New version Taranis erSky9x-x9d (VERS:V.687-Mike / DATE: 08.05.2015) is working. It did not work at first even after restarted several times.
I think I may have had extra space or spaces behind model image name.
I was not able to remove them before.
I think I was not understanding how to use the deleting/backspace with the new keyboard menu.
I think I got it now.

Thank you Mike.

Bob B.

Hi Mike,
When I tried setting a Model Image to eeprom model "700QUAD-A" its not working.
When I was able to get model image working with "700 TEST" I had tried a lot of ways to delete any unseen spaces and some how did succeeded.
I so far have not been able to repeat what I did before.
If able and when to have copy/past in eePSkye may be a help to see extra spaces.
I am not understanding how to use LONG UP LEFT LEFT to see extra spaces.
I must be thick headed here, I try it some more.

Bob B.

Hi Mike,
I think I am understand the LONG UP LEFT LEFT to see the extra spaces now
and have (I believe) deleted all the extra spaces, but still not working with eeprom model "700QUAD-A".

Bob B.

Are you trying to use the quad.bmp file for this as well?

I'll investigate further. I think I can get a situation where the image isn't displaying at power on, but if I select a different model, then select back to the required model, the image does display.

Mike.

A minor bug, but if you are on the telemetry screen to start with, the image doesn't display to start with. If you go to a non-telemetry screen the image does display, and stays displaying if you go back to the telemetry screen.

Mike.

OH YES ! it dose!

Thank you !

Restarting in Telemetry dose not do it, must change to different screen.

Thank you Mike ! It was looking like it was not working.

Bob B.

I have the fix for that bug, it will be in the next test version.

Mike.

Hi Mike,
Confirm new features are working in test version Taranis-x9d VERS: V.720-Mike / DATE: 09.05.2015 / MOD: X9D.

Thank you Mike.

Some of the BMP OpenTX model images are not working.
Is this because the model image names are to long ?

Bob B.

I'm allowing 10 characters for the filename, not including the .bmp.
It may be those images are in a slightly different .bmp format I'm not (yet) handling. Please let me know some of the files that are not working, I can investigate them from the file of images you posted above.

Mike.

Hi Mike,
I shorten some of the more then 10 characters model image names to 10 characters and then they do work.

Some long model image names: Cessna 182 Skylane / Cessna 195 / Cessna 337 that do not work.

So the ones that do not work just need to be renamed to 10 characters long.

Bob B.

Add Edit: With the Cessna 195 and Cessna 337 I believe there is two spaces between Cessna and the #s.

I just tried "Cessna 337" and it failed, but was trying to load "Cessna.bmp", so something isn't right with handling the space character in the filename, I'll investigate.

Mike.

Edit: Got the fix for that!

Hi all,
I found out this issue in both taranis. I made a video, its not very good, but i think its able to show the essential.
Its mainly about the model name not showing even though its has been writen.
http://youtu.be/U7fn2PLwxVI

Just on slot 32. I have a fix!

I'll hopefully post an updated test version tomorrow.

Mike.

Hi all,
after updating to the latest test version (13-May-2015 15:36) my Taranis started beeping by himself. I went to the "Diagana" menu and realised the values there were very "chaotic", all of them changing very rapidly. So i did a recalibration and the beeping stoped. Is this rapid value changes normal or they shoud be more steady?

I have increased the CPU clock to 120MHz (from 60MHz). It may be there is more "noise" on the analog inputs doing this. I'll see if I can improve things.

Mike.

I switched back to 60MHz and there is less "noise" on the analog inputs, so far I haven't managed to reduce this, but I'm still thinking about it.

Mike.

isnt it possible to overclock half way, like 90MHz, probably it will stabilized, i think?

I don't think the chip is overclocked at 120Mhz..

João

The chip is specified to run up to 120MHz, we were running it at half speed.
It looks like openTx has less jitter, but why I don't know as the code is pretty much the same on both, not surprising since I wrote the ADC driver for both!

I have done one small change and I think the jitter is now less. The amount of jitter is not enough to really affect the actual servo pulses.

Mike.

Hi Mike,
In trying erSky9x-9xd test version V. 737-Mike, Dated 13-May-2015 15:36,
confirm Fix image filenames with spaces bug, strip trailing spaces from image filename, improve image decoding and Increase CPU clock to 120MHz. Mainly for the standard to get the image on the display.
New Model Image feature seems to be working well.
Did some test flying with my 700A Quad and seems to be still working well.

I would like to have the option, to not have the New Model Image feature with my Telemetry screens.
Maybe to be able to turn it off in radio setup.

Bob B.

Hi Mike,
I have an idea, is it possible to use my external DJT module with its D8R-II plus Receiver
and the Taranis internal XJT with its X8R Receiver at the same time.
If it could be done, there would be a need to identify the 1-8 channels between both receivers.
So maybe have ability to select in model setup when using both external and internal transmitters/Receivers
at the same time the Channel Numbers would change to 1A-24A for internal and 1B-24B for the external Transmitter/Receiver.
This could be another way to have 16 channels using an external DJT module with one of the D series Receiver.

Bob B.

That should all work, as long as the DJT isn't modified to send telemetry data on pin 5 of the module connector.
Both the internal and external modules have a configuration parameter of "1st chan".
If you set the internal to PXX, D16, 1st chan=1, and the external to PPM, and 1st chan=17, then channels 1-16 will go to the internal module and channels 17-24 will go to the external module.

Mike.

Hi Mike,
Thank you, I did not know about this feature or remember it maybe.

I have the Taranis-x9d and at Aloft Hobbies (http://www.alofthobbies.com/frsky-taran ... -case.html) / FrSky Taranis Plus / Details, down to Features, one of the features listed is: 16 channels (32 channels when combined with an external XJT module).
So it looks like we could use 4 X8R receivers and have 32 channels.

Dose this work the same way as 1-16 channels internal XJT transmitter
and 17-32 channels with an external XJT module (erSky9x-x9d) ?

I also see listed in Features: ARM Cortex M3 32-bit 60MHz
This maybe a stupid question but: Should the CPU clock be listed as 120MHz or 60MHz which openTX is running at ?

MikeB wrote:I have increased the CPU clock to 120MHz (from 60MHz). Mike.

MikeB wrote:The chip is specified to run up to 120MHz, we were running it at half speed.Mike.

Bob B.

bob195558 wrote:So it looks like we could use 4 X8R receivers and have 32 channels.

No. 2 off X8R receivers, one bound to the internal module and the other bound to the XJT, but using the X8R 16 channel S.Bus outputs.

Hi RCHH,
I have not used S.Bus and not have an understanding about how it works and how to use it as of yet.
So what you are saying when using 4 X8R receivers we must use the S.Bus feature ?

Bob B.