Maiden flight on newly setup Brain2 Hd on an older 700n. Everything seemed to be setup correctly. Went for some forward flight, on second banked turn seemed to loose connection to model. Regained control and landed. On the bench, it appeared to be related to the satellite wiring, as it would reset when moving those wires. Now I've removed my tail and throttle servos. With only the 3 8717 cyclic servos, gov sensor, 2- SPM9745 Spectrum satellites, direct 2S lipo and stick inputs i've captured a video of a full reset. Radio 9303, setup in the Brain2 DSM 2 2048/11ms. Both satellite wiring cables are brand new.Since the sateliite LED goes out completely, I could i be losing power completely?
As far as we know, JR radios only work properly with Spektrum satellites if binding is done according to the old 22ms DSM2 protocol.
NOTE: As also indicated in our instructions, the 22mS DSM2 Protocol has a low resolution (1024 bit) and a maximum of 7 channels handled.
However, make sure you have the latest firmware version of your radio in your transmitter.
Our units unlike other units on the market, also have a DIAGNOSTIC section specially designed and developed to help users understand what their problems may be caused by.
Loss of connection could be caused by voltage drops due to low battery, battery with C too low, faulty soldering, faulty connectors, too thin cables, slide switches inserted in series to the power supply, or by excessive absorption of servos that could be faulty or go into binding by sending the internal electric motors stalled. To check this, simply activate the "Servo Voltage" parameter in the flight logs (already active by default).
Or there may be problems with the received radio signal by Spektrum Satellites and this can be verified by activating the various QOS (Qality Of Signal) parameters for the Flight Logs: Sat1 Fades, Sat2 Fades, Frame Losses, Holds, Frame Rate (already active by default).
As far as Spektrum satellites are concerned, we would like to point out that when there are problems, 98% of the cases are due to Spektrum cables that are too small and thin and are hardly crimped correctly on the connectors supplied with the cables. To check this, simply move the cable near the connector connected to the control unit and then move the cable near the connector connected to the satellite. The remaining 2% of the problems occur when equivalent satellites (not spektrum) or clones of the original satellites are used (there are many of them around and they are detected by the use of locking screws with different heads.
If you have a JR transmitter you could also try to use a JR receiver with X-Bus output protocol (you must set the transmitter to "B" mode). Our control units also handle this type of protocol. Maybe you would have less problems.
I captured this log yesterday but can't tell what it is showing me is happening. I did think it was a bad wire/crimp on those connections as i thought i was just getting a satellite disconnect when i pushed on the connector at the control unit. however i was able to capture were the satellite just goes dark with no contact to the helicopter, just stick inputs. These are matched spectrum satellites. It is interesting that i can get the satellites to appear to bind in 11ms mode, I may just bind in 22ms mode and tie my setups to flight mode as if i only had a 7 channel radio. or just buy a new transmitter which will give me bi-directional communications as well.
In your actual channel configuration, you are using only 7 chennels:
1, 2, 3, 4, 6, 8, 9
So, you can use DSM2 22ms mode using channe 5 instead of channel 8 and channel 7 instead channel 9
Why you are using the same channel for Setup change and for CH2 output? You are using CH2 Output connector? For which purpose?
With your actual DSM2 11ms setup and the following QOS values after only 24,22 seconds, the radio communication is not working for sure. Try DSM2 at 22ms as suggested to see if you can have normal values (Hold = 0, Also Frame Losses with two sat must be at 0, and either Fades values must remain below 100):
Thank you for the explanation on the log analysis. When i change the binding to 22ms it changes my receiver configuration and i stopped fixing it as i was trying different receiver protocol/binding options. I dug up some older SPM9545 dsm2 only satellites. They work as expected and do not drop out and bind as 11ms (I would assume as i set it to dms 11ms and can configure Aux 3 as 8 and Aux 4 for 9). I took my SPM9745s and a AR7100 and bound that to the 9303 and it continued to drop out and act odd. So not sure why the 9745s don't like my 9303, going to explore that with Specktrum for closure. I will try to rebind at 22ms and see if i can make the changes you suggest to the channels and the device switch settings on the 9303 as well. I also retry to real time capture the same log for frame losses with both settings using the 9545's.
Okay.
We are sure that as other hundreds of users have already done, you will be able to correctly connect your transmitter to the SPM9745 satellites using them in 22ms mode or to the SPM9545 satellites.
Otherwise, as we have already suggested, use a JR receiver with X-Bus serial output by selecting the X-Bus protocol in Brain2 and connecting it to the CH3 connector of Brain2.