Hi,
I have a brain 2 HD on a goblin 580 raw
ESC is Castle Creations 120HV, using 6s config on the heli
I am also using Radiomaster 16S Mkii, and have a native 4 in 1 module. I bound the unit with 2 Spektrum DSMX satellites
I updated the Brain2 ( and my PC app) to latest Software release for unit an app on first boot today
I have verified that the Brain2 bound correctly, as 3 cyclic and rudder servos are functioning as expected when unit is powered up
I have verified that my ESC throttle input cable is correctly plugged into channel 1 on the Brain, and not inverted, wrong pins, etc.
I have verified that I am not on throttle hold
I have verified that the channel monitor is outputting signal from radio perspective.
After the Brain 2 finishes initializing. the swash is responsive, but the ESC LED blinks continuously, indicating either non valid zero signal for off, or is getting no signal at all
In an attempt to verify anything is coning out of the brain2 on throttle, I hooked up a servo to channel 1 and it did not move - indicating to me that perhaps no signal is present on this channel - I also verified that servo worked (also tried disconnecting one of the functioning Cyclic servos and moved it into Channel 1) - both test failed to move servo
I have tried numerous throttle curves including 2 point linear (-100 to 100) - 0 to 100, ramp to 60% etc - nothing works
I have tried setting ESC into calibration mode by powering up heli with throttle stick full forward and also, nothing happens
I have tried moving throttle stick to various positions and leaving for 30+ seconds and nothing works
ESC is behaving as if n throttle signal is coming from Channel 1
I am out of ideas and lost - any help is appreciated
Joe
Hi jfinkel48,
From the configuration file you sent, we can see that in panel 12 of the Wizard you have activated Castle Creation's Live Link Telemetry decoding, which requires the signal sent to the ESC to have the polarity of the PWM signal reversed.
The PWM signal with reversed polarity is not able to control servos that require normal, non-reversed polarity of the PWM signal.
In order for the Live Link output signal with reversed polarity to control the ESC, the ESC must know that it will receive this type of signal and therefore the ESC must also be programmed to be able to operate with a Live Link signal that has reversed polarity. In addition, an adapter cable with pull-up resistor is required between the flight controller output and the ESC input of the throttle signal.
All this is explained on page 1 of the ‘Telemetry’ PDF manual, which you can download and view from the MANUALS section of the configuration app (alternatively, you can also download the same manual from the Downloads section of our website).
From the configuration file, we can also see that with the collective pitch stick at -102%, the throttle signal is at +3%.
Please note that all ESCs have a safety feature that prevents the ESC from activating until it ‘sees’ the throttle signal go to zero. You should therefore check the throttle channel range in the transmitter and make sure that it drops from 3% to 0%.
Hi,
Thank you for the detailed info - This helps considerably. Is there a glossary or guide to the parameters in the XML config file? - I looked at the file myself and noticed this line , <OtherParam Value="3%" Tag="Th" />
which I assumed is the 3% throttle at low pitch/throttle from the tag "Th"
understanding all of these parameters would be quite helpful to me, as I have 3 Ikons now
We are pleased to know that we were able to help you solve your problem.
As regards the contents of the configuration file, most of the data is not clear and directly interpretable because it is processed by the configuration interface software before being read and written from/to the flight control units.
By running the interface software in Demo Mode (no control unit connected) and loading the configuration file, the interface's random number generators will be stopped and the values of the parameters in the configuration file will be displayed in plain text by the interface. All parameters are explained in the interface using the side instructions or in ADVANCED using the balloons that open when you hover the mouse cursor over a configuration parameter.