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: Blackhorse Hurricane 46|
For that to be true you also then need to use larger wires between the battery and the ESC and the ESC and the motor, probably bigger connectors (so they have a lower resistance), and an ESC rated at a higher current so it also has a lower resistance.
|Thread: FrSky Taranis - user chat|
I've put openTx on the Taranis plus (release 2.2.1) and repeated the latency measurements. Because openTx doesn't (currently) synchronise to the XJT heartbeat pulse, and, in 16 channel mode, only sends one frame to the XJT every 9 mS, there is quite a variation in the latency, slowly changing over time.
The shortest latency I found was 19.3 mS, jumping to 37.3 mS, and the longest I found was 53.9 mS jumping down to 36.1 mS. These are times from control input to servo pulse. With the longer times, sometimes the SBUS output does occur 9mS before the servo pulse, so the 53.9 mS was 44.9 mS to the SBUS output.
|Thread: Dead Lipo remedy?|
I'm just wondering, the OP said the pack registered nothing on a multimeter. I would have thought even a flattened battery would show some voltage rather than nothing, so perhaps the multimeter never connected to the battery properly. This would mean we don't know how low each cell dropped. It may be the battery wasn't actually too low in voltage, which might explain why it seems to have recovered.
|Thread: FrSky Taranis - user chat|
You probably won't notice the varying latency.
There are 3 parts to the latency:
1. This is random.
The varying latency is caused by 1. It is 0 to 9mS if the radio sends only 8 channels (or uses the "double rate" I describe), and is 0 to 18 mS if you send 16 channels normally.
In passing, going back to the 27/35 MHz days of sending PPM, the servo pulses were sent in "real time", so zero latency for items 2 and 3, but a varying latency for 1 of the frame time, from 0mS to, typically, 20 to 25 mS.
Using SBUS and either the "double rate" or 8 channels only mode minimises the latency so the variation is only 9mS. Note that if you use a SBUS decoder, it may also only output servo pulses every 18mS for analog servos, but may provide them every 9mS if you use digital servos.
I've been investigating latency on a Taranis (plus) to a X8R receiver. The results are posted here: **LINK**.
Note the last sentence!
|Thread: Dead Lipo remedy?|
Simon: What make of battery is it? Maybe it is a newer design that recovers better than older designs.
|Thread: Taranis to Spektrum Trainer.|
By using the method I posted above, (which was the only method at one time) all the required settings are in a model, so it is then possible to create a model in Companion and post it for the OP to just copy to the Taranis.
Using the trainer menu is useful as it replaces the normal stick values with those from the student radio before inputs and mixers are processed.
CH1: Ail weight(100%)
The first mix is the normal aileron mix, the second uses channel 2 (assuming TAER order this is aileron) from the student radio when the SH switch is active. I don't know for certain with openTx, but with ersky9x, this second mix will automatically become inactive if there is no valid trainer input.
Yes you may map the trainer input channels in any order you like. You also have a calibration setting so you set the trainer input centres and also you may scale the inputs. Spektrum tends to only use about 80% of the channel range the Taranis does, so you may wish to scale the inputs by a factor of 1.2 to match.
Only the first 4 trainer input channels are directly handled in the trainer setup, but the trainer inputs also appear as mix sources (TR1 to TR16). They were renamed recently from PPM1 to PPM16, but still appear (in Companion) named PPM1 to PPM4 in the trainer calibration.
You also need to use a special function to assign a switch to swap to using the trainer inputs. You also have the option to pass only some of the 4 main inputs, so the instructor could, for example, keep control of the throttle while passing the rudder, aileron and elevator to the student.
In passing, in ersky9x firmware I have 4 "trainer profiles" available, so if you do a lot of instruction you may have the trainer setup for 4 different student transmitters, and simply select the one you require.
|Thread: Throttle cut button - why the bad press?|
Which is why, on ersky9x firmware, I have a "Safety switch" menu where you just select the "Sticky" type and set the controlling switch and output value for the throttle channel, no complex programming.
I also use a throttle disable switch with electric, and have for many years. It is automatic for me to switch to the "safe" position before handling a model. Specifically, I use a "sticky" throttle disable, where, once disabled, it doesnt allow the throttle output to change from minimum unless the throttle stick is moved to minimum, so if the throttle stick gets knocked, and then the switch is changed to "enable", the motor still won't start.
I have this in ersky9x firmware as a simple "safety switch" selection, but it may also be implemented in openTx with some logical switches and special functions.
I'm curious regarding a club insisting that the battery is not connected until you are at the flight line, how do you deal with range checks when the radio needs the battery connected?
|Thread: Companion2.2 - Taranis X9D anomalies|
Check in the radio settings that LS and LR are set to "Slider with Detent" as opposed to "None".
|Thread: Who wants a Warbird Replics Hurricane?|
Making slow (by possibly steady) progress. I've bolted the wings on, the retratcs and flaps are complete, except for linking the outer flaps to the inner ones.
Rather than use the dihedral braces, I've opted to use fibreglass cloth and resin to join the outer wing panels to the centre section.
The outer flaps have a 3mm dia carbon tube at the front, with a 2mm carbon rod inside that extends beyond the flap to form the hinge.
|Thread: Battery problem|
I agree to not charging lipos unattended, but where are you getting information from regarding NiMhs?
Many devices have inbuilt NiMh cells that are on continuous trickle charge e.g. cordless 'phones. They don't say "don't charge overnight"!
A 2500mAh NiMh may be charged at 250mA for 24Hr, at 70mA they will be fine for months. From flat at 70mA they will take around 36 hours to fully charge.
Mistreating in what way?
Low current trickle charging is fine, and doesn't damage NiMh cells. For example, I just checked a datasheet for a 1100mAh AAA cell. This specifies you may charge at 45mA for a year continuously! As I mentioned above, only using a "smart" charger will lead to cell imbalance over time, so then you will need to do a trickle current charge to balance a pack.
What capacity are the batteries? As long as they are at least 700mAh, then a trickle charger of 70mA may be used. NiMh batteries will handle being charged at 1/10th 'C' for over 24 hours, indeed, this type of charging is needed to ensure all the cells are fully charged (balanced).
Even if a "smart" chrger is used most of the time, a trickle charge is needed occasionally to 'balance' the pack.
My NiMh batteries have lasted for many years without any problems.
|Thread: Turnigy 9X range issues?|
Is that the 9Xtreme board?
The original RF module should work fine still.
If you want to use the Orange module, you might consider updating the firmware on it to the version that uses the Multiprotocol, see this thread: **LINK**.
|Thread: S6R receivers|
Download the latest manual from here: **LINK**.
You have "Quick mode" available on new receivers (it is the default mode), and you also get it if you update the firmware on the receiver.
There is a new download of firmware for the S6R/S8R available, which a description of "Fix the Bug"!
I've found out that the change is to remove the flashing of the blue Led on power up when in "Quick mode". It seems the Rx didn't start operating while flashing the blue Led, so was slow to recover from a brownout when in "Quick mode".
|Thread: The 2018 Transmitter Survey!|
One thing that FrSky do is listen to users and developers. When they were developing the XJT module, I had PXX protocol firmware for the DJT module to test (back in 2011). When developing the Taranis, developers received prototype units. We gave quite a lot of feedback on the hardware design (which FrSky changed), including making sure even the original gimbals were good quality, as well as porting ersky9x/openTx to the radio.
Most of the time, if there are problems reported back they fix them and provide updated firmware (and even hardware mods) as a result.
Open source firmware developers are also provided with documentation (circuit diagrams, protocol specifications etc.), so are able to provide a level of support on these forums to end users.
After a number of problems with the S6R (stabilising receiver) firmware, I received a S8R from them to test before it became available for general purchase.
In the US, Aloft hobbies provide excellent support for FrSky equipment, which provides a significant level of "word of mouth" advertising.
Of course, since the Taranis uses open source firmware, the development cost was much lower, which is one reason the price point of the radio is lower than some competitors.
Want the latest issue of RCM&E? Use our magazine locator link to find your nearest stockist!