Jump to content

Philip Lewis 3

Members
  • Posts

    495
  • Joined

  • Last visited

Posts posted by Philip Lewis 3

  1. 1 hour ago, Neddy said:

    The FrSky Manual for my module is on the previous post it does mention setting failsafe. But seems to lack actual information about it.

     

    It tells you on pages 8 and 9 of the manual you uploaded, you almost certainly have the first version (ROM A):

     

    FAILSAFE: For those instances when the model flies out of range of the transmitter for more than a brief instant, the receiver provides a settable failsafe function on all servo channels. There are two implementations of this failsafe function. The ROM A version is shipped with all modules.

     

    ROM A version To use the failsafe function, follow the steps below. 1- Bind the receiver first (see binding section above). 2- Move the transmitter controls for all channels to the desired position whenever failsafe occurs. 3- Press briefly the F/S button of the receiver (less than 1 second), the transmitter module will make a long “beep”, indicating the failsafe position is stored in the receiver. These settings will be stored until the receiver is bound again to the transmitter.

     

    • ROM B version This version is provided as a user installed firmware upgrade. The firmware is available from the download section of the FrSky website. With this version you can set failsafe position on the Transmit module at any time during your flight. 1- Bind the receiver first (see binding section above). 8 DJT Manual Rev.0.12- Move the transmitter controls for all channels to the desired position whenever failsafe occurs. 3- Press briefly the F/S button of the Transmitter module (less than 1 second), the transmitter module will make a long “beep”, indicating the failsafe position is remembered by the receiver, even when flying. The same action can be achieved when the model is on the ground by pushing the F/S button on either the transmitter or the receiver. Ifyou wantto disable the failsafe function, with eitherROM version, re-bind the receiver to the transmitter. This will set the failsafe feature in the normal offstate. Note that ifyou accidentlypress the “F/S Range”button ofthe transmitter module during yourflight(with ROM B), you willupdate the failsafe positions inadvertently.

  2. Well I found two out of six, not a great hit rate really, as they are they will have ACCST V2 on them.

     

    £30.00 plus postage at cost for the pair if anyone wants them.

    2024-04-11 20.37.31.jpg

  3. They are all D8 receivers, you will need either D16 or Access to bind with a X18, there doesn't appear to be any D16 or Access firmwares available for these.  

  4. Failsafe is set in the receiver, normally by setting the sticks and switches to the failsafe positions you want then a quick press on the bind button and the receiver will acknowledge by flashing the LED lights, that's standard but can depend on what actual receiver you are using, look up the receiver manual on the FrSky website if unsure.

  5. I really need to take a look into this, in theory I've got at least 6 6XR or 8XR Rx's, a few R9 Slims and some 6 channel Access RX's none of which have been involved in a crash or ever damaged, question is where, if I can find them I'll put a post on here because since moving over to the TD line I'll certainly never use them again.  

  6. I completely flatten them with headlight bulbs, then I connect the two leads together to evidence that they are dead and then take them to my local recycling plant which has a battery section. 

    • Like 3
  7. Now you know and if you bookmark this thread you can look back at it if you decide to update to 1.5X although I believe a fix was put into place to ensure existing sound setups weren't broken when updating as too many people didn't understand how or what they needed to change.

  8. 1 hour ago, David Holland 2 said:

    Still no luck, chaps. Phillip, bearing in mind that I am an old bloke with limited computer skills and I'm using an iMac, could you please talk me through your post from yesterday in words of one syllable. I have, on the sd card, an en folder in which is a system folder containing the .wav files. I am not at all sure what the root audio folder is. Do I need to put the .wav files directly into the en folder, not within the system folder?

    Sorry to be a pain and I really appreciate your help.

     

    David

    They go straight into the Audio folder itself, so when you plug into the PC and open the SD card (or the PC does for you) then you see folders, Audio, Models, etc. Open Audio folder and they go straight in there, the Audio folder contain the en folder, your audio folder should look like my first post above at 13:34, in the audio folder you should currently see the en folder and a file called audio version.  

     

    The three files you see in my post leader etc are my custom sound files.

  9. On 1.4.17 any custom sound files (which these are) need to be in the Audio folder not in the en folder as shown in my first post above. If you have put them in the Audio/en folder or a folder within en then they won't be able to select them in the special functions menu.

     

    Ethos uses a system folder but I'm sure it doesn't use the sounds folder, if that is where the wav you want to use are then copy them out of the sound file and put them straight into the Audio file a level above the en folder.  

     

    You can also delete all the languages you don't need.

    • Like 1
  10. OK I can see some problems here for those who do update and think they have lost their voice files, below is what you will need to do if you choose to update.

     

    Whilst there were some initial problems with 1.5.0, 1,2 and 3 if using particular complex glider templates like Mike Shellim's but I believe they have been ironed out now with 1.5.4.

     

    I am currently flying on 1.5.4 and have no issues.

     

    You can for sure stay on 1.4.X with no problems but you'll miss out on some potentially new additions in 1.5.X such as:

     

    1. Trims to sub trims, takes your trim settings and puts them in the sub trim whilst re zeroing the trim
    2. Instant trim, fly straight and level on the sticks and hit the switch, the trim you were in with the sticks gets transferred to the sub trim, be careful with that one but could be useful with way out of trim models
    3. Perhaps potentially the most useful to the most, inbuilt set up of the stabilized receivers in the model wizard. 
    4. Different voices available (can't really see the point in that), now all voice files can go in the Audio/en/gb folder, you can also have an entirely separate folder if you want and call it what you want, in my case Caller because it's a sequence of maneuvers, see attached file structure, then in the system settings you select the folders you want it to use and you can have up to three, as in the other screenshot.

     

    Hope that helps someone out.  

     

    Capture.PNG

    screenshot-2024-04-01-46210.bmp

    • Like 1
  11. I assume we are talking user made audio files here rather than system files, they need to go in the root of the audio folder not in the en sounds folder, see attached. a very common mistake to have made.

     

    This will all change if/when you upgrade to 1.5.X so fee free to come back and ask again.

    Capture.PNG

    • Like 2
×
×
  • Create New...