Tim Ballinger

Just been fitting rods to the end of snake inners and ball clevis’s using the aforementioned 2 mm threaded rods. These are soft and threads cut easily if required. I find the rods just the right diameter for screwing into the inner but of course a 2mm die is too large. Being old and grey I still have some BA dies and an 8BA cuts just enough thread to make a good screw fit into the inner. The rolled 2mm threaded end screws into the 2mm ball clevis as is. I suppose I could buy a smaller metric die but in this case ‘old’ money works just as well. Tim

Lucas, Several of us started off before the mass build evolved and we all just chipped in snippets to Tony’s original build log which actually cover all the mini jets but I suppose mainly the JP and the Gnat. This the original thread...... All Forum Topics > Tony Nijhuis plan builders > New EDF Mini Jets- Jet Provost & Folland Gnat Tim

Hi Lucas, Glad to see you have started. You probably noted from earlier build logs that some of us found making the wing join much easier as you do the final assembly into the fuselage. It is a bit of a fiddle with the completed wing and you stand a chance of breaking balsa as you manoeuvre them in. Others seem to manage ok but I decided to join in situ after making sure the brace was a perfect fit of course. Tim

I standardised on 4Max esc having monitored the SBEC voltage output on several others and not been impressed. Even then on anything precious I always used a separate BEC for the Rx. These are always clean and constant. Having said that I am now trialing 2 FrSky Neuron S Esc. Again clean and constant output trace on the telemetry. Big bonus is they have inbuilt voltage, current, temp and rpm sensors which for me easily offsets the extra cost. Despite the extra sensors ,they are also the smallest/lightest around. You need to be on FrSky Sport compatible Rx’s of course. Not been released that long so yet to have a view on their longevity/reliability but they look well engineered. Tim

Barry, it is now many years since I finished in the aircraft industry and jet propulsion in particular. So with the huge caveat that there is a huge scale effect involved which generally makes small scale less efficient.... First thing is that thrust is made up of change in momentum of the air flow and the difference in static pressure at exit multiplied by the exit area ( there is also a drag associated with intake flow but I will ignore that). If you push air down a convergent tube it will increase the speed and reduce the static pressure. There is an optimum balance to be had between the increased momentum and loss in static pressure. So one thing early to note is that engines generally have jet pipes and nozzles. The jet pipe is really just a means of getting from the engine to the nozzle. The longer it is the less efficient it is. What we really have in our small scale gnat is just a long jet pipe . I have never undertaken measurements at this scale so I am just guessing that the jet pipe gives more losses than any marginal increase in momentum. I guess the thing to remember is that all the input energy is in the fan , after that you simply exchange one form of energy for another. If it is an inefficient exchange you will loose out. Just ramblings of an old engineer . At this scale You really need measurements to find the sweet spot. Tim

Andy , Thanks. Hope it cures your problems. There are not too many of using the FrOS so you have to be, shall we say, resourceful at times. Tim

Andy, Sure you are aware but just in case, that is only a beta version and it is down for a new beta as soon as they can sort out the sensor/telemetry peaks. Might not be too long I am guessing as they seem very keen to turn their attention to ACCESS viz ACCST D16 problems. Bob, While I ‘m happy to wait a bit longer , luckily for me, I can fly my glider and some models from my own field so as soon as I think the odds are better with new than without I’ll make my move. Tim

Andy J, I think that The latest GRX Rx’s firmware are only available as betas atm so if you only used the 16 Jan firmware That may be the issue but you would need to check on that one to be sure. The RX8Rpro was updated along with the Horus update on 24 March which is why it was ok. Tim

Allan, Just my view you understand. if you check the Rx’s noted above that still have bug reports and you do not use them then I think it is probably time to implement the latest firmware release for Tx and Rx’s. Personally I use a Grx6 which is in the list but the odd spike in telemetry value does not worry me and has probably always been there. The miniature Rx (XM series) looks more concerning , to my eyes these mainly input into flight controllers via Sbus . I do not use those. If you use stabilised Rx,s then there looks to be some issues to sort out. Tx dependant issues were the big one at the first release, I am seeing less ( perhaps none) of those reports now but as I am a Horus user on FrOS I tend to concentrate on anything in my camp . I am in still in no rush to update but I will do it in the next few weeks if nothing drastic is flagged up. None of that may help you but that’s where I am atm. Tim

Congratulations you’ve become the first tester and now the expert !😉

Andy, You select the bin file according to name that matches your setup . Yesterday’s release has 3 options EU, NEU and Flex. EU means LBT so that is the one you should pick. Some upgrades also select by mode but I am not sure why. Always bearing in mind I have only ever undertaken 3 firmware upgrades so they might do something different each time. Release notes are to say the least ‘ very brief’. Tim Edited By Tim Ballinger on 25/03/2020 16:17:21

Andy , The iXJT is in the main bin file for FrOS updates that is why it is not in the latest FrOS download as an explicit item. Plus had it not been included your original Rx would still have worked. At least that’s how I read it. OpenTX loads it separately I believe. Tim

Mike, I see this from the github testing Sounds like there are still problems despite the full release. Any advice? Receiver XM/XMP RSSI output wild fluctuation SBUS output FS bit is not set correctly Receiver G-RX8/G-RX6 Telemetry data peak issue Receiver S6R/S8R S8R quick mode startup slowly S8R works with RB20 without telemetry back S8R Aileron Inversion Problem in V-Tail-mode

Andy, The December issue of 1.3.06 is fine. It did not include the iXJT upgrade and did not need the Rx upgrade. I assume the iXJT upgrade from the jan release would be removed if you re flashed with an older firmware but this is new ground for me so I can not be certain. Certainly the December release would not work with the upgraded Rx. The Rx upgrade process change is I guess not unexpected as the System Files capability was only added in the December release. Absolutely right about keeping backups of old versions, I have all my Working Rx firmware files archived. Sure more help will come as folks assess the virtue of the latest release. Tim

Andy, As I mentioned earlier I was not undertaking this upgrade (16 jan) until it had been debugged and a new version issued. That said I have not seen any reports of Suitably updated Rx’s not binding. I did not know about today’s releases of Tx and Rx firmware until I read your post. I see it is there now but will still wait for good reports before doing it so Not sure I can help you. What I would do in your position is upgrade the Tx firmware to 1.306 as issued in December and make sure that works. That functionality I can vouch for as I have been running it since it came out. Tim

Mike, Thanks, I always like to know how things work. Tim

I have had a Mac for many years. Email from any provider I have used ( Bt, gmail, Sky, Yahoo) all work fine. As has been said above you just need to set the right attributes regarding server names. Most load in automatically if starting from scratch ie as soon as you type in your email address the system recognises the required settings automatically. Same with the iPad and iPhone. Tim

Out of interest I connected to the S port on the back of my Horus 10X just to see what voltage was on it. Can not say I understand the result, it started at 4.5V then slowly decayed to zero. Turned the Tx off then on again and it recharged as it were then decayed to zero again. Anyone bored enough to explain that to me? Tim

Andy, yes there is it’s on page 22 of the same manual you have been using. It uses the Sport on the back of the Tx and the Rx. You first need to download the relevant Rx firmware file then put it in the firmware folder. Then just follow the instructions. You are on your own here as I have never flashed a Rx yet but folks say it is very simple process ! I assume you had more than one file in the firmware folder which was stopping the Tx update process ? Tim

Andy Yes you do. Tim

Andy, Final thing I notice ( which I do not think would affect your failure to get the flash process at least displaying something) is that there were a few file additions needed to be made to the flash memory in 1.303 which were not noted in release notes of subsequent revisions even though the Flash memory files were included in the download files) I am assuming this was done before your 1.304Beta installation but since the relevant flash files do not appear in the 1.304 beta download I can not be sure. As I say i do not think it would stop anything trying to install but you do need to check they have been added. Includes ability to use lua scripts btw which are also needed to be added as indicated in the 1.303 release notes. If you have them all good and I do not know why the upgrade does not work. Tim

Andy, So the only file you have in the FIRMWARE folder is Release_X10_mode2_EU_frtx.bin - correct ? If so and holding the on switch and the right knob switch down at the same time does not enter the flashing sequence then I run out of ideas. Not sure what the up/down key should do as I have never read about it or tried it ! Looking like you need to get more expert advice. Tim

Andy, A little clearer then. Can I ask have you had the Horus from new and did you or someone else format the SD card. The 1.3.04 Beta folder I see which is dated 24/04/19 looks like an attempt was made to install that version of the FrOs. The folder itself would not cause a problem but the installation would only have worked if the relevant bin file was in the folder labeled FIRMWARE (and the relevant flashing sequence as noted in the guide followed). Does any of that ring true to you ? Tim

One further thought I was assuming you have downloaded the ‘How-to Horus X10 X10S Flashing instructions at the bottom of the FrSky downloads page. It is written by Mike Dailey. The FrOS update procedure starts on page 16 /17. Tim

If you have never used the SD card it may have only Firmware and LOGS folders but what you have shown is definitely the internal flash memory. Unless you are very confident I am wrong do not overwrite any of the files you showed . I think I would need to see that you have both internal flash and SD card file structures before going further. Tim