Thread Tools
May 16, 2017, 08:59 PM
Registered User
plasoneal's Avatar
Quote:
Originally Posted by Michaelwu21
Does anyone know how to connect a high gain antenna into the video receiver that has an antenna soldered on? I don't really want to desolder it, so I was wondering if I could just cut it, and then cut the end of this: https://goo.gl/V5DEK3, and then just solder those two ends together. Would that work?
I am not a HAM specialist, but given what I know I think the most important part is to keep the signal wire shielded. So if you cut and solder this together, you'll want to pull back and restore or replace some type of shielding. Bottom line you're not going to damage anything ( so long as you don't power on w/o any antenna) but you could degrade the reception if not done well.
Sign up now
to remove ads between posts
May 17, 2017, 07:32 AM
Registered User
Quote:
Originally Posted by 2bowhunter
I´ve seen that, but i have the 3 plug gimbal/camera board, so, its a completely different connection. That is why maybe watching a picture of the cable i can sort out where to plug them. Thanks for the help thou.
May 17, 2017, 07:51 AM
Registered User
Quote:
Originally Posted by NiN3X
Will it work with the PX4 Board?

Definitely not plug and play...
Hi NiN3X can you send me a picture of the red and black multiwire that connects the drone to the gimbal? my cables got disconnected in a crash and i dont know how to reconect them!

Thanks
May 17, 2017, 07:14 PM
Registered User
So I got terrible results from my 600mw vtx with fatshark antenna. About 50 meters before a lot of static would show up. Then, I saw a forum that warned you not to buy 600mw vtx from ebay sellers... Going to see if I can get a refund.
On the other hand, which vtx should i get?
I currently am looking at these:
https://www.amazon.com/dp/B01IEX4SLG?psc=1
https://www.amazon.com/dp/B01MQ485SC?psc=1
https://www.amazon.com/AKK-40Ch-600m...BR83T7BM91FDM3
May 17, 2017, 09:08 PM
Registered User
plasoneal's Avatar

Unsuccessful USB Mod


Ok, I recently purchased another (used) UpAir with the intent fixing it up, doing a couple key mods, and reselling.

After repairing controller antennae which were both torn off the box, the Initial test flight went well. It flew real nice after these repairs. However the camera gimbal was pointing straight down at best and the wheel only rotated it "backwards" as far as it would physically travel.

I assumed I could fix configuration in Mission planner so I set out to do the USB mod.

This one apparently has the PX4 board in it (no micro USB port) so I had to order the DF13 connector cables and splice into a female USB cable. Done.

I initially bench tested the connection (with the GPS unit and compass detatched) as all was well in Mission Planner and the AH was responding OK

After assembly and re-connection of all the components, I can't get any telemetry activity on the UpAir display, there is zero voltage, no satellite reading showing, no AH activity, etc.

If I connect to Mission Planner with UpAir powered off, I can get the AH to work and I do get compass readings and "something" picks up my location, so I don't know if the GPS is working or if it's just picking up location from my computer IP address.

But as soon as I plug in USB and start up Mission Planner, I get "No Mav Data" on the UpAir.

I can't arm motors at all either, and flight modes just stay in STAB mode. The only thing that sorta works is the camera gimbal, which I can still rotate (the wrong way).

I'm going to disassemble again and check all my connections, but any ideas are greatly appreciated. Although I've connected with MP, I haven't upgraded firmware or even attempted to make/save any changes.

Any ideas would be greatly appreciated!
May 18, 2017, 11:02 AM
Registered User
plasoneal's Avatar
Quote:
Originally Posted by Michaelwu21
So I got terrible results from my 600mw vtx with fatshark antenna. About 50 meters before a lot of static would show up. Then, I saw a forum that warned you not to buy 600mw vtx from ebay sellers... Going to see if I can get a refund.
On the other hand, which vtx should i get?
I currently am looking at these:
https://www.amazon.com/dp/B01IEX4SLG?psc=1
https://www.amazon.com/dp/B01MQ485SC?psc=1
https://www.amazon.com/AKK-40Ch-600m...BR83T7BM91FDM3

I suggest the AKK products, especially the switchable MW ones.
May 18, 2017, 04:35 PM
Registered User
plasoneal's Avatar

re: Failed USB Mod


Quote:
Originally Posted by plasoneal
....
But as soon as I plug in USB and start up Mission Planner, I get "No Mav Data" on the UpAir.

I can't arm motors at all either, and flight modes just stay in STAB mode. The only thing that sorta works is the camera gimbal, which I can still rotate (the wrong way).

....
Any ideas would be greatly appreciated!

Update...
I tested with Mission Planner connected only (no power from battery) and confirmed I am getting satellite lock. So that confirms that the GPS is working properly
Doing some more testing, I thought I found the problem. I disconnected my USB, and the UpAir booted OK and I had full telemetry to the screen.
I then checked my USB cable for shorts, but found none.
I then repeated my tests and again get the OSD displaying no data. Sometimes I get no OSD display, sometimes I get ODS fields but with no data, sometimes I get "No Mav Data". But I've tested again with USB disconnected, and this time no impact.

What I have noticed is the startup beeps ... I get 3 rising pitch beeps, repeated, and then pause, and a final single beep (but not higher in pitch)
When I compare that to my good unit, I get 3 rising pitch beeps, repeated, and then pause, and a final single beep that is higher in pitch.

So "something" knows it's not right.

Does that raise any more possible root causes? I'm now thinking that the assumed connection to my USB mod is an incorrect assumption.

Paul
May 18, 2017, 06:51 PM
Registered User
plasoneal's Avatar

UpAir One Procedures


Here are some helpful tips I just got from G10:

1. Controller self calibration:
* Keep the remote controller power off. Toggle the left switches upper.
1. Push the left joystick to down right by your left hand, and pull the right joystick to upper left by your right hand at the same time.
2. Turn on the controller, the RC is constantly beeping.
3. Move the throttles up and down right and left in circle, repeat it several times and ensure that the joysticks can go through the maximum.
4. Move the right switches up and down to the maximum and repeat it several times.
5. Turn the gimbal dial front and back to the maximum and repeat it several times.
6. Press the picture and video shotting button respectively, and then press both of the buttons together,then a long beeping-well done!
Teaching video link for your reference:
Remote Controller Self Calibration (0 min 54 sec)


2. Relink the UPair controller and the aircraft.
*Keep the Remote controller and Aircraft power off,remove 4 propellers for safety.
1.Toggle the left switch down to "Return to Home" mode.
2.Pull the left throttle stick to the bottom right,hold it and turn on the controller at the same time,
You will hear a beeping sound when remote controller is trying to link to the aircraft.
3.Power on the Aircraft ,within few minutes the “beep beep”sound will stop,which indicates
you have now finished linking the remote controller and the aircraft.
4.Toggle the left switch up to the "Normal-mode",now you can successfully unlock the motors.
Teaching video link:
Upair channel calibrating frequency (0 min 53 sec)


3. Reset the video channel
1. Trun on the controller
2. Turn on the drone
3. Press the black button(on the back of the cotroller) for about 13 seconds, the controller will automatic search the most suitable frequency.
Attached video for your reference(sorry it is in Chinese, but quite clear)
May 18, 2017, 07:39 PM
UpAir One 4K
NiN3X's Avatar
Quote:
Originally Posted by plasoneal
Update...
I tested with Mission Planner connected only (no power from battery) and confirmed I am getting satellite lock. So that confirms that the GPS is working properly
Doing some more testing, I thought I found the problem. I disconnected my USB, and the UpAir booted OK and I had full telemetry to the screen.
I then checked my USB cable for shorts, but found none.
I then repeated my tests and again get the OSD displaying no data. Sometimes I get no OSD display, sometimes I get ODS fields but with no data, sometimes I get "No Mav Data". But I've tested again with USB disconnected, and this time no impact.

What I have noticed is the startup beeps ... I get 3 rising pitch beeps, repeated, and then pause, and a final single beep (but not higher in pitch)
When I compare that to my good unit, I get 3 rising pitch beeps, repeated, and then pause, and a final single beep that is higher in pitch.

So "something" knows it's not right.

Does that raise any more possible root causes? I'm now thinking that the assumed connection to my USB mod is an incorrect assumption.

Paul
I hope you get this nailed down. I just ordered a df13 cable to do the same as you. But can I ask what settings in MP did you mess with so I don't do the same....LOL I do have PID FILES, GIMBAL FILES that work from drones4.life
May 18, 2017, 07:43 PM
UpAir One 4K
NiN3X's Avatar
Also, It is my understanding that the new PX4 boards need to be used with QGC and not MP...But I have not confirmed this.
May 19, 2017, 01:32 AM
UpAir One 4K
NiN3X's Avatar
Has anyone on this forum had any success with the new PX4 board + USB DF13 Mod connecting and using MP?
May 21, 2017, 02:05 PM
Registered User
plasoneal's Avatar

re: Faild USB Mod


Quote:
Originally Posted by NiN3X
Also, It is my understanding that the new PX4 boards need to be used with QGC and not MP...But I have not confirmed this.
Some further updates....

-Regarding the 4-wire DF13 connector, for me it had the right pitch on the wire, but I had to trim some shoulders off the side and ends of the connector in order to get it to fit the port.
-Further investigating my issues, I found that there is a 6 wire connector between the power distribution board and the FC. On the PDB it is near the battery plug, just to the right when looking at it from the rear. In my PX4 board, it is all black wires. On my [presumably] older model, the colors are White, Blue, Green, Yellow, Black, Red. Testing reveals:
--White (-5v)
--Blue (-5v)
--Green(-1v)
--Yellow(+ 1v)
--Black (+5 v)
--Red (+ 5v)

My assumption is that green/yellow are data +/-
-I continue to get good telemetry and GPS data when I connect only via USB with MP.
-I did get one successful drone startup after removing the USB cable mod. But probably a dozen or more attempts after that have all failed.
-If I power the drone up, using just the standard controller box & screen, first time I always get a "No Mav Data" message.
-If I power it off and quickly back on, I get the OSD to engage but all data is static (no volts, no telemetry response, etc).
-I've had problems on another model where I tried to add the minum OSD (which I'm pretty sure is what the UpAir uses) and I know it's very susceptible to voltage stability issues. So I tried replacing the voltage feeds with a separate 5V BEC, just to make sure it wasn't a voltage stability issue. That didn't resolve the issue.
-I do have control over the camera gimbal, so that confirms that I have TX/RX bind
-I cannot arm the motors.

Interesting you mention that it might be a problem with using MP. Although I didn't "save" any data with MP, perhaps just the reading action caused some problems? Perhaps I should try QGC?

This drone was purchased 2nd hand and I have no knowledge of it's previous history. So it's possible I didn't cause any of these issues. Perhaps they've been there all along.

It seems the OSD isn't booting properly, but I don't know if that's a cause or a symptom. Here's a brief video:

-Oddly enough, the original problem I was trying to solve (camera gimbal pointing down/back instead of forward) has somehow healed itself along the way. I really have no idea what did that. I tried to follow the self calibration routine posted above, but it didn't respond (beep) the way indicated. But sometime after that, the gimbal starting working correctly.

Although I seem to have ruled out a voltage supply issue between the FC and PDB/ESCs I still think there is a data communication issue somehow.

I can try connecting with QGC or the only other hair-brain idea I have is to try to "patch" the data +/- from the USB port to the feed gloing to the PDB. Of course, I need to check to make sure they are running at compatible voltages. But on another connection between the FC and PDB there is a 2-wire WHITE/GREEN wire only. Is that a data connection? I just don't know and since this is all proprietary, I don't think there any offical pinout charts out there, are there?

I guess the QGC test should probably be first as that won't require any more cutting/soldering risks.

ANY other ideas or guildance greatly appreciated!

Paul
Last edited by plasoneal; May 24, 2017 at 11:33 AM.
May 21, 2017, 10:15 PM
Registered User
fael's Avatar

Transmitter


Quote:
Originally Posted by fael
Transmitter Mainboard PCBA V1.0

Placa do Radio UpAir4k, Tx, COMO RESOLVER O PROBLEMA DE NÃO BIPA (7 min 1 sec)
May 21, 2017, 10:26 PM
Registered User
fael's Avatar
UpAir New 4k , Meus drones apresentando (7 min 37 sec)
May 24, 2017, 11:32 AM
Registered User
plasoneal's Avatar

re: Faild USB Mod


Quote:
Originally Posted by plasoneal
Some further updates....

-Regarding the 4-wire DF13 connector, for me it had the right pitch on the wire, but I had to trim some shoulders off the side and ends of the connector in order to get it to fit the port.
-Further investigating my issues, I found that there is a 6 wire connector between the power distribution board and the FC. On the PDB it is near the battery plug, just to the right when looking at it from the rear. In my PX4 board, it is all black wires. On my [presumably] older model, the colors are White, Blue, Green, Yellow, Black, Red. Testing reveals:
--White (-5v)
--Blue (-5v)
--Green(-1v)
--Yellow(+ 1v)
--Black (+5 v)
--Red (+ 5v)
Well, my assumption about the green/yellow wires being related to my MAV data problem has been found to be an incorrect assumption, plus the voltages didn't align with the USB port data voltage, so I never tried that connection patch yet.

On my working UpAir, I was able to disconnect nearly all the wires above and still get full OSD telemetry data. Only when I disconnected them all (which cut the power feed entirely) did the OSD telemetry drop off.

I also tested disconnection of the 2 wire While/Green pair. OSD was still functional. So that appears to not be the MAV channel either.

I think that leaves only one other wiring hardness that flows between the FC and PDB. I'll test that next when I can.

The only thing I learned in the above is that the battery voltage feed appears to be related to disconnection of the BLUE wire (I believe). When I disconnected that, there was still a voltage readout on the OSD, but it dropped from ~12v to ~ 3v

So, next I'm going to test the other multi-wire connection and see if I can isolate the channel for the MAV data.

I did confirm that when 5v power is applied to the USB connection, I'm getting a 3v response on the data wires. So I'm probably looking for a 3v feed from the FC (assuming it works the same).

Since it appears that dropping the MAV data internally is normal response when connecting to USB, I'm suspecting that for some reason my internal channel isn't working correctly when the USB connection is dropped. Assuming I can find that channel, I'm hoping to redirect /patch it's data via the USB connection (driving voltage to is via a separate 5v BEC. That's my current plan at least.


Quick Reply
Message:

Thread Tools