Jump to content

Mike Blandford

Members
  • Posts

    939
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Mike Blandford

  1. I just did a test using a FrSky stabilising Rx. 1. Mount the stabiliser at right angles to the expected orientation. This swaps the aileron and elevator gyro controls. 2. Configure the stabiliser in v-tail mode. 3. Connect the rudder servo to the rudder output and the elevator servo to the aileron output. 4. On the Tx send the elevator control to the aileron channel. Check the operation of the rudder servo, it should move to correct yaw and move to provide rudder movement towards the higher wing when rolling, so "corrects" for both yaw and roll! If the servo corrects for one, but moves in the wrong direction for the other, then put the rudder servo on the elevator output. You may need to configure the stabiliser to reverse the servo operation (if the servo now moves in the wrong direction for both). If the stabiliser has the ability to adjust the gain for individual corrections, then you may have different amounts of corrective movement caused by yaw and roll. Mike
  2. Please answer questions 3 and 4 from my previous post. If you don't do the "self check" you will not have "taught" the receiver how far the servos are allowed to move. This could explain the elevator only moving one way. If you don't set channel 5 and channel 6 to AUX, then these will act as second aileron and elevator outputs. Mike
  3. On my S6R, inside there is a pad labelled P6. This has the SBUS signal from the processor. However, when used, the SBUS signal is inverted, so to use SBUS on the S6R you will need to provide an external inverter, even if you configure the SBUS to be a seventh servo signal. You also have the option of using the SPort signal as FBUS. Provided any sensors you use support FBUS (e.g. ADV sensors), you also get all 16 servo channels. I'm not sure, but I believe the openXsensor project provides servo signals when operating in FBUS mode, as well as providing sensor data. Mike
  4. I think there might be a place on the PCB of the S6R where you may connect a wire to get SBUS. I do generate the SBUS signal. My only S6R is in a model, I'll need to pull it out and have a look! Mike
  5. 1. No, Using the UNI-SXR script does the required calibration, auto-level position and the servo limit settings, nothing else needed for those. 2. A long press of "EXIT" should end the scripts. Mike
  6. The file "UNISXR.pdf" I referred to above details how to handle the calibration with UNI firmware, it does NOT use the same method as FrSky, but is actually much simpler. You perform the calibration, mounting configuration and servo limit settings all in a quick and simple process using a LUA script on the Tx. I do the gain settings etc. from the LUA script normally used o the Tx. I have trouble with the Freelink software, it falls foul of my antivirus! I'll check if I can make that work. Mike
  7. We need some more information. 1. Have you successfully used S6R or S8R receivers before? 2. Have you recently updated the firmware on the receivers? 3. Have you carried out the "Self Check" procedure on each receiver. 4. Have you set all the parameters available, e.g. gains, setting ch5 and 6 to AUX? 5. What Tx and firmware are you using? Mike
  8. Yes! Specifically, you will need to do the levelling process AND re-enter all the enable, Aux and gain settings. Check the file UNISXR.pdf in the second post of the linked thread. It is worth noting the existing settings before flashing (if you haven't already flashed it!). Mike
  9. UNI, ACCST firmware also provides VFR, and is available for the G-RX8. In the case of UNI, the VFR value sent provides the number of valid frames received out of the last 100 frame times. It is a "rolling" value (as a new frame is due, the value for 100 frames earlier is discarded) so is always up to date. With ACCST the frame time is 9mS (7mS for ACCESS). I don't know what method FrSky use to calculate their VFR value. RSSI is sent every other frame, so if a few frames are missed together, you may get a RSSI warning. VFR would only drop by the few missed frames. Depending on your Tx and firmware, you may be able to display the VFR value when in range check mode (or set up a voice output to report it). This would enable you to compare RSSI and VFR while doing a range check. When testing UNI (by several people), it was felt that VFR was OK down to around 60%. Both RSSI and VFR are useful. If you are close to losing signal, then RSSI will frequently be low, even though VFR is still quite high. If VFR is frequently low, then you are probably suffering from interference or the Rx antennae are masked. On a recent flight (with UNI on a S8R) I heard one RSSI warning, the log file (1 second intervals) shows RSSI was under 50 for 4 seconds. During this time VFR didn't drop below 87, and was above 96 for almost all the flight. On two other flights the same day, with the same model, one never had a VFR below 95 and the other had just two values below 96 (89 and 91). While the logging was only at 1 seconds intervals, 100 frames at 9mS spacing is 0.9 seconds so low values of VFR won't have missed being logged. Mike
  10. My Archer plus R10+ binds to an MPM (FrSkyX2) without any problems. In general Archer plus receivers do bind to the MPM as long as the MPM firmware is sufficiently recent (I fixed a bug in the MPM a while ago). I just checked using 1.3.3.33 on the MPM. Mike
  11. An aeroplane is flying at 40kts into a 40kt headwind and is 1 foot off the ground (a runway). What is its kinetic energy? The aircraft now lands so it is on the ground, stationary, facing into the 40kt wind, what is its kinetic energy now? Mike
  12. Kinetic energy is calculated using the ground speed. It doesn't matter whether the moving object is on the ground or flying. If the mass is the same and the ground speed is the same then the kinetic energy is the same. An aircraft moving at a constant airspeed through air moving at some, non zero, speed WILL have more kinetic energy when travelling downwind than when travelling into wind. If an aircraft changes direction from into wind to down wind it WILL have to gain kinetic energy and if it changes from down wind to be into wind it WILL have to lose kinetic energy. Mike
  13. I don't believe you may discount kinetic energy changes when turning. When flying downwind and aeroplane does have more kinetic energy than when flying into wind (even if the airspeed is less than the wind speed. You cannot have negative kinetic energy as the expression for it involves a velocity squared term. The answer to my simple question above is as the airspeed is increased the lift generated increases so the aircraft increases in height. Mike
  14. OK, simple question: An aircraft is flying straight and level at a constant speed and angle of attack. With no other changes, the airspeed is increased, what happens? Mike
  15. Sorry but the inside of the Galaxy is a somewhat different problem. The kinetic energy of the model is based on the velocity. The model velocity is the sum of the velocity of the Galaxy and the velocity of the model relative to the Galaxy. The relative velocity is positive when the model is flying towards the nose and negative when flying towards the tail. As it turns the model's kinetic energy will reduce. The question is where does the "lost" kinetic energy go? Mike
  16. An aeroplane travelling downwind has a certain amount of kinetic energy, which is related to ground speed. On turning into wind the ground speed becomes reduced, so the kinetic energy is also reduced. The "lost" kinetic energy needs to go somewhere and gets turned into potential energy, appearing as an increase in height. Mike
  17. That description almost certainly pre-dates the existence of UNI firmware. Only UNI firmware does tuning at the Rx end. If using UNI, use the method I described above. Mike
  18. The crystals used by FrSky for the RF devices on both Tx modules and receivers have a tight tolerance. As a result they always work well together. There is some slight variation, and UNI firmware on the Rx does tune the frequency used on the Rx to match the Tx to get the absolute best performance. The frequency tolerance of the crystals used by RadioMaster (and others) on the multi module is much less tight, requiring the use of the tuning function on the Tx to bring them into alignment (I need a setting of -40 on one module and +40 on another!). In my opinion, multi modules (used with FrSky) should be tuned to match the frequency used by FrSky modules. This may be done by tuning to any FrSky receiver running FrSky firmware. The tuning should then be OK for all FrSky receivers. While UNI firmware will tune to multi modules that are a long way off tune, the module is then using hopping frequencies that are off from where they should be. If only UNI firmware receivers are available, bind to a receiver, use the UNI statistics script to find what the receiver has detected for the tuning, then set the tuning on the Tx to the negative of this value, then bind again and check the UNI tuning value is close to 0. UNI firmware also monitors the packet transmission rate from the Tx and synchronises with it. If the signal is lost for about 0.9 seconds, then failsafe is entered. With FrSky firmware, the Rx then enters a searching mode trying to find the signal again. This can take half a second or more. UNI firmware, being still in sync with the Tx, follows the hopping frequency sequence for another 4 seconds, so regains the signal quickly. After this time, synchronisation cannot be guaranteed so UNI also enters searching mode. Mike
  19. The heating of NiCd and NiMh batteries while charging is confused by the fact that the chemical reaction of NiCd while charging is endothermic (cools down) while that for NiMh is exothermic (heats up). Both will, of course, heat up once fully charged if a charging current is still present. Mike
  20. The processor chip that is used in some receivers (by FrSky now and, I believe, Spektrum now) is specified to operate down to 1.9V (RF section, actual processor 1.8V). Add on whatever the LDO voltage is (likely less than 0.5V) and the Rx should continue operating down to less than 2.5V. As a receiver, it will only take a small current, but if sending telemetry the current draw will be higher, up to 100mA. Mike
  21. In the second post of the thread from where you downloaded the UNI firmware, there is a file "Universal ACCST Guide.pdf". This included the details of how to activate the Rx. Mike
  22. I suggest the following. Flash the Rx with UNI firmware. The file is here: https://forum.alofthobbies.com/index.php?threads/uni-receiver-firmware-release-files-universal-accst-d16.3270/ There is a guide to using UNI firmware in the second post on that thread. Download the file UNI_all_V83sm.zip, extract the file UNI_x8r_83sm.frk, and flash this to the Rx. Don't worry about activating it yet, the first thing to do is bind the Rx. With the Tx powered off, power on the Rx with the bind button pressed. The green LED should be off and the red LED on, blinking off briefly every half a second. If this is not happening, check if the red LED is flashing slowly (green still off). If it is, then the Rx didn't detect the bind button so try again. If you do get the red LED blinking off, power the Tx on and enter bind mode. Have the Tx about 3 feet away from the Rx. The red LED on the Rx should stop blinking (UNI then carries out a tuning process), and after a while the green LED will come on (UNI is then binding) and finally the red LED will go off and the green LED will flash slowly indicating binding is complete. If that all works we will go through the activation operation. Mike
  23. If bought in the UK/Europe, the Tx will be in EU/LBT mode, so you would need the LBT (not FCC) firmware for the X8R. Alternatively, put UNI firmware on the X8R and it will automatically detect the required protocol when binding. Mike
  24. The FrSky X20 supports ACCST (V2) so will bind to a G-RX6 provided the Rx is flashed either with V2 firmware or with UNI firmware. The G-RX6 also has ACCESS firmware available so may be flashed with that and then be compatible with the X20 using ACCESS. Mike
  25. From the manual: "How to Disable/Enable altimeter function a) The factory default setting is “enabled”. b) In case you want to disable altimeter functionality bring the receiver into normal operational mode, hold the F/S button > 5 s, the BLUE LED will flash 3 times, indicating the switch was successful and the function will be disabled. (If you want to enable the function, just repeat steps)." So worth checking the vario is enabled. If the 6-way socket is not present, then the Rx should have come with a loose socket for you to fit yourself. I remember one of my FrSky receivers arriving like that, I just soldered the socket on. Only needed if you need one, or more, of the functions available on the socket (SPort, Analog voltage in, SBUS in and SBUS out). Mike
×
×
  • Create New...