What I have done so far:
I have gone through the binding process for the Flash 7 and Optima 7, and I am able to control servos on all channels using an Acro Model on the transmitter. I have used the configuration tool selecting the Vtail 4 and left most of the default settings alone. On the Receiver Protocol i have tried the SerialSumPPM- Rx Protocol with the Transmitter Model of both Hitec 1 and 2. After successfully flashing the QN, I have opened the WinGUI selected the proper COM Port, verified the BAUD Rate and Connected. I then Calibrated the Accelerometer and was able to read the values in the Sensor Graph. The Mag Calibration does not seem to be effective, probably an operator head-space issue.
Wiring:
Following the QN Quick-Start Guide, I wired the the controller to the receiver following the Guides convention and check the Optima 7 Manual to make sure wore orders were compatible. See Picture.
Issues:
I am unable to read Throttle, Pitch, or Yaw values from the WinGui Flight Deck. I have attempted to Arm the system by moving the left joystick down and left. No change. Other Telemetry data “seems” to be fine, other than the mag. The issue seems to revolve around the communication between the controller and the transmitter. The motors never spin. [NOTE: the only power source currently connected is through the micro USB, no battery is attached.]
As you will note in the picture, the Alarm is flashing on, then off for ~3 seconds, then back on, etc. This happens when connected via USB and also with just the battery connected. Perhaps this is not and issue at all.
If this has been addressed in the forum i apologize, I have not found it. Any assistance would be greatly appreciated!
In the FCT (Firmware Configuration Tool) you need to choose “StandardPCM” as the type of Rx Protocol.
This should solve your problem of Receiver signals.
Thanks for the help, I can now see the values in the WinGUI and the motors spin now. I’m glad it was something easy. As mentioned in the original post, I am still having issues with the Mag Calibration. I have followed the steps on the screen and read through the Wiki but without result. It seems straightforward but from my flight deck the values jump from approximately 350 deg to 60 deg. The ACC calibration is fine. Attached is a plot of the Sensor Graph. Is there a way to see if the magnetometer is defective as opposed to bad calibration? I can re post this under a different subject if that would be more appropriate.
Correct. Also, I verified that the yellow and green status lights were lit indicating that the QN was in calibration mode. I stopped the 360 deg rotations once the lights stopped blinking. I also tried one rotation in each axis then stopped rotation. Neither approach worked.
Yes, that how I conducted the calibration. This is also why I am questioning whether the Mag is defective; it can’t really be more simple.
In the FCT I have entered the Declination as 0 deg 10’ East for Jefferson City, MO and selected ‘Not Present’ for the GPS. Would this configuration effect the Mag? Perhaps a dumb question, but at this point I am grasping for anything.
When you are on the Welcome screen of the FCT, you have a link to the profile location just under the drop down “Explore Profiles on Disck”.
Can you Zip the folder and send put it as an attachment here ?
Are those “spikes” in the MAG values recorded while the board was not moving ?
This could be a MAG solder issue and we would like you to open a Support Center Ticket and add a link to this Forum topic in it.
If this is not moving on a desk, with the calibration done right than there is an issue with the MAG sensor.
Create a ticket as suggested earlier and we will help you out.
