I'm using a Jeti Duplex R3/RSW .
Connected via EX bus.
Don't know what Scott is using.
Gov 1.3.1 Goblin 700 Gasser
Weather here is getting colder and days shorter so opportunity to fly has been limited, however got out yesterday for three flights. Gov performance observation:
transition from normal to IU1 rpms from telemetry readings 1795, fly around some and they jump to 1955
Switch to IU2 and no change
Switch to IU1 and no change
Leave in IU1 and fly, up to 500 rpm swing, evidenced by a flying buddy reading off the telemetry on the screen.
After I landed I redid the max throttle set up. Disabled gov, arbitrarily increased throttle end point in transmitter by 10 points, adjusted max setting in the gov tab to max full throttle position on carb, re-enabled gov - went and flew.
Observation: no change in gov performance from previous flight.
Third flight observation: no change from second flight, gov races to full speed, and IU settings make no difference, still the rpms vary significantly
Take off rpms are low, evidence by the gov no kicking in, IU1 setting is about 1600 rpms, IU2 is 1800 rpm.
Won't be able to fly again until this weekend, hoping the warm air stays around. Thinking of upgrading to 1.3.2 and redo the set up and test. Hopefully that will have an impact.
Scott
transition from normal to IU1 rpms from telemetry readings 1795, fly around some and they jump to 1955
Switch to IU2 and no change
Switch to IU1 and no change
Leave in IU1 and fly, up to 500 rpm swing, evidenced by a flying buddy reading off the telemetry on the screen.
After I landed I redid the max throttle set up. Disabled gov, arbitrarily increased throttle end point in transmitter by 10 points, adjusted max setting in the gov tab to max full throttle position on carb, re-enabled gov - went and flew.
Observation: no change in gov performance from previous flight.
Third flight observation: no change from second flight, gov races to full speed, and IU settings make no difference, still the rpms vary significantly
Take off rpms are low, evidence by the gov no kicking in, IU1 setting is about 1600 rpms, IU2 is 1800 rpm.
Won't be able to fly again until this weekend, hoping the warm air stays around. Thinking of upgrading to 1.3.2 and redo the set up and test. Hopefully that will have an impact.
Scott
Thank you for the info.
It is little bit hard to understand your description but if I am not wrong, you observe higher RPM then requested.
So when switching from lower to faster RPM or immediately after spool up, RPM is always higher.
You do not have to redo any settings after update to 1.3.2. I recommend to change RPM Sensor Filter in the Expert settings. This should decrease delay from Sensor and governor should not exceed Requested RPM.
It is little bit hard to understand your description but if I am not wrong, you observe higher RPM then requested.
So when switching from lower to faster RPM or immediately after spool up, RPM is always higher.
You do not have to redo any settings after update to 1.3.2. I recommend to change RPM Sensor Filter in the Expert settings. This should decrease delay from Sensor and governor should not exceed Requested RPM.
Spirit System developer
Yesterday I was able to fit in one flight before I got called away. Updated to 1.3.2 and despite ZeX suggesting I did not need to redo my set up, I decided to start from scratch. Redid my end points (didn't need to they were right already, redid the max/min settings in the gov tab. Power to 5, holding to 3. Throttle curves to give me 1600 and 1800 rpms. (confirmed that my settings were as I had designed them in the gov tab). Reduced the rpm sensor filter as suggested to 5, did not do anything, then to 4, that gave me success with both IU settings and the correct rpms as read from telemetry. The rpms varied in each IU by 3-4 hundred and I didn't have any more time to change settings.
Today I was able to fit in three flights. Prior to the first flight I changed the holding power to 5 and away I went. IU1 seemed right, but IU2 went to full throttle. Landed and changed gov holding back to 3 and got the same result. Then tried to lower the rpm sensor filter to 3 and IU 1 was fine, IU2 went to full speed. I didn't bother trying anything else. Kind of tired of trying things. If winter wasn't upon us here in New Hampshire I'd be changing to a GV1 cause it just works. As it is I'm maybe going to get a few flights in next weekend and probably not again until spring.
I'm hoping ZeX you don't give up developing the gov and you have a chance to refine this further, but as it is it doesn't work for me. I certain do appreciate your efforts to make it better and look forward to the day that it "just plain works" but today is not that day.
Today I was able to fit in three flights. Prior to the first flight I changed the holding power to 5 and away I went. IU1 seemed right, but IU2 went to full throttle. Landed and changed gov holding back to 3 and got the same result. Then tried to lower the rpm sensor filter to 3 and IU 1 was fine, IU2 went to full speed. I didn't bother trying anything else. Kind of tired of trying things. If winter wasn't upon us here in New Hampshire I'd be changing to a GV1 cause it just works. As it is I'm maybe going to get a few flights in next weekend and probably not again until spring.
I'm hoping ZeX you don't give up developing the gov and you have a chance to refine this further, but as it is it doesn't work for me. I certain do appreciate your efforts to make it better and look forward to the day that it "just plain works" but today is not that day.
Thank you for the info.
In version 1.3.1 there was pre-configured sensor filter to the value of 7. So what may help you is higher value than that.
All in all I believe that the only problem is in bad readings, as soon as it will be stable, it will work well. So it is not related directly with governor - but governor will never work correctly when there are missing RPM data.
So hopefully value of 8 will help. If not, then decreasing distance between sensor and magnets may help.
Alternatively it could be caused by high voltage noise.
In version 1.3.1 there was pre-configured sensor filter to the value of 7. So what may help you is higher value than that.
All in all I believe that the only problem is in bad readings, as soon as it will be stable, it will work well. So it is not related directly with governor - but governor will never work correctly when there are missing RPM data.
So hopefully value of 8 will help. If not, then decreasing distance between sensor and magnets may help.
Alternatively it could be caused by high voltage noise.
Spirit System developer
It is possible to measure the signal with osciloscope.
The easiest thing that can be done is to check if there is no connection between motor and high voltage source by multimeter. Sometimes spark plug is by mistake connected with the motor frame.
The easiest thing that can be done is to check if there is no connection between motor and high voltage source by multimeter. Sometimes spark plug is by mistake connected with the motor frame.
Spirit System developer