IanR

Has anybody else noticed how fragile the whisker portion of the antenna seems to be? I bought an S6R from T9 recently and the whisker portion of one antenna seemed to angle itself to the remaining, covered, portion of the antenna as I moved it about, setting up etc. Sure enough, as I fitted it to my model, the whisker portion broke off. T9 replaced it n/c. Now, the same thing is happening again, with one whisker showing a propensity to sit at an angle. I am not kack-handed and treated both antenna very gently. Second question - can I just remove some of the covering from a broken antenna to make a new whisker on a now-shortened antenna?

I heard someone bragging, once, about how easy it was to tamper with the odometer with a laptop with suitable software. He had had his car done - dropped the mileage from 30 odd thousand to 18000 prior to selling. I would get an experienced mechanic - perhaps someone from the garage where you have your cars serviced - to give the car the once-over. He might be able to tell from wear and tear how much use the car has had. Even little things like wear on the pedals, steering wheel, carpets, seats etc not to mention mechanical parts.

Sorry, Chris, I'm not quite with you. Are you saying that I can use LUA scripts in 2.1.9 to re-configure the S6R directly from the Taranis or should I upgrade to 2.2, first? Ian

Thanks Mike and Chris. Does this mean I can use LUA scripts with my Taranis X9D+ (on 2.1.9) to re-calibrate my S6R receiver, in situ, without having to connect the receiver to my computer in order to use the Config programme? I just want to reduce the rudder gain. If so, this would keep me happy for the time being since, at this time, I am not concerned about sending/receiving SPort telemetry data but I will have to purchase the manual because I cannot see any reference to LUA scripts either on my Taranis or OpenTX. Ian

I think I am missing something. T9's description states that the manual is for "...reference to the Taranis X9D plus and OpenTX firmware 2.1.9..." and goes on to state "...There is a chapter on learning to create custom functions for the Taranis using LUA script, including examples you can work with..." I thought that LUA scripts would only work with 2.2 firmware. Can anybody explain, please? Whilst I am on, can anybody clarify for me - I am currently on OpenTX 2.1.9 but would like to familiarise myself with 2.2. Can I download and run OpenTX 2.2 for familiarisation but continue to use 2.1.9 or will downloading 2.2 automatically overwrite 2.1.9? Thanks, Ian

My point is that software developers often point out that their products may - or even - will not work properly out of the box and have said so from the very beginning. When I was nobbut a lad (in the 60's) the company I worked for introduced a computer system which worked mainly from punch cards. The cost of this system included a full-time person from the software company, who remained on site for 1 year, to iron out bugs. I think that we have become so used to this that we accept it without complaint. Having said that, I am not complaining, just making an observation. In this instance, I accept that I will have to wait until others have said that 2.2 is robust enough even for the not very adventurous among us to give it a go. And I do love playing with my Taranis and OpenTX. Ian

Good question, Trebor. The announcement which Chris has linked to doesn't make it clear. But even if it is ok for the x9d+ I shall be holding off installing it on mine because "...This is a .0 release. A lot of testing has been done by developers and beta testers, but inevitably some issues only pop up with large scale use and particular use cases, if you’re not very adventurous hold off for a few releases until things are well ironed out..." Is there any other industry where getting a new model comes with this type of caveat? If you bought a new version of a car or vacuum cleaner or TV, or whatever, you would expect it to function as required. Only with computers and software, which is what these transmitters basically are, are you told from the start that they may not work properly. Ian

Thanks, Andy. Now I know its not me. And thanks for the advice to hold off on 2.2. I most certainly will not be trying things out with a pre-release version. I agree - it really is a fantastic system. The more you get into it the more fantastic it seems to become. Ian

Re missing timer, I saw the following on the RCMF forum, dated 27 February 2015:- "...Have now solved the problem, which is simple if you know How. My good friend Pete Hindle who is more savvy in these things found it with me when we compared Tx screens. The timer screen comes up by paging through the initial screen, when the Tx is switched on, to the screen that comes after the Channel Monitor screen. If you keep this screen live when you switch off, it will return when switched on. If however you change from that screen to another on the paging sequence, the timer/s do not show until you page through again to the screen after the C M screen. Even rich at T9 was not aware of this, probably because few owners use the timer facility..." As mentioned in my previous post I had fixed this in my transmitter so could not try it there. However, I had not deleted the file in my PC so loaded it into OpenTX Companion. On the Transmitter Simulator, after paging through to get back to the main screen, the timer re-appeared. Previous to this, when I set the timer running, the minute call-outs worked normally even though the timer was not visible. Apparently, this happened when the temperature got below 10 degs and was supposed to have been fixed with ver 2.0.16 - but I am using 2.1.9 and the temperature yesterday was way above 10 degs.

Strange Behaviour! I hope I'm not hi-jacking Phil's thread but since he is concerned about upsetting his transmitter's "programming" I thought I would add this here. 1) As mentioned above, I had made changes, using the transmitter, to a models settings whilst putting in trims and endpoints etc. I wrote from the radio to OpenTX and a new window/box appeared with all my models in it, side by side with the old one. 2) I closed the old window/box 3) I then "saved as" the new window/box with today's date in the name and closed OpenTX 4) Then I went into Windows Explorer and moved the old file into my Backup folder. 5) Then I re-opened OpenTX and the new file. Strange behaviour now:- 6) All the models to which I had previously added the timer function had now lost the timer function. The Setup Screen still showed that the timer was selected and should be functioning but no timer appeared on the Taranis Simulator. Even stranger behaviour:- 7) All the timers had disappeared from my Taranis !!! 8) I copied and pasted the model setup I had been working on from the new file (without timer) to the old file (with timer). The new settings transferred to the old model file - no problem - but now the timer had re-appeared. Don't forget - this model had lost its timer. 9) So, then I was back to working with the old file, but with an up-dated model and all with timers. 10) Then I wrote from OpenTX to the transmitter and have all my timers and the new model changes in the transmitter. If anyone has bothered to follow the above I would be grateful for any insight as to what went wrong and what I should avoid doing in future. Ian

Andy, its not a problem. I try to remember to write changes to/from the transmitter as I go along but, sometimes, like now for instance, I forget and then I'm not sure if I've forgotten to update somewhere. I've just been setting throws and sub-trims on the bench (dining table) and was told by swmbo to clear up and writing this has reminded me that I need to write from the transmitter to OpenTX. Its an age thing, this forgetfulness. I think I shall combine your advice with Bob's advice and have a WIP eepe file alongside the main, working eepe file and copy from one to the other but renew the date in the filename as I go along. Since you have mentioned OpenTX 2.2, can I ask if you know whether or not there is a final version which I can put onto my X9D Plus. Ian

Yes, Bob, I understand what you are saying, even though I do not know what a WIP is (ooh, matron) It's just that I was hoping that a future version of the firmware might allow for "syncing" - much more elegant. And a small warning to others not to inadvertently overwrite settings. Ian

I, more or less, follow the procedures in Andy's post, above. However, I am not sure that it always works. For instance, lets say I am taking my time working on OpenTX with a complicated setup for Model A and doing it in a few separate sessions on the PC, over a matter of days. In the meantime, I take Model B flying and make changes at the field, lets say, setting various trim values. When I get back home the settings on my transmitter will be different from the settings on OpenTX. If I read from the transmitter to OpenTX I will lose the settings I have put into OpenTX for Model A. If I read from OpenTX to the transmitter I will lose my trim settings for Model B. Unless it is possible to read a specific model's settings from one to the other, rather than all model settings, I can't see a way round this except to do what I currently do i.e. as soon as I have finished a session I load the models from one to t'other so that the transmitter and OpenTX are always in sync. Following Andy's instructions, above, I am guessing would mean potentially losing any changes made in OpenTX and reverting back to an earlier state as per the transmitter. Ian Edited By IanR on 27/05/2017 12:56:47

Phil, for me, the instructions provided with the receiver are next to useless - but that's me, daft as a brush. There are 2 very useful threads here on the S6R. Start by reading through them and, if you're still stuck, get googling. My main problem was getting the S6R configured but, since you appear to have done that, I would say you are nearly there. The rest is the transmitter and OpenTX. As far as I am aware, you need to activate channels 9, 10, 11, and 12 or the S6R will not behave. 9 is the gain control: 10 and 11 are used to select between the 4 different modes: 12 is used for the self-check routine. Even if you do not intend to use all the functions you still need to allocate the channels - I think.

Have you set up channels 9, 10, 11 and 12 on the transmitter?

Neil, send me a PM with your email address. Ian

When I think of all the time spent in school learning the intricacies of a log book! At least, that was provided by the school - but we had to buy our own slide rules. Edited By IanR on 20/05/2017 09:48:12

Order for xt30/60s received ! Hobbyking's service is far better than their tracking information. Order placed on Friday AM and received the following Monday AM. No complaints - far from it, in fact. Well done Hobbyking. Ian

I want to change over from deans to xt30/60s. So, believing Hobbyking's blurb that I would have to order from them, if I was to get the genuine article and not a cheap and nasty alternative, I placed a decent sized order, all ex-stock from the UK warehouse. The order confirmation/tracking details show that they are being sent from AUSTRALIA !!!??? Ian

Devcon, I like the flying lead idea except that, for me, the configuration process doesn't work quite how I would have liked. I have mentioned before that, after using the Config programme and switching everything off, if I went back into the Config programme and "read" my settings from the receiver, and got different readings to the ones I had programmed in. This left me unsure as to whether the Config programme wasn't reading correctly or whether the settings in the receiver had changed themselves. I then started using the S8R Config programme AND before exiting the programme, I made sure that the receiver MOUNTING position (in my case left side up) was displayed before I switched off. This gave me the same "readings" 3 times in a row. However, I still don't fully trust what's going on and would prefer to remove the receiver from the model and go through the calibration process etc after making changes to the gain settings... ...or make the change in the TX using the lua script - when I eventually upgrade to 2.2. Ian

Thanks for the replies. Simon, when I wrote "...testing on the dining room table..." I should have said holding the model and jiggling it all over the place to see what happens. Since turning the ESC around so that the label/heatsink is pointed outwards I cannot replicate the problem. Ian

Further to my problem with the control surfaces moving in steps, rather than in one smooth continuous movement. It seems that this was an ESC problem and not an S6R problem. The model is profile epp and I had the ESC hot-glued to the fuselage side with the label (read heatsink) to the fuselage. Whilst testing I was jiggling the model to see how it reacted and the ESC became quite hot - I assume because all the servos were constantly moving. With the stabiliser switched off and the motor running the ESC quickly cooled down. Taking advice from others I turned the ESC so the label was facing out and then I could not replicate the moving-in-steps condition. Problem solved. After performing a range check I went flying in very windy conditions. Everything seemed to work OK - particularly the self-levelling mode. However, I wanted to increase the gain for stabiliser mode but doing so made the model fishtail quite badly. I need to remove the S6R from the model and re-connect it to my PC so that I can reduce the Rudder Gain in the Config program. What a pain. Am waiting to hear that I can safely upgrade my Taranis X9D Plus to Open TX 2.2 so that I can use lua script to make these kinds of alterations with the S6R in situ. Ian

Thanks Dick. My thanks to Matty crossed with your post. I have turned the esc around so that the label side is in the open air and, hopefully, will give it a go this afternoon. Ian

Thanks Matty (again!) I will do as you say. Ian

I have a small epp profile Hacker Strega model fitted with a FrSky S6R stabiliser/rx. When testing on the dining room table, with the stabiliser function on, the servos are all going like the clappers and I have noticed that the esc gets quite warm. I am assuming that this is because all the servos are working at the same time. I have hot glued the esc to the side of the flat fuselage with the flat label against the epp. This is because this label gives a good flat surface to glue to the fuselage. Is this wrong? Is the heatsink immediately underneath the label? Should the label always be in the airflow? I am asking this because the servos are occasionally behaving strangely and I am wondering if this strange behaviour is because the esc is getting hot and being overloaded. Ian PS when I run the motor gently, without the servos moving, the esc quickly cools down. Edited By IanR on 11/05/2017 10:34:38