Here is a list of all the postings Mike Blandford has made in our forums. Click on a thread name to jump to the thread.
|Thread: Unable to save settings for S8R|
Well I'm running the Freelink app on my PC under Windows 10.
If you go here: **LINK**
Select the Tool-FrSky Freelink and download the .zip file, open the .zip file and navigate to the 32-bit or 64-bit version you need then just run the setup.exe.
I currently have an older version installed, but that version should be OK.
Which "app" are you using. FrSky now use the Freelink app, which handles the SxR using the STK as well as a number of other devices and connections.
|Thread: FrSky Neuron ESC|
Some settings to check, I had some interesting results with a 600 kV motor and 3S/4S cells:
What is the current limit?
Increase the "ramp up power", I had to do this to get 3 cells to give full power..
Turn rpm power protection off. This is significant more for low kV motors. The Neuron can decide the motor is too slow (e.g. stalled) so limit the current.
BTW, I reckon the full size pup flew on 40 to 50 watts per pound!
Edited By Mike Blandford on 14/06/2020 23:38:13
|Thread: FrSky Neuron rpm readings|
My understanding is the Neuron provides the number of flux reverse cycles per second (not flux reversals which is twice as many). On the Neuron I'm using I have to divide the raw value from the ESC by 7 to get the correct RPM.
|Thread: Horus RTC battery|
The value should be fine. It is read (and stored I believe) at power on, so just after it comes off load.
Even if it was measured later, it would be the voltage off load, so not very useful.
The RTC battery only supplies the real time clock, nothing else.
The spec. for the RTC battery supply is 1.65V to 3.6V, so the battery is OK down to around 1.7V, but will drop from there very quickly.
The capacity of a typical CR1220 is 37mAH. The typical current consumption of the RTC (at 25 C) is 0.75uA, so it should last for 5.5 years.
On the Horus, it could also be used to supply 4K of RAM, which about doubles the current it has to supply. At present, neither erskyTx not openTx do this, I don't know about FrOS.
As the circuit that is used to measure the battery voltage adds an extra load on the battery, the battery voltage is only measured at power on, then the measuring circuit is disabled.
I don't know why openTx doesn't assign a receiver number for the external module, perhaps raise an issue on Github.
Until recently, the multi-protocol module only supported 16 receiver numbers, so with more than 16 model memories available, maybe it was considered it couldn't be done.
The multi-protocol module now supports 64 receiver numbers, and these apply to ALL protocols. For a protocol that doesn't support receiver numbers natively, the receiver number is used to modify the module unique ID to provide the function.
If you haven't seen this, I have D16 firmware for D8 receivers available, see here: **LINK**.
For information, if using the older 'D' FrSky receivers these don't support the receiver number (model match), so if you have two models that both use 'D' receivers, you cannot make the Tx tell them apart, both will respond to either model memory in the Tx.
Since adding this warning to erskyTx was little more than adding a single line of code to call the receiver checking routine, I've added it anyway (code in and tested!). If you do Rx off then Tx off you won't even see it, but it will catch the situation.
So when selecting another model, without powering the Tx off, we could do with a similar alert to say the Rx is still powered.
|Thread: Sign of the times - funnies|
Dave - you might want to go and turn the hose off
|Thread: Why sudden dramatic voltage drop in 700mAh 4.8v NiMh pack?|
Also for some time the NiCd batteries were centre tapped (4 wires to the servo), and only 2 cells were used to move a servo, the "other" 2 moved it in the opposite direction. Many servos also used a 5 ohm motor, so with only 2 cells driving it you could not draw more than 0.5Amp (from half the battery) in any one servo.
|Thread: Horus and Taranis X9D Express differences?|
To keep development costs down, FrSky were able to purchase the case moulds for use by the Taranis from another company (that was not JR). They didn't therefore copy the JR.
The operating system was not copied from Multiplex. It is an open source development, started by someone in Germany and written for the "9X" radios (initially called TH9X firmware). This was further developed for the 9X radios as er9x firmware. er9x was also forked as open9x somewhat later.
An arm processor based board was then developed for the 9X radios (SKY board) and I ported er9x to this (ersky9x firmware), open9x was also ported to this.
Then FrSky started the development of the Taranis, and provided the small number of developers with prototype transmitters and we ported both to the Taranis (I wrote most of the low level drivers for both).
The Taranis doesn't just have a single "operating system", it has TWO. Some of the recent transmitters (XLite for example) are supplied with a choice of operating system, openTx or erskyTx (as it is now called).
You might try erskyTx as many users have reported the user interface is better than openTx.
|Thread: RCV engines|
The first RCV engines were made in the UK, I saw parts being made when I visited the factory. When they were developing a larger engine with spark ignition, I designed and programmed an electronic ignition controller for them. I also taught maths to the inventor!
|Thread: Horus and Taranis X9D Express differences?|
The X10S also has a 6-position switch and two extra trim switches as standard.
|Thread: Toying with selling up|
Have a look at my post in this thread: **LINK**
Quite possible to use a motorbike and go flying!
Edited By Mike Blandford on 13/05/2020 10:23:43
|Thread: VE Day Tribute|
I had these on our drive today while having a street party at a distance. Several passers by stopped then grabbed their 'phone and took a picture.
|Thread: Lockdown Models|
It will be electric, I haven't chosen the motor yet.
I started this many (tens of) years ago, an own design Sopwith Camel. This was before I had enough money to do it properly. This is a rebuild, about 70% is new. Some time ago I was helping at a local school young engineers club and managed to get a set of ribs and riblets laser cut for it. The cowling is from fibreglass, rather more resin than glass, and is heavy, but I doubt that will matter as it will just be part of the needed nose weight.
|Thread: Your standard insatallation of FRSKY equipment|
Perhaps don't believe everything you see on videos!
The "lockout/uncommanded servo movement bug" in V1 firmware has been proven (I've done it myself!), so the firmware needed to change. Due to the nature of the bug, the protocol HAD to change in a way that makes V2.1 not compatible with V1. FrSky did put in some other changes that maybe were not necessary, but at least one of those changes was removed before the firmware was released.
Why should any manufacturer be concerned about "third party" compatibility. The third parties haven't paid anything! In any case, the multiprotocol firmware was already updated to use V2.1 before V2.1 was released. That wasn't made "public" in case anything changed before release (as one thing did). The multiprotocol does support V2.1 protocol.
I also have firmware available that runs on "D8" receivers and supports D16 protocol. This also supports V2.1 protocol (autodetected at bind time).
Want the latest issue of RCM&E? Use our magazine locator link to find your nearest stockist!