Just that you know, I also split the RPM sensor to both Spirit an TM1n00, but the Spirit guys say it's not safe to split. FYI.Dawiev wrote:Subscribed with a lot of interest and concern .......... !
Planning to maiden a G700 with TRM 300 this weekend. Align sensor reading of the main gear and split to feed TM1000 and Spirit Pro.
Gov 1.3.1 Goblin 700 Gasser
Oxy 2 ♦ X-Vert ♦ Warp 360 ♦ Blade 450X ♦ Blade 450X Nightflyer ♦ Goblin 500 (RIP) ♦ 2 X mCPX v2 ♦ night fly mQX ♦ LadyMQX ♦ nano QX ♦ nano QX FPV ♦ Inductrix ♦ DX8 G1
Scott H: Don't worry, we are never out of options until the problem is solved.
Unfortunately we have to work very hard so my response is delayed.
If changing Sensor Divider makes no difference is readout, then there is definitively something wrong.
By changing the value your RPM must be changed, respectively divided.
So instead of previous approx. 2000, you have to get noticeable different real RPM (measured by RPM meter)
Unfortunately we have to work very hard so my response is delayed.
If changing Sensor Divider makes no difference is readout, then there is definitively something wrong.
By changing the value your RPM must be changed, respectively divided.
So instead of previous approx. 2000, you have to get noticeable different real RPM (measured by RPM meter)
Spirit System developer
Hi Zex,
Thanks for your response. I wish I could be an easier customer and have it just work, but it is not.
As I mentioned in posts prior to this, I decided to change to UDI and see if that made a difference. It did not. Still the rpm goes to very fast (I did not test it with an rpm meter). However, and maybe this is by design, but I do not get a readout on the Jeti display when I turn to Idle up 1 (which is what turns the gov on). I thought that the telemetry would still work.
I'm attaching both of my last flight logs to this email. Both show the gov being turned on several times that's because I switched it on and off several times).
Thanks
Thanks for your response. I wish I could be an easier customer and have it just work, but it is not.
As I mentioned in posts prior to this, I decided to change to UDI and see if that made a difference. It did not. Still the rpm goes to very fast (I did not test it with an rpm meter). However, and maybe this is by design, but I do not get a readout on the Jeti display when I turn to Idle up 1 (which is what turns the gov on). I thought that the telemetry would still work.
I'm attaching both of my last flight logs to this email. Both show the gov being turned on several times that's because I switched it on and off several times).
Thanks
- Attachments
-
- spirit-log-2015-10-26-170902 udi flight 2.pdf
- (594.42 KiB) Downloaded 109 times
-
- spirit-log-2015-10-26-165142 udi flight 1.pdf
- (913.37 KiB) Downloaded 95 times
Thank you for the logs.
Everything looks very good.
You can get telemetry from unit only with EX Bus, thus you will not see RPM with UDI. Behavior should be same with all receiver types.
Everything looks very good.
You can get telemetry from unit only with EX Bus, thus you will not see RPM with UDI. Behavior should be same with all receiver types.
Spirit System developer
It looks like there is only problem with the basic setup of the governor.
First from all you should check what do you see as Requested RPM - this value is determined by your throttle curve.
When you set flat 100% TC, you will get 2000 RPM, respectively value that is configured as Max. Head Speed.
So first you should check if you can see correct Requested RPM.
If it is OK, then you should make sure that your throttle servo travel range is configured so it can halt the motor and then that you can open it to the max. extent (But no more).
This is configured by Min. and Max. parameters.
When you disable the governor, you can check it easily in the way, that you will configure linear 0-100% (can be even 0-150%) TC in your transmitter.
When you will find correct Min./Max. values, then the governor will be able to reach correct RPM and use full range of the servo to control the motor.
Right now it looks like the throttle servo reached preconfigured Max. value, so it can't go higher to the Requested RPM.
So the problem is probably just in Min./Max. settings.
First from all you should check what do you see as Requested RPM - this value is determined by your throttle curve.
When you set flat 100% TC, you will get 2000 RPM, respectively value that is configured as Max. Head Speed.
So first you should check if you can see correct Requested RPM.
If it is OK, then you should make sure that your throttle servo travel range is configured so it can halt the motor and then that you can open it to the max. extent (But no more).
This is configured by Min. and Max. parameters.
When you disable the governor, you can check it easily in the way, that you will configure linear 0-100% (can be even 0-150%) TC in your transmitter.
When you will find correct Min./Max. values, then the governor will be able to reach correct RPM and use full range of the servo to control the motor.
Right now it looks like the throttle servo reached preconfigured Max. value, so it can't go higher to the Requested RPM.
So the problem is probably just in Min./Max. settings.
Spirit System developer
I'm a little vague about how the min/max and throttle end points should be adjusted. For example if I've adjusted the min/max endpoints already (like I've already done), turn off the gov and change my normal throttle curve to linear 0-100. Then mechanically the servo is in the wrong position. So, I adjusted the min and that worked fine, but when I adjusted the max, lowering it or raising it did nothing. It wasn't until I lowered it about 20 points did the servo move. That seems odd and maybe part of this out of range / misconfigured issue.
I don't understand the relationship between the three, (mechanical, throttle end points and min/max).
So, when I redo this (if I do it again) should I reset the min/max to some set of numbers and then get the mechanical throw dead on, and then the 0 - 100 via endpoint adjustment and then do the min/max?
I don't understand the relationship between the three, (mechanical, throttle end points and min/max).
So, when I redo this (if I do it again) should I reset the min/max to some set of numbers and then get the mechanical throw dead on, and then the 0 - 100 via endpoint adjustment and then do the min/max?
I've just redone my throttle as part of trying to sort out my problem.
I reset the min and max values back to default,unchecked the governor on box and saved the settings.
Mid position on the throttle trim and software at 0 low stick and 100 high.
For me I then had to move the ball out on the throttle servo to get the mechanical set up as close as possible to full throttle movement.
Governor then back on and min and max adjusted in the software to fine tune the throttle range.
I only had to increase each by a few points.
So as far as I can see this is absolutely spot on now - but it makes no difference to anything for me.
I reset the min and max values back to default,unchecked the governor on box and saved the settings.
Mid position on the throttle trim and software at 0 low stick and 100 high.
For me I then had to move the ball out on the throttle servo to get the mechanical set up as close as possible to full throttle movement.
Governor then back on and min and max adjusted in the software to fine tune the throttle range.
I only had to increase each by a few points.
So as far as I can see this is absolutely spot on now - but it makes no difference to anything for me.