I haven't used the Castle for a long time. I think that this may be what you want to know?  It was written for the V4.4, not the newer V.6, but should be similar in the ESC.  Try the Jeti ESC.

https://stunthanger.com/smf/gettin-all-amp'ed-up!/another-dog-another-'tric-fiorotti-v4-4-timer-with-accelerometer/

"V4.4 uses Castle Gov-Hi as noted.  The throttle screen for Gov-Hi shows optional “head speed” boxes.  The boxes are not used to govern in Gov-Hi, but if an RPM value is entered a corresponding needed pulse width is generated from the program.  If the RPM is too high or low, that will also be noted.  Motor Kv, direct drive/gearing, and battery voltage or cell count are also entered, so the user can know the system is in the correct range before mounting or flying.  Of course the method assumes that you have a system and know the RPM for your prop and line length.  The ESC program gives the needed pulse width to run the system at desired RPM and that pulse width can then be selected on the Jeti box.  The actual entry is a number from 0 – 400 and the selected number will correspond to a pulse width, also seen on the box.  From discussion with Castle, the method should be valid.  A datalog of a short run will confirm pulse width and RPM without use of a tachometer, though use of a tachometer is the alternative method for set up.  Two runs similarly done with say 10 or 20 “Jeti numbers” apart will allow calculation of the RPM change/Jeti number change making field RPM changes easy.  As an example a 12X6 APC used about 9800 RPM and the prop was changed to a Xoar 12X5.  I had recalled about 10,400 – 10,500 RPM, so added 20 numbers form 112 to 132 on the Jeti box and ended up going to 133 after one flight.  So about 600 RPM change for 30 RPM/Jeti number."

I have to try to decide what I meant since it has been a few years :-) 
As I recall, you don't need anything in the boxes ("The boxes are not used to govern in Gov-H").  If you put something in the boxes for rpm, the Castle program will tell you the pulse width to get that rpm.  The Jeti box can be set to that pulse width for the desired rpm.  You normally set a timer number, the the Jeti box also shows pulse width.  You will get a reasonable starting rpm from entering the rpm in the Castle program and then selecting that pulse, width at whatever number it takes on the timer.

Put the desired flight rpm in the first box and see the pulse width that it will show and use that pulse width as your starting set rpm in the timer. Then remove the number from the ESC after you get the information, as it doesn't use the number.  Or just leave the boxes blank and guess the starting rpm number in the timer.  I don't think anything happens if you leave a number in, but best to remove.

What is your nose up setting?  I actually prefer nose up off and let the sensitivity setting control acceleration and deceleration.

G-force is another method of adding acceleration and tends to add acceleration when overhead. 

My suggestion is to trim the plane with acceleration and deceleration functions off, then start with sensitivity, max and min.

This may be a better off line discussion.

One other thing I forgot to mention about the sensor.  It can be either sticky side up or down, so above or below the wing, but you have to select that in the Jeti box.  If nose up didn't work when nose up was on, perhaps you have the sensor setting, normal or reverse, incorrect.

Not Rogerio, but I believe that he used Graupner 3 blade for his profile and 4 cell.

https://www.gravesrc.com/graupner-3-blade-e-prop-10x5.html

I think available in either rotation, so be sure to check on what you order.  They can be difficult to find, I heard that Graupner changed hands or may have ceased.

Does anyone know the weight of the 3 blade  , 10" Graupner prop ? It's not a multi-rotor prop, right ?

I'm considering converting my Classic ship from a Passive to Active system. It currently runs on 4S with an E-Flight Power 15 with a C.C. Phoenix 45. Actually, quite a nice set-up, but it could be better.

Rogerio : In a PM to you, I mentioned this . My thoughts are to go with a 5Sor 6S(25C) 2200mAh- which no one outside of some obscure( read: here today, gone tomorrow) Chinese manufacturer has on eBay.

The Jeti Spin 44(non- Pro) and a lower KV motor were mentioned by me. You recommended going with a higher KV motor and sticking with 4S. That advice left me scratching my head 

Can you assure that a 4S battery, Power 15 motor and CC ESC will give OPTIMAL or at least EQUAL  performance  with your latest v.6 timer ?

Sorry with all due respects, but I'm somewhat doubtful.

Did some testing and I have to say this is the cats meow big time, I mounted the timer with velcro to isolate vibrations so I could use a two blade prop, I  didn't play with the Jeti box to much just to dial in lap times and was very easy to do, the break so to speak is quite noticeable very cool.  I'm very happy with how it performed and highly recommend it to anyone flying electric. 
 

Edit: Now that I think about it, maybe vibration isn't the reason a 3 blade is highly recommended,  Fred? Rogelio?

Sorry I messed this a couple of days ago.  Velcro may not transfer vibration, but does it firmly mount the sensor?  If the sensor lead moves in the wind, does it move the sensor.  If so, you will have problems.  You could get more stability without a hard mount by adding tape over the sensor lead from sensor to leading edge.  But be careful not to change sensor level, or re-level after you tape.

I mounted the sensor externally when I started, but it is not very satisfactory.  You can slot the profile fuse, or you can attach a plate at the fuse wing fillet area and leave it external but more attached.  Bundle the lead length and tape it on the wing so there is not a lot of extra length loose.

You may have seen this
https://stunthanger.com/smf/gettin-all-amp'ed-up!/old-dog-new-trics-old-plane-new-rogerio-fiorotti-timer/

Very timely post Fred, I didn't have  the sensor leveled properly, it is now.
This system is going in a new build and I wanted to learn all I could before mounting it permanently in a full fuse plane. Please I see you are using a 2 blade prop, in the instructions it strongly recommends a 3 blade, I'd really like to use a 2  blade as I already have the spinner.

3 blades may balance better, or you may be better able to balance then.  What is recommended is a light weight prop and total rotating mass.  Igor's 2 blade props are in the 15 - 18 gram range.  Xoar wood PJN/electric props for 2 blade 12x5.  Heavy rotating mass slows the speed change for acceleration or deceleration and will likely occur in the wrong place in a maneuver.  Light prop and light spinner for electrics recommended.  I learned the hard way, my own experience instead of others.  It seemed to work because the acceleration came on and off, but timing is very important and it wasn't right until the light prop and spinner.

What plane will it go into, and what battery and ESC?

Thanks Fred. The plane will be based on a Legacy 40, I'm shooting for around 44 .oz, motor is a E-Flite 15  CC 50 esc and 2700ma  4s batts right now using a apc 11X5.5  with a E-Flite spinner

Not Rogerio, but I believe that he used Graupner 3 blade for his profile and 4 cell.

https://www.gravesrc.com/graupner-3-blade-e-prop-10x5.html

I think available in either rotation, so be sure to check on what you order.  They can be difficult to find, I heard that Graupner changed hands or may have ceased.

International shipping to Canada $56.00. 

This thread has been very helpful but I always struggle understanding some of these settings especially going from the ver 4.4 to 6.3 timer. What I’m hoping to do is convey my understanding and get feedback to tell me if I have it right or where I went wrong. Since RPM is dependent on so many variables; voltage, motor, prop, etc., I would like to level set and discuss this only in terms of the pulse width and using the default settings listed in the 6.3 user guide:
RPM = 1.420 ms
Nose Up = 20 us
RPM Max = 1.500 ms
RPM Min = 1.240 ms
Sensitivity = 12
And let’s set GForce = Off  (because I still don’t fully understand what that does and how to use it.)

Given those settings
Condition 1
Normal level flight – The RPM will be whatever RPM that can be achieved with a 1.420 ms pulse width.

Condition 2
Nose pitches up to a vertical climb – Nose Up will increase the pulse width to 1.420ms + 20 us = 1.440 ms thus increasing RPM.
RPM Max will allow the pulse width to increase beyond 1.440 ms to 1.500ms further increasing the RPM. If RPM Max where to equal 0 then the pulse width would remain at 1.440ms during the climb. If RPM Max truly overrides Nose Up, why bother setting Nose Up?

Condition 3
Nose pitches down to a vertical dive – Nose Up parameter comes out of the equation. RPM Min will allow the pulse width to decrease to 1.240 ms thus reducing RPM. If the RPM Min where set to equal 0, then the pulse width would return to 1.420ms.

So does that theoretically correctly summarize how those functions operate?
Thank you,
Frank

My understanding follows.

Condition 1
Looks correct.

Condition 2
For nose up, the "us" settings are not added to the ms settings.  Microseconds are much smaller than milliseconds and would not contribute.  The settings given in "us" are levels, presumably of strength.  Similar to the increased numbers of V4 nose up.

RPM max and min are used for sensitivity and do not affect nose up function or G-force function.

Condition 3
Sounds correct.

Fred,
I was thinking about this a little more and perhaps the Nose Up value is a measure of how quickly the timer will apply the RPM Min and Max settings. Does that make sense?
Frank

Can you elaborate more on what you mean by ("us'' are levels, presumably of strength)? Since the ESC only responds to one input, the pulse width, how does the Nose Up function exert any influence on RPM if it's value isn't added? I know it's a very small value, and likely would add no noticeable RPM increase.

So how does RPM Min and Max relate to Sensitivity?

Microseconds, "us" are the units to go with the numeric values in nose up.  I'm not sure that the units are useful, maybe leftover from the algorithms.  I think of the numeric values as the strength of nose up response.  Part of the original question was comparing the settings of V4 to V6.  V4 used numbers for nose up without units.  Pointing the nose up beyond a specific set angle will cause acceleration, presumable by adding to the pulse width in milliseconds.  I don't think that nose up is activated until about 30°, probably so that it doesn't cause oscillation with every small angle change.

My non-engineer explanation.  I think of the main function of the system as being controlled by acceleration.  Sensitivity controls the response to acceleration changes. Pitch change will likely cause acceleration or deceleration so that even with "Nose up function" turned off acceleration would likely happen in response to pitch change.  On the other hand, with sensitivity off, nose up function will add acceleration because of the pitch angle.  The Max and Min functions regulate Sensitivity function only.  Turning sensitivity off should be similar to turning Max and Min to 0 and leaving Sensitivity off.  Part of the confusion may be that nose up is a direction to some users, but is also function name, actually renamed in V6 to "Climb RPM."

I hope that some of this makes sense.  Written while Rogerio was posting.