A new software update is available for the Climb_and_Dive Timer.  I just released v1.4 of the program code.  The  instructions have been revised to incorporate the latest developments, notably https://circuitflyer.com/Climb_and_Dive/docs/Advanced%20Modifications.html  Please have a look through them.

The Software page of the instructions https://circuitflyer.com/Climb_and_Dive/docs/Software.html has all the details of how to download the new code and update your timer.  It’s just a simple drag and drop.  This update is a little different as I added a new library file so you will need to drag and drop both the code.py and the whole lib folder onto your CIRCUITPY drive.  Remember to "Replace all" when asked, don't merge or keep both.

The most notable change is the ability to wire up an optional super bright NeoPixel LED.  The LED can be mounted through a 5mm hole in the side of full fuse airplanes.  It should be bright enough (except for the blue colour) to be seen from 60' away on a sunny day.  This is sort of an advanced feature and is only recommended if you are confident with your electronics skills.

Other new items:
- improved nose over protection.
- increase in the throttle setting for the start-up blip.  This was required or Castle Creations ESC's.
- decrease in the length of the start-up blip.  Reduced from the previous 1.5 seconds to just a quick 0.5 second pulse.
- For those that are comfortable personalising the code I moved a few variables up near the top for easier access.

Give this new version a try and let me know what you think.

Full details here:
https://circuitflyer.com/Climb_and_Dive/

The Climb and Dive timer can be ordered here:
https://www.tindie.com/products/circuitflyer/climb_and_dive-an-advanced-control-line-timer/

The diagram shows mounting location on a profile. I'd imagine a full fuse ship would be the same. So essentially, locating the device isn't as critical say as with an active timer ?

CF,
Does a new timer come with the latest program upgrades installed?

Best,  DennisT

Canadian Paul and Cheryl Emmerson visited me in Arizona last week and talked about updates to his Climb and Dive Timer. I don' want to let the cat out of the bag but the latest update will make it easy for contest flyers (and others) to fine tune their model's performance.  Stay tuned for more updates.

Randy

The default axis orientation (+Z, -X) is correct for the photo of the timer mounted on the side of the nose like that.  If you want to test for changes in the RPM from the accelerometer input you need to roll the airplane not point the nose up or down.    Check the ESC settings to make sure there is no soft-start or anything that could slow down the throttle response.  Changing the motor acceleration setting in the timer will only increase the amount of time that the motor takes to go from start-up (off) to the governed RPM at take-off.  When bench testing, sometimes a motor needs a bit of load to govern properly.  A smaller diameter or lower pitch prop should suffice without causing anything to overheat.

What motor, ESC and battery are you intending to use and have you successfully used that combination before?

I mount my timers with velcro.  The timer is designed to filter out higher frequency "noise" from vibration.  I don't recommend the older Castle ICE series of ESC's with the Climb_and_Dive timer.  I suggest replacing it with a lower cost BadAss ESC or equivalent.  If you insist on using the ICE try: Airplane Mode, Fixed Endpoints (you won't get the start-up throttle blip) and make sure the Throttle Response is cranked up to 10.

Switched to Badass ESC. Speed hunting cured. Startup sequence is back to normal. One small problem : about 1/2 the time I get no-start; maybe 20 revolutions then stops with the 2-red flash LED message (motor phase feedback signal missing). Connections/wires look good. What am I missing : is the motor start acceleration too fast/slow? My motor has only 8 poles; could this be confusing the startup logic?

Thanks for Your Help,

Steve Manganelli

It could be the 8 pole motor.  Unfortunately I don't have one on hand to test but I'll take a closer look at my math.  What are your program settings for RPM and Motor Acceleration?

Motor Acceleration=5, RPM = 9750. I increased RPM from 9650 when I last flew it and had false starts. Should I try Acceleration= 8 ? I'm not trying to self launch; I have patient helpers whom will wait until full throttle before letting go!

Thanks,

Steve Manganelli