Jump to content
Please be aware of scammers when using the Sale/Wanted forum areas

Mike Blandford

Members
 View Profile  See their activity

  • Posts

    949

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by Mike Blandford

  1. Mike Blandford
    Not set - as it says, and should show a warning. Hold - Sent by the Tx every 9 seconds, Rx outputs hold thei last position Custom - Sent by the Tx every 9 seconds, Rx outputs go to the values programmed in the Tx No pulses - Sent by the Tx every 9 seconds, Rx outputs are stopped Receiver- Tx doesn't send any failsafe settings, Rx outputs go to position as set using the Rx button (if set). Note that if you use a S8R or S6R (stabilising) receiver, you cannot use the receiver option as pressing the button causes the Rx to enter "Self check" mode. Mike.
  2. Mike Blandford
    If you created the EEPROM on companion , then flashed it to the radio, you will have overwritten the stick calibration. Try calibrating the sticks. Mike.
  3. Mike Blandford
    I note several references to using ohm's law regarding servos, as though they a simple resistances. As they have motors in them, they are inductive, as well as being motors. The inductance means as soon as a voltage is applied to the motor it immediately generates an opposing voltage, which then decays over time, allowing the current to increase. In adition, as soon as the motor starts to rotate, it acts as a dynamo and also generates a voltage that opposes the applied voltage. The mechanical power out from the motor is this "dynamo" voltage multiplied by the current flowing (less any mechanical losses). These mean that the actual servo response is very complicated. Mike.
  4. Mike Blandford
    I think you will find the FrSky thermistors are 100K. What you can try is to get some 100K ones, physically like the 10K ones you are using. Connect them to the FrSky sensor, then test the response in boiling water and freezing water, making sure the water doesn't come into contact with any wires on the thermistors. If you get readings of 100 deg and 0 deg, then you can use them OK. Freezing water is water with Ice cubes in it, but making sure the thermistor isn't touching the ice itself as that will be below 0 deg. I think it doubtful a PICAXE can drive the Smart Port directly. The arduino in the openXsensor has to use "bit-bashing" at 57600 baud on a bi-directional signal for the Smart Port (I wrote that part of the code!). Mike.
  5. Mike Blandford
    Posted by Trevor Crook on 20/06/2017 12:34:55: I thought that FrSky had receiver matching, but will it perform a matching check if you are using a DSM2/X module and a corresponding rx? I suspect it can't, . . . Depends on the DSM module you use. If you use a "hack" module, or a Multi-protocol module (or an Orange module re-flashed to the Multi protocol), then the Model matching on DSM is supported by both ersky9x firmware and openTx firmware on FrSky transmitters. If you use a module that uses a PPM signal, then it won't support model matching. Note that you may use FrSky transmitters with ersky9x firmware which offers, in my opinion, an easier to follow user interface. Mike.
  6. Mike Blandford
    Manuals for the 9XR-PRO are here: **LINK** Latest releases of ersky9x and eepskye are here: **LINK** I suggest you install eepskye on your PC, then start the radio i "bootloader mode", and you will be able to backup your existing firmware and EEPROM so you can revert if you feel you need to. Mike.
  7. Mike Blandford
    Well try my suggestion. I tested it before I posted it, although I do have the latest firmware running (test version of r221!). If that doesn't work, come back and I'll offer some more suggestions (I may need to load r204 to test them!). Do you have eepskye loaded on you computer so you can easily read/wirte the EEPROM and update the firmware? Mike (Developer of ersky9x firmware).   Edited By Mike Blandford on 07/06/2017 18:41:01
  8. Mike Blandford
    I have a Blackhorse Mosquito, which was difficult to steer on the ground (grass). I've set up differential throttle control by mixing rudder control with the two throttle outputs. With that, it will now turn while keeping one wheel stationary. I have this as an option enabled by a switch. Mike.
  9. Mike Blandford
    Set up a logical switch: SW3: v>val THR -98 then set Trigger to ON and TriggerB to SW3m The timer will start when you advance the throttle, but will continue running when you bring the throttle off. Advancing the throttle again will then stop the timer (SW3m toggles the timer state whenever it becomes ON). Revision 204 firmware (which I think the Tx came with) is around 3 years old. You might consider updating to the latest (220). See here: **LINK** for a summary of the changes. Mike.
  10. Mike Blandford
    As I said above, the facility to send/receive data "over the air" using SPort telemetry packets was only added in 2.2. So, while LUA is available in 2.1.9, the S6R LUA script will only work with 2.2 (or later!). Mike.
  11. Mike Blandford
    LUA scripts are available in openTx before 2.2, but certain specific support, like sending/receiving SPort telemetry data, was not introduced until 2.2. In passing, I've just added LUA support to ersky9x firmware. Mike.
  12. Mike Blandford
    To avoid CH12 accidently triggering the self check, the current requirement is CH12 changes 3 times away from and back to the centre position within 3 seconds. OpenTx V2.2 has now been released. Ersky9x firmware also supports configuring the S6R from the transmitter. Mike.
  13. Mike Blandford
    Make absolutely sure you have channel 9 (master gain) set correctly. If channel 9 is sending the centre position, then the gain is ZERO and stabilisation doesn't do anything. Mike.
  14. Mike Blandford
    I mentioned this before, but the range you get (in range check or normal mode) depends on the height of both the Tx and the Rx above the ground. If you do a range check with the model on the ground (say Rx antenna 6" off the ground) you will get a certain distance. Put the model on, say, a flight box with the Rx antenna now 12" off the ground, you will likely get 40% more range. The same applies to the Tx height. Mike.
  15. Mike Blandford
    But Hobbyking are simply selling this, they don't manufacture it. I got one in July 2016 from bangood, who also are just selling it, not making it. So, in your opinion, is a: Futaba 14SG 14-Channel 2.4GHz Computer Radio System 2.4GHz FASSTest (Set) (Mode 2) costing several hundred pounds "Cheap and nasty" because Hobbyking are selling it? Please read the thread on RCG (with over 9000 posts) to which I linked on the second post of this thread to understand what this module is all about, and how well, or otherwise, it performs. Mike.
  16. Mike Blandford
    I use a 3-position switch to select normal, stab or auto-level modes. My settings for channels 10 and 11 are: CH10: +100% MAX !SC^ CH11: +100% MAX SCv With the switch up, I have normal mode, in the centre I have stab mode and down is auto-level mode. Being able to adjust the settings direct from the Tx, at the field, is very useful. I needed to reduce the rudder gain in stab mode last time I was flying, very easy to do (I'm using ersky9x on the Tx and this includes the facility). There should be no problems using channels 10 and 11 in this way, the outputs to the Rx should be perfectly stable. Mike.   Edited By Mike Blandford on 24/05/2017 23:41:09
  17. Mike Blandford
    Frank: I mentioned "serial mode". This mode uses a serial protocol between the Tx firmware and the module, NOT PPM. Ersky9x reads the sticks/switches and calculates the servo positions over 250 times per second, typically 500 times per second, so every 2 to 4 mS. OpenTx does this a couple of milliseconds before sending the data to the module. In both cases the servo positions are sent to the module every 7mS, in digial form. No significant conversion is needed to change these to the values needed by the RF protocol in use. The RF protocol operates at whatever rate is "standard" for the protocol in use, e.g. FrSky is 9mS, DSM2 is 22mS, DSMX is 22 or 11mS and so on. So, the latency, in this mode, is quite short. This module supports at least 29 basic protocols, may of which have several sub-protocols. It has 2 modes of operation, serial mode (as I describe above) where the selector switch is set to the '0' position, and PPM mode where you may select one of 15 possible protocol/sub-protocol options. Unless your Tx doesn't support serial mode, then you should normally use serial mode to get both the best performance and the option of selecting all the protocols that fit in the flash space. Guvnor: What do you base your opinion on? Mike.
  18. Mike Blandford
    The following transmitters work with this: Flysky/Turnigy 9X running er9x. Flysky/Turnigy 9X upgraded with 9Xtreme board running ersky9x. Flysky/Turnigy 9X upgraded with AR9X (or SKY) board running either ersky9x or openTx. Turnigy 9XR-PRO. FrSky Taranis/TaranisPlus/QX7/X9E/Horus running either ersky9x or openTx. Bangood offer a case for it. I have mounted one in a FrSky DJT case (obtained from T9HobbySport). If you look at the third picture on the web page, you will see it comes with an antenna. The latency is no worse than the transmitters it replaces. It uses the same "over the air" protocol, so matches the performance, and, in serial mode, the servo data is updated every 7mS. As long as you do a proper range check before flying anything, there is no reason to doubt it would be OK with larger models. Mike.
  19. Mike Blandford
    This is an "open source" project, read about it here: **LINK**. That module has been available from bangood for some time. Note that it is based on an Atmel AVR processor and not all possible protocols can be included at the same time. There is a version that uses a STM processor, with more flash memory, that does support all possible protocols. When used in serial mode, these are supported by the open source firmware for transmitters (ersky9x/er9x and openTx). To be able to use these fully, you will likely need to update the firmware on the module. This will need you to install the Arduino development software, download the source code and build the required firmware, then flash it to the module. Initially, this will require a programmer (USBASP or similar) and the addition of a programming header to the module. Should you then flash a (specific) bootloader, and use ersky9x firmware on your Tx, you would be able to flash the module "in situ" from the Tx. Mike.
  20. Mike Blandford
    Regarding a fabric finish, this depends on how much heavier it might be. I reckon every gram added to the tail is likely to mean 3-4 grams of nose weight being needed, so saving 10 grams at the back could easily mean the model being 50 grams (2 ounces) lighter. The tailplane, with elevators, currently weighs 37 grams and the fin/rudder is 19 grams. When I added the balsa block at the tail of the fuselage, I hollowed it out to save a bit of weight. I'm looking at all options to save weight at the tail. For example, do the 1/8th balsa sides need to be solid all the way to the tail, or would they stand for some lightening holes in them? Maybe it would only save a couple of grams, but with perhaps a couple saved by hollowing the block, I would get 4 grams saved, meaning 16 more saved in the nose. This all adds up to a tidy weight saving. Mike.
  21. Mike Blandford
    Well I've been (slowly) progressing my build, I have the basic fuselage put together, then I moved on to the tail. Hopefully, I'm keeping this light. I've kept to the "oversize" size. I started with the raw slabs, cut out the centre, fitted ribs and capstrips, and then capped the slabs outside the capstrips before sanding to profile. I'm using pin hinges. I may need to do a bit more sanding before I cover it all, but this is what it looks like so far: I intend to use iron on film, then a coat of "Prymol" then paint it! I shall, as usual, seal the balsa with a coat of (thinned) sanding sealer first as this provides a very good surface for the film to stick on. Mike.
  22. Mike Blandford

    Mike Blandford posted a gallery image in Member Albums

  23. Mike Blandford
    I thought I was missing something for the cockpit area (this venereed foam part). I found it inside the cowling in the box. Mike.
  24. Mike Blandford
    I thought that, but, if I understand correctly, the rear (non-veneered) foam deck butts up to a piece of foam that is veneered. If these pieces are mounted on the plain foam, they protrude outside the veneer of the piece in front. Mike.
  25. Mike Blandford
    What, exactly, does one do with the parts labelled "rear cockpit fairing" (the ply with the 'D' cutout)? From the plan, they look as though they should fit behind the veneered foam piece at the rear of the cockpit, but they would then fit outside the rear foam decking and stick out. Sholud they be inset into the rear foam decking? Mike.
×
×
  • Create New...